The SEI helps advance software engineering principles and practices and serves as a national resource in software engineering, computer security, and process improvement. The SEI works closely with defense and government organizations, industry, and academia to continually improve software-intensive systems. Its core purpose is to help organizations improve their software engineering capabilities and develop or acquire the right software, defect free, within budget and on time, every time.

System Architecture Tradeoff and Analysis Method

The purpose of the System Architecture Tradeoff Analysis Method (ATAM) is to

assess the consequences of architectural decisions in light of quality attribute requirements and business goals and

discover risks created by architectural decisions in the system and software architectures of systems

Scenarios derived from quality attribute augmented mission threads, system use cases, architectural documents, and SoS architecture challenges (from the MTW) form the basis for evaluation in a System ATAM. The System ATAM is a variant of the ATAM and addresses the following system areas:

System architecture notions and specifications - functional block diagrams, system control and data flow diagrams, electrical diagrams, mechanical drawings, DoDAF views, and so on

Quality attribute concerns – new quality attributes that serve as system architectural drivers (physical robustness, continuity of power supply source, and field-ability)

Architectural approaches – new architectural approaches may be needed to support additional engineering consideration required to create a system. (dynamic resource management, use of development common toolsets)Scope – additional considerations for a system (logistical, electrical , mechanical, weapons, sensor systems, .etc.)

There are three phases to a System ATAM:

Preparation Phasea. Determine if sufficient information and expertise (architectural documentation, relevant system architects, mission threads, system use cases) is availableb. Develop scenarios for use during evaluationc. Identify stakeholders to participate

Post-Evaluation Phasea. Evaluation team analyzes the information gathered and develops a set of architectural risk themes, which are vetted with system lead architects

The System ATAM is one of the methods used in the SoS Architecture Development and Analysis process. It can be used independently of the SoS Architecture Evaluation and the Mission Thread Workshop or as a follow-on.

Availability

The System ATAM is ready to use. The SEI is currently looking for organizations that would like to incorporate the System ATAM as one of their routine software development practices. If you would like technical details about the System ATAM or if you would like to schedule one, contact us using the link in the For more information box at the bottom of this page.