Loading...
 

Architecture-Engineering

Definition:

The Architecture-Engineering Process puts in place the Systems-Architecture, which is a controlling mechanism for the Design-Engineering of any project. Architecture-Engineering defines the strategic framework (the Systems-Architecture), which Design-Engineering has to Work within. It lays down the Standards, which control such matters as the tradeoff Processes amongst Requirements. It helps synchronize Design-Engineering disciplines across different Systems.

Alternative Names

Concept Number: *499
English Master: Architecture-Engineering
Synonyms, Variations & Acronyms: Architecting

Detailing

The Architecture-Engineering Process is a subset of the Systems-Engineering Process.


Illustrations

none


Type

Process


Examples

None


Notes

1. The Architecture-Engineering Process is distinct from the larger Systems-Engineering Process in that it is focused on design Issues. (Systems-Engineering is broader. It includes consideration of the Requirements, Quality-Control, project management, and any other discipline, that is useful for satisfying Requirements.)

2. The Architecture-Engineering Process is distinct from the other system Level Design-Engineering Processes because it operates at a higher Level, and is therefore concerned with wider Issues. It has to consider the overall strategic framework, and provide guidance to all the lower-Level systems.
The Architecture-Engineering Process considers especially the long-term objectives, and the totality of the Requirements for all systems.

3. The Architecture-Engineering Process is, ideally, technologically neutral. It should provide guidance on design, using any relevant technology, Policy, motivation, organizational Idea, contractual agreement, sales practice and other devices. One of the main criteria is that the Architecture is cost-effective.
Technological neutrality is not always achieved! For example, promotion of the use of Standard platforms could be included within a Systems-Architecture; and while that is an architectural decision, it is not technologically neutral.


Keyed Icons

none


Drawn Icons

none


Systems-Architecture *564
• Requirement-Engineering *614
• Design-Engineering *501
Architecture-Specification *617


History of Concept

none










This Concept entered by Kai.

Created by system. Last Modification: Sunday 06 of November, 2016 21:46:15 CET by Admin (Kai).