Third,
It is also evident from the definition that every system has architecture, because it is always be composed of elements that interact with each other. In the most trivial case, a system is itself a single element -- an uninteresting and probably non-useful architecture, but architecture nevertheless. Architecture can exist independently of its description or specification, which raises the importance of architecture documentation and architecture reconstruction.
Fourth,
A system is composed of independent elements and behaviors that can be discarded or ignored in favor of other elements. This behavior is what allows elements to interact with each other, which is clearly part of the architecture. This does not mean that the exact behavior and performance of every element must be documented in all circumstances; but to the extent that an element’s behavior influences how another element must be written to interact with it or influences the acceptability of the system as a whole, this behavior is part of the software architecture.
Finally,
Architecture is supposed to meet its requirement and is considered to be fully implemented according to the specifications. To decide whether an Architecture is good or bad one can only be judged upon the criteria of meeting its behavioral, performance and life-cycle requirements.
next previousBack to JATIT Free Content Research Articles
©2005 Jatit Grid Computing Software Architecture