Performance depends largely on the volume and complexity of the inter-component communication and coordination, especially if the components are physically-distributed processes. Component reusability depends on how strongly coupled components are with other components in the system. Modifiability, for example, depends extensively on the system's modularization, which reflects the encapsulation strategies. First approach to achieving quality attributes: An architecture can either allow or preclude the achievement of most of a system's targeted quality attributes.As such, architectural decisions are the hardest to change, and have the most far-reaching consequences. All downstream design decisions must be consistent with the architectural choices. The selection of components and connections, as well as the allocation of functionality to each component, is a codification of the earliest design decisions about a project. In this case, the importance of an appropriate architecture is magnified across all the projects it will serve.Įmbodiment of earliest design decisions: The architecture represents the first mapping from requirements to computational components. If managed carefully, an entire product family may be produced using a single architecture. An architecture may be re-used on other systems for which it is appropriate. Once it is made, an architectural decision has an extremely long lifetime and survives even outside of the software that it describes.īlueprint for product line development. Project blueprint: The choice of architectural components is institutionalized in the developing organization's team structure, work assignments, management units, schedule and work breakdown structures, integration plans, test plans, and maintenance processes. Roles include:īasis for communication: Project team members, managers, and customers all turn to the architecture as the basis for understanding the system, its development, and how it works during execution. A formal architecture representation is more likely to be maintained and followed than an informal one, because a formal architecture can more readily be consulted and treated as authoritative, and can more easily be transferred to other projects as a core asset. Architecture and ADLsĪn architecture plays several roles in project development, all of them important, and all of them facilitated by a formal representation of the architecture, such as with an ADL. Current examples include Rapide, UniCon, ArTek, Wright and Meta-H. Today, ADLs are in a maturing phase, but several exist. Sophisticated ADLs allow for early analysis and feasibility testing of the design decisions.ĪDLs trace their roots to module interconnection languages of the 1970s.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |