3rd International Conference on COTS-Based Software Systems

3rd International Conference on COTS-Based Software Systems

A Comparison of Requirements Specification Methods from a Software Architecture Perspective

In this report, five methods for the elicitation and expression of requirements are evaluated with respect to their ability to capture architecturally significant requirements.

A Comparison of Requirements Specification Methods from a Software Architecture Perspective

Presented: April 2006

A Design Space and Design Rules for User Interface Software Architecture

Design Space and Design Rules for User Interface Software Architecture, A

A Federation Object Model (FOM) Flexible Federate Framework

The concept of a framework as a reusable software component has become a state-of-the-practice technique in software companies. A number of frameworks based on High Level Architecture (HLA) are available commercially, and many companies have developed their own frameworks for internal applications. Using a framework reduces development time and allows software architects and programmers to focus on the unique aspects of the simulation. However, the challenge of developing a reusable component to support dynamic reconfigurability remains. Indeed, existing frameworks use a static object-model representation that requires full knowledge of object model components when a federate is built (at compile-time). This report describes an approach to designing a domain framework that encapsulates expertise in developing an HLA federate by hiding runtime infrastructure (RTI) internal operations from the developer. This approach uses a JavaTM virtual machine and a parser to map object representations of federation object model (FOM) elements dynamically.

A Life-Cycle View of Architecture Analysis and Design Methods

This report examines these methods and activities to understand their commonalities and relationships to life-cycle changes, and proposes a means of tailoring the activities so that they can fit more easily into existing life-cycle models.

A Practical Application of the Ceiling Protocol in a Real-Time System 

This paper briefly discusses some of the real-time design issues that arise when using the priority ceiling protocol for real-time systems. The paper shows a small real-time system design and shows how the code in the system could be structured to satisfy the requirements of the ceiling protocol. This paper will be presented at the 2nd International Workshop on Real-Time Ada Issues in May 1988.

A Practical Example of Applying Attribute-Driven Design (ADD), Version 2.0

A Practical Example of Applying Attribute-Driven Design (ADD), Version 2.0

A Proactive Means for Incorporating a Software Architecture Evaluation in a DoD System Acquisition

This technical note provides guidance on how to contractually incorporate architecture evaluations in an acquisition. A sample Software Architecture Evaluation Plan is provided that can be easily customized by a DoD program office for use in its own RFP and contracts.

A Software Architecture for Dependable and Evolvable Industrial Computing Systems

Software Architecture for Dependable and Evolvable Industrial Computing Systems, A

A Workshop on Architecture Competence

This report summarizes a workshop on architecture competence that was held at the SEI in June 2008, where practitioners discussed key issues in assessing architecture competence in organizations.

ADA Performance Benchmarks on the Motorola MC68020: Summary and Results

This report documents the results obtained from running Ada performance benchmarks on a DEC VAXELN MicroVAX II using the DEC VAXELN Ada compiler.

ADA Validation Tests for Rate Monotonic Scheduling Algorithm

This report presents a set of tests for checking whether an ADA runtime system properly supports certain rate monotonic scheduling algorithms, specifically, the basic inheritance and priority ceiling protocols.

ADA for Embedded Systems: Issues and Questions

This report addresses issues and questions related to the use of ADA for embedded systems applications; it contains some preliminary recommendations for compilation system implementors, application developers, program managers, and ADA policy makers. The issues and questions provide the context for the Real-Time Embedded Systems Testbed (REST) Project at the SEI, where staff members are investigating software development and performance issues for real-time embedded systems.

ASSIP Study of Real-Time Safety-Critical Embedded Software-Intensive System Engineering Practices

ASSIP Study of Real-Time Safety-Critical Embedded Software-Intensive System Engineering Practices

ATAM and Collaboration at the Enterprise Level

Presented: April 2006

ATAM: Method for Architecture Evaluation

ATAM: Method for Architecture Evaluation

Achieving Product Qualities Through Software Architecture Practices

Presented: March 2004

Achieving Usability Through Software Architecture

Achieving Usability Through Software Architecture

Active Reviews for Intermediate Designs

Active Reviews for Intermediate Designs

Aligning Business Models, Business Architectures, and IT Architectures

Aligning Business Models, Business Architectures, and IT Architectures

Aligning Organizational Activities with Architectural Design

A presentation with audio

An Approach to Software Architecture Analysis for Evolution and Reusability

An Approach to Software Architecture Analysis for Evolution and Reusability

An Architectural Analysis Case Study:Internet Information Systems

An Architectural Analysis Case Study:Internet Information Systems

An Architectural Approach to Software Cost Modeling

An Architectural Approach to Software Cost Modeling

An Architecture Journey

SATURN 2007 keynote by Jeromy Carrière

An Evaluation Theory Perspective of the Architecture Tradeoff Analysis Method (ATAM)

An Evaluation Theory Perspective of the Architecture Tradeoff Analysis Method (ATAM)

An Experience Report on Using UML 2.0 to Document Software Architectures

Presented: April 2005

An Introduction to Software Architecture

An Introduction to Software Architecture

Analysis of Input/Output Paradigms for Real-Time Systems, An

This paper illustrates how these principles can be applied to input/output interfaces  to predict the timing behavior of various design alternatives.

Analyzing Enterprise JavaBeans Systems Using Quality Attribute Design Primitives

Analyzing Enterprise JavaBeans Systems Using Quality Attribute Design Primitives

Analyzing Quality Attributes

Analyzing Quality Attributes

Analyzing the Reuse Potential of Migrating Legacy Components to a Service-Oriented Architecture

Analyzing the Reuse Potential of Migrating Legacy Components to a Service-Oriented Architecture

Annual Technical Report for ADA Embedded Systems Testbed Project

This technical report provides an overview of the results produced in the first year of the ADA Embedded Systems Testbed Project (through September 30, 1987).

Applicability of General Scenarios to the Architecture Tradeoff Analysis Method

Applicability of General Scenarios to the Architecture Tradeoff Analysis Method

Application of the Architecture-Based Design Method to the Electronic House, An

An Application of the Architecture-Based Design Method to the Electronic House

Application-Level Implementation of the Sporadic Server, An

The purpose of this paper is to introduce a sporadic server algorithm that can be implemented as an application-level task, and that can be used when no runtime or operating system level implementation of the sporadic server is available.

Applying SEI Architecture Tradeoff Analysis Method (ATAM) as Part of Formal Software Architecture Review

presented as part of SATURN 2008, May 2008

ArchE – An Architecture Design Assistant

presented as part of the SEI Software Architecture Workshop for Educators, August 2007

ArchE – An Architecture Design Assistant

The Fourth SEI Software Architecture Workshop for Educators was held at the Software Engineering Institute in Pittsburgh, PA on July 31- August 2, 2007.

ArchE—the Architecture Expert

ArchE—the Architecture Expert

Architecting Security In

Presented: May 2007

Architectural Design of an Industrial AGV Transportation System with a Multiagent System Approach

Presented: April 2006

Architectural Evaluation of Collaborative Agent-Based Systems

Architectural Evaluation of Collaborative Agent-Based Systems

Architectural Refinement for the Design of Survivable Systems

Architectural Refinement for the Design of Survivable Systems

Architectural Tactics

Architectural Tactics

Architecture Analysis Boeing’s Experiences using the SEI ATAM and QAW Processes

Presented: April 2006

Architecture Analysis Overview and Observations

Architecture Analysis Overview and Observations by Don O'Connell, Software/Systems Architect, The Boeing Company. Presented at Saturn 2006.

