Design Review Meeting Minute

We take a meeting to review our project to check the design base on the system bug and performance problem. The following comments are came to an agreement for us to improve.

 

1. The Oracle Sequence ID can not take any business logic. It's just a PK to unique data.

2. Log table control rule.

    The Log table will keep the right result data for each modification. All temporary operation will work on main table. If user want to query the last stable data, he should query the last data from log table.

 

3. Undo and redo. System allow undo and redo operation base on a undo point. The undo point can be set as “operation type” or  “operation date”. It's base on the business process.

 

4. Data module layer.

Don't take too much layer to make logic complex. The module layer should keep simplify. We suggest just keep two layer: View Object and Business Object.

The view object lifecycle is base on view layer page display.

The business object lifecycle is base on whole business process.

 

5. Database table cannot too big. We suggest the table filed number cannot bigger than 50 fields. If your table bigger than 50 fields you should take time to seperate and redesign the table.

 

6. Regularly review the defect and take the typical defect to agreement with teams.

 

7. check the TOGAF document. 

Basic introduce

http://baike.baidu.com/view/1305226.htm

 

Infoq introduce with attachement

http://www.infoq.com/cn/news/2009/02/togaf9

 

Official introduce and document

http://www.opengroup.org/togaf/