Unified Process Summary History of UP Introduction to UP Three key Aspects of UP Lifecycle of UPDisciplinesPurposes Rational Unified Process (RUP) ConclusionUnified Process SummaryCIS 79000 Spring 2003(Copy for professor)By Jing Zou, April 14, 2003 History of UPIn 1995, Rational company acquired Objectory and formed Rational Objectory Process (ROP), which was a complementary approach and evolved into Rational Unified Process in 1998. It had process model and templates. In 1999, Jacobson, Grady Booch and James Rumbaugh published the Unified Software Development Process. Introduction to UPThe Unified Process (UP) is a de facto standard development process within the object-oriented and component-based software communities.The Unified Process is not a product at all. It is a set of ideas written about by many people. Three key Aspects of UPThere are three key aspects of UP: use-case driven, architecture-centric as well as iterative and incremental.1Use-case driven means that development precedes through a series of workflows that derive from use case.Architecture is the view of the whole design with key characteristics without too many details.Iteration & Increments means steps in the workflow (mini-project) & growth in the product. Lifecycle of UPBasically, the lifecycle of UP includes 4 phases and 5 core workflows (or disciplines) that run through these 4 phases.4 phases include: inception, elaboration, construction and transition.5 core disciplines are: requirements, analysis, design, implementation and test.Inception phase: Develop a good idea into a vision of the end product and present business case for the product.Inception is the time to sit down with the person who is initiating the project. This is where a developer gets the overall idea of what the project is about, its size, scope and maybe a feeling for the political climate that the project will be conducted.2Elaboration phase: Detailed use cases, what is going to be built?During phase II, elaboration, most of user’s use cases are specified in detail. Architecture is expressed as views of all the models of the system, such as use case model, analysis model, design model, implementation model and deployment model. Project manager need to plan the activities and estimate the resources required completing the project. Construction phase: Software added to the architecture.During phase III, construction, the architecture baseline grows to become the full-fledged system and the bulk of the required resources are expanded. The vision evolves into a product ready for transfer to the user community.Transition phase: Products move to beta release.A small number of experienced users will try the product and report defects and deficiencies. The developers will correct the reported problems and incorporate some of the suggested improvements into a general release for the larger user community.The following table lists some of the disciplines of UP and their purpose.The Modeling Disciplines of the Unified Process.3Disciplines PurposesBusiness Modeling The purpose of this discipline is to model the business context, the scope, of your system. Common modeling activities include the development of:*A context model (often a data flow diagram) showing how your system fits intoits overall environment*A high-level business requirements model (often an essential use case model)*A glossary defining critical business terms*A domain model (often a class diagram ordata diagram) depicting major business classes or entities*A business process model (often a data flow diagram or activity diagram) depictinga high-level overview of the business process to be supported by your system. This diagram is one level of detail greater than your context diagramRequirements The purpose of this discipline is to engineer4the requirements for your project, includingthe identification, modeling, and documentation of those requirements. The main deliverable of this discipline is the Software Requirements Specification (SRS), also referred to as the Requirements Model, which encompasses the captured requirements. Analysis & Design The purpose of this discipline is to evolve a robust architecture for your system based on your requirements, to transform the requirements into a design, and to ensure that implementation environment issues arereflected in your design. Enterprise Management (EUP only) This discipline encompasses activities that are outside of the scope of a single project, including:*Enterprise requirements modeling, the act of creating and evolving models that reflect the high-level requirements of your organization. 5*Enterprise architectural modeling, the act of creating and evolving models that depict the business and technical infrastructure of your organization.  Rational Unified Process (RUP)UP is an open SEP while RUP, Rational Unified Process, is a Rational process (commercial) product. If we think in UML terms, then UP defines a class of software development processes and the available commercial variants -including RUP- are like subclasses of UP. This means that the commercial variants take all the features of UP, override some and add new ones. RUP is a development process, not a software process. It inevitably misses or shortchanges some of the concepts that are most important for software professionals. RUP has the following weaknesses:1) Only developing process, not the entire software process2) Not supporting multi-system infrastructure development efforts3) Iterative nature foreign to experienced developers4) Tool-driven approach, not sufficient for complex system6Following a mature software process is a key determinant to the success of a software project. Build Web Solutions with RUPHow to integrate the creative design process with the software engineering process of the Rational Unified Process? Developing Web solutions has a lot of similarities to development of other software applications, but also differs significantly ina number of areas. The challenge for the Web developer is not just the new technologies, but using a process that will facilitate bringing this new set of stakeholders together. Enterprise Unified Process (EUP)EUP, Enterprise Unified Process, was created to 1) Add processes for operation, support, and maintenance.2) Add support for the management of a portfolio of projectsEUP is based on RUP but has two more phases: production and retirement.Production phase: Keep