W10 L1 - Testing and Validation

Question 1

What is construction

Answer 1

Application development

• Requirements specification document (use case models, use case documentation, activity diagrams, DFDs) - Analysis Phase
• Design document (ERD, UI design for various interfaces, architecture design) - Design Phase

Largest component (time and cost) - want to complete your Due diligence 
Best understood component
Fewest problems (SDLC)

Focus is on managing the programming process

Question 2

What is the implementation phase

Answer 2

The system has been built (in the construction phase).

Prepare the system before it can be used
‘Install’ the system: all five components (tech vs non-tech)
Some key activities: change management, documentation, testing etc. People is very important here - soft issues, are the ppl ready and willing for the change.

The deliverable for this phase is a completely functioning information system (ready for use in the Operations & Maintenance phase).

Question 3

Describe the Traceability pyramid

Answer 3

draw it out:
At the top we have the NEEDS [high level business needs] - starting point how project gets initiated
FEATURES -resulting system features to address business needs
USE CASES - functional requirements with SUPPORT which are non-functional requirements [high level UC]
SCENARIOS - More detailed UC [low level]
TEST CASES - specific actions or tasks as part of the scenarios

Question 4

What are some testing types and their levels

Answer 4

Business (non-tech) and System (tech) Low Lvl

Unit testing - done by programmers

• Black-box - don’t look at the code;
• white-box - programmer goes through each line of code

Integration testing - integration with other systems

• UI testing
• Scenario testing
• Data flow testing -
• System interface testing

System testing
- Requirements; usability (UI); performance; security

Acceptance testing - done by users [employees, customers etc]

• UAT or CAT High Lvl
• Alpha and beta

Question 5

What is the Double-v Model

Answer 5

• a type of SDLC
• Traceability and abstraction [testing] is inherent with this
• The way this model works is that on the left hand side of the V is what we call “conceptual artefacts” and on the right hand side we have “system artefacts”. You are validating each conceptual artefact by using the system artefact to see if it matches what you said in theory. User requirement models feed into system requirement models.

Question 6

What are reasons for system project failure

Answer 6

• “Failure to plan into the project appropriate reviews, tests or checkpoints at which quality can be verified”
• “Quality is viewed simply in terms of testing rather than a culture of working”
• “Testing focuses on the simple test cases while ignore the more complex situations such as error and recovery handling when things go wrong”
• “Integration and testing of the individual components created in the project is left until all development activities are complete rather than doing ongoing incremental ingratiation and verification to find and fix problems early”
• “Testing in a test environment that is configured differently from the target production, or operational environment in which the project’s deliverables will be used”