1. Domain Analysis Zhen Jiang West Chester University

2. Outline Overall picture Steps

3. Overall picture Information Objects Identity, Active action, Effect 1. Do not make your plan too ambitious. 2. Try to simplify each object. The more complex, the more functions are needed to develop. Classes Kinds of objects 1. Each object has identity value. Each status of this object is expressed by different & unique identity value. 2. The change of identity value leads to the change of object status. 3. The range of such a change is defined via data type. 4. Such a data type is CLASS. UML Object relation Class relation Domain Analysis

4. Steps Consider all the objects in each class SET. Consider all the object relations Find object relation (place, time, and etc) Identify each object relation via identity value If a single value and its variation (with the value change) are not enough to cover all different object relations between two classes, a re-design of these two classes are needed. That is, the object relations are too complex to derive a class relation. Pack the object relations into class relation Each relation, with a unique identity value, may have several objects involved. All the relations between two classes are identified with a type of identity values. (Otherwise, go to the above step and redesign the classes.) Name such a type and use this name also for class relation. Analyze all the class relations within the class domain.

5. Analysis (It is a testing to cover all different cases.) Consider the variation of the existence of relation (such as type, number, constraint). Consider sceneries with more classes involved) When you draw/analyze the class domains are the cases you used complex enough? is everything in well organization? is the numbers correct? try association, not just apply your analysis on two classes.

6. Class sample

7. Object relation sample

8. Association sample