|
This page last changed on Jul 18, 2005 by jflowers.
- Putting it All Together
There are a lot principles, practices and values to adher to. At times they may be difficult to reconcile. The referenced sources as well as a design lead will be able to help achive harmony. Design Patterns *follow these standards and are good examples how to apply them. To borrow from *Design Patterns terminology Design Patterns are examples of these standards were all forces have been accounted for creating a self supporting system. Design Patterns are not concrete examples but they are less abstract than the standards detailed here.
- Clean Slate
- Additions
- Changes
- Fixes
- Review
- Pre
A per-review of a desing before its implementation is a practive we will follow. This practice is most obvious at the macro level, were magor effort is put into producing design artifacts liek UML and design papers. Where it is seen less but needed just as much is at the micro level, those everyday design desicions. Where you are making a fix and you have a choice, you alwasy do, do do it one way or the other. You should be reviewing this with a peer to validate the design before implementation.
- Post
Post implementation review is seen less often than pre implemation review. These should be triggered as a result of one if not more of the following events:
- Breaking of one or more object oriented metric's thresholds.
- Accumulation of major changes or a large number of changes over time to a subject.
- Overtly buggy subject.
PAG
Performance
See document: default.asp
|
