| INDEPENDENT VERIFICATION & VALIDATION |
The Carnegie Mellon Software Engineering Institute reports that at least 42-50 percent of software
defects originate in the requirements phase.
The Defense Acquisition University Program Manager Magazine reports that a Department of
Defense study that over 50 percent of all software errors originate in the requirements phase.
GWIS believes that early error detection and correction are vital to the success of System
Development and Integration. The cost to correct software errors multiplies during the Software
Development Life Cycle (SDLC). Early error detection and correction reduce costs and save time.
GWIS IV&V Process provides tools and analysis procedures appropriate to each phase of the SDLC:
If you would like to learn more about how we can help. Let’s Talk.
defects originate in the requirements phase.
The Defense Acquisition University Program Manager Magazine reports that a Department of
Defense study that over 50 percent of all software errors originate in the requirements phase.
GWIS believes that early error detection and correction are vital to the success of System
Development and Integration. The cost to correct software errors multiplies during the Software
Development Life Cycle (SDLC). Early error detection and correction reduce costs and save time.
GWIS IV&V Process provides tools and analysis procedures appropriate to each phase of the SDLC:
- Concept Phase:
- Verify candidate reuse software will satisfy the domain of the new system
- Assess the proposed architectural schema for feasibility
- Analyze the system requirements
- Requirements Phase:
- Verify that system and software requirements are correct, complete, traceable and
testable - Verify test plans and acceptance criteria are sufficient to validate system
requirements and operational needs - Ensure testing methods are sufficient to verify and validate software requirements
- Verify the correct software development, management, and support processes are in
place
- Design Phase:
- Verify the design will satisfy the requirements levied against it
- Ensure test plans and test environments are sufficient to verify and validate
software and operational requirements - Verify that the design does not have any characteristics that will cause it to fail
under operational scenarios
- Coding Phase:
- Verify the code reflects the design
- Verify the code is correct
- Verify that test cases trace to and cover software requirements and operational needs
- Verify that software test cases, expected results, and evaluation criteria fully meet
testing objectives - Analyze selected code unit test plans and results to verify full coverage of logic
paths, range of input conditions, error handling, etc.
- Test Phase:
- Verify correct disposition of software test anomalies
- Validate software test results versus acceptance criteria
- Verify tracing and successful completion of all software test objectives
- Operational (Production) Phase:
- Verify that regression tests are sufficient to identify adverse impacts of changes
- Continuous Process Improvement (with SCAMPI Reviews and Six Sigma
Evaluations)
If you would like to learn more about how we can help. Let’s Talk.
1 – Carnegie Mellon Software Engineering Institute, The Business Case for Requirements Engineering,
RE’ 2003, 12 September 2003
2 - Defense Acquisition University Program Manager Magazine, Nov-Dec 1999, Curing the Software Requirements and Cost
Estimating Blues
RE’ 2003, 12 September 2003
2 - Defense Acquisition University Program Manager Magazine, Nov-Dec 1999, Curing the Software Requirements and Cost
Estimating Blues
 | |  | |  | |  |
Independent Verification &
Validation (IV&V)
Validation (IV&V)
G.W. Integrity Systems, Inc
Management & Technology
Consultants
GregoryWaters@gwisinc.com
240.535.9644
©2007 All rights reserved.
Legal Disclaimer and Privacy
Management & Technology
Consultants
GregoryWaters@gwisinc.com
240.535.9644
©2007 All rights reserved.
Legal Disclaimer and Privacy
Anchored in Integrity