1. Requirements Management and Changes Copyright, 2003 © Jerzy R. Nawrocki Jerzy.Nawrocki@put.poznan.pl www.cs.put.poznan.pl/jnawrocki/require/ Requirements Engineering Lecture 10 Requirements Engineering Lecture 10

2. J. Nawrocki, Requirements Management.. IntroductionIntroduction SCI = “ Information that is created as part of the software engineering process.” [ R.Pressman ] Types of SCIs: computer programs (source code or exec) documents (also requirem. specification) data (e.g. test cases) Soft. Configuration Item (SCI) if (a > b) a-= b;  18 27

3. J. Nawrocki, Requirements Management.. IntroductionIntroduction A specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control procedures. Baseline [IEEE 610-1990] SpecificationDesignCodeTest cases

4. J. Nawrocki, Requirements Management.. Base- line IntroductionIntroduction Baseline or SCI? Engineering Change it! Change control SCI FTR SCI Baseline library Baseline

5. J. Nawrocki, Requirements Management.. Soft. Configuration Control Board SCCB SCCBSCCB Authorises: the establishment of software baselines, the identification of configuration items, the creation of products from the baseline library. Represents the interests of the project manager and all groups affected by changes to baselines. Reviews and authorises changes.

6. J. Nawrocki, Requirements Management.. CMM & Change Management Ac5. Change requests & problem reports for all SCIs are initiated, recorded, reviewed, approved, and tracked according to a documented procedure. Remove 2nd floor!

7. J. Nawrocki, Requirements Management.. CMM & Change Management Change control Change request Err User S.C. Manager Change request Developer Change report SCCB Deci- sion

8. J. Nawrocki, Requirements Management.. CMM & Change Management Change control Change request Err UserS.C. Manager Change request Developer Change report SCCB Deci- sion Change order P. Manager

9. J. Nawrocki, Requirements Management.. CMM & Change Management Change request Change request number:............................ Sender:......................................................... Sender’s e-mail:........................................... Date:.............................................................. Urgency:................. Importance:.............. Description:........................................................................................................................ Evaluator:..................................................... Evaluate by:........... Type (in/external).......

10. J. Nawrocki, Requirements Management.. CMM & Change Management Change report Change request number:.......................... Evaluator:................................................... Evaluator’s e-mail:..................................... Date:............................................................ Urgency:................ Importance:.............. Is the change justifiable?.......................... Main risk factors:....................................... Possible implementor:.............................. Change implement. effort (expect):......... Change evaluation effort (actual):............

11. J. Nawrocki, Requirements Management.. Overview of RE guidelines The requirements document Requirements elicitation Reqs analysis & negotiation Describing requirements System modelling Requirements validation Requirements management RE for critical systems BasicIntermAdv 8 6 5 4 3 4 4 2 36 - 6 2 1 3 3 3 3 21 - 1 1 - - 1 2 4 9

12. J. Nawrocki, Requirements Management.. Basic guidelines Requirements management Uniquely identify each requirement

13. J. Nawrocki, Requirements Management.. Basic guidelines Requirements management Uniquely identify each requirement Tag

14. J. Nawrocki, Requirements Management.. Basic guidelines Requirements management Uniquely identify each requirement Define policies for requirements management Requirements Management Policy Goal : Understand the requirements Obligatory practices : 1. Define specialised terms using the template available at www.cs.put.poznan...

15. J. Nawrocki, Requirements Management.. Basic guidelines Requirements management Uniquely identify each requirement Define policies for requirements management Define traceability policiesDefine traceability policies

16. J. Nawrocki, Requirements Management.. Basic guidelines Traceability policy Traceability information Who is responsible Problems Visions Requirements (FURPS) Acceptance test cases User documentation Design Code

17. J. Nawrocki, Requirements Management.. Basic guidelines Requirements management Uniquely identify each requirement Define policies for requirements management Define traceability policiesDefine traceability policies Maintain a traceability manual

18. J. Nawrocki, Requirements Management.. Intermediate guidelines Requirements management Use a database to manage requirements Define change management policies Identify global system requirements

19. J. Nawrocki, Requirements Management.. Advanced guidelines Requirements management Identify volatile requirements Record rejected requirements

20. J. Nawrocki, Requirements Management.. SummarySummary CMM approach to changes Requirements management practices

21. J. Nawrocki, Requirements Management.. Quality assessment 1. What is your general impression? (1 - 6) 2. Was it too slow or too fast? 3. What important did you learn during the lecture? 4. What to improve and how?