Architecture Business Cycle Revisited: A Business Goals Taxonomy to Support Architecture Design and Analysis, The

The Architecture Business Cycle Revisited: A Business Goals Taxonomy to Support Architecture Design and Analysis

Architecture Centric Design Method

Presented: April 2006

Architecture Competence: What Is It? How Do We Measure It?

Architecture Competence: What Is It? How Do We Measure It?

Architecture Competency

SATURN 2006 Working Session.
This summary is meant to convey preliminary ideas for the purpose of getting feedback. It does not necessarily represent the consensus of the members of the session.

Architecture Competency SATURN 2006

Presented: April 2006

Architecture Curve, New Formatted SEI ATAM Report Shaped in a Single Graph

presented as part of SATURN 2008, May 2008

Architecture Empowerment - A Quality Attribute of Software Architecture Realms to Build Empowered Organizations

presented as part of SATURN 2008, May 2008

Architecture Evolution Working Session

presentation made at the Software Architecture Technology User Network (SATURN) Workshop, April 25-26, 2006, Pittsburgh, PA

Architecture Evolution Working Session SATURN 2006

Presented: April 2006

Architecture From a Manager’s Perspective

presented at SATURN 2008, April-May 2008

Architecture Mechanisms

Architecture Mechanisms

Architecture Reconstruction Guidelines

Architecture Reconstruction Guidelines

Architecture Reconstruction Guidelines, Third Edition

Architecture Reconstruction Guidelines, Third Edition

Architecture Reconstruction of J2EE Applications: Generating Views from the Module Viewtype

Architecture Reconstruction of J2EE Applications: Generating Views from the Module Viewtype

Architecture Tradeoff Analyses of C4ISR Products

Architecture Tradeoff Analyses of C4ISR Products

Architecture and Design

guest lecture for COMP 180: Software Engineering, Tufts University, Fall 2006

Architecture from a Manager’s Perspective (SATURN 2008)

presented at SATURN 2008, April-May 2008

Architecture-Based Development

Architecture-Based Development

Architecture-Centric Approach to Predicting Real-Time Performance

The information sheet describes the SEI architecture-centric toolkit for prediciting end-to-end latency and other qualities of real-time systems.

Architecture-Centric Approach to Predicting Security

This information sheet describes an approach to security analysis that allows software validation by identifying data elements to be protected, components that should be allowed access to those elements, and appropriate communication channels.

Architecture-Centric Approach to Predicting System Reliability

This information sheet describes the SEI architecture-centric, model-based toolkit for more accurate prediction of system reliability.

Architecture-Centric Approach to Predicting System Resource Consumption

This information sheet describes the SEI architecture-centric, model-based toolkit for predicting behavior in bandwidth usage, CPU time, and power consumption.

Architecture-Centric Software Project Management: A Practical Guide

The book addresses each cornerstone of effective project management -- planning, organizing, implementing, and measuring.

Architectures for Adaptive Mobile Systems

Architectures for Adaptive Mobile Systems

Are Software Architects Like Building Architects?

Are Software Architects Like Building Architects?

Assessing Architectural Complexity

Assessing Architectural Complexity

Assessment of CORBA and POSIX Designs for FAA En Route Resectorization

Modernizing the En Route system presents major acquisition issues to the Federal Aviation Administration (FAA). At the present time, efforts are underway to upgrade the En Route system, primarily focusing on the host computer system. This report addresses the use of different technologies and an architectural tradeoff approach on a typical En Route system problem. We were requested to consider the problem of resectorization, i.e., the combination and decombination of sectors (and fix posting areas) during operation of the En Route center. Such capabilities may become desirable for an implementation of free flight. Two technologies have been applied to develop solutions to this problem, namely Common Object Request Broker Architecture (CORBA) and POSIX.21 (Portable Operating System Interface Standard). The former is based on an object-oriented model, while the latter is based on a message-passing model.

Assurance for Software-Intensive Systems

Assurance for Software-Intensive Systems

Attribute-Based Architectural Styles

Attribute-Based Architectural Styles

Attribute-Based Architectural Styles

Attribute-Based Architectural Styles

Attribute-Driven Design (ADD), Version 2.0

Attribute-Driven Design (ADD), Version 2.0

Automated Requirements Processing Overview

presentation made at the 2007 SATURN Workshop

Autonomic Computing

Autonomic Computing

Best Practices in Software Architecture

presentation given by Paul Clements, July 26, 2006

Best Practices in Software Architecture

Best Practices in Software Architecture, by
Paul Clements

Best of Three Worlds: Combining QAW, MDRE, and GA, The

Presented: April 2006

Building Secure Systems Using Model-Based Engineering and Architectural Models

Building Secure Systems Using Model-Based Engineering and Architectural Models

Building a Software Architecture Community

SATURN 2006 Working Session. This summary is meant to convey preliminary ideas for the purpose of getting feedback. It does not necessarily
represent the consensus of the members of the session.

Building a Software Architecture Community (SATURN 2006)

Building a Software Architecture Community (SATURN 2006)

Case Study in Assessing the Maintainability of Large, Software-Intensive Systems, A

presented at the International Symposium and Workshop on Systems Engineering of Computer Based Systems, March 1995, Tucson

This paper presents a case study in assessing the maintainability of a large, software intensive system. The techniques we used are described, and their strengths and weaknesses discussed.

Categorizing Business Goals for Software Architectures

Categorizing Business Goals for Software Architectures

Challenges and Observations of Applying the SEI ATAM to a Software Testing Automation Solution

presented as part of SATURN 2008, May 2008

Characteristics of Higher Level Languages for Software Architecture

Characteristics of Higher Level Languages for Software Architecture

Classifying Architectural Elements as a Foundation for Mechanism Matching

Classifying Architectural Elements as a Foundation for Mechanism Matching

Coming Attractions in Software Architecture

Coming Attractions in Software Architecture

Common ATAM Errors

Presented: May 2007

Comparative Evaluations of Four Specification Methods for Real-Time Systems

The primary audience of this report is the software development practitioner involved in the method selection or adoption process. The paper attempts to provide proper context to assist the practitioner in making appropriate method adoption decisions. Secondarily, the results of the paper also should be of to tool vendors, method developers, and program managers.

Comparing the SEI's Views and Beyond Approach for Documenting Software Architectures with ANSI-IEEE 1471-2000

Comparing the SEI's Views and Beyond Approach for Documenting Software Architectures with ANSI-IEEE 1471-2000

Components of Software Architecture Design and Analysis, The

The Components of Software Architecture Design and Analysis

Conceptual Framework for System Fault Tolerance, A

A major problem in transitioning fault tolerance practices to the practitioner community is a lack of a common view of what fault tolerance is, and how it can help in the design of reliable computer systems. This document takes a step towards making fault tolerance more understandable by proposing a conceptual framework. The framework provides a consistent vocabulary for fault tolerance concepts, discusses how systems fail, describes commonly used mechanisms for making systems fault tolerant, and provides some rules for developing fault tolerant systems.

Cost-Benefit Analysis Method

Cost-Benefit Analysis Method

Creating and Using Software Architecture Documentation Using Web-Based Tool Support

Creating and Using Software Architecture Documentation Using Web-Based Tool Support

Criteria for Constructing and Using an ADA Embedded System Testbed

