1. RUP/UP Software Development Method Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn

2. Contents Summary of Rational Unified Process RUP Structures and Roles Project Management Systems and Procedures in RUP RUP and different types of software projects 2

3. RUP. Some History Behind The need in software development process What is a software development process History of RUP RUP and UP 3

4. Summary of RUP Use-case driven Architecture-oriented Iterative and Incremental 4

5. Use-case driven What is a use-case? Use-case driven principle: RequirementsAnalysisDesignImplementationTesting 5

6. Architecture Oriented Architecture Grows from Use-Cases. Steps to build architecture: Draft version not related to use-cases Use-cases that correspond to the system key functionalities The built architecture serves as a base for subsequent development of other use-cases 6

7. Iterative and Incremental Big project is split in many mini-projects called iterations Each iteration increments the overall project result 7

8. Guidelines for Planning Iterations Iteration should deal with the group of use- cases which increases the usefulness of the product over time. The most serious risks are handled by earlier iterations 8

9. Advantages of Iterative Process Financial risks are limited to one iteration only The risks of late product delivery are reduced. Iterations speeds up the overall development process as short and clear plan is more preferable for efficient work Facilitates requirements elicitation 9

10. Project Life-Cycle in RUP All iterations are organized into 4 phases:  Inception  Elaboration  Construction  Transition Milestones are used to evaluate the project progress 10

11. RUP Structures – elements Entities that make up RUP (Kruchten)  Worker: the who  Activities: the how  Artifacts: the what  Workflows: the when The above are predefined Relations predefined All together define process framework 11

12. RUP Elements - workers Responsibilities of:  Individual or  Number of individuals Behavior determined by activities Responsible for artifacts 12

13. RUP Elements - activities Create result (artifacts) Take from a few hours to a few days Activity can be applied many times to the same artifact Basic steps of activity  Thinking  Performing  Reviewing 13

14. RUP Elements - artifacts Main pieces of the project Produced, modified and used during activities Fall into following sets:  Management (ex: software development plan)  Requirements (ex: specifications)  Design (ex: design model)  Implementation (ex: source code)  Deployment (ex: training material) 14

15. RUP Elements – workflows “A workflow is a sequence of activities that produces a result of observable value”. Grouped in categories  Core  Workflow details  Iteration plans 15

16. RUP Elements – workflows cont. 16

17. RUP Elements – additional Guidelines Templates Tool mentors Concepts 17

18. Roles in RUP Each artifact has worker assigned to it All workers are defined (fixed) Behavior determied by workflow the artifact belongs to 18

19. Roles in RUP - examples Project management workflow  Project manager  Project reviewer Requirements workflow  System analyst  Use-case specifier  User-interface designer  Requirements reviewer 19

20. Project Management Systems and Procedures in RUP Project planning Project control Risk management Project evaluation 20

21. RUP project planning Phase plan Iteration plan Planning supporting tool 21

22. RUP project control Project indicators Change control management (CCM) 22

23. RUP risk management Risk-driven approach :  Risk List  Use-case Survey  Development Case 23

24. RUP project evaluation Iteration close-out Phase close-out Transition phase close-out 24

25. RUP and different types of software projects 25

26. RUP Process for Commercial Software High number of iterations Extensive testing  A lot of test-cases  Regression testing Remember to keep a balance between quality assurance and time to market 26

27. RUP for Contract Software High number of iterations Focus more on requirements elicitation in the beginning  Active prototyping  User involvement Focus more on testing in the end 27

28. RUP for In-house Software Very close to waterfall model  Small number of iteration  Good testing is preferred 28

29. Conclusion - Advantages of RUP architecture brings us overall understanding of the big and complex system early risk handling easier requirements change management high level of reuse project teams learn easier because the project is broken down into small manageable parts better quality assurance Extensive CASE tool support 29

30. Conclusion – Disadvantages of RUP Very broad and complex You have to customize it to start really using it Demands big initial efforts and investments 30

31. Waterfall model 31

32. Questions? 32