Saturday, February 13, 2010
Architecture/Design Guidelines
Below is a few points which need to be considered while arhitecting or designing an enterprise application
1. Use multi tiered architecture
2. Reduce coupling between components
3. Increase component cohesion
4. Identify areas of expected high frequency changes and design to facilitate maitenance
5. Identify the reusable components
6. Documentthe architecural goals and constraints
7. Avoid using platform/vendor specific components
8. Avoid using third party components unless there are specific reasons
9. Identify interfaces to external device or applications
10. Define the projected data volume from the business requirements for an extended time period.
11. Identify all the specific hardware and software needs
12. Define the performance benchmark and design accordingly. Plan for continuous performance tests during development.
13. Address all the non functional requirements at the time of design.
14. Concurrency, Security and Transaction management are to be addressed.
15. Follow standard OOAD guidelines
16. Follow standard Design Patterns to avoid common problems.
1. Use multi tiered architecture
2. Reduce coupling between components
3. Increase component cohesion
4. Identify areas of expected high frequency changes and design to facilitate maitenance
5. Identify the reusable components
6. Documentthe architecural goals and constraints
7. Avoid using platform/vendor specific components
8. Avoid using third party components unless there are specific reasons
9. Identify interfaces to external device or applications
10. Define the projected data volume from the business requirements for an extended time period.
11. Identify all the specific hardware and software needs
12. Define the performance benchmark and design accordingly. Plan for continuous performance tests during development.
13. Address all the non functional requirements at the time of design.
14. Concurrency, Security and Transaction management are to be addressed.
15. Follow standard OOAD guidelines
16. Follow standard Design Patterns to avoid common problems.
Labels: Architecture, Design
Saturday, January 30, 2010
Architecture
Definition of Architecture
1. An architecture is the set of significant decisions about the organization of a software system, the selection of the structural elements and their interfaces by which the system is composed, together with their behavior as specified in the collaborations among those elements, the composition of these structural elements and behavioral elements into progressively larger subsystems, and the architecture style that guides this organization these elements and their interfaces, their collaborations, and their composition.
2. The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution.
3. A formal description of a system, or a detailed plan of the system at component level to guide its implementation.
4. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time.
Labels: Architecture
Subscribe to Posts [Atom]