RUP

Apr 28 posted in Development (RSS), comments.

Quote Address: http://java.chinaitlab.com/UML/36676.html

1 Foreword

Software process is the implementation in software development and maintenance of the stage, methods, technology, practice and related products (plans, documents, models, code, test cases and manuals, etc.) collection. Software process can be effective software development organizations improve productivity, improve software quality, reduce costs and reduce risk. Currently on the market leading software has mainly RUP (Rational Unified Process), OPEN Process and OOSP (Object-Oriented Software Process).

RUP has a higher awareness of one of the reasons is probably because its author Rational Software Corporation brings together object-oriented three prominent experts in the field of Booch, Rumbaugh and Jacobson, meanwhile it is also object-oriented development of industry-standard language?? standard modeling language (UML) founder. RUP is a process Objectory evolved from its initial version 5.0, has undergone 5.1,5.11,5.5, etc. until the latest version of Rational Unified Process2000 version. This paper mainly discusses the main elements of RUP and characteristics.

RUP two two-dimensional development model

RUP can be used to describe two-dimensional coordinates. Transverse time organizations, are to start the process of life cycle characteristics, reflecting the dynamic development process structure, the terminology used to describe it include cycle (Cycle), stage (Phase), iteration (Iteration) and milestones (Milestone); longitudinal axis of content to organize the logic of natural activity, reflecting the development of the static structure, the terminology used to describe its main activity (Activity), the product of (Artifact), workers (Worker) and workflow (Workflow). Figure 1:

Figure 1 RUP development of two-dimensional model

Three development process at all stages and milestones

RUP in software life cycle at the time the order was broken down into four stages, namely: the initial phase (Inception), refinement phase (Elaboration), construction phase (Construction) and delivery stage (Transition). The end of each stage of a major milestone in the (Major Milestones); the essence of each stage are both on the time span between milestones. At the end of each stage of the implementation of an evaluation to determine whether or not the objectives of this phase have been met. If the assessment results are satisfactory, they can permit the project into the next phase.

1. The initial stage of

Sometimes also called the initial phase of the first phase of the Kai. The initial stage of the system's goal is to set up the business case and determine the project boundaries. In order to achieve the aim must be to identify all systems interact with external entities, at a higher level on the definition of interactive features. This stage of great significance, at this stage in the concerns of the entire project are ongoing operations and the demand side the main risks. The system set up at the original foundation on the development projects, the initial phase may be very short.

The end of the initial phase is the first important milestone: the life cycle of the target (Lifecycle Objective) milestone. Milestone in the life cycle of the target basic viability of the project evaluation.

2. Refinement stage

Refinement phase objective is to analyze the problem areas, establish and improve the basic architecture, preparation of project plans, out of the project element of the highest risk. In order to achieve this end, it is important in understanding the whole system on the basis of decision-making structure, including its scope, major functionality and performance, such as non-functional requirements. At the same time for the project set up to support the environment, including the creation of the development of the case, create templates, guidelines and tools ready.

Thinning the end of the second phase of an important milestone: the structure of the life cycle (Lifecycle Architecture) milestone. Milestone in the life cycle of the structure of the structure of the system set up to manage the baseline and the project team be able to phase in building measure. At this moment, it is necessary to test the detailed system objectives and scope, structure and selection of major risk solutions.

3. Construction phase

In building a stage, all remaining components and application features are developed and integrated product, all the functional tests have been detailed. In a sense, building a stage is a manufacturing process, with emphasis on the management of resources and control to optimize the cost of the operation, progress and quality.

Construction at the end of phase is the third important milestone: the initial function (Initial Operational) milestone. Milestone in the initial function can decide whether the product in a test environment to deploy. At this moment, to determine the software, the environment, users can begin operation of the system. At this point the product version is also often referred to as "beta" version.

4. Delivery phase

Delivery phase of the focus is to ensure that software to end-users are available. Delivery across a number of iterative stages, including preparation for the release to do the product testing, based on user feedback from a small amount of adjustment. Life cycle at this point, user feedback should focus primarily on Product adjust, setup, installation and usability questions, all of the major structural problems at the project should have been the early stages of the life cycle resolved.

At the end of the delivery stage is the fourth milestone: Product Release (Product Release) milestone. At this point, to determine whether the target implementation, should start another development cycle. In some cases this may be related to the next milestone in the initial stage of a cycle, the end of coincidence.

