Anzeige
Presentation V Model
26. Oct 2010•0 gefällt mir•3,831 Aufrufe
4 gefällt mir
Sei der Erste, dem dies gefällt
Mehr anzeigen
Aufrufe
Aufrufe insgesamt
0
Auf Slideshare
0
Aus Einbettungen
0
Anzahl der Einbettungen
0
Melden
Presentation used to explain the phases and phase transitions in the Center Parcs ICT development chain.
rputkerFolgen
Anzeige
Presentation V Model
- Remco Putker / 30 September 201011 V-Model requirements and testing
- Remco Putker / 30 September 201033 V-Model requirements and testing ‘The’ V-Model
- Remco Putker / 30 September 201011 V-Model requirements and testing A-REQ Validation Validation Validation BUILD Design ITS B-REQ NF-REQ LPS Validation Validation PC RT HT PAT UT F-REQ RT HT RT HT UAT FAT Validation Validation Inspection Validation Validation RT HT ITL IDEA What? - Primary idea! Example: - Booking app for iPhone/iPad Who: - Client Deliverables: - Approval to write project mandate Entry criteria: - Exit criteria: - Main goal defined Phase transition responsible - Client - Author mandate
- Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation Validation Validation BUILD Design ITS LPS Validation Validation PC RT HT PAT UT F-REQ RT HT RT HT UAT FAT Validation Validation Inspection Validation Validation RT HT ITL What? - Functional business requirements Example: - B-req: Multi brand support Who: - All (!) stakeholders involved Deliverables: - Project Mandate - Stakeholder declaration - Prioritised B-Req’s/stakeholder (user stories) - Referenced NF-Req file per stakeholder - Scope of the change A-REQ B-REQ NF-REQ - Non-functional Requirements - NF-req: Performance Entry criteria: - Main goal defined
- Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation Validation BUILD Design ITS LPS Validation Validation PC RT HT PAT UT F-REQ RT HT RT HT UAT FAT Validation Validation Inspection Validation RT HT ITL What? - Validation mandate and high level requirements Who/what: - Client Coverage main goal - MT Approval change - Steering comity Business case - Stakeholders involved Needs and boundaries - Testmanager Testability - Manager requirements Conformity and coverage - Requirements analyst Understandability Deliverables: Project Mandate - High level requirements - Categorized - Prioritized - Scope - Baseline NF-Req’s Initial test preparation - UAT - PAT - LPS Validation Validation A-REQ B-REQ NF-REQ
- Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation Validation Validation BUILD Design ITS LPS Validation Validation PC RT HT PAT UT F-REQ RT HT RT HT UAT FAT Validation Validation Inspection Validation Validation RT HT ITL What? - Functional business requirements Example: - B-req: Multi brand support Who: - All (!) stakeholders involved Deliverables: - Project Mandate - Stakeholder declaration - Prioritised B-Req’s/stakeholder (user stories) - Referenced NF-Req file per stakeholder - Scope of the change Entry criteria: - Main goal defined Exit criteria: - Project mandate approved - Previous phase revisited Phase transition responsible - Manager requirements A-REQ B-REQ NF-REQ - Non-functional Requirements - NF-req: Performance
- A-REQ B-REQ NF-REQ Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation Validation Validation BUILD Design ITS LPS Validation Validation PC RT HT PAT UT RT HT RT HT UAT FAT Validation Validation Inspection Validation Validation RT HT ITL What? - Functional requirements Format: - Use cases Who: - Requirements analyst Deliverables: - Use case model - Glossary - Actor declaration - Supplementary requirements - Use cases Entry criteria: - Approved mandate F-REQ
- Validation Validation A-REQ B-REQ NF-REQ Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation Validation BUILD Design ITS LPS Validation Validation PC RT HT PAT UT RT HT RT HT UAT FAT Validation Inspection Validation RT HT ITL What? - Validation functional requirements Who/what: - Author mandate Interpretation analysis - Requirements manager conformity and coverage B-Req & NF-Req - Test manager testability - Developer design ability Deliverables: Initial test preparation - FAT F-REQ Validation
- A-REQ B-REQ NF-REQ Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation Validation Validation BUILD Design ITS LPS Validation Validation PC RT HT PAT UT RT HT RT HT UAT FAT Validation Validation Inspection Validation Validation RT HT ITL What? - Functional requirements Format: - Use cases Who: - Requirements analyst Deliverables: - Use case model - Glossary - Actor declaration - Supplementary requirements - Use cases Entry criteria: - Approved mandate Exit criteria: - Approved set of requirements - Previous phases revisited Phase transition responsible - Requirements manager - Development manager F-REQ
- F-REQ A-REQ B-REQ NF-REQ Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation Validation Validation BUILD Design ITS LPS Validation Validation PC RT HT PAT UT RT HT RT HT UAT FAT Validation Validation Inspection Validation Validation RT HT ITL Project lifecycle Product lifecycle Requirements lifecycle Time Why requirements don’t belong to projects
- F-REQ A-REQ B-REQ NF-REQ Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation Validation Validation BUILD Design ITS LPS Validation Validation PC RT HT PAT UT RT HT RT HT UAT FAT Validation Validation Inspection Validation Validation RT HT ITL Why requirements don’t belong to projects Stakeholder Proces Compliance Coverage General library of non-functional and architectural requirements in list format categorized by ISO 9126-1 ext. and grouped by stakeholder. Contains a number, a description, a priority, a stakeholder, a status and statusdate and a column for references. Background and objectives as formulated in the project mandate. User stories as formulated in the project mandate: Contains a stakeholder list, a list of user stories grouped by stakeholder including, motivation, priority and business value. Written down in use case model, use cases, supplementary functional requirements and a glossary (per use case model) To be defined Product A-REQ B-REQ Design NF-REQ F-REQ IDEA
- Remco Putker / 30 September 201011 V-Model requirements and testing Validation Validation BUILD Design ITS LPS Validation Validation PC RT HT PAT UT RT HT RT HT UAT FAT Validation Inspection Validation RT HT ITL F-REQ A-REQ B-REQ NF-REQ IDEA Validation Validation Validation Process requirements (needs, features) Stakeholder requirements (project boundaries) Product specific requirements Context
- Validation ITS RT HT UT Remco Putker / 30 September 201011 V-Model requirements and testing Validation LPS Validation Validation PC PAT RT HT RT HT UAT FAT Validation RT HT ITL F-REQ A-REQ B-REQ NF-REQ IDEA Validation Validation Validation BUILD Design Validation Inspection To be aligned with development as soon as possible!!!
- F-REQ A-REQ B-REQ NF-REQ Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation Validation Validation BUILD ITS LPS Validation Validation PC RT HT PAT RT HT RT HT UAT FAT Validation Validation Inspection Validation Validation RT HT ITL Exit criteria: - Test passed - Results / issues documented Test base: - Technical design What? - Unit test Explanation: - Validation of smallest testable units Example: - Statements, field validations, etc. Who: - Development Entry criteria: - Unit build - test base updated UT Phase transition responsible - Development manager Design Environment - Development
- Validation F-REQ Validation Validation A-REQ B-REQ NF-REQ Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation BUILD Design LPS Validation Validation PC RT HT PAT RT HT RT HT UAT FAT Validation Inspection Validation RT HT ITL What? - Validation test results technical tests Who/what: - Development manager Coverage, results - Test manager Open issues / acceptance criteria - Release manager Package for deployment T Deliverables: - Package for deployment T - New software tested - Old software regression tested - Documented test results - Documented issues - Acceptance criteria passed - Updated test base (req’s) Validation ITSUT
- Validation RT HT UT Validation ITSDesign A-REQ B-REQ NF-REQ Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation Validation BUILD LPS Validation Validation PC PAT RT HT RT HT UAT Validation Inspection Validation Validation RT HT ITL Test base: - Use case set What? - Functional acceptance test (system test) Explanation: - Validation use cases and supp. Req’s Example: - Make booking iPad app Who: - Tester Phase transition responsible - Test manager Exit criteria: - Test passed - Results / issues documented Environment - Test Entry criteria: - Intake test object - Intake test environment F-REQ FAT
- Design RT HT Validation Validation ITSUT Validation F-REQ Validation Validation A-REQ B-REQ NF-REQ Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing BUILD LPS Validation Validation PC PAT RT HT RT HT UAT Inspection Validation RT HT ITL What? - Validation test results FAT Who/what: - Senior user Coverage, results - Test manager Open issues / acceptance criteria - Release manager Package for deployment A Deliverables: - Package for deployment A - New software tested - Old software regression tested - Documented test results - Documented issues - Acceptance criteria passed - Updated test base (req’s) Validation FAT
- Validation HT Validation F-REQ FAT Validation RT HT UT Validation ITSDesign B-REQ NF-REQ Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation BUILD LPS Validation Validation PC PAT RT RT HT UAT Inspection Validation Validation RT HT Test base: - Architectural requirements What? - Integration test large Explanation: - Fitting ICT infrastructure / landscape Example: - Interfacing, backup mechanisms, etc. Who: - Tester Phase transition responsible - Test manager - Systems manager Exit criteria: - Test passed - Results / issues documented Environment - Acceptance Entry criteria: - Intake test object - Intake test environment A-REQ ITL
- RT HT Validation FAT Design RT HT Validation Validation ITSUT Validation F-REQ Validation Validation A-REQ B-REQ NF-REQ Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing BUILD LPS Validation Validation PC PAT RT HT UAT Inspection RT HT What? - Validation test results ITL Who/what: - Systems manager Coverage, results - Test manager Open issues / acceptance criteria Deliverables: - Documented test results - Documented issues - Acceptance criteria passed - Updated test base (req’s) Validation ITL
- RT HT A-REQ ITL Validation HT Validation F-REQ FAT Validation RT HT UT Validation ITSDesign Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation BUILD LPS Validation Validation PC PAT RT RT HT Inspection Validation Validation Test base: - Business requirements What? - User acceptance test Explanation: - Useability Example: - Look and feel, clickpaths, etc. Who: - Senior user Phase transition responsible - Test manager - Senior user Exit criteria: - Test passed - Results / issues documented Environment - Acceptance Entry criteria: - Intake test object - Intake test environment B-REQ NF-REQ UAT
- RT HT UAT RT HT A-REQ ITL Validation HT Validation F-REQ FAT Validation RT HT UT Validation ITSDesign Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation BUILD LPS Validation Validation PC RT Inspection Validation Validation Test base: - Non functional requirements What? - Production acceptance test Explanation: - Maintainability Example: - Conventions Who: - Systems manager - eService manager Phase transition responsible - Test manager - Systems manager - eService manager Exit criteria: - Test passed - Results / issues documented Environment - Acceptance Entry criteria: - Intake test object - Intake test environment B-REQ NF-REQ PAT
- UAT RT HT A-REQ ITL Validation HT Validation F-REQ FAT Validation RT HT UT Validation ITSDesign Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing Validation BUILD Validation Validation PC PAT RT RT HT Inspection Validation Validation Test base: - Non functional requirements What? - Load / Performance / Stress test Explanation: - Performance, robustness Example: - Nominal load, peakload, breakpoint, etc. Who: - Specialist tester Phase transition responsible - Test manager - Stakeholder requirement Exit criteria: - Test passed - Results / issues documented Environment - Acceptance - (Test) - (Development) Entry criteria: - Intake test object - Intake test environment B-REQ NF-REQ LPS LPS LPS
- RT HT Validation ITL RT HT Validation FAT Design RT HT Validation Validation ITSUT Validation F-REQ Validation Validation A-REQ B-REQ NF-REQ Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing BUILD Validation PC RT HT Inspection What? - Validation acceptance test results Who/what: - User representative Coverage, results - Systems manager Coverage, results - eService manager Coverage, results - Other stakeholders involved Coverage, results - Test manager Open issues / acceptance criteria - Release manager Package for deployment P Deliverables: - Package for deployment P - New software tested - Old software regression tested - Documented test results - Documented issues - Acceptance criteria passed - Updated test base (req’s) LPS Validation PATUAT
- RT HT UAT Validation LPS Validation B-REQ NF-REQ PAT RT HT A-REQ ITL Validation HT Validation F-REQ FAT Validation RT HT UT Validation ITSDesign Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing BUILD Validation RT Inspection Validation Validation Test base: - none What? - Production check Explanation: - Final check after deployment before go live! Example: - Functional regression test primary process Who: - Test manager Phase transition responsible - Test manager - Release manager - eService manager - Systems manager Exit criteria: - Test passed - Results / issues documented Environment - Production Entry criteria: - Successful production deploymentPC
- RT HT RT HT LPS Validation PATUAT Validation ITL RT HT Validation FAT Design RT HT Validation Validation ITSUT Validation F-REQ Validation Validation A-REQ B-REQ NF-REQ Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing BUILD Inspection What? - Validation production check Who/what: - Systems manager Results - eService manager Results - Release manager Finish go live Deliverables: - Package deployed production - Documented test results - Documented issues - Acceptance criteria passed - Updated test base (req’s) Validation PC
- Design Validation Validation F-REQ Validation Validation A-REQ B-REQ NF-REQ Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing BUILD Inspection RT HT RT HT LPS Validation PATUAT Validation ITL RT HT Validation FAT RT HT Validation ITSUT Validation PC Production Acceptance Develop Environment Test
- PC HT UAT Validation LPS Validation B-REQ NF-REQ PAT HT A-REQ ITL Validation HT Validation F-REQ FAT Validation HT UT Validation ITSDesign Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing BUILD Validation Inspection Validation Validation Test base: - Depends on phase What? - Regression test (f.k.a. smoke test) Explanation: - Does it still work? Example: - Compilercheck with new build Who: - Depends on phase Phase transition responsible - Depends on phase Exit criteria: - Test passed - Results / issues documented Environment - Depends on phase RT RT RT RT Entry criteria: - Intake test object - Intake test environment
- RT RT RT RT PC UAT Validation LPS Validation B-REQ NF-REQ PAT A-REQ ITL ValidationValidation F-REQ FAT Validation UT Validation ITSDesign Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing BUILD Validation Inspection Validation Validation Test base: - Depends on phase What? - Re-test Explanation: - Does it work now? Example: - Re-test fixed issues Who: - Depends on phase Phase transition responsible - Depends on phase Exit criteria: - Test passed - Results / issues documented Environment - Depends on phase HT HT HT HT Entry criteria: - Intake test object - Intake test environment
- Remco Putker / 30 September 20101 Process requirements (needs, features) Stakeholder requirements (project boundaries) Product specific requirements 1 V-Model requirements and testing A-REQ Production Acceptance Test Develop Validation Validation Validation BUILD Design ITS B-REQ NF-REQ LPS Validation Validation PC RT HT PAT UT F-REQ RT HT RT HT UAT FAT Validation Validation Inspection IDEA Validation Validation RT HT ITL Context Environment
- Remco Putker / 30 September 201011 V-Model requirements and testing PATD DEV 1 DEV 2 DEV n DEV 1 DEV 2 DEV n D-Team 1 D-Team 2 PROJECT 1 DEV 1 DEV 2 DEV n D-Team n PROJECT n ACC DEV PROD ACC OPP Data deployment Software deployment
- RT RT RT RT HT HT HT HT PC UAT Validation LPS Validation B-REQ NF-REQ PAT A-REQ ITL ValidationValidation F-REQ FAT Validation UT Validation ITSDesign Remco Putker / 30 September 20101 IDEA 1 V-Model requirements and testing BUILD Validation Inspection Validation Validation What’s next? - Align requirements management with development - Agree on model (integral) - Define checklists per validation point - Define checklists per phase transition - Include in procedures requirements management, development, testing and go live
Anzeige