[原创] Use UML to do fast design (3- Use UML in Design phase)

不好意思，因为文章原本是给公司同事准备的培训材料（只有些大的提纲），所以都用的英文。等我把一些文档慢慢整理完贴上来以后，我会把一部分的内容翻译成中文的，再加入一些说明。 

 1.5           Analysis

Inputs:

 1      Use case diagram

 2      Domain objects

 3      Activity diagram

Steps:

 1      Analyze real use case

 

 

 

 1.1  Sub use case (1.1.1 Analyze action between roles and system)

 

 

1.2      Realized use case (1.1.1.1 Analyze MVC)

 

 

* We can use sequence or activity diagram to show logic. Mind: check error branch for keeping it cover all requirement.

 2      Analysis Object Model

 

 

 3      Update domain object: According to the logic

 4      Write description

 5      Add the nonfunctional requirements.

 1.6           Detail Design

Not finish yet.

Key Points

 1      Describe the life cycle and relation of all classes.

 2      Describe the logic in complex class internal.

 3      Use design patterns

 

Process

 1      Class diagram

 2      Sequence diagram

 3      Activity diagram

 4      Class diagram: Find the hidden no-functional classes

 5      Class-class relationship: Use sequence diagram to show the relationship to represent the object life-cycle

 6      Inside the class: Use activity diagram to show the logic flow

 

 1.7         Questions

 1      How to do review high design?

Joy >> If you involved into a design review meeting, you can follow next rules to check their design is correct or not.

1.       Check roles description. Did they design parent role?

2.       Check use case package diagram to understand module in project.

3.       Check domain objects, the project concept is completed or not.

4.       Check relations between domain objects.

5.       Check high level use case diagram

6.       Check use case’s business logic diagram (Activity diagram for Role-Role). Check all domain object’s status in business logic diagram. Please read before session article.

7.       Following high use case’s business logic diagram, go to check sub use case diagram. Mostly sub use cases are from the business logic steps, and mostly sub case is only related one role.

8.       Check sub use case or realize use case’s internal logic diagram (Sequence diagram for Role-System).

9.       Check main business logic. (Activity diagram or sequence diagram)

 

 2      What’s relation between Domain object, class and DB schema?

Joy >> First, clear concept of domain object, class and DB schema

Domain Object: Based on business knowledge, team will design domain object. And then go to clear relation between domain objects, this step, can help us find new domain object which customer didn’t mention.

Class: business classes are from domain object diagram, one thing we need mind is, we need define some class to manage the relation of domain object. If there are too complex for a few domain objects, the best way is declare a management class for their relation.

Still we need define some system function class too. Such as: user, permission management class, and so on.

DB Schema: DB schema comes from Domain Object too. But need cover all business or system manager objects.

 

 

 

 [原创] Use UML to do fast design (1 - Introduce work steps)  http://www.cnblogs.com/joyyuan97/archive/2008/07/26/1251886.html

 [原创] Use UML to do fast design (2- Use UML in requirement phase)   http://www.cnblogs.com/joyyuan97/archive/2008/07/26/1251889.html

[原创] Use UML to do fast design (3- Use UML in Design phase)  http://www.cnblogs.com/joyyuan97/archive/2008/07/26/1251928.html