RUP's four core workflow (Core Workflows)

Medium RUP has nine core workflow is divided into six core process workflows (Core Process Workflows) and three core support workflow (Core Supporting Workflows). 6 even though the core of the workflow process may give rise to think of the traditional waterfall model some stage, but it should be noted in the stage of the iterative process are completely different, these workflows throughout the life cycle again and again visited. 9 core workflow in the project to be used in rotation, at each iteration with different focus and intensity of duplicate.

1. Business modeling (Business Modeling)

Business modeling workflow describes how the objectives for the new organization to develop a concept and is based on the idea in the business use case model and business object model defined in the process of organization, roles and responsibilities.

2. Demand (Requirements)

Demand workflow goal is to describe the system should do, and developers and users to reach a consensus on this description. In order to achieve this goal, necessary to carry out the functions and constraint extraction, organization, documentation; above all understand the system to solve the problem of definition and scope.

3. Analysis and Design (Analysis & Design)

Analysis and design work will flow into the future demand for system design, system development of a robust structure and adjust the design so that it matched with the implementation environment, and optimize its performance. Analysis of the results of the design is a design model and an optional analysis model. Design models are the source code of the abstract, by design and some description of the composition. Designed to be organized into categories of good interface design package (Package) and design subsystem (Subsystem), which reflects the type of description is the object of how to work together to achieve the function of use cases.

Events Designed to architecture-centric, architecture by a number of structures to express their view, structural view is the whole design of the abstract and simplified, the view has been omitted from some of the details, so that embodies the essential characteristics of a more clear. Architecture is not just a good design model carrying the media, but also in the system can improve the quality of the model is created.

4. Implementation (Implementation)

The purpose of workflow implementation including hierarchical subsystems form the definition of the organizational structure of the code; to the form of components (source files, binary files, executable files) implementation classes and objects; the components will be developed as a unit for testing and integrated by a single developer (or group) results, making it executable system.

5. Test (Test)

To verify that the test workflow interaction between objects to verify the software integration of all components of the right to test all of the demand has been the correct implementation, identify and verify defects in software prior to deployment has been put forward and deal with. RUP proposed iterative method, meaning that the entire project at test, thus as soon as possible to find defects, fundamentally reducing the cost of amending the defects. Test is similar to three-dimensional model, respectively, from the reliability, functionality and system performance to carry out.

6. Deployment (Deployment)

The purpose of the deployment workflow is successful and will generate the version of software to end-users. Describes the deployment of workflow software products to ensure that those with end-users with the availability of related activities, including: software package to produce products other than the software itself, installation software, to provide users with help. In some cases, may also include planning and conduct beta test version, the transplantation of existing software and data as well as formal acceptance.

7. Configuration and Change Management (Configuration & Change Management)

Configuration and change management workflow describing how members in a number of projects to control many products. Configuration and change management workflow provides guidelines to manage the evolution of the system a number of variants, the creation of the process of tracking software version. Workflow describes how to manage parallel development, distributed development, how to automate the creation of works. Also elaborated on the reasons for product modifications, time and personnel to maintain the audit records.

8. Project Management (Project Management)

Software Project Management balance may have conflicting objectives, manage risk and overcome the various constraints and allows the user satisfaction with the successful delivery of products. Its objectives include: To provide a framework for project management for the plan, staffing, implementation and monitoring of projects to provide practical guidelines for the provision of risk management frameworks.

9. Environment (Environment)

The purpose of the environment workflow is to software development organizations to provide software development environment, including processes and tools. Environment Workflow projects concentrate on the process of configuration required for activity, but also support the development of the project activity norms, provides a step-by-step instruction manual and describes how the process of implementation in an organization.

Friday RUP iterative development model

RUP for each stage can be further broken down into iterations. An iteration is a complete development cycle, resulting in an executable product version, the final product are a subset of its incremental development process from one iteration to another iteration process to be the ultimate system.

Organize traditional items are on the order flow through each job, each job stream only once, that is, we are familiar with the waterfall life cycle. If we do so, to achieve the end products are completed and begin testing at the analysis, design and implementation stages of the hidden legacy of a large number of questions will arise, the project may have to stop and start a long cycle of bug fixes.

Figure 2 RUP iterative development model

A more flexible, less risk is many times through different development work flow, so that a better understanding of needs, construct a robust architecture, and finally delivered a series of progressively completed version. This is called an iterative life cycle. Job stream at every order the adoption of said