"Software Engineering--theory, Method and practice"--a summary of the seventh chapter object-oriented Analysis

The 7th Chapter Object-Oriented Analysis

Object-oriented Analysis model: Functional model, analytical object model, dynamic model.

First, the concept of analysis

Analytic classes can be divided into entity classes, boundary classes, and control classes.

In the UML language, use stereotypes <<entity>>,<<boundary>> , and <<control>> represents entity classes, boundary classes, control classes, respectively.

Analysis Activities: Understanding the use case model, identifying the analysis class (identifying entity classes, identifying boundary classes, identifying control classes), defining interaction behaviors, building analytic class diagrams (defining attributes, defining behaviors, defining relationships), and reviewing analytical models. The analysis process is a cycle-by-step process, and the identification and refinement of analytical models require multiple iterations of iterative implementations.

Second, the Identification analysis class

Typically, an actor interacts with a use case or communicates with a boundary class. The boundary class collects information from the participants, which can be used by entity classes and control classes.

The control class is responsible for reconciling boundary classes and entity classes, usually in the real world, and it is responsible for receiving information about the boundary class and distributing it to entity classes. The control class has a close relationship with the use case, which is created when the use case starts executing and is canceled at the end of the use case.

An entity class is usually a participating object in a use case, which corresponds to a "thing" in the real world.

Inspiring analysts the elements of the entity class include the following: People, organization, goods, equipment, events, tables.

Third, define the interaction behavior

Sequence diagram Drawing steps:1. List The participants who initiated the use case; 2. the boundary object used by the participant when the use case is started;3. lists the control objects that manage the use case; 4. According to all processes described by the use case, lists the sequence of message accesses between the analysis objects in chronological order.

Iv. building an Analytic class diagram

For each analysis class, consider and discover the properties of the analysis class from the following aspects:

• According to general knowledge, find out some properties of the object;

• Study the problem domain carefully and find out some properties of the object;

• Identify certain characteristics of the object according to the requirements of system responsibility;

• Consider the information the object needs to save and manage, and find out the corresponding attributes of the object;

• object in order to implement this function in the service, some additional attributes are required;

• Identify the state in which the object needs to be differentiated, and consider whether an attribute needs to be added to differentiate the States;

• Determines that the attribute represents the whole and part structure and instance connections.

Analysis mode is a common part that describes the discovery in the system business domain, improves the reusability and the consistency.

Five, evaluation analysis model

After the modeling is completed, developers and users must be organized to formally review the formed analysis model to ensure the correctness, completeness, consistency and feasibility of the analysis model.

"Software Engineering--theory, Method and practice"--a summary of the seventh chapter object-oriented Analysis