We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8
UNIFIED PROCESS(UP)
UP is popular iterative and incremental s/w
development process framework. Refinement of UP is Rational Unified process. (RUP). Has foll key features: Used to coordinate object oriented programming projects. Uses UML Design process is anchored and driven by use case. Is architecture centric. Design is iterative and incremental. UP: referred to as unified s/w development process. UP Phases: A UP project organizes the work flow and iterations across four major phases. They are: Inception. Elaboration. Construction Transition. INCEPTION
During the inception phase, establish the business
case for the system and delimit the project scope. To accomplish this it must identify all external entities with which the system will interact (actors) and define the nature of this interaction at a high- level. This involves identifying all use cases and describing a few significant ones. The business case includes success criteria, risk assessment, and estimate of the resources needed, and a phase plan showing dates of major milestones. ELABORATION The purpose of the elaboration phase is to analyze the problem domain, establish a sound architectural foundation, develop the project plan, and eliminate the highest risk elements of the project. Architectural decisions have to be made with an understanding of the whole system: its scope, major functionality and nonfunctional requirements such as performance requirements. CONSTRUCTION During the construction phase, all remaining components and application features are developed and integrated into the product, and all features are thoroughly tested. The construction phase is, in one sense, a manufacturing process where emphasis is placed on managing resources and controlling operations to optimize costs, schedules, and quality. In this sense, the management mindset undergoes a transition from the development of intellectual property during inception and elaboration, to the development of deployable products during construction and transition. TRANSITION The purpose of the transition phase is to transition the software product to the user community. Once the product has been given to the end user, issues usually arise that requires developing new releases, correcting some problems, or finishing the features that were postponed. The transition phase is entered when a baseline is mature enough to be deployed in the end-user domain. This typically requires that some usable subset of the system has been completed to an acceptable level of quality and that user documentation is available so that the transition to the user will provide positive results for all parties. FIVE WORKFLOW OF UP Requirement Analysis Design Implementation Test REQUIREMENT