Architectural Design Basic Principles

Design to achieve user's functional requirements

 

Design to achieve user's non-functionl requirements

 

Design that can easily respond to changes

• A very good SW organization desgined for this level.
• Design that focuses not only on availability, performance, and ease of use, which are important customer concerns, but also on changeability or testability.

 

How do I know what is changing?

• I can find out whether user or customer needs are likely to change in light of current market trends.
• Based on the revision history otf the past module, I can check whether it will change in the future.
• Very specific methods can evolve and change over time.

 

Stability Indicator

• One of the ways to measure component stability can be by counting the number of dependencies coming into and going out of compnents.

 

Measuring the degree of abstraction

• It is a simple calculation of the number of interfaces and abstract classes compared to the total number of classes in the component.