1 / 32

RUP/UP Software Development Method

RUP/UP Software Development Method. Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn. Contents. Summary of Rational Unified Process RUP Structures and Roles Project Management Systems and Procedures in RUP RUP and different types of software projects. RUP. Some History Behind.

wesley
Télécharger la présentation

RUP/UP Software Development Method

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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

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

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

  5. Requirements Analysis Design Implementation Testing Use-case driven • What is a use-case? • Use-case driven principle:

  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

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

  8. Guidelines for Planning Iterations • Iteration should deal with the group of use-caseswhich increases the usefulness of theproduct over time. • The most serious risks are handled by earlieriterations

  9. Advantages of Iterative Process • Financial risks are limited to one iterationonly • The risks of late product delivery are reduced. • Iterations speeds up the overall developmentprocess as short and clear plan is morepreferable for efficient work • Facilitates requirements elicitation

  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

  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

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

  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

  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)

  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

  16. RUP Elements – workflows cont.

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

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

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

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

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

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

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

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

  25. RUP and different types of software projects

  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

  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

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

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

  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

  31. Waterfall model

  32. Questions?

More Related