Software Engineering Institute | Carnegie Mellon University
Software Engineering Institute | Carnegie Mellon University

Digital Library

Javascript is currently disabled for your browser. For an optimal search experience, please enable javascript.

Advanced Search

Basic Search

Content Type

Topics

Publication Date

Mario R. Barbacci
December 2003 - Technical Note Integrating the Architecture Tradeoff Analysis Method (ATAM) with the Cost Benefit Analysis Method (CBAM)

Topics: Software Architecture

Authors: Robert Nord, Mario R. Barbacci, Paul C. Clements, Rick Kazman, Mark H. Klein, Liam O'Brien, James E. Tomayko

This technical note reports on a proposal to integrate the SEI ATAM (Architecture Tradeoff Analysis Method) and the CBAM (Cost Benefit Analysis Method).

October 2003 - Technical Report Quality Attribute Workshops (QAWs), Third Edition

Topics: Software Architecture

Authors: Mario R. Barbacci, Robert J. Ellison, Anthony J. Lattanze, Judith A. Stafford, Charles B. Weinstock, William G. Wood

This report describes the newly revised QAW (Quality Attribute Workshop) and describes potential uses of the refined scenarios generated during it.

July 2003 - Technical Note Using the Architecture Tradeoff Analysis Method (ATAM) to Evaluate the Software Architecture for a Product Line of Avionics Systems: A Case Study

Topics: Acquisition Support, Software Architecture

Authors: Mario R. Barbacci, Paul C. Clements, Anthony J. Lattanze, Linda M. Northrop, William G. Wood

This 2003 technical note describes an ATAM evaluation of the software architecture for an avionics system developed for the Technology Applications Program Office (TAPO) of the U.S. Army Special Operations Command Office.

June 2003 - Technical Report Interactions Among Techniques Addressing Quality Attributes

Topics: Software Architecture

Authors: Hernan R. Eguiluz, Mario R. Barbacci

This report provides software architects a chart for determining the relationships among techniques that promote different architectural qualities.

March 2003 - Technical Note DoD Architecture Framework and Software Architecture Workshop Report

Topics: Software Architecture

Authors: William G. Wood, Lyn Uzzle, John Weiler, Art Krummenoehl, Mario R. Barbacci, Paul C. Clements, Steve Palmquist, Huei-Wan Ang, Loring Bernhardt, Fatma Dandashi, David Emery, Sarah Sheard

This report summarizes the activities of the Workshop on the Department of the 2003 Defense Architecture Framework and Software Architecture workshop.

October 2002 - Technical Note SEI Architecture Analysis Techniques and When to Use Them

Topics: Software Architecture

Authors: Mario R. Barbacci

When analyzing system and software architectures, the Quality Attribute Workshop (QAW) and the Architecture Tradeoff Analysis Method (ATAM) can be used in combination to obtain early and continuous benefits.

June 2002 - Technical Report Quality Attribute Workshops, 2nd Edition

Topics: Software Architecture

Authors: Mario R. Barbacci, Robert J. Ellison, Anthony J. Lattanze, Judith A. Stafford, Charles B. Weinstock, William G. Wood

This report clarifies the context in which a QAW (Quality Attribute Workshop) is applicable, provides a rationale for developing the process and describes it in detail, and concludes with a list of lessons learned and a discussion of how these lessons have helped evolve the process to its current state.

May 2001 - Technical Report Quality Attribute Workshops

Topics: Software Architecture

Authors: Mario R. Barbacci, Robert J. Ellison, Judith A. Stafford, Charles B. Weinstock, William G. Wood

This report describes the QAW (Quality Attribute Workshop) approach, which is a method for evaluating a software-intensive system architecture during the acquisition phase of major programs.

July 2000 - Technical Note Using Quality Attribute Workshops to Evaluate Architectural Design Approaches in a Major System Acquisition: A Case Study

Topics: Acquisition Support, Software Architecture

Authors: John K. Bergey, Mario R. Barbacci, William G. Wood

This report describes a series of Quality Attribute Workshops (QAWs) that were conducted on behalf of a government agency during its competitive acquisition of a complex, tactical, integrated command and control system.

June 2000 - Newsletter News At SEI: Quality Attribute Workshop

Topics: Software Architecture

Authors: Mario R. Barbacci

In this column, I describe one way for combining several of these components into a process that allows early insight into a system's architecture, including its quality-attribute sensitivities, tradeoffs, and risks.

January 2000 - Special Report Quality Attribute Workshop Participants Handbook

Topics: Software Architecture

Authors: Mario R. Barbacci, Robert J. Ellison, Charles B. Weinstock, William G. Wood

This report describes the 1) process we use to conduct QAW (Quality Attribute Workshop), 2) information required, 3) suggested tools, and 4) expected outcomes of QAWs.

October 1999 - Technical Report Architectural Evaluation of Collaborative Agent-Based Systems

Topics: Software Architecture

Authors: Steve Woods, Mario R. Barbacci

This report identifies features in agent-based systems that could be used to classify agent-system architectures and to guide the generation of scenarios applicable to these architectures.

July 1999 - Technical Report Architecture Tradeoff Analyses of C4ISR Products

Topics: Software Architecture

Authors: Mario R. Barbacci, William G. Wood

This report describes how various C4ISR products can be used in the context of an ATAM evaluation and their relative value for generating quality attribute-specific scenarios required for an ATAM evaluation.

