RUP Methodology Software Development Framework RUP Backstory Was
RUP Methodology Software Development Framework
RUP Backstory • Was originally developed by Rational Software Corporation. • They are also the creators or Rational Rose and the UML Modeling Language. • They’ve been a division of IBM since 2003; purchased for 2. 1 Billion. UML Legend>
Rational Unified Process (RUP) • RUP is an Object-Oriented program development methodology. • Rational states that it is an online mentor that provides guidelines, templates, and examples. • There is no 1 set of framework to be used in RUP, it is dynamic; to be able to it a large number of situations. • Process framework that can be tailored to a specific organization or project need.
RUP Terminology • Cycle: A development cycle is the period of time from the very start of the project until product release (or project cancellation); it includes all the activities that are executed during that time. • Phases: Each cycle of the RUP is broken down into a sequence of 4 stages called Inception, Elaboration, Construction and Transition. (More on this later) • Milestone: The point at which an iteration formally ends; corresponds to a release point. • Workflow: is a sequence of activated that produces a result of observable value.
RUP Terminology Cont. • Iteration: Inside each phase there may be one or more iterations. Software is developed in each iteration, which is concluded by a minor milestone, including a release (internal or external) that is a point for assessing the project progress. • The primary goal of each iteration is to slowly chip away at the risk facing the project, namely: Performance risks, integration risks, conceptual risks (design flaws). • The result of a single iteration is an incremental improvement of the system.
Phases of RUP • RUP is broken into four phases of development, each of which is organized into a number of separate iterations that must satisfy defined criteria before the next phase is undertaken. 1. Inception 2. Elaboration 3. Construction 4. Transition
Inception Phase • Build a good understanding of the requirements and scope of the system • Initial requirements captured • Cost benefit analysis • Initial risk analysis • Defining a candidate architecture
Elaboration Phase • Use Case Analysis- Sequence and collaboration diagrams • Domain Model- To understand the problem. (System requirements are within this context) • Risk Assessment Plan revised • Developers analyze the project's needs in greater detail and define its architectural foundation
Construction Phase • This phase is concerned with moving from the executable architecture created in the elaboration phase to an operational system • The focus here is to develop the application to the point where it is ready for deployment • Focus is on implementation and design; developers create the application design and source code
Transition Phase • Also known as the termination phase • Development team begins to shrink • Control is moved to maintenance team • Deliver System into production
Cons of RUP • The process may be too complex to implement in certain cases • Development can get out of control • It’s a heavyweight process • You need an expert to fully adopt this process
Pros of RUP • Regular feedback from stakeholders • Efficient use of resources • You deliver exactly what the customer wants • Issues are discovered early in your project • Supports iterative development • Improved risk management
- Slides: 13