Architectural Design Optimization

Some discussion of design optimization should be prefaced with the following comment: Remember that an optimal design that does not work has questionable merit. Software designer should be concerned with established a representation of software which will meet all performance and functional requirement and merit acceptance based on design quality measures.

The Refinement of program structure in the duration the early stages of design are to be encouraged. The Alternative representation may be derived evaluated and refined for the best approach. This approach optimization is one of the true advantages derived from establishing a representation of software architecture.

It is very important to note that in which structural simplicity often reflects both efficiency and elegance. The Design potation should strive for the smallest number of modules which is consistent with effectual modularity and the least come data structure which adequately serves information needs.

For the performance critical applications it may is important to optimize during later design possibly and iterations during coding. The software engineer should note still in which a relatively small percentage of a program often accounts for a high percentage of all processing time period. It is not unreasonable to propose the following approach for performance critical software:

1.    Refine   and Develop   program   structure     without   concern   for performance   critical optimization.
2.    Use CASE tools which simulate run time performance to isolate field of in efficiency.
3.    During late design iterations select modules which are suspect carefully and time hogs establish procedures for time efficiency.
4.    The Code in an appropriate programming language.
5.    Instrument the software to isolate modules which account for heavy processor utilization.
6.    If important recode or redesign in machine-dependent language to improve efficiency.