The purpose of this report is to list some of the criteria used in five aspects of the project: the hardware configuration, the software configuration, the real-time application, the ADA real-time experiments, and the benchmarking and instrumentation techniques. Each criterion will include a rationale. Each of the criteria listed in this report will be categorized as either essential, highly desirable, or desirable.

Current SAT Work in Architecture Evolution

Presented: April 2008

Current SEI SAT Initiative Technology Investigations

presented as part of SATURN 2008, May 2008

Data Model as an Architectural View

The data model for a given system can be seen as an architectural view; for example, a view of a database structure that shows data entities and their relationships. Among other practical purposes, the data model would serve as the blueprint for the physical database, help implementation of the data access layer of the system, and have a strong impact on performance and modifiability.

Debugging Software Architectures

Presented: April 2008

Defining Composite Critical Scenarios for the Development of Large-Scale System Architecture Using an SEI ADD-Based Framework

This presentation will discuss how SEI Attribute-Driven Design (ADD) was employed to develop a framework that was employed as a basis to develop the software architecture of a complex large-scale control system in a multinational organization.

Defining the Terms Architecture, Design, and Implementation

Defining the Terms Architecture, Design, and Implementation

Definition and Evaluation of Geographic Information System Architecture Using ADD and ATAM

Presented: April 2006

Definition and Evaluation of Geographic Information System Architecture Using ADD and ATAM (SATURN 2006)

Presented: April 2006

Dependability Cases

Dependability Cases

Dependability Modeling with the Architecture Analysis & Design Language (AADL)

Dependability Modeling with the Architecture Analysis & Design Language (AADL)

Deriving Architectural Tactics: A Step Toward Methodical Architectural Design

Deriving Architectural Tactics: A Step Toward Methodical Architectural Design

Design Specifications for ADAptive Real-Time Systems

The design specification method described in this report treats a software architecture as a set of run-time entities, including tasks and external input/output elements, which interact either via messages or shared data structures. Tasks have a single thread of execution and represent program units that may be executed concurrently. External input elements produce input requests which in turn trigger a set of low level activities to be executed by tasks. External output elements consume results which are produced by tasks. The specification method discussed here facilitates the description of the dynamic structure of run-time entities, the synchronization and communication between these entities, and their resource consumption and production properties (which include timing and sizing).

Design and Analysis Principles for Software Architecture

Presented: January 2004

Diagrams and Languages for Model-Based Software Engineering of Embedded Systems UML and AADL

Diagrams and Languages for Model-Based Software Engineering of Embedded Systems UML and AADL

Discovering Architectures from Running Systems: Lessons Learned

Discovering Architectures from Running Systems: Lessons Learned

Distributed Real-Time System Design: Theoretical Concepts and Applications

Distributed real-time system design raises new theoretical issues and application challenges, beyond those of centralized systems. Rate monotonic scheduling (RMS) theory has been successfully applied in the scheduling of centralized systems. RMS and its generalizations have been adopted by national high technology projects such as the Space Station and has recently been supported by major open standards such as the IEEE Futurebus+ and POSIX.4. In this paper, we describe the use of generalized rate monotonic scheduling theory for the design and analysis of a distributed real-time system. We review the recent extensions of the theory to distributed system scheduling, examine the architectural requirements for use of the theory, and finally provide an application example.

Distributed System Design Using Generalized Rate Monotonic Theory

In this paper, we describe the use of generalized rate monotonic scheduling theory for the design and analysis of a distributed real-time system. We review the theory, examine the architectural requirements for the use of the theory, and finally provide an application example.

DoD Architecture Framework and Software Architecture Workshop Report

DoD Architecture Framework and Software Architecture Workshop Report

DoD Experience with the C4ISR Architecture Framework

DoD Experience with the C4ISR Architecture Framework

Documenting Component and Connector Views with UML 2.0

Documenting Component and Connector Views with UML 2.0

Documenting Software Architecture: Documenting Behavior

Documenting Software Architecture: Documenting Behavior

Documenting Software Architecture: Documenting Interfaces

Documenting Software Architecture: Documenting Interfaces

Documenting Software Architectures

Documenting Software Architectures

Documenting Software Architectures Podcast

Paul Clements talks about best practices for communicating (documenting) software architectures and summarizes key points from the book Documenting Software Architectures: Views and Beyond and the related two-day course, Documenting Software Architectures.

Documenting Software Architectures in an Agile World

Documenting Software Architectures in an Agile World

Documenting Software Architectures: Organization of Documentation Package

Documenting Software Architectures: Organization of Documentation Package

Documenting Software Architectures: Views and Beyond

The SEI has produced an approach for documenting software architectures known as the "Views and Beyond" approach. It allows software architects to produce only the documentation that has a demonstrated community of consumers, while producing high-quality documentation that will serve the project throughout its entire lifecycle.

Duties, Skills, and Knowledge of Software Architects, The

The Duties, Skills, and Knowledge of Software Architects

Economic Modeling of Software Architectures

Economic Modeling of Software Architectures

Elements of a Usability Reasoning Framework

Elements of a Usability Reasoning Framework

Embedded Systems Architecture Analysis Using SAE AADL

Embedded Systems Architecture Analysis Using SAE AADL

Engineering Performance-Critical Systems: meeting and exceeding performance, dependability, and interoperability goals

Engineering Performance-Critical Systems: meeting and exceeding performance, dependability, and interoperability goals

Evaluating Distributed Systems Architectures for Fault-Tolerant Applications

presented as part of SATURN 2008, May 2008

Evaluating Service-Oriented Architectures

The emergence of service-oriented architecture (SOA) as an approach for integrating applications that expose services presents many new challenges to organizations resulting in significant risks to their business. Particularly important among those risks are failures to effectively address quality attribute requirements such as performance, availability, security, and modifiability. Because the risk and impact of SOA are distributed and pervasive across applications, it is critical to perform an architecture evaluation early in the software life cycle. This report contains technical information about SOA design considerations and tradeoffs that can help the architecture evaluator to identify and mitigate risks in a timely and effective manner. The report provides an overview of SOA, outlines key architecture approaches and their effect on quality attributes, establishes an organized collection of design-related questions that an architecture evaluator may use to analyze the ability of the architecture to meet quality requirements, and provides a brief sample evaluation.

Evaluating a Service-Oriented Architecture

Presented: May 2007

Evolution of Quality Attribute Workshops as an Architecture-Evaluation Technique, The

The Evolution of Quality Attribute Workshops as an Architecture-Evaluation Technique

Evolving Persistent Objects in a Distributed Environment

This paper considers a class of objects, called incrementally mutable objects, that are intermediate between mutable and immutable objects. Intuitively, the only permitted modifications to an incrementally mutable object are those that add new information to the object while preserving existing information. Changes to incrementally mutable objects do not require central synchronization. When a network becomes partitioned, the same incrementally mutable object can be safely modified in each subnetwork. A mutable object can be modeled by a set of immutable objects that represent each value of the object over time and an incrementally mutable object that relates each immutable object to its successor. Multiple successors are permitted to represent parallel changes.

Experience Using the Web-Based Tool Wiki for Architecture Documentation

Experience Using the Web-Based Tool Wiki for Architecture Documentation

Experience with a Course on Architectures for Software Systems Part I: Course Description

Experience with a Course on Architectures for Software Systems Part I: Course Description

Experience with a Course on Architectures for Software Systems, Part II: Educational Materials

Experience with a Course on Architectures for Software Systems, Part II: Educational Materials

Experiences Porting the Distributed ADA Real-Time Kernel

