COMP3120_11-Verification-and-Validation-2009-v1

COMP3120_11-Verification-and-Validation-2009-v1 - MANAGING...

Info iconThis preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon
MANAGING SOFTWARE DEVELOPMENT COMP 3120 VERIFICATION AND VALIDATION Mark Grundy, Ian Hirst COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 2 Agenda Definitions Technical Reviews Testing Other Verification and Validation Methods Independent Verification and Validation
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 3 Definitions Verification IEEE 1012:2004 - The process of evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase ISO/IEC 12207:1995 - Confirmation by examination and provision of objective evidence that specified requirements have been fulfilled HAS IT BEEN BUILT THE RIGHT WAY ? COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 4 Definitions Validation IEEE 1012:2004 - The process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements ISO/IEC 12207:1995 - Confirmation by examination and provision of objective evidence that particular requirements for a specific intended use have been fulfilled HAVE WE BUILT THE RIGHT THING ?
Background image of page 2
COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 5 Technical Reviews Formal and informal reviews Requirements reviews Design reviews Code reviews Integration and Test reviews Other reviews Audits Administration of formal reviews Customer involvement in technical reviews Pitfalls in conducting technical reviews COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 6 Informal Reviews Reviews are high leverage quality control/assurance activities Informal reviews should be standard features of the development process for any enabling or end product Peer reviews and team leader reviews are simplest and cheapest to conduct Walkthroughs are guided explanations of a product, led by the author, and includes discussions on issues and recommendations Walkthroughs result in a walkthrough report and recommendations
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 7 Formal Reviews Formal Reviews A technical review is a formal team evaluation of a software product or component Technical review objective = to evaluate conformance with specifications and process standards and directives/guidelines Roles = leaders, team members, recorder May include overview, preparation and multiple examination/meeting activities Results in an evaluation report and actions list Resolved issues may require re-review before acceptance COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 8 Requirements Reviews Requirements reviews confirm that: All originating system requirements are expressed correctly and fully and consistently decomposed and allocated to subordinate hardware and software Interfaces requirements are defined and documented Dataflow documents are correct and complete The development plans are adequate and have been implemented
Background image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 18

COMP3120_11-Verification-and-Validation-2009-v1 - MANAGING...

This preview shows document pages 1 - 5. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online