Cab and OOAD (I) Continued 1

1.1 Requirement

We require that the recorded requirements be accurate, clear, and reasonable. On this basis, the products required by the system mainly include:

GuiA quick prototype can be drawn on a whiteboard or on a straw paper. If it is a whiteboard, You need to retain digital photos for reference in the case of rough finalization. You can alsoVisioOrUistudio. Note thatGuiA quick prototype does not constitute part of a final product. It serves only as a means of obtaining and verifying requirements.

For use cases, we need to describe the main use case diagram of the system. Each use case requires a text description, which can be an overview or based onCockburnUse Case format. However, note that each use case text must contain three elements: system operations by the participant, system operations, and information returned by the system to the participant.

 

The glossary needs to record existing domain models in the system. Its main purpose is to help stakeholders reach consensus on their fields. The glossary can be sorted by referring to the classification list and the noun recognition method.

The supplemental specification is mainly used to record the non-functional requirements in the system. You can also specify the supplemental Protocol text at the end of the case text.

Note that you should not fully define all requirements at the beginning. The demand is changed, so we need to be as broad as possible at the beginning(The broad meaning is not rough. Maybe, It is rigorous.)Records the requirements we can find at that time, find out the most important parts of the system, and divide the priority of the requirements. Create the first iteration product based on the priority and continuously feedback and improve it. In fact, this is the best way to avoid waste.

1.2 Analysis

In the analysis part, our main purpose is to convert the requirements into analysis classes: boundary class, control class, and entity class.

The main source of the boundary class isGuiQuick prototyping.

The main source of the entity class is from the glossary in the requirement product.

The control class is used to connect the boundary class and object class to help them communicate.

With the robust analysis graph, we can obtain the following content:

The active boundary class refers to the interaction between the active participants and the system.

The passive boundary class is part of the communication and interaction between the system and the passive participant. It mostly refers to the interface with a third-party system.

Entity classes are often used to record system status information in the system.

The control class has two major tasks: one is to process the communication with the boundary class, and the other is to communicate with the entity class.

1.3 Simple Design

We need to set the basis of the analysis classMVCOrMVPTo the system architecture.

 

In most cases, the active boundary class directly correspondsView. WhileModelThe Section consists of two parts: one is a domain model package composed of entity classes, and the other is to split the control classes and extract operations related to the entity classes and place them inModelModule. Another part of the control class is formed.Controller.

1.4 Initial knowledge architecture

the system consists of the client and server. Both ends are designed as containers and communicate with each other through Web Service . The skeleton can run independently without any modules. To create a new module, you only need to place the DLL of the module in the specified directory of the system, specify DLL information in the configuration file. The skeleton automatically identifies the module.