Software Engineering--analysis of the face object of theory, method and practice

Software Engineering--object-oriented analysis of theory, method and practice

During the requirements acquisition phase, developers focus on understanding the user and their usage needs. In the demand analysis phase, developers focus on understanding what the system needs to build, at the core of which is to produce an accurate, complete, consistent, and verifiable system model called an analytic model.

The object-oriented analysis model consists of three independent models:

1. Function Model: represented by use case and scene.

2. Analysis object Model: Represented by use case diagram and object graph.

3. Dynamic model: Represented by state diagram and sequence diagram.

In the Analysis object model, the analytic class is the content at the conceptual level, which is used to describe the higher-level objects in the system. In the analysis phase, the analysis class is directly related to the application logic, but not to the purely technical implementation problem. From the functional requirements of software, the analysis class can be divided into 3 types of entity class, boundary class and control class.

Entity classes: Permanent information that represents system storage and management

Boundary class: Represents the interaction between the participant and the system.

Control class: Represents the business control logic of the system during operation.

In order to identify analysis classes, it is often necessary to fully understand the behavior inside the system, so it is necessary to supplement the initial use case model with instructions on how to respond to external requests within the system. On the basis of understanding and supplementing the use-case model, developers need to identify a set of alternative analysis classes that support use case behavior.

A sequence diagram can associate a use case with an analytic object to assign the behavior of the use case to the identified analysis class, and help the developer Discover and supplement the previously missed analysis classes and get an improved analysis class.

After analyzing the interaction between objects, developers need to create analytic class diagrams that define the relationships between the analysis classes and the properties of the analysis classes.

The analytical model is generated during multiple iterations and adjustments and requires close communication between the developer and the user to ensure the correctness of the analysis model. After modeling, you must organize the developers and users to formally review the formed analysis model to ensure the correctness, completeness, consistency and feasibility of the analysis model.

Software Engineering--analysis of the face object of theory, method and practice