The Distributed ADA Real-Time Kernel (DARK) is a mechanism for supporting the execution of distributed real-time ADA applications in embedded computer systems. It provides a solution to scheduling and distributing tasks without modifying the ADA language or vendor-supplied run time systems. An important test of the utility of the Kernel is whether or not it can be ported to different hardware architectures and still function effectively. As part of an independent research and development project, Boeing Military Airplanes and The Wichita State University became co-acceptors of a copy of DARK for the purpose of demonstrating a port to a 68000-based distributed architecture. This technical report describes the experiences in accomplishing the port.

Experiences in Architecture Reconstruction at Nokia

Experiences in Architecture Reconstruction at Nokia

Exploring Enterprise, System of Systems, and System and Software Architectures

In this webinar, we  present our findings from a U.S. Army workshop on architecture that was held at the SEI in September of 2008, under the auspices of the Army Strategic Software Improvement Program (ASSIP).

Fault Tolerant Systems Practitioner's Workshop June 10-11, 1991

On June 10-11, 1991, a Fault Tolerant Systems Practitioner's Workshop was held at the Software Engineering Institute. The purpose of the workshop was to attempt to identify how fault tolerance is being applied today, why fault tolerance is under used, and what can be done to bring fault tolerant practices into wider use. Attendance at the workshop was limited to a small number of practitioners who had successfully applied fault tolerance in a systems context. This report summarizes the proceedings of the workshop which included a discussion of barriers to the deployment of fault tolerant systems, a summary of the state of the practice, and a discussion of the technology needs of fault tolerance. The report concludes with a discussion of ways the Software Engineering Institute may be able to help bring fault tolerant practices into wider use.

Features of Architecture Description Languages

Features of Architecture Description Languages

Flow Latency Analysis with the Architecture Analysis and Design Language (AADL)

Flow Latency Analysis with the Architecture Analysis and Design Language (AADL)

Formal Methods in Describing Architectures

Formal Methods in Describing Architectures

Formal Specification and Verification of Concurrent Programs

This module introduces formal specification of concurrent software and verification of the consistency between concurrent programs and their specifications. First, what one might want to be able to prove about a concurrent program is discussed.

Formal Verification of Programs

This module introduces formal verification of programs. It deals primarily with proofs of sequential programs, but also with consistency proofs for data types and deduction of particular behaviors of programs from their specifications. Two approaches are considered: verification after implementation that a program is consistent with its specification, and parallel development of a program and its specification. An assessment of formal verification is provided.

Framework Document: Model-Based Verification Pilot Study

This Pilot Study Framework document describes the processes, activities, artifacts, and deliverables associated with an Engineering Practice Investigation of Model-Based Verification (MBV).

From Domain Models to Architectures

presentation given at the Workshop on Software Architecture, USC Center for Software Engineering, Los Angeles, 1994

From Subroutines to Subsystems: Component-Based Software Development

From Subroutines to Subsystems: Component-Based Software Development

Functional Performance Specification for an External Computer System Simulator

This document defines the functional and performance requirements for the inertial navigation system simulator that interfaces with the external computer system (ECS) simulator.

Functional Performance Specification for an Inertial Navigation System

This document defines the functional and performance requirements for the inertial navigation system simulator that interfaces with the external computer system (ECS) simulator. Both the INS simulator and the ECS simulator are being developed in ADA by the Real-Time Embedded Systems Testbed Project at the Software Engineering Institute. The INS simulator is similar to a real-world INS, but has reduced functionality. This document provides specifications for the major functions of the INS simulator.

Future Directions of the Software Architecture Technology Initiative

Presented: April 2006

Future Trends of Software Technology and Applications: Software Architecture

Presented: January 2006

Gadfly: An Approach to Architectural-Level System Comprehension, The

white paper presented at the Fourth IEEE Workshop on Program Comprehension, Berlin, March 1996

Generic Avionics Software Specification

This report informally specifies the general functions, data interactions, and timing constraints for an avionics mission control computer system typical of those found in some existing U.S. Navy/Marine Corps aircraft.

Global Software Development Working Session

SATURN 2006 Working Session.
This summary is meant to convey preliminary ideas for
the purpose of getting feedback. It does not necessarily
represent the consensus of the members of the session.

Global Software Development Working Session (SATURN 2006)

Presented: April 2006

Governance Issues for a Service-Oriented Architecture

Governance Issues for a Service-Oriented Architecture

Hartstone Benchmark Results and Analysis

Hartstone Benchmark Results and Analysis

Hartstone: Synthetic Benchmark Requirements for Hard Real-Time Applications

The purpose of this paper is to define the operational concept for a series of benchmark requirements to be used to test the ability of a system to handle hard real-time applications. Implementations of such benchmarks would be useful in evaluating scheduling algorithms, protocols, and design paradigms, as well as processors, languages, compilers, and operating systems. Several ADA programs are under development to test standard versions of the benchmark requirements and will be released into the public domain.

How the QAW Helped our Enterprise Architecture Effort

presentation from the 2007 SATURN Workshop

Identifying and Documenting Primary Concerns in Industrial Software Systems

presented as part of SATURN 2008, May 2008

Illuminating the Fundamental Contributors to Software Architecture Quality

Illuminating the Fundamental Contributors to Software Architecture Quality

Impact of Army Architecture Evaluations

This report details the results of a study of 12 U.S. Army programs that used the ATAM or QAW as part of the Army Strategic Software Improvement Program (ASSIP) effort.

Implementing Priority Inheritance Algorithms in an ADA Runtime System

This paper presents a high-level design-in the form of necessary data structures, mechanisms, and algorithms-for implementing the basic priority inheritance and priority ceiling protocols in an ADA runtime system.

Implementing Sporadic Servers in ADA

The purpose of this paper is to present the data structures and algorithms for implementing sporadic servers in real-time systems programmed in ADA.

Improving Predictability in Embedded Real-Time Systems

Improving Predictability in Embedded Real-Time Systems

Improving Software Architecture Competence

Improving Software Architecture Competence by Paul Clements, International Association of Software Architects (IASA), March 2007.

Improving Software Architecture Competence

Presented: March 2007

Inexpensive ATAM-Peer Review Detects and Fixes Architecture Problems Early

Presented: April 2008

Integrated City Operation Center: An Architecture Case Study with ADD & Data Flow Analysis

presentation made at the 2007 SATURN Workshop

Integrating Analysis and Design Methods for the Software Life Cycle

Integrating Analysis and Design Methods for the Software Life Cycle

Integrating Architecture Methods: The Case of Extreme Programming

Integrating Architecture Methods: The Case of Extreme Programming

Integrating Architecture Methods: The Case of the ATAM and the CBAM

Integrating Architecture Methods: The Case of the ATAM and the CBAM

Integrating Architecture Methods: The Case of the QAW and the ADD Method

Integrating Architecture Methods: The Case of the QAW and the ADD Method

Integrating Architecture Methods: The Case of the Rational Unified Process

Integrating Architecture Methods: The Case of the Rational Unified Process

Integrating Quality-attribute Reasoning Frameworks in the ArchE Design Assistant

Integrating Quality-attribute Reasoning Frameworks in the ArchE Design Assistant

Integrating Software-Architecture-Centric Methods into Extreme Programming (XP)

Integrating Software-Architecture-Centric Methods into Extreme Programming (XP)

Integrating Software-Architecture-Centric Methods into the Rational Unified Process

Integrating Software-Architecture-Centric Methods into the Rational Unified Process

