Activity: Analyze a Use Case. Activity: Analyze a Class. Activity: Analyze a Package. Summary of Analysis. Artifact: Design Model. Artifact: Design Class. Artifact: Use-Case Realization—Design. Artifact: Design Subsystem. Artifact: Interface. Artifact: Deployment Model.
Activity: Architectural Design. Activity: Design a Use Case. Activity: Design a Class. Activity: Design a Subsystem. Summary of Design. Artifact: Implementation Model. Artifact: Component. Artifact: Implementation Subsystem. Artifact: Integration Build Plan.
Worker: System Integrator. Activity: Architectural Implementation. Activity: Integrate System. Activity: Implement a Subsystem. Activity: Implement a Class. Activity: Perform Unit Test. Summary of Implementation. Artifact: Test Model.
Artifact: Test Case. Artifact: Test Procedure. Artifact: Test Component. Artifact: Plan Test. Artifact: Defect. Artifact: Evaluate Test. Worker: Test Designer. Worker: Integration Tester. Worker: System Tester. Activity: Plan Test. Activity: Design Test. Activity: Implement Test. Activity: Perform Integration Test.
Activity: Perform System Test. Activity: Evaluate Test. Summary of Testing. The Need for Balance. Inception Phase Establishes Feasibility.
Construction Phase Builds the System. Transition Phase Moves into the User Environment. The Generic Iteration Revisited. Core Workflows Repeat in Each Iteration. Workers Participate in the Workflows.
Planning Precedes Doing. Plan the Four Phases. Plan the Iterations. Think Long Term. Plan the Evaluation Criteria. Risks Affect Project Planning. Manage a Risk List. Risks Affect the Iteration Plan. Schedule Risk Action. Use-Case Prioritization. Risks Specific to a Particular Product. Risk of Not Getting the Architecture Right. Risk of Not Getting Requirements Right. Resources Needed. Projects Differ Widely. Complex Projects Have Greater Needs.
New Product Line Calls for Experience. Paying the Cost of the Resources Used. Assess the Iterations and Phases. Criteria Not Achieved. The Criteria Themselves. The Next Iteration. Evolution of the Model Set. The Inception Phase in Brief. Early in the Inception Phase. Before the Inception Phase Begins. Planning the Inception Phase. Expanding the System Vision.
Setting the Evaluation Criteria. The Archetypal Inception Iteration Workflow. Introduction to the Five Core Workflows. Fitting the Project into the Development Environment. Finding Critical Risks. Execute the Core Workflows, Requirements to Test. Capture the Requirements. Make the Initial Business Case. Outline Business Bid. Estimate Return on Investment. Assess the Iteration s in the Inception Phase. Planning the Elaboration Phase.
The Deliverables for the Inception Phase. The Elaboration Phase in Brief. Early in the Elaboration Phase. Building the Team.
Modifying the Development Environment. Setting Evaluation Criteria. The Archetypal Elaboration Iteration Workflow. Capture and Refine Most of the Requirements. Develop the Architectural Baseline.
Iterate While the Team Is Small. Execute the Core Workflows—Requirements to Test. Make the Business Case. Prepare the Business Bid. Update Return on Investment. Assess the Iterations in the Elaboration Phase. Planning the Construction Phase. The Key Deliverables. The Construction Phase in Brief. Early in the Construction Phase. Staffing the Phase. The Archetypal Construction Iteration Workflow. Execute the Core Workflows—Requirements to Testing. Controlling the Business Case.
Assess the Iterations and the Construction Phase. Planning the Transition Phase. The Transition Phase in Brief. Early in the Transition Phase. Staffing the Transition Phase. What We Do in the Transition Phase.
Getting the Beta Release Out. Installing the Beta Release. Responding to the Test Results. Adapting the Product to Varied User Environments. Completing the Artifacts. When Does the Project End? Completing the Business Case. Controlling Progress. Review of the Business Plan. Assess the Transition Phase. Assess the Iterations and the Phase. Postmortem of the Project. Planning the Next Release or Generation. The Life Cycle Objectives.
The Life Cycle Architecture. Initial Operational Capability. Product Release. The Major Themes. Management Leads Conversion to Unified Process. The Case for Action. The Reengineering Directive Persuades.
Implementing the Transition. Specializing the Unified Process. Tailoring the Process. Filling in the Process Framework. Relate to the Broader Community.
Get the Benefits of the Unified Process. Extensibility Mechanisms. Graphical Notation. Structural Things. Behavioral Things. Grouping Things. Annotational Things. Dependency Relationships. Association Relationships.
Generalization Relationships. Glossary of Terms. Tagged Values. Pearson offers special pricing when you package your text with other student resources. If you're interested in creating a cost-saving package for your students, contact your Pearson rep.
Ivar Jacobson, Ph. He was one of the three amigos who originally developed the Unified Modeling Language. He is the principal author of five best-selling books on these methods and technologies, in addition to being the coauthor of the two leading books on the Unified Modeling Language. Ivar is a founder of Jaczone AB, where he and his daughter and cofounder, Agneta Jacobson, are developing a ground-breaking new product that includes intelligent agents to support software development.
Ivar also founded Ivar Jacobson Consulting IJC with the goal of promoting good software development practices throughout teams worldwide. He has been working on object-oriented methodology and tools for many years.
He developed the DSM object-oriented programming language, the state tree model of control, the OMT object modeling notation, and the Object Modeling Tool graphic editor. Rumbaugh received his Ph. Profile of a typical project showing the relative sizes of the four phases of the Unified Process.
The Unified Process is not simply a process, but rather an extensible framework which should be customized for specific organizations or projects. The Rational Unified Process is, similarly, a customizable framework. As a result it is often impossible to say whether a refinement of the process was derived from UP or from RUP, and so the names tend to be used interchangeably.
Since then various authors unaffiliated with Rational Software have published books and articles using the name Unified Process, whereas authors affiliated with Rational Software have favored the name Rational Unified Process. Unified Process Characteristics. Iterative and Incremental. The Elaboration, Construction and Transition phases are divided into a series of timeboxed iterations. The Inception phase may also be divided into iterations for a large project.
Each iteration results in an increment, which is a release of the system that contains added or improved functionality compared with the previous release. Requirements, Design, Implementation, Testing the relative effort and emphasis will change over the course of the project. Use Case Driven. Each iteration takes a set of use cases or scenarios from requirements all the way through implementation, test and deployment.
Architecture Centric. Since no single model is sufficient to cover all aspects of a system, the Unified Process supports multiple architectural models and views. This partial implementation of the system serves and validate the architecture and act as a foundation for remaining development.
Risk Focused. The deliverables of each iteration, especially in the Elaboration phase, must be selected in order to ensure that the greatest risks are addressed first. Project Lifecycle. Inception Phase. If the Inception Phase is long then it may be an indication of excessive up-front specification, which is contrary to the spirit of the Unified Process.
Elaboration Phase. However, the primary goals of Elaboration are to address known risk factors and to establish and validate the system architecture. Common processes undertaken in this phase include the creation of use case diagrams, conceptual diagrams class diagrams with only basic notation and package diagrams architectural diagrams.
This is a partial implementation of the system which includes the core, most architecturally significant, components. It is built in a series of small, timeboxed iterations.
By the end of the Elaboration phase the system architecture must have stabilized and the executable architecture baseline must demonstrate that the architecture will support the key system functionality and exhibit the right behavior in terms of performance, scalability and cost.
0コメント