1. RUP and Elaboration Phase Copyright, 2003 © Jerzy R. Nawrocki Jerzy.Nawrocki@put.poznan.pl www.cs.put.poznan.pl/jnawrocki/require/ Requirements Engineering Lecture 8 Requirements Engineering Lecture 8

2. J. Nawrocki, RUP and Elaboration Phase Dimensions of the RUP InceptionElaborationConstruction Transition Business model Requirements Analysis&Design Implementation Test Deployment Configur.&Change Project Manag. Environment

3. J. Nawrocki, RUP and Elaboration Phase The PRINCE Process Model Directing a Project DP Managing Stage Boundaries SB Starting up a Project SU Controlling a Stage CS Planning PL Managing Product Delivery Initiating a Project IP Closing a Project CP

4. J. Nawrocki, RUP and Elaboration Phase Incep -tion Elabora- tion Construc- tion Transi- tion PRINCE 2 and RUP SBIP PL CSSB PL CSSB PL CS Directing a Project SU PL Ar  R1 Construc- tion Transi- tion SB PL CSSB PL CS  R1 CP

5. J. Nawrocki, RUP and Elaboration Phase PRINCE 2 and RUP 16.1027.1123.018.0427.0517.061.07 StartingInitiat.Stage1Stage2Stage3Stage4Closing Inception 17.10-6.11 Elaborat. 28.11-18.12 Constr. 5 - 18.03 Constr. 16-29.04 Constr. 28.5-10.06 Inception 7 - 27.11 Elaborat. 5 - 23.01 Constr. 19.03-1.04 Constr. 7 – 20.05 Transit. 11 - 17.06 Transit. 2 - 8.04 Transit. 21-27.05

6. J. Nawrocki, RUP and Elaboration Phase PRINCE 2 and RUP 16.1027.1123.018.0427.0517.061.07 StartingInitiat.Stage1Stage2Stage3Stage4Closing Inception 17.10-6.11 Elaborat. 28.11-18.12 Constr. 5 - 18.03 Constr. 16-29.04 Constr. 28.5-10.06 Inception 7 - 27.11 Elaborat. 5 - 23.01 Constr. 19.03-1.04 Constr. 7 – 20.05 Transit. 11 - 17.06 Transit. 2 - 8.04 Transit. 21-27.05

7. J. Nawrocki, RUP and Elaboration Phase PRINCE 2 and RUP 16.1027.1123.0129.0417.061.07 StartingInitiat.Stage1Stage2Stage3Closing Inception 17.10-6.11 Elaborat. 28.11-18.12 Constr. 5 - 25.03 Constr. 7 – 27.05 Inception 7 - 27.11 Elaborat. 5 - 23.01 Constr. 26.3 - 22.4 Constr. 28.5-10.06 Transit. 23 - 29.04 Transit. 11 - 17.06

8. J. Nawrocki, RUP and Elaboration Phase InceptionInception 16.1027.1123.018.0427.0517.061.07 StartingInitiat.Stage1Stage2Stage3Stage4Closing Inception 17.10-6.11 Elaborat. 28.11-18.12 Constr. 5 - 18.03 Constr. 16-29.04 Constr. 28.5-10.06 Inception 7 - 27.11 Elaborat. 5 - 23.01 Constr. 19.03-1.04 Constr. 7 – 20.05 Transit. 11 - 17.06 Transit. 2 - 8.04 Transit. 21-27.05

9. J. Nawrocki, RUP and Elaboration Phase Inception Objectives 1.Understand what to build (vision + scope; PID.Introduction)

10. J. Nawrocki, RUP and Elaboration Phase

12. Inception Objectives 1.Understand what to build (vision + scope; PID.Introduction) 2.Identify key system functionality (detailed description of ~20% of use cases – most essential ; e.g. PID.Products)

13. J. Nawrocki, RUP and Elaboration Phase

14. Inception Objectives 1.Understand what to build (vision + scope; PID.Introduction) 2.Identify key system functionality (detailed description of ~20% of use cases – most essential ; e.g. PID.Products) 3.Determine at least one possible solution (Project Approach or PID.Products) 4.Understand the costs, schedule, and risks (PID – Business Case, Risk Log)

15. J. Nawrocki, RUP and Elaboration Phase

16. Inception Objectives 1.Understand what to build (vision + scope; PID.Introduction) 2.Identify key system functionality (detailed description of ~20% of use cases – most essential ; e.g. PID.Products) 3.Determine at least one possible solution (Project Approach or PID.Products) 4.Understand the costs, schedule, and risks (PID – Business Case, Risk Log) 5.Decide what process to follow and what tools to use (PID - Activities)

17. J. Nawrocki, RUP and Elaboration Phase

18. ElaborationElaboration 16.1027.1123.018.0427.0517.061.07 StartingInitiat.Stage1Stage2Stage3Stage4Closing Inception 17.10-6.11 Elaborat. 28.11-18.12 Constr. 5 - 18.03 Constr. 16-29.04 Constr. 28.5-10.06 Inception 7 - 27.11 Elaborat. 5 - 23.01 Constr. 19.03-1.04 Constr. 7 – 20.05 Transit. 11 - 17.06 Transit. 2 - 8.04 Transit. 21-27.05

19. J. Nawrocki, RUP and Elaboration Phase Elaboration Objectives 1 Get a more detailed understanding of the requirements 2 Design, implement, validate, and baseline the arch-ture 3 Mitigate essential risks, and improve schedule/cost estim. 4 Refine the development case and make the tools ready

20. J. Nawrocki, RUP and Elaboration Phase ElaborationElaboration 1 Get a more detailed understanding of the requirements Steps’ desc. of ~50% of Elabor. Ucs; decreasing priority 2 Design, implement, validate, and baseline the arch’ture DI&T a few critical scenarios to identify architecture type and architecture mechanisms. I&T an initial set of architecture mechanisms. Do a preliminary logical database design. 3 Mitigate essential risks, and improve schedule/cost estim. Identify possible performance problems and test them First Iteration

21. J. Nawrocki, RUP and Elaboration Phase ElaborationElaboration 1 Get a more detailed understanding of the requirements Steps’ desc. of remaining Elaboration’s Ucs 2 Design, implement, validate, and baseline the arch’ture Fix first-iteration’s issues. DI&T the remaining architecturally significant scenarios. D&I a preliminary version of the database. I&T remaining architectural mechanisms. 3 Mitigate essential risks, and improve schedule/cost estim. Address technically high-risk issues: concurrency, distribution, performance, (external) interfaces. Second Iteration

22. J. Nawrocki, RUP and Elaboration Phase Ideal Architect Experience Leadership Communication Goal-oriented and proactive Who on my team? Analyst? Project manager?

23. J. Nawrocki, RUP and Elaboration Phase SummarySummary Integrating RUP with PRINCE 2 Inception goals Elaborations goals Architect selection

24. J. Nawrocki, RUP and Elaboration Phase 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?