Integrating the Architecture Tradeoff Analysis Method (ATAM) with the Cost Benefit Analysis Method (CBAM)

Integrating the Architecture Tradeoff Analysis Method (ATAM) with the Cost Benefit Analysis Method (CBAM)

Integrating the Quality Attribute Workshop (QAW) and the Attribute-Driven Design (ADD) Method

Integrating the Quality Attribute Workshop (QAW) and the Attribute-Driven Design (ADD) Method

Interactions Among Techniques Addressing Quality Attributes

Interactions Among Techniques Addressing Quality Attributes

Introducing Scenario-based Architecture Reviews

presentation made at the 2007 SATURN Workshop

Introduction to Software Engineering Practices Using Model-Based Verification, An

This is an introductory report on the use of model-based verification techniques within software development and upgrade practices.

Introduction to Software Verification and Validation

This curriculum module provides an overview needed to understand in-depth curriculum modules in the verification and validation area.

Issues in Real-Time Data Management

This report explores issues related to the use of database management technology in support of real-time systems programming. It describes the potential benefits of database support for real-time systems, and it describes the state of the art in database technologies relevant to real-time. The report concludes that more research and development will be needed before the benefits of database management can be applied to real-time system development.

Leadership and Management in Software Architecture Leadership and Management in Software Architecture

Leadership and Management in Software Architecture Leadership and Management in Software Architecture

Learn to use the SAE AADL Standard Model-Based Engineering with SAE AADL

Learn to use the SAE AADL Standard Model-Based Engineering with SAE AADL

Lessons Learned about Software Architecture

Lessons Learned about Software Architecture

Lessons Learned from Deployment and Production Use of Architects’ Workbench - An Architectural Thinking and Modeling Tool

Presented: April 2008

Let’s Teach Architecting High Quality Software

Presented: April 2006

Light-Weight Architecture Trade Off Process Based on ATAM, A

Presented: May 2007

Making Architecture Design Decisions: An Economic Approach

Making Architecture Design Decisions: An Economic Approach

Managing Risks in Modernizing Legacy Systems

Managing Risks in Modernizing Legacy Systems

Method Framework for Engineering System Architectures, The

To be successful, every system needs a good architecture and that requires the use of a good architecture engineering method. However, systems vary greatly in size, complexity, criticality, domain, operational dependence on other systems, the technology used and its diversity, requirements volatility, required quality characteristics and attributes, and volatility of technology and component parts.

Methodical Design of Software Architecture Using an Architecture Design Assistant (ArchE)

Presented: April 2005

Mitigating the Risk of Using Service-Oriented Architectures

Mitigating the Risk of Using Service-Oriented Architectures

Mode Change Protocols for Priority-Driven Preemptive Scheduling

This paper discusses a protocol for systematically accomplishing mode change in the context of a priority-driven preemptive scheduling environment.

Model-Based Verification: A Technology for Dependable Upgrade

This is a preliminary report on the technological foundations of model-based verification for engineering software system upgrades.

Model-Based Verification: Abstraction Guidelines

Model-Based Verification: Abstraction Guidelines

Model-Based Verification: An Engineering Practice

Model-Based Verification: An Engineering Practice

Model-Based Verification: Analysis Guidelines

This technical note provides guidance for the analysis activity that occurs during the interpretation of results produced by model-checking tools.

Model-Based Verification: Claim Creation Guidelines

Model Based Verification (MBV) is a systematic approach to finding defects (errors) in software requirements, designs, or code. MBV involves creating essential models of system behavior and analyzing these models against formal representations of expected properties, known as claims. Claim generation has been identified as a particularly complex activity within model-based verification. This technical note describes a pattern-based approach to facilitate claim generation. The report includes a list of directly usable patterns for the most frequent expected properties found in system specifications.

Model-Based Verification: Guidelines for Generating Expected Properties

Model-Based Verification: Guidelines for Generating Expected Properties

Model-Based Verification: Scope, Formalism, and Perspective Guidelines

The goal of model-based verification (MBV) is to reduce the number of defects. Like any other quality assurance (QA) technique, it is not equally efficient in every situation. It is critical to determine where and how to use MBV to achieve the largest impact in terms of the number and criticality of defects found with a reasonable amount of effort. This document provides guidance for defining the scope, formalism (approach and tools), and perspective for applying MBV. The critical (important or risky) aspects of the system and its development, including both programmatic and technical issues, drive these choices and form the basis for these guidelines.

Modeling of System Families

Modeling of System Families

Modeling the Space Shuttle Liquid Hydrogen Subsystem

Modeling the Space Shuttle Liquid Hydrogen Subsystem

Models for Evaluating and Improving Architecture Competence

Models for Evaluating and Improving Architecture Competence

Modifiability Tactics

Modifiability Tactics

Negative Impacts of Ignoring Stakeholder Quality Attributes

Presented: May 2007

Neglected Aspects of Software Architecture

SATURN 2007 presentation in which Todd Kaiser delivers the message that software architects sometimes ignore non-technical aspects of software architecture and that results in collateral damage.

OOD Paradigm for Flight Simulators (2nd Edition), An

This report presents a paradigm for object-oriented implementation of flight simulators. It is a result of work on the ADA Simulator Validation Program (ASV) carried out by members of the technical staff at the SEI.

On ADLs and Tool Support for Documenting View-Based Architectural Descriptions

presented as part of SATURN 2008, May 2008

On Software Architecture, Agility, Cost and Value

SATURN 2008 keynote by Philippe Kruchten, Professor of Software Engineering, Department of Electrical and Computer Engineering, University of British Columbia, Vancouver

On System Scalability

On System Scalability

Performance and Reliability Enhancement of the Durra Runtime Environment

Performance and Reliability Enhancement of the Durra Runtime Environment

Perils and Joys of Reconstructing Architectures, The

The Perils and Joys of Reconstructing Architectures

Perspective on the State of Research in Fault-Tolerant Systems, A

As computers take on a greater role in society, their dependability is becoming increasingly important. Given software's critical role in computing systems, reliable software has emerged as crucial to achieving a dependable infrastructure. Using a system perspective that recognizes the prominence of software, we characterize the current state of fault-tolerance research as it contributes to the dependability of computer systems and we conjecture on future directions for this research area.

Place of Architecture in a Crowdsourced World, The

The Place of Architecture in a Crowdsourced World

Playing Detective: Reconstructing Software Architecture from Available Evidence

Playing Detective: Reconstructing Software Architecture from Available Evidence

Predictable, Model-Based Engineering for Embedded Systems

Predictable, Model-Based Engineering for Embedded Systems

Preliminary Design of ArchE: A Software Architecture Design Assistant

Preliminary Design of ArchE: A Software Architecture Design Assistant

Principles for Evaluating the Quality Attributes of a Software Architecture

Principles for Evaluating the Quality Attributes of a Software Architecture

Principles of Architecture Design and Evaluation

Presented: January 2004

Priority Ceiling Protocol: A Method for Minimizing the Blocking of High-Priority ADA Tasks, The

The priority ceiling protocol is a new technique that addresses the priority inversion problem, i.e., the possibility that a high-priority task can be delayed by a low-priority task. Under the priority ceiling protocol, a high priority task can be blocked at most once by a lower priority task. This paper defines how to apply the protocol to ADA. In particular, restrictions on the use of task priorities in ADA are defined as well as restrictions on the use of ADA tasking constructs. An extensive example illustrating the behavior guaranteed by the protocol is given.

Proceedings of the First Software Architecture Technology User Network (SATURN) Workshop