July 1998 - Special Report Mapping MetaH into ACME

Topics: Performance and Dependability

Authors: Mario R. Barbacci, Charles B. Weinstock

This 1998 report explores the translation of MetaH into ACME.

July 1998 - Technical Report The Architecture Tradeoff Analysis Method

Topics: Software Architecture

Authors: Rick Kazman, Mark H. Klein, Mario R. Barbacci, Thomas A. Longstaff, Howard F. Lipson, Jeromy Carriere

This 2008 paper presents the Architecture Tradeoff Analysis Method (ATAM), a structured technique for understanding the tradeoffs inherent in the architectures of software-intensive systems.

May 1998 - Technical Report Steps in an Architecture Tradeoff Analysis Method: Quality Attribute Models and Analysis

Topics: Software Architecture

Authors: Mario R. Barbacci, Peter H. Feiler, Mark H. Klein, Howard F. Lipson, Thomas A. Longstaff, Charles B. Weinstock, Jeromy Carriere

This paper presents some of the steps in an emerging architecture tradeoff analysis method (ATAM).

April 1998 - White Paper The Architecture Tradeoff Analysis Method

Authors: Rick Kazman, Mark H. Klein, Mario R. Barbacci, Thomas A. Longstaff, Howard F. Lipson, Jeromy Carriere

This paper presents the Architecture Tradeoff Analysis Method (ATAM), a structured technique for understanding the tradeoffs inherent in design.

May 1997 - Technical Report Principles for Evaluating the Quality Attributes of a Software Architecture

Topics: Software Architecture

Authors: Mario R. Barbacci, Mark H. Klein, Charles B. Weinstock

This report describes a few principles for analyzing a software architecture to determine if it exhibits certain quality attributes.

December 1995 - Technical Report Quality Attributes

Topics: Software Architecture

Authors: Mario R. Barbacci, Mark H. Klein, Thomas A. Longstaff, Charles B. Weinstock

This report describes efforts to develop a unifying approach for reasoning about multiple software quality attributes.

December 1992 - Technical Report Durra: A Task Description Language User's Manual (Version 2)

Authors: Dennis N. Doubleday, Mario R. Barbacci

This 1992 document describes the use of Durra, a task-level application description language, and its associated toolset.

December 1991 - Technical Report Durra: A Task-Level Description Language Reference Manual (Version 3)

Authors: Mario R. Barbacci, Dennis N. Doubleday, Michael J. Gardner, Randall W. Lichota, Charles B. Weinstock

This 1991 report describes the Durra language and incorporates the language changes introduced as a result of our experiences writing application descriptions in Durra.

December 1991 - Technical Report Building Distributed ADA Applications from Specifications and Functional Components

Authors: Dennis N. Doubleday, Mario R. Barbacci, Charles B. Weinstock, Michael J. Gardner, Randall W. Lichota

This report describes Durra, a language and support environment for the specification and execution of distributed Ada applications.

September 1991 - Technical Report Durra: An Integrated Approach to Software Specification, Modeling, and Rapid Prototyping

Authors: Mario R. Barbacci, Dennis N. Doubleday, Charles B. Weinstock, Randall W. Lichota

This 1991 paper discusses the relationship between software specification, modeling and prototyping activities as part of a real-time system development strategy.

September 1989 - Technical Report Durra: A Task-Level Description Language User's Manual

Authors: Mario R. Barbacci, Dennis N. Doubleday, Charles B. Weinstock

This manual is for users of the Durra compiler, runtime system, and support tools.

September 1989 - Technical Report Durra: A Task-Level Description Language Reference Manual (Version 2)

Authors: Mario R. Barbacci, J. Wing

This 1989 report is a revised version of the original Durra reference manual. This revision describes the syntax and semantics of the language and incorporates several language changes.

February 1989 - Technical Report Command, Control, Communications, and Intelligence Node: A Durra Application Example

Authors: Mario R. Barbacci, Dennis N. Doubleday, Charles B. Weinstock

This report describes an experiment in implementing a command, control, communications and intelligence (C3I) node using reusable components.

July 1988 - Technical Report The Software Technical Review Process

Authors: Mario R. Barbacci

This 1988 report describes MasterTask, a program that can emulate any task in an application by interpreting the timing expression describing the behavior of the task, performing the input and output port operations in the proper sequence and at the prope

July 1988 - Technical Report MasterTask: The Durra Task Emulator

Authors: Mario R. Barbacci

This 1988 report describes MasterTask, a program that can emulate any task in an application by interpreting the timing expression describing the behavior of the task, performing the input and output port operations in the proper sequence and at the proper time.

July 1988 - Technical Report The Durra Runtime Environment

Authors: Mario R. Barbacci, Dennis N. Doubleday, Charles B. Weinstock

This 1988 report describes the Durra Runtime Environment for Durra, a language designed to support PMS-level programming.

July 1988 - Technical Report Generalized Image Library: A Durra Application Example

Authors: Mario R. Barbacci, Dennis N. Doubleday

This 1988 report describes an experiment in writing task descriptions and type declarations for a subset of the Generalized Image Library, a collection of utilities developed at Carnegie Mellon University.

December 1986 - Technical Report Specifying Functional and Timing Behavior for Real-Time Applications

Topics: Performance and Dependability

Authors: Mario R. Barbacci, J. Wing

This 1986 report presents a notation and a methodology for specifying the functional and timing behavior of real-time applications for a heterogeneous machine.