OOT with VP-UML. review1

1. Structure Modeling and Analysis

Domain object and implementation object
Domain objects correspond to entities in the real world and are more stable throughout the entire development lifecycle. The implemented object refers to some abstract general objects. The former is like an ATM or a bank account, and the latter is like a transaction log or an error log.

Polymorphism
The runtime can store its own class and subclass capabilities

Structure Analysis Technology

How to obtain classes: reusability is a standard. Domain Analysis and case analysis should be carried out at the same time. domain analysis starts from the problem statement to generate a class model that identifies reusable objects. These objects are common for most applications in the same problem field and can be identified from use cases. Emphasize reusability again.

Heuristic Analysis Method:
Do not try to develop a large single class chart.
Use the model management results such as subsystems and packages to form the system architecture from top to bottom.
Consider both the logical and physical aspects.
Data coupling is used instead of logical coupling, that is, data is used for communication between subsystems.
Use design patterns wisely.
Perform domain analysis using bottom-up methods such as text analysis and CRC.
Artifact found in two ways ).
Incrementally use packages to organize domain classes.

Generate Domain Models and Analysis
A common method is to obtain a statement of the problem field and perform text analysis to identify candidate classes. This is a good starting point.
1. The most important thing about the problem statement is to clearly describe the problem in the domain context, and mainly describe the general requirements.
2. Text Analysis identifies objects and classes. According to Amour and Miller (2001), the following types of nouns or noun phrases are more likely to be objects.

Clear things... classrooms, venues
Concepts... courses, modules
Things... exams, lectures
External organization... publisher and provider
Roles played by students and teachers
Other systems... Enrollment System, grade report system

Eliminate inappropriate classes:

Redundancy class: indicates the class of a transaction.
Irrelevant class
Fuzzy
Attribute
Operation
Role
Implementation Structure (details)

3. Develop a data dictionary
For each class, write a brief description to define its scope and details about the class, such as attributes and operations.

4. Identify associations between classes and name them based on the nature of the connected verb or verb phrase to eliminate unnecessary and inappropriate relationships.

5. Identify the attributes and associated relationships of a class. Nouns and phrases behind all cells, and adjectives close to nouns and corresponding classes may also be enumerated values of a certain attribute. At this stage, attribute discovery is less likely, but does not affect the structure of domain-class models. In the later stages of the development lifecycle, it is easier to identify attributes.

6. inherit the organizational class from bottom to top (compare attributes to find commonalities) and from top to bottom (check special circumstances and check whether special features are required ).

7. Verify the access path for possible queries

8. iterate and refine the Model

A category has no attributes.
Some attributes and operations
Not found
The property or operation does not have a host