Proceedings of the First Software Architecture Technology User Network (SATURN) Workshop

Proceedings of the Real-Time Systems Engineering Workshop

This report presents the results of a workshop on the topic of real-time systems engineering. The workshop was held as part of the SEI Symposium in Washington, DC, during September 2000. The objective of the workshop was to identify key issues and obtain feedback from attendees concerning real-time systems engineering. Two broad keynote presentations were presented, followed by topical presentations concerning predictability, fault tolerance, and interoperability. This report summarizes the workshop in terms of foundation, management, and technical topics, and it contains a discussion related to developing a community of interest for real-time systems engineering.

Proceedings of the Second Software Architecture Technology User Network (SATURN) Workshop

Proceedings of the Second Software Architecture Technology User Network (SATURN) Workshop

Product Line Architecture for Army Aviation Diagnostics and Maintenance: Views and Evolution, A

Presented: May 2007

Prototype Real-Time Monitor: ADA Code

This report documents the ADA code of the prototype real-time monitor (RTM).

Prototype Real-Time Monitor: Design

The requirements imposed by flight simulators and good software engineering practice on Ada systems force software engineers to seek new solutions to the problem of monitoring executing software. This report examines some of these requirements and, based on these requirements, defines a subset for implementation as a prototype real-time monitor (RTM).

Prototype Real-Time Monitor: Executive Summary

This report summarizes the history, goals, and conclusions of the prototype real-time monitor development effort.

Prototype Real-Time Monitor: Requirements

The requirements imposed by flight simulators and good software engineering practice on Ada systems force software engineers to seek new solutions to the problem of monitoring executing software. This report examines some of these requirements and, based on these requirements, defines a subset for implementation as a prototype real-time monitor (RTM).

Prototype Real-Time Monitor: User's Manual

Prototype Real-Time Monitor: User's Manual

Putting Software Architecture in Its Place - Fitting Software Architecture into the Enterprise Technology Landscape

Presented: April 2008

Quality Attribute Design Primitives

Quality Attribute Design Primitives

Quality Attribute Workshop

Quality Attribute Workshop

Quality Attribute Workshop Participants Handbook

Quality Attribute Workshop Participants Handbook

Quality Attribute Workshops

Quality Attribute Workshops

Quality Attribute Workshops

Quality Attribute Workshops

Quality Attribute Workshops (QAWs), Third Edition

Quality Attribute Workshops (QAWs), Third Edition

Quality Attribute Workshops, 2nd Edition

Quality Attribute Workshops, 2nd Edition

Quality Attributes

Quality Attributes

Quality Attributes and Requirements Traceability

Presented: April 2008

Quality Attributes and Service-Oriented Architectures

Quality Attributes and Service-Oriented Architectures

Quality-Attribute-Based Economic Valuation of Architectural Patterns

Quality-Attribute-Based Economic Valuation of Architectural Patterns

Quantifying the Value of Architecture Design Decisions: Lessons from the Field

Quantifying the Value of Architecture Design Decisions: Lessons from the Field

Rate Monotonic Analysis for Real-Time Systems

In this report, we review important decisions in the development of RMA. Our experience indicates that technology transition considerations should be embedded in the process of technology development from the start, rather than as an afterthought.

Rate Monotonic Analysis for Real-Time Systems: Instructor's Guide

This educational materials package has been developed for instructors of software engineering and, more specifically, real-time systems. This package will help instructors teach rate monotonic analysis (RMA) to graduate and undergraduate software, computer, and electrical engineering students. The package can also be used to teach RMA to continuing education students. The presentation materials and exercises included have been used by Ruth Ravenel in both graduate and undergraduate courses.

Raytheon's Architecture Journey

Raytheon's Architecture Journey by Rolf Siegers, Chief Architect, Raytheon GEC. Presented at Saturn 2006.

Raytheon’s Architecture Journey

presentation given at the Software Architecture Technology User Network (SATURN) Workshop, April 25-26, 2006, Pittsburgh, PA

Real-Time Application Development with OSEK: A Review of the OSEK Standards

Real-Time Application Development with OSEK: A Review of the OSEK Standards

Real-Time Locking Protocol, A

When a database system is used in a real-time application, the concurrency control protocol must satisfy not only the consistency of shared data but also the timing constraints of the application. In this paper, we examine a priority-driven two-phase lock protocol called the read- or write-priority ceiling protocol. We show that this protocol is free of deadlock, and in addition a high-priority transaction can be blocked by lower priority transactions for at most the duration of a single embedded transaction. We then evaluate system performance experimentally.

Real-Time Scheduling Theory and ADA

Real-Time Scheduling Theory and ADA

Real-Time Scheduling Theory and ADA (1988)

The ADA tasking model was intended to facilitate the management of concurrency in a priority-driven scheduling environment. In this paper, we will review some important results of a priority-based scheduling theory, illustrate its applications with examples, discuss its implications for the ADA tasking model, and suggest workarounds that permit us to implement analytical scheduling algorithms within the existing framework of ADA.

Real-Time Software Engineering in ADA: Observations and Guidelines

Two important aspects of developing a real-time system are controlling devices and managing concurrency. In this report, we present several techniques for controlling devices with ADA and several ADA tasking paradigms for managing concurrency. The material presented in this report is taken from our experiences in developing a real-time embedded system in ADA, and we use examples from this system to illustrate the various methods we present. We begin by describing our experiences using ADA to control devices. Specifically, we identify issues related to accessing device registers and handling interrupts, and present techniques for dealing with such issues. We then recount our experiences using ADA to manage concurrency. Specifically, we present coding paradigms for implementing periodicity and constructing synchronization mechanisms. We illustrate analytical methods for determining the schedulability of a task set. We then discuss the effect of aperiodic processing requirements on the schedulability of a task set.

Real-Time Systems Engineering: Lessons Learned from Independent Technical Assessments

The Software Engineering Institute (SEI) has performed several Independent Technical Assessments (ITAs) on mission-critical/real-time systems for the Department of Defense and other agencies. This paper contains observations, recurring themes, trends, and lessons learned about systems development as derived from real-time/mission-critical programs that have been reviewed over the last three years. It is hoped that the observations contained in this paper will be of value to future program managers and help ensure their success.

Realizing and Refining Architectural Tactics: Availability

Tactics are fundamental elements of software architecture that an architect employs to meet a system's quality requirements. This report describes an updated set of tactics that enable the architect to build availability into a system.

Realizing the Business Value of IT: An Approach for Architecture Evaluation

presented as part of SATURN 2008, May 2008

Reasoning Frameworks

Reasoning Frameworks

Recommended Best Industrial Practice for Software Architecture Evaluation

Recommended Best Industrial Practice for Software Architecture Evaluation

Reconstructing the Architecture Model for a Sustainable Software System

presented as part of SATURN 2008, May 2008

Reducing Uncertainty In Architecture Plans

Presented: April 2008

Report on the Second International Workshop on Development and Evolution of Software Architectures for Product Families

Report on the Second International Workshop on Development and Evolution of Software Architectures for Product Families

Representing Software Architecture

Representing Software Architecture

Requirements for Integrating Software Architecture

presented at the 1998 Working Conference on Reverse Engineering, Honolulu HI, October 1998

Rethinking the Software Life Cycle

Rethinking the Software Life Cycle

Risk Themes Discovered Through Architecture Evaluations

Risk Themes Discovered Through Architecture Evaluations

Risk Themes from ATAM Data: Preliminary Results

Presented: May 2006

