Architectural Design

The primary goal of architectural design is to build a modular program structure and represent the control relationships among modules.   Additionally architectural design melds program data structure and structure defining interfaces which enable data to flow by the program.

There are several brief stories from everyday life to understand the importance of architecture design we present:

You have saved your money, you have bought a beautiful piece of land and you have decided to establish the house of your dreams. By having no experience in such matters you visit a builder and explain your desires number and contemporary styling, size of rooms and spa of course lots of glass, cathedral ceilings, etc.The builder listens carefully and asks a few questions and them tells you that he will have a design in a few weeks.

As you wait anxiously for his call you conjure up many various and out rigorously expensive images of your new house. What will he come up with? Later, the phone rings, you rush to his office.

Pulling out a large manila file the builder spreads a diagram of the plumbing for the 2nd floor bathroom in front of you and proceeds to explain it in great detail.

But what about the whole design? you say.
Don’t worry; says the builder, we will get to that later.

Does the builder’s final response?  Of course not you need to see a sketch of a floor plan, the house and other information which will give an architectural view.   Still several software   developers act like the builder in our story. They concentrate on the plumbing code and procedural details to the exclusion of the software architecture.   The design technique presented in this section encourages the software engineer to concentrate on architectural design previously worrying about the plumbing.