Object-Oriented Analysis and Design

Rational Unified Development Process

This is a learning note for Object-Oriented Analysis and design methods. This is an understanding of the "unified development process. Hope you guys can give me some advice!

"Unified development and development process" can be achieved

Provide guidance on the development activities of the entire development team.

Provides comprehensive guidance to individual developers and development teams.

What are the development results?

Provides criteria for monitoring and measuring products and activities in a project.

"Unified Development Process" Overview

A unified development process is a general term for translating users' needs into a series of activities of a software system, not just a process. it is also a general process framework (which can cope with a wide range of software systems, different application fields, different organization types, different performance levels, and different project scales.

Features of "unified development process"

The "Unified Development Process" is component-based. The software system developed by Alibaba Cloud is composed of components, and components are interconnected through well-defined interfaces.

The "Unified Development Process" uses the "unified modeling language)

The "Unified Development Process" is case-driven, centered on the basic architecture, iterative and incremental.

What does "Unified Development Process" Use Case-driven mean?

A use case is a function that provides valuable results to users in the system. All the use cases are combined to form a "Use Case model", which describes all the functions of the system.

Here, let's take a look at the concepts of "Use Cases" and "users ".

In the "unified development process", you must understand what potential users need?

The term "user" refers not only to the limitation of human users, but also to other systems. In this sense, "user" represents someone or something that interacts with a system developed using the "unified development process.

The system completes a series of actions, which provide users with a meaningful result. This interaction is a "Use Case ". Use Cases are not just a tool that defines the requirements of a system. Use Cases also drive system design, implementation, and testing. They drive the entire development process. First, define the use case, and then design the use case (Opportunity case model. The software engineer creates a series of design and implementation models to implement various use cases ). Finally, use cases are the source for testers to build test cases.

The "Unified Development Process" is centered on the basic architecture

In essence, the role of software architecture is to grasp a complete software from different perspectives.

The basic architecture of the software system is also described in different views.

What is the relationship between use cases and the basic architecture?

Each product is an organic unity of functions and forms.

The function should correspond to the use case, and the form should correspond to the basic architecture.

On the one hand, the use cases we implement must adapt to the basic architecture. On the other hand, the basic architecture must have room for all the use cases needed to implement the present and the future.

Use Cases and basic architecture must be developed in parallel.

First, you can create an outline of the architecture without the specific use case.

Designers should start with a subset of validated use cases, which refer to the use cases that represent the key functions of the system to be developed.

As the use cases have been defined and gradually become mature, the basic architecture is gradually formed.