Risk Themes from ATAM Data: Preliminary Results (SATURN 2006)

Presented: April 2006

SACAM: The Software Architecture Comparison Analysis Method

SACAM: The Software Architecture Comparison Analysis Method

SAE Architecture Analysis and Design Language Fact Sheet

The SAE AADL is an international standard for predictable model-based engineering 
of real-time and embedded computer systems.

SATURN 2006 Working Session Out-brief Bridging System and Software Architecture

Presented: April 2006

SATURN 2006 Working Session: Strategic Risk Management for Architectures

Presented: April 2006

SATURN SEI Software Architecture Technology User Network

SATURN SEI Software Architecture Technology User Network

SATURN Session Summary: Use of the SEI ATAM in Practice

This presentation reviews the discussion that took place during Session 2: Architecture Evaluation: Experiences in Using the SEI ATAM, that was led by Felix Bachmann on April 30. It will also summarize observations made by both the presenters and attendees during that session.

SATURN: SEI Software Architecture Technology User Network

Presented: April 2005

SEI Architecture Analysis Techniques and When to Use Them

SEI Architecture Analysis Techniques and When to Use Them

SEI Architecture Practices Propel Successful Startup

SEI Architecture Practices Propel Successful Startup

SEI Architecture Techniques Complementary to the RUP

presentation made by Stuart Kerrigan and Richard van Schelven at the Third Annual SATURN Workshop, May 2007

SEI Software Architecture Workshop for Educators

presented as part of the SEI Software Architecture Workshop for Educators, August 2007

SEI Software Architecture Workshop for Educators (Presentation)

The Fourth SEI Software Architecture Workshop for Educators was held at the Software Engineering Institute in Pittsburgh, PA on July 31- August 2, 2007.

SEI Workshop on Software Architecture Representation, 16-17 January 2001

SEI Workshop on Software Architecture Representation, 16-17 January 2001

Safety-Critical Software: Status Report and Annotated Bibliography

Many systems are deemed safety-critical and these systems are increasingly dependent on software. Much has been written in the literature with respect to system and software safety. This report summarizes some of that literature and outlines the development of safety-critical software. Techniques for hazard identification and analysis are discussed. Further, techniques for the development of safety-critical software are mentioned. A partly annotated bibliography of literature concludes the report.

Scenario-Based Analysis of Software Architecture

Scenario-Based Analysis of Software Architecture

Scheduling Sporadic and Aperiodic Events in a Hard Real-Time System

A real-time system consists of both aperiodic and periodic tasks. Periodic tasks have regular arrival times and hard deadlines. Aperiodic tasks have irregular arrival times and either soft or hard deadlines. In this paper, we present a new algorithm, the Sporadic Server algorithm, that greatly improves response times for soft-deadline aperiodic tasks and can guarantee hard deadlines for both periodic and aperiodic tasks. The operation of the Sporadic Server algorithm, its performance, and schedulability analysis are discussed and compared with previous, published aperiodic service algorithms.

Second International Conference on COTS-Based Software Systems

Second International Conference on COTS-Based Software Systems

Simplex Architecture Performance and Cost

The Simplex Architecture facilitates the building of dependable and upgradable real-time systems. Before using the technology, potential users want to know more about the costs of adopting the Simplex paradigm compared to the benefits of using it. This paper examines Simplex performance and the costs associated with its use.

Simplex in a Hostile Communications Environment: The Coordinated Prototype

This report describes an approach to using Simplex to construct a COTS-based computer system capable of coordinated real-time motion control in a hostile communications environment.

Software Architectural Transformation

Software Architectural Transformation

Software Architecture Book Provides Practical Guidance about Documentation

Software Architecture Book Provides Practical Guidance about Documentation

Software Architecture Design with ArchE

The goal of our work in software architectures is to understand the mechanics behind creating good architectures and make this knowledge public.

In collaboration with the Bosch Research and Technology Center in Pittsburgh (Bosch-RTC) we addressed the question: Is it possible to codify architectural knowledge in a tool that provides the right information at the right time to the architect? The answer is ArchE.

Software Architecture Documentation in Practice: Documenting Architectural Layers

Software Architecture Documentation in Practice: Documenting Architectural Layers

Software Architecture Evaluation in the DoD Systems Acquisition Context

Software Architecture Evaluation in the DoD Systems Acquisition Context

Software Architecture Evaluation with ATAM in the DoD System Acquisition Context

Software Architecture Evaluation with ATAM in the DoD System Acquisition Context

Software Architecture Evaluation: A Key to System Success

Software Architecture Evaluation: A Key to System Success

Software Architecture Reconstruction: Practice Needs and Current Approaches

Software Architecture Reconstruction: Practice Needs and Current Approaches

Software Architecture Renaissance, The

The Software Architecture Renaissance

Software Architecture Technology Initiative

presentation made by Mark Klein at the Third Annual SATURN Workshop, May 2007

Software Architecture Technology Initiative (SATURN 2008)

presented at SATURN 2008, April-May 2008

Software Architecture Technology User Network (SATURN) 2005 Working Session Notes

Presented: April 2005

Software Architecture Technology User Network (SATURN) 2005 Wrap Up

Presented: April 2005

Software Architecture in DoD Acquisition: A Reference Standard for a Software Architecture Document

Software Architecture in DoD Acquisition: A Reference Standard for a Software Architecture Document

Software Architecture in DoD Acquisition: An Approach and Language for a Software Development Plan

Software Architecture in DoD Acquisition: An Approach and Language for a Software Development Plan

Software Architecture in Practice (2nd Edition)

This book provides a concise, all-in-one, easily accessible overview of software architecture. Anyone requiring a comprehensive overview of the field of software architecture will benefit from this book. Software Architecture in Practice, 2nd edition, provides a comprehensive overview of the field of software architecture in a single, easy-to-digest package.

Software Architecture in an Integrated Engineering Methodology

Presented: April 2008

Software Architecture: An Executive Overview

Software Architecture: An Executive Overview

Software Architecture: The Next Generation 

Software Architecture: The Next Generation 

Software Architectures for Shared Information Systems

Software Architectures for Shared Information Systems

Some Perspectives in Teaching Software Architecture

presented as part of SATURN 2008, May 2008

Specifying Functional and Timing Behavior for Real-Time Applications

We present a notation and a methodology for specifying the functional and timing behavior of real-time applications for a heterogeneous machine. In our methodology, we build upon well-defined, though isolated, pieces of previous work: Larch and Real-Time Logic. In our notation, we strive to keep separate the functional specification from the timing specification so that a task's functionality can be understood independent of its timing behavior. We show that while there is a clean separation of concerns between these two specifications, the semantics of both pieces as well as their combination are simple.

State of the Practice Report: Problems in the Practice of Performance Engineering

As systems have performance requirements, sometimes dominant and explicit, and other times subordinate and implicit. Despite the pervasiveness and importance of performance requirements, performance problems persist. To help us understand why, we sponsored a workshop in performance engineering and conducted some structured interviews with software contractors. This report summarizes our observations.

Steps in an Architecture Tradeoff Analysis Method: Quality Attribute Models and Analysis

Steps in an Architecture Tradeoff Analysis Method: Quality Attribute Models and Analysis

Strategic Architecting

Strategic Architecting

Structural Modeling: An Application Framework and Development Process for Flight Simulators

Structural Modeling: An Application Framework and Development Process for Flight Simulators

Study in the Use of CORBA in Real-Time Settings: Model Problems for the Manufacturing Domain, A

In this report, we describe the application of an off-the-shelf ORB to two real-time model problems.

Study of Practice Issues in Model-Based Verification Using the Symbolic Model Verifier (SMV), A

This report presents the results of a study on the practice issues involved in using the Symbolic Model Verifier (SMV) for model checking software systems.

Studying Software Architecture Through Design Spaces and Rules

Studying Software Architecture Through Design Spaces and Rules

Supporting the CANCEL Command Through Software Architecture

Supporting the CANCEL Command Through Software Architecture

Survey of Architecture Description Languages. A

white paper presented at the Eighth International Workshop on Software Specification and Design,
Germany, March 1996

Survey of Real-Time Performance Benchmarks for the Ada Programming Language, A

This survey provides a summary description of some of the major Ada benchmarks currently available and an evaluation of their applicability to the Real-Time Embedded Systems Testbed Project at the SEI. The benchmarks discussed are the University of Michigan benchmarks, the ACM Performance Issues Working Group (PIWG) benchmarks, and the prototype Ada Compiler Evaluation Capability (ACEC) of the Institute for Defense Analyses (IDA).

System of Systems Architecture Evaluation with Concurrent Development

presentation made at the 2007 SATURN Workshop

Talking Architects with Len Bass

Matt Deacon talks with Len Bass, co-author of Software Architecture in Practice, about how quality attributes (non-functional requirements) as first class citizens of a project in an agile development environment.

Technology Evolution – Impact on Architecture of a Complex Medical Product

Presented: May 2007

The Architecture Analysis & Design Language (AADL): An Introduction

The Architecture Analysis & Design Language (AADL): An Introduction

The Architecture Based Design Method

The Architecture Based Design Method

The Architecture Tradeoff Analysis Method

The Architecture Tradeoff Analysis Method

The Recovery of Runtime Architectures

The Recovery of Runtime Architectures

The SAE Avionics Architecture Description Language (AADL) Standard: A Basis for Model-Based Architecture-Driven Embedded Systems Engineering

The SAE Avionics Architecture Description Language (AADL) Standard: A Basis for Model-Based Architecture-Driven Embedded Systems Engineering

Three Perspectives Required of Service-Oriented Architectures

Three Perspectives Required of Service-Oriented Architectures

Three Perspectives of Service-Oriented Architectures

Three Perspectives of Service-Oriented Architectures

Tool Support for Architecture Analysis and Design

The needs of software architectural design and analysis have led to a desire to create CASE tools to support the processes. Such a tool should help: to document an architecture; to reuse architectural artifacts; to aid in exploring architectural alternatives; and to support architectural metrics. This position paper first presents a set of requirements that an ideal tool for architectural design and analysis, and then presents a tool—called SAAM tool—that meets most, but not all, of these requirements. SAAM tool embodies both SAAM (Software Architecture Analysis Method) and an architectural description framework which describes architectural elements according to their static and temporal features. The tool serves several purposes. It supports and documents the results of architectural design and analysis efforts at varying degrees of resolution, it acts as a repository of both designs and design rationales in the form of scenarios, it applies metrics to architectures, and it visualizes architectures with respect to architectural metrics. 

Tools for Making Better Architecture Decisions

Keynote address from SATURN 2007: Tools are essential to support software architecture design and evaluation methods. In the presentation, Ian Gorton describes novel, prototype tools for architecture knowledge management, collaborative architecture design and decision making, and performance analysis of COTS-based architectures. A brief overview of the aims and major features of each tool is presented, and their use in industrial projects is discussed.

Toward Deriving Software Architectures from Quality Attributes

Toward Deriving Software Architectures from Quality Attributes

Towards an Assurance Case Practice for Medical Devices

This report explores how the assurance case promises a technology answer for the challenge that manufacturers and federal regulators face in gaining confidence about the performance of software-dominated medical devices.

U.S. Army Workshop on Exploring Enterprise, System of Systems, System, and Software Architectures

The workshop summarized in this report confirms that various architectural genres enjoy more commonalities than differences. Nevertheless, each one has its own important knowledge base, and openness among the various architectural tasks within an organization is growing in importance.

Understanding Architectural Influences and Decisions in Large-System Projects

paper presented at the First International Workshop on Architectures for Software Systems, Seattle, April 1995

Understanding Architectural Patterns in Terms of Tactics and Models

Understanding Architectural Patterns in Terms of Tactics and Models

Use of ASN.1 and XDR for Data Representation in Real-Time Distributed Systems, The

This report provides an overview of two standards that are used for data specification and representation in distributed systems.

Use of the ATAM in the Acquisition of Software-Intensive Systems

Use of the ATAM in the Acquisition of Software-Intensive Systems

Use of the Architecture Tradeoff Analysis Method (ATAM) in Source Selection of Software-Intensive Systems

Use of the Architecture Tradeoff Analysis Method (ATAM) in Source Selection of Software-Intensive Systems

User Network for Software Architecture Technology Is Growing Steadily

User Network for Software Architecture Technology Is Growing Steadily

Using ArchE in the Classroom: One Experience

Using ArchE in the Classroom: One Experience

Using Architecture-Centric Methods within Plan Driven and Agile Software Development Processes

Presented: January 2005

Using Aspect-Oriented Programming to Enforce Architecture

Using Aspect-Oriented Programming to Enforce Architecture

Using Economic Considerations to Choose Among Architecture Design Alternatives

Using Economic Considerations to Choose Among Architecture Design Alternatives

Using Model-Based Engineering and Architectural Models to Build Secure Systems

Using Model-Based Engineering and Architectural Models to Build Secure Systems

Using Quality Attribute Workshops to Evaluate Early-Stage Architecture Design Decisions

Using Quality Attribute Workshops to Evaluate Early-Stage Architecture Design Decisions

Using Scenarios in Architecture Evaluations

Using Scenarios in Architecture Evaluations

VAXELN Experimentation: Programming a Real-Time Periodic Task Dispatcher Using VAXELN ADA 1.1

The purpose of this paper is to provide the reader with some technical information and observations ADA source code, and measurement results based on experimentation with respect to developing a real-time periodic task dispatcher in ADA.

VAXELYN Experimentation: Programming a Real-Time Clock and Interrupt Handling Using VAXELYN ADA 1.1

This report describes the results of implementing an interrupt handler totally in ADA for a MicroVAX II/VAXELN 2.3 target system, the VAXELN 1.1 ADA compiler, and a KWV11-C programmable real-time clock.

View Extraction and View Fusion in Architectural Understanding

View Extraction and View Fusion in Architectural Understanding

Welcome Presentation (SATURN 2008)

Software architects from around the world attended the Fourth Annual SEI Software Architecture Technology User Network (SATURN) Workshop in May 2008

Welcome to SATURN 2007

presentation from the Third SEI Software Architecture Technology User Network Workshop
May 14-16, 2007, Pittsburgh, Pennsylvania

Working Session: Software Architecture Competence

presentation made by Paul Clements at the SATURN 2007 Working Session "Architecture Competence," May 15, 2007

Workshop on the State of the Practice in Dependably Upgrading Critical Systems

This report describes the results of the Workshop on the State of the Practice in Dependably Upgrading Critical Systems held April 16-17, 1997 at the Software Engineering Institute.

Workshop to Present Best Practices in Software Architecture

Workshop to Present Best Practices in Software Architecture

presentation by Paul Clements at SATURN 2007, May 2007

presentation by Paul Clements at SATURN 2007, May 2007