Requirement Driven Development Process

Transcription

1 Requirement Driven Development Process Ulrich Hörmann

2 Agenda Motivation Grundlegende Strategien Anforderungsmanagement Anforderungsbasiertes Change-Management Fragen 2

3 3 Motivation

4 Warum Anforderungsmanagement? Distribution of Defects Distribution of Effort to Fix Defects Requirements 56% Code 7% Other 10% Requirements 82% Code 1% Other 4% Design 13% Design 27% Quelle: An Information Systems Manifesto, James Martin 4

5 Wasserfall Requirements Gap Quality Gap Ressourcen Req s Analyze Design Develop Test Implement 5

6 6 Grundlegende Strategien

7 Application Lifecycle Management Architect DESIGN DEVELOP Developer Analyst DEFINE CHANGE MANAGEMENT Managers DEPLOY TEST Tester 7 IT Ops

8 Schlüsselfunktionen des RDDP Drives Definition Drives Development Stimulates Proves Validation Proves 8

9 Simplifying RDDP Need (Why?) User Acceptance Test Requirement (What?) Systems Test Specification (How) Integration Test Task (When?) Unit Test Deliverable (Where?) 9

10 Ein strukturierter, integrierter Prozess Requirements Management Analyze Analyze Design Design Develop Develop Implement Implement Quality Assurance / Testing Project Management 10

11 RDDP Beispiel Activities Requirement Management Process Modelling Phases Initiation Design Development Migration Design Modelling Implementation Configuration and Change Management Verification Deployment Project Management 11

12 Konzept Definition Development Validation 12

13 Zielsetzung des RDDP Focus Development is for approved requirements only Traceability Specific versions of development assets are linked to each other Visibility Development assets are seen from the requirement perspective 13

14 14 Anforderungsmanagement

15 Warum Anforderungsmanagement? Trace Requirements into Analysis and Design Models and Implementation Requirement 128 User must logon to system CCM Requirement 5 User must logon to system Modellierung: UML Diagrams and Implementation File: Main.cpp Revision: 1.1 File: Layout.java Revision: 1.1 File: Logo.jpg Revision:

16 Anforderungspyramide Needs (Why) Features (What?) Rohanforderung Kundenanforderung Software Requirements (How?) Produktanforderung Test Procedures Design User Docs 16

17 Software Requirement Hierarchie Business Requirements Why? Vision and Scope Document User Requirements What? Quality Attributes System Requirements Business Rules Use Case Document Functional Requirements How? Nonfunctional Requirements Software Requirements Specification Constraints Quelle: Software Requirements, Karl Wiegers 17

18 Use Case Analyse Narrative 1. User does System does System does System does User does 6. System does Interfaces System Features (BR1) System must enable order processing (UC1) Place an Order (UC2) Delete an Order (UC3) Modify an Order (UC4) Status an Order (UC5) Return a Product (UC6) Register a Complaint Each User Requirement is analyzed to derive interface and system features

19 Traceability Manages Change Why? What? How? When? Where? 19

20 Iteratives Vorgehen AA D D II Aktuelle Iteration Baseline Nächste Iteration AA D D II Neue Anforderungen 20

21 21 Anforderungsbasiertes Change-Management

22 Task Driven Development Trace Tasks into Analysis and Design Models and Implementation Projektmanagement Task 1:Change Layout Task2: Replace Logo CCM Task 2:Replace Logo CCM Task 1: Change Layout Modellierung: UML Diagrams and implementation Modellierung: UML Diagrams and implementation File: Main.cpp Revision: 1.1 File: Layout.java Revision: 1.1 File: Main.cpp Revision: 1.2 File: Logo.jpg Revision:

23 Change Request Driven Development Trace Change Requests into Analysis and Design Models and Implementation Testfallverwaltung Bug 89 Out of date logo on web site and all applications CCM Change Request 58 Out of date logo on web site and all applications Modellierung: UML Diagrams and implementation File: Main.cpp Revision: 1.1 File: Layout.java Revision: 1.1 File: Logo.jpg Revision:

24 Änderungsprozess Neue Funktion Vision Kunden- u. Anwenderrückmeldungen Änderungsprozess Neue Anforderung Fehlerbehebung Require. & Use Cases Code Marketing Entwicklerrückmeldungen Tests Testergebnisse Change Request System 24

25 Iteratives Vorgehen Neue Anforderungen AA D D II Aktuelle Iteration Baseline Nächste Iteration AA D D II 25

26 26 Fragen?