This information sheet describes the SOA Migration, Adoption, and Reuse Technique (SMART), its benefits, and the SMART "family members."
12/10/2012The SEI Architecture Practices Initiative aims to improve product development and quality by using architecture to gain early confidence in achieving system-related business and mission goals.
06/06/2012Information sheet describing the Advanced Software Architecture Workshop
04/25/2012This presentation introduces the STRategic Ecosystem Analysis Method (STREAM), which uses the architecture construct of a view to reduce model complexity.
03/22/2012This report provides an overview of changes and improvements to the Architecture Analysis & Design Language (AADL) standard for describing both the software architecture and the execution platform architectures of performance-critical, embedded, real-time systems.
02/27/2012John Klein reviews the SEI perspective on architecture-centric engineering, and discusses how this approach scales from its original software context through systems-of-systems.
02/27/2012At this 2012 event, Felix Bachmann discussed the concepts used by an Architecture Tradeoff Analysis Method (ATAM) that make an evaluation successful, which can be integrated into the architecture design process to ensure the creation of successful systems.
02/27/2012Although software architecture is a key factor in determining the success or failure of a software system, software professionals throughout the industry continue to struggle with questions like: What exactly is a software architecture? Why is software architecture important?
09/06/2011This one-pager was produced for SPLC 2011 and focuses on how the SEI provides various types of software product lines training.
08/10/2011To improve architecture capability, the SEI has developed a diagnostic method to systematically assess your architecture competence at the individual, team, and organizational levels.
06/07/2011A one-page brochure about the SEI's hands-on software architecture course.
01/28/2011This information sheet describes the Architecture Tradeoff Analysis Method (ATAM.)
01/11/2011This report details the results from 18 experiments to investigate Adaptive Quality of Service, an approach to enable applications to fulfill their missions despite network infrastructure limitations.
12/16/2010Enabling Agility Through Architecture: A Crosstalk article by Nanette Brown, Rod Nord, and Ipek Ozkaya.
11/17/2010This report summarizes a workshop on the analysis and evaluation of enterprise architectures that was held at the SEI in April of 2010.
11/08/2010Linda Northrop describes the basic concepts of software product lines, summarizing the software engineering and management practices needed for a product line approach.
09/30/2010This book provides the most complete and current guidance on how to capture a software architecture in a commonly understandable form.
08/25/2010Some basics of software product line practice, the challenges that make product line acquisition unique, and three basic acquisition strategies are all part of this white paper.
08/25/2010Len Bass's keynote presentation from ICGSE 2010 talks about the structure of coordination models, especially after development has begun.
08/20/2010This report presents COVERT, an automated framework aimed at finding buffer overflows in C programs using state-of-the-art software verification tools and techniques.
08/20/2010This report attempts to facilitate better elicitation of high-pedigree quality attribute requirements by understanding how business goals influence quality attribute requirements and architectures.
07/07/2010Rob Wojcik discusses the the role that software architecture plays in an organization, the role of quality attribute requirements in architectural design, and more.
06/30/2010This report synthesizes presentations and discussions from a 2010 workshop to discuss product line practices and operational accomplishments.
05/14/2010The Hard Choices game is a simulation of the software development cycle meant to communicate the concepts of uncertainty, risk, options, and technical debt. In the quest to become market leader, players race to release a quality product to the marketplace. By the end of the game, everyone has experienced the implications of investing effort to gain an advantage or of paying a price to take shortcuts, as they em-ploy design strategies in the face of uncertainty.
03/18/2010Three diagnostic tools for understanding an organization's readiness for and initial approach to software product lines
03/18/2010Achieving architecture competence will ensure that you realize the benefit of architecture-centric practice, including the alignment of your architecture to your business goals and predictable, routine success in architecture.
03/12/2010Designing Software Architecture to Achieve Business Goals: a presentation by Len Bass given to the Academy for Software Engineering Education and Training on March 12, 2010.
01/29/2010Enhance your skills in software product line adoption and learn how to employ the proven strategies and techniques that make software product lines successful.
12/18/2009This 2009 technical note proposes a structured approach for reviewing architecture documentation that is centered on the documentation's stakeholders.
11/30/2009This white paper explores the idea that subway maps provide a good, common example of architecture documentation and that they might be instructive about good software architecture documentation,
11/24/2009Video of interview with the SEI's Len Bass, co-author of Software Architecture in Practice, about quality attributes (non-functional requirements) in an agile development environment
10/29/2009This 2009 report describes the data model as an architectural style in an effort to help architects apply this style to create data model architectural views.
08/04/2009Tactics 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.
08/01/2009This 2009 report describes a technique for formulating the production strategy of a production system.
06/01/2009Paul 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.
04/01/2009This report is a synthesis of the presentations and discussions that took place during the 2009 U.S. Army Software Product Line Workshop.
04/01/2009This report summarizes a June 2008 architecture competence workshop where practitioners discussed key issues in assessing architecture competence in organizations.
03/05/2009To 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. (1hr:3 mins)
02/12/2009presented at the SEI Army Software Product Line Workshop, February 12, 2009
02/12/2009presented at the SEI Army Software Product Line Workshop, February 12, 2009
02/12/2009Presented: February 2009
02/12/2009This page contains the slides from the “Army Software Product Line Workshop,” which was hosted by Linda M. Northrop of the Software Engineering Institute (SEI) in February 2009.
02/12/2009This page contains the slides from the “Army Software Product Line Workshop,” which was hosted by Linda M. Northrop of the Software Engineering Institute (SEI) in February 2009.
10/14/2008Bachmann et al present their work on a design assistant called ArchE that provides third-party researchers with an infrastructure to integrate their own quality-attribute models.
09/17/2008presented at SOAPL 2008: Service-Oriented Architectures and Software Product Lines - Putting Both Together, Limerick, Ireland, September 8-12, 2008
09/08/2008This 2008 presentation – “Combining Product Line Engineering and Service Oriented Architecture in Health Care Infrastructure” – was delivered by Jörg Bartholdt, Bernd Franke, C. Schwanninger, and Michael Stal of Siemens AG.
09/08/2008presented at the 12th International Software Product Line Conference, 2008, in Limerick, Ireland, September 8-12, 2008
09/08/2008presented at SOAPL 2008: Service-Oriented Architectures and Software Product Lines - Putting Both Together, Limerick, Ireland, September 8-12, 2008
09/08/2008presented at SOAPL 2008: Service-Oriented Architectures and Software Product Lines - Putting Both Together, Limerick, Ireland, September 8-12, 2008
09/08/2008presented at SOAPL 2008: Service-Oriented Architectures and Software Product Lines - Putting Both Together, Limerick, Ireland, September 8-12, 2008
09/08/2008This presentation on business process lines to service-oriented architecture through the software product lines paradigm was delivered by five members of the University of Bari in 2008.
07/01/2008Presented: July 2008
06/02/2008The 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.
06/01/2008This 2008 report includes an overview of the First Workshop on Service-Oriented Architectures and Product Lines, four invited presentations, details of the workshops outcomes, and the workshop position papers.
05/11/2008The workshop on Leadership and Management in Software Architecture that took place at ICSE 2008 was focused on understanding these non-technical duties and the type of support an architect should expect from an organization.
04/01/2008Making SIMPLE Decisions about Software Product Lines
01/01/2008Resources for Getting Started with Software Product Lines
09/10/2007presented at Service Oriented Architectures and Product Lines - What is the Connection? (SOAPL - 07), September 10, 2007, Kyoto, Japan
09/10/2007Similarities and differences in service oriented computing modeling and software product family modeling.
09/10/2007Presentation by Jaejoon Lee (Fraunhofer Institut Experimentelles Software Engineering) on identifying and specifying reusable services for service-oriented architecture (SOA).
09/03/2007presented at Service Oriented Architectures and Product Lines - What is the Connection? (SOAPL - 07), September 10, 2007, Kyoto
09/01/2007This report illustrates how to use AOP (aspect-oriented programming) to ensure conformance to architectural design, proper use of design patterns and programming best practices, conformance to coding policies and naming conventions.
09/01/2007This report describes how architectural tactics are based on the parameters of quality attribute models.
08/02/2007presented as part of the SEI Software Architecture Workshop for Educators, August 2007
08/02/2007presented as part of the SEI Software Architecture Workshop for Educators, August 2007
08/02/2007The Fourth SEI Software Architecture Workshop for Educators was held at the Software Engineering Institute in Pittsburgh, PA on July 31- August 2, 2007.
07/01/2007Mitigating the Risk of Using Service-Oriented Architectures
07/01/2007Lessons Learned about Software Architecture
06/01/2007A presentation with audio
05/15/2007presentation made by Paul Clements at the SATURN 2007 Working Session "Architecture Competence," May 15, 2007
05/14/2007Presented: May 2007
05/14/2007presentation made by Mark Klein at the Third Annual SATURN Workshop, May 2007
05/14/2007presentation made by Stuart Kerrigan and Richard van Schelven at the Third Annual SATURN Workshop, May 2007
05/14/2007Presented: May 2007
05/14/2007presentation made at the 2007 SATURN Workshop
05/01/2007ArchE-the Architecture Expert
05/01/2007Software Product Lines FAQs Part VI: Using Software Product Lines with Other Approaches
05/01/2007This 2007 report shows how an analysis of the options embodied within architectural patterns allows a software and system architect or manager to make reasoned choices about the future value of design decisions, considering this value along multiple quality attribute dimensions.
04/01/2007Coming Soon: A New Version of the SEI's Framework for Software Product Line Practice
03/29/2007Presented: March 2007
03/26/2007Felix Bachmann, Lenn Bass, and Philip Bianco present ArchE, a tool that provides the right information at the right time for architect when designing software architecture.
03/01/2007Workshop to Present Best Practices in Software Architecture
03/01/2007Improving Software Architecture Competence by Paul Clements, International Association of Software Architects (IASA), March 2007.
03/01/2007Software Architecture: The Next Generation
03/01/2007Presented: March 2007
02/01/2007SEI Publishes Framework for Software Process Research
02/01/2007This 2007 report describes an example application of the ADD method, an approach to defining a software architecture in which the design process is based on the quality attribute requirements the software must fulfill.
01/01/2007FAQs Part 5: Getting Started
11/01/2006This report revises the steps of the Attribute-Driven Design (ADD) method and offers practical guidelines for carrying out each step.
10/16/2006This page contains the slides for John Klein’s guest lecture for COMP 180: Software Engineering, held at Tufts University, during the 2006 fall semester.
09/01/2006This 2006 report analyzes the output of 18 evaluations conducted using the Architecture Tradeoff Analysis (ATAM). The goal of the analysis was to find patterns in the risk themes identified during those evaluations.
08/01/2006In this report, five methods for the elicitation and expression of requirements are evaluated with respect to their ability to capture architecturally significant requirements.
07/26/2006This presentation on best practices in software architecture was delivered by Paul C. Clements of the Software Engineering Institute (SEI) on July 26, 2006.
06/01/2006Best Practices in Software Architecture, by Paul Clements
06/01/2006The Hottest Issues in Software Product Lines:
06/01/2006In this presentation, Len Bass attempts to determine more precisely what the relationship is between software architecture and software quality attributes such as performance, security, testability and so on.
05/01/2006Quality Attributes and Service-Oriented Architectures
04/26/2006This page contains the slides from a working session conducted at the Software Architecture Technology User Network (SATURN) 2006 workshop, held in Pittsburgh, PA.
04/25/2006Presented: April 2006
04/25/2006Presented: April 2006
04/19/2006Presented: April 2006
04/03/2006This presentation on Software Product Lines: Reuse That Makes Business Sense was delivered by Linda M. Northrop of the Software Engineering Institute (SEI) in April 2006.
04/01/2006This report examines selected aspects of autonomic computing and explores some of the strengths and weaknesses of that technology.
04/01/2006FAQs Part 4: Product Lines in the Context of Acquisition
03/01/2006Strategic Architecting
03/01/2006This 2006 report contains the proceedings from the First International Workshop on Reengineering Towards Product Lines (R2PL) 2005, which was held in November 2005.
01/02/2006Presented: January 2006
01/01/2006FAQs Part 3: Exploring the Issues More Deeply
12/01/2005This report provides a categorization of possible business goals for software-intensive systems, so that individuals have some guidance in the elicitation, expression, and documentation of business goals.
11/01/2005This 2008 report includes an overview of the First Workshop on Service-Oriented Architectures and Product Lines, workshop position papers, and more.
09/27/2005Presented: November 2005
09/01/2005In this 2005 presentation, Linda M. Northrop of the Software Engineering Institute (SEI) provides an introduction to software product line acquisition.
09/01/2005This 2005 report discusses the benefits and challenges of using a wiki-based collaborative environment to create software architecture documentation.
09/01/2005This 2005 report by Felix Bachmann and Paul C. Clements describes the concepts needed when creating core assets with included variability.
09/01/2005This note describes an ARL implementation of two usability scenarios: displaying progress feedback and allowing cancel.
09/01/2005This 2005 report describes the application of a reasoning framework to the design of an industrial communications library and the problems that were found.
09/01/2005This 2005 report provides an end-to-end view of the activities that are needed to support the automatic derivation of products within a software product line.
07/01/2005This report summarizes the V&B and 1471 approaches to architecture description, and shows how a software architecture document prepared using V&B can be made compliant with 1471.
07/01/2005This report describes a vehicle for encapsulating the quality attribute knowledge needed to understand a system's quality behavior as a reasoning framework that can be used by nonexperts.
06/13/2005Presented: June 2005
05/02/2005Presented: May 2005
04/12/2005Presented: April 2005
04/06/2005This presentation – on methodically designing software architecture using ArchE, an architecture design assistant – was presented by Felix Bachmann and Mark H. Klein in 2005.
04/01/2005The Components of Software Architecture Design and Analysis
04/01/2005FAQs Part 2: Are Product Lines Right for My Organization?
03/01/2005Integrating Architecture Methods: The Case of the QAW and the ADD Method
03/01/2005FAQs: An Introduction to Software Product Lines
03/01/2005Using Product Line Analysis to Get Started With Software Product Lines
03/01/2005This 2005 report summarizes discussions and presentations from the Seventh Department of Defense (DoD) Product Line Practice Workshop.
02/01/2005The Architecture Business Cycle Revisited: A Business Goals Taxonomy to Support Architecture Design and Analysis
02/01/2005Only Leaders Need Apply
02/01/2005New Curriculum Fosters Adoption of Software Product Line Practices
02/01/2005This 2005 report presents SIMPLE, a general-purpose business model that supports the estimation of the costs and benefits in a product line development organization.
01/01/2005Presented: January 2005
01/01/2005Integrating Architecture Methods: The Case of Extreme Programming
01/01/2005Pas de Deux: Making the Two-Part Organization Work
01/01/2005An Adoption Roadmap for Software Product Line Practice
12/01/2004This report describes a technique that uses automatically generated runtime observations of an executing system to construct an architectural view of the system.
09/01/2004This 2004 report introduces the Adoption Factory pattern, which provides a generic roadmap to guide a manageable, phased product line adoption strategy.
09/01/2004The report presents a summary of XP (Extreme Programming) and examines the potential uses of the SEI's architecture-centric methods.
09/01/2004This report describes a design prototype that demonstrates a web-based approach to creating, communicating, and using software architecture throughout the life of the system.
08/30/2004Presented at the Third Software Product Line Conference (2004)
07/01/2004This technical note reports on a proposal to integrate the SEI Quality Attribute Workshop (QAW) and the SEI Attribute-Driven Design (ADD) method.
07/01/2004This report presents a summary of the RUP (Rational Unified Process) and examines the potential uses of the SEI's architecture-centric methods.
04/01/2004This 2004 report explores how changes in UML 2.0 affect UML's suitability for documenting component and connector views.
03/03/2004Presented: March 2004
03/01/2004Integrating Architecture Methods: The Case of the Rational Unified Process
03/01/2004Marathon Man
03/01/2004Making the Use of the DoDAF Easier for DoD Organizations
03/01/2004This 2004 report summarizes the presentations and discussions from the Sixth Department of Defense (DoD) Product Line Practice Workshop in September 2003.
03/01/2004This 2004 report presents the results of a study that focused on how product line organizations create products.
02/01/2004Calculating Return on Investment for Software Product Lines
02/01/2004The Recovery of Runtime Architectures
02/01/2004Tiptoe Carefully or Dive Right In?
02/01/2004This report describes the process of architecture reconstruction using the Dali architecture reconstruction workbench.
01/01/2004Presented: January 2004
01/01/2004Presented: January 2004
01/01/2004This 2004 whitepaper offers eight lessons from history for the software architecture field, drawn from peer fields i.e. Military, Civil, Finance, Mathematics, Astronomy, Social and Medical.
01/01/2004Integrating Architecture Methods: The Case of the ATAM and the CBAM
12/01/2003Integrating Analysis and Design Methods for the Software Life Cycle
12/01/2003It Takes Two
12/01/2003This technical note reports on a proposal to integrate the SEI ATAM (Architecture Tradeoff Analysis Method) and the CBAM (Cost Benefit Analysis Method).
12/01/2003The report outlines the first version of the Software Architecture Comparison Analysis Method (SACAM). This method was created to provide rationale for an architecture selection process by comparing the fitness of architecture candidates for required systems.
11/01/2003This report outlines the application of architecture reconstruction techniques to the Sun Microsystems' Duke's Bank system- Java2 Platform, Enterprise Edition/Enterprise JavaBeans (J2EE/EJB) application implemented mainly in Java.
10/01/2003This report describes the newly revised QAW (Quality Attribute Workshop) and describes potential uses of the refined scenarios generated during it.
09/01/2003Rethinking the Software Life Cycle
09/01/2003The Man with the Plan
09/01/2003This 2003 report presents a procedure for moving from a set of quality attribute scenarios to an architecture design that satisfies those scenarios.
09/01/2003This 2003 technical report describes the addition of development requirements to product line analysis.
09/01/2003This report examines the architecture-centric analysis and design methods that were created at the SEI between 1993 and 2003.
09/01/2003This report discusses the context for using the C4ISRAF, the observations made during the interviews about its use, and the strengths and challenges of using it.
07/01/2003This 2003 report defines key factors to consider in taking an incremental approach to fielding a product line.
07/01/2003What's the Difference Between Product Line Scope and Product Line Requirements?
06/01/2003Documenting Software Architectures
06/01/2003This 2003 document summarizes the presentations and discussions from the Fifth Department of Defense (DoD) Product Line Practice Workshop, held in August 2002.
06/01/2003This report provides software architects a chart for determining the relationships among techniques that promote different architectural qualities.
06/01/2003The focus of this 2003 technical report is how evolutionary changes affect the various types of assets in a software product line.
05/03/2003Architecture, design, and implementation are used informally in partitioning software specifications into three coarse strata of abstraction. These strata are not well-defined in either research or practice, causing miscommunication and needless debate.
04/19/2003This book provides an easily accessible overview of software architecture. Anyone requiring a comprehensive overview of the software architecture field will benefit from this book.
03/01/2003Components As Products
03/01/2003This report summarizes the activities of the Workshop on the Department of the 2003 Defense Architecture Framework and Software Architecture workshop.
03/01/2003This 2003 report describes an approach to designing a domain framework that encapsulates expertise in developing an HLA federate by hiding RTI internal operations from the developer.
03/01/2003This 2003 technical report provides the status on the work being done by the SEI to understand the relationship between quality requirements and architectural design.
01/01/2003Defining the Terms Architecture, Design, and Implementation
01/01/2003This paper outlines experiences with using economic criteria to make architecture design decisions.
01/01/2003Presented: January 2003
01/01/2003This presentation provides an overview of the SCAMPI appraisal method.
12/01/2002SEI Hosts Software Product Line Conference
12/01/2002E Pluribus Unum
12/01/2002This report, published in 2002, details the responsibilities that a system must implement to support command cancellation.
10/01/2002When 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.
09/30/2002The CBAM (Cost Benefit Analysis Method) extends the ATAM framework to elicit and model costs, benefits, and uncertainty.
09/01/2002The Evolution of Quality Attribute Workshops as an Architecture-Evaluation Technique
09/01/2002Software Architecture Book Provides Practical Guidance about Documentation
09/01/2002Product Lines Are Everywhere
09/01/2002This 2002 report outlines the state of software product line practice in industry. The report blends a case study with the results of a product line questionnaire.
09/01/2002This 2002 technical note examines the significant characteristics of the production plans of three hypothetical organizations that create product lines of home integration systems.
09/01/2002This report describes the improvements to the CBAM (Cost Benefit Analysis Method) and provides a pilot case study conducted with NASA.
08/01/2002This 2002 report presents the basic concepts of analysis models for two quality attributes-modifiability and performance, identifies a collection of tactics that can be used to control responses within those models, and discusses how to analyze the models in terms of these tactics.
06/01/2002Aligning Business Models, Business Architectures, and IT Architectures
06/01/2002This report provides guidance for documenting the interfaces to software elements.
06/01/2002This report explains the role of software architecture evaluation in a source selection and describes the contractual elements that are needed to support its use.
06/01/2002This 2002 technical report provides guidance for creating, using, and evaluating a production plan, which is a description of how core assets are to be used to develop a product in a product line.
06/01/2002This 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.
03/01/2002Architectures for Adaptive Mobile Systems
03/01/2002Cost-Benefit Analysis Method
03/01/2002SEI Architecture Practices Propel Successful Startup
03/01/2002This 2002 report outlines details of past and current architecture reconstruction work on several systems at Nokia.
01/01/2002This report describes ways to document the behavior of systems, subsystems, and components of software architecture.
12/01/2001This report describes test-related activities that form the test process for a product line organization, along with techniques and activities that can meet these challenges.
12/01/2001The SEI developed the CBAM (Cost Benefit Analysis Method), which incorporates the costs and benefits of architectural design decisions and provides an effective means of making such decisions. This paper reports on the application of this method to a real world case study.
10/03/2001This paper discusses the understanding of quality attributes and their application to the design of a software architecture.
10/01/2001This report introduces the notion of quality attribute design primitives, which are architectural building blocks that target the achievement of one or sometimes several quality attribute requirements.
10/01/2001This paper describes a process for systematically refining an enterprise system architecture to resist, recognize, and recover from deliberate, malicious attacks by applying reusable design primitives that help ensure the survival of the enterprise mission.
10/01/2001In this report, we compare the scenarios elicited from five ATAM (Architecture Tradeoff Analysis Method) evaluations with the scenarios used to characterize the quality attributes.
10/01/2001The report summarizes the workshop presentations and discussions from the Fourth Department of Defense (DoD) Software Product Line Practice Workshop, held in March 2001.
09/01/2001Economic Modeling of Software Architectures
09/01/2001Software Product Line Practice Patterns
09/01/2001This report synthesizes the workshop presentations and discussions from the Fifth Software Engineering Institute Product Line Practice Workshop, held in December 2000.
08/20/2001This book provides a framework of specific practices, with detailed case studies, to guide the implementation of product lines in your organization.
08/01/2001That comprehensive handbook outlines how to produce high-quality documentation for software architectures.
08/01/2001This report describes the process of architecture reconstruction using the Dali architecture reconstruction workbench.
06/01/2001Using Quality Attribute Workshops to Evaluate Early-Stage Architecture Design Decisions
06/01/2001Software Architecture Evaluation: A Key to System Success
06/01/2001OAR is a systematic, architecture-centric, decision-making method for mining existing components for a product line or new software architecture.
05/18/2001This paper presents experience with explicitly managing variability within a software architecture.
05/01/2001This 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.
05/01/2001This report summarizes the discussions from the 2001 Architecture Representation Workshop, where five leading software architects and practitioners were invited to discuss aspects of the architecture representation with senior members of the SEI technical staff.
04/01/2001This 2001 report provides a practical introduction to product line requirements modeling and describes product line analysis in the context of product line development.
03/01/2001Architecture Mechanisms
03/01/2001Advancing the State of Software Product Line Practice
03/01/2001This paper outlines an approach to improving the usability of software systems by means of software architectural decisions.
12/01/2000This report addresses mechanisms that significantly affect quality attribute behavior and have sufficient content for analysis.
12/01/2000This report synthesizes the presentations and discussions of the Third Department of Defense Product Line Practice Workshop held in March 2000.
10/01/2000This report elaborates an example of the application of the ABD (Architecture-Based Design) method to designing software architecture.
09/01/2000This report presents technical and organizational foundations for performing architectural analysis, and presents the SEI's ATAM, a technique for analyzing software architectures.
09/01/2000The target, evaluation criteria, yardstick, data-gathering techniques, synthesis techniques and evaluation process of ATAM are identified and analyzed in this report.
08/01/2000This paper describes ARID, a piloted software design review technique.
06/01/2000Quality Attribute Workshop
04/01/2000Attribute-Based Architectural Styles
03/01/2000Quality Attribute Workshops
03/01/2000An Architectural Approach to Software Cost Modeling
03/01/2000Probing Product Line Practices
03/01/2000The 2000 report lays out our approach and organization for the book-in-planning titled Software Architecture Documentation in Practice, and provides guidance for the layer diagram.
02/01/2000This 2000 report provides background information to a series of SEI reports designed to provide concise and usable information about product line acquisition practices.
02/01/2000This report synthesizes the results of the 1999 Product Line Practice Workshop, which described practices and issues associated with tool support for software product lines.
01/01/2000This paper presents the Architecture Based Design (ABD) method for designing the high-level software architecture for a product line or long-lived system.
01/01/2000This 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.
12/01/1999Software Architecture Evaluation in the DoD Systems Acquisition Context
10/01/1999This report establishes a common format for documenting ABASs in the hope that they will become the foundation for anyone who is doing system design and analysis.
10/01/1999This 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.
10/01/1999This report synthesizes the workshop presentations and discussions of the Second DoD Product Line Practice Workshop, held in March 1999.
09/01/1999The Net Effects of Product Lines
09/01/1999The Perils and Joys of Reconstructing Architectures
09/01/1999A Scenario for Using the Product Line Practice Framework
09/01/1999A Framework for Software Product Line Practice
09/01/1999Product Lines in Practice at Three Major Corporations
09/01/1999Software Product Lines: A New Paradigm for the New Century
08/01/1999This 1999 report provides guidelines for an organization that is developing a CONOPS document.
07/01/1999This 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.
06/01/1999Using Scenarios in Architecture Evaluations
06/01/1999This report presents a description of architecture-centric system development.
03/01/1999Analyzing Quality Attributes
03/01/1999This report describes product line practices and analyzes issues in the areas of software engineering, technical management, and organizational management.
01/01/1999This paper presents a concrete example of an architecturally-motivated reengineering task. In executing this task, the authors perform architecture reconstruction, reason about the reconstructed architecture, motivate an architectural transformation with new architectural quality requirements, and realize this architectural transformation via an automated code transformation.
12/01/1998Representing Software Architecture
09/01/1998Are Software Architects Like Building Architects?
08/01/1998This paper presents a workbench for architectural extraction called Dali, and shows how Dali supports flexible extraction and fusion of architectural information. Its use is described through two extended examples of architectural reconstruction.
05/01/1998This report summarizes the discussions and outcomes of the Second International Workshop on Development and Evolution of Software Architectures for Product Families, held in February 1998.
05/01/1998This report synthesizes the results of the 1998 product line workshop that described selected practices and identified barriers and enablers to achieving these practices within the DoD.
05/01/1998This paper presents some of the steps in an emerging architecture tradeoff analysis method (ATAM).
04/01/1998This 1998 report synthesizes the presentations and discussions from the Second SEI Product Line Practice Workshop, held in November 1997.
03/09/1998This paper describes a system, called IAPR, that aids in architectural exploration and measurement by attempting to match patterns to an architecture.
01/01/1998This paper discusses the requirements and a generic framework for the integration of architectural and code-based reengineering tools. It was presented at the 1998 Working Conference on Reverse Engineering, Honolulu HI, October 1998 and was written by Rick Kazman, S. G. Woods, and S. J. Carriere.
11/10/1997This paper presents a set of well known but informally described software architectural elements used in system composition, and taxonomizes them under a basic set of characteristic features.
11/10/1997This paper presents an approach to capturing and assessing software architectures for evolution and reuse. The approach consists of a framework for modeling various types of relevant information and a set of architectural views for reengineering, analyzing, and comparing software architectures.
10/01/1997This paper presents Dali, an open, lightweight workbench that aids an analyst in extracting, manipulating, and interpreting architectural information.
06/01/1997This 1997 report synthesizes the presentations and discussions from the 1996 SEI Product Line Practice Workshop.
05/01/1997This report describes a few principles for analyzing a software architecture to determine if it exhibits certain quality attributes.
01/01/1997This report details the results of two workshops on software architecture evaluation, held at the SEI in 1996.
11/01/1996This paper presents an experiential case study illustrating the methodological use of scenarios to gain architecture-level understanding and predictive insight into large, real-world systems in various domains.
11/01/1996This 1996 report introduces an approach that will help managers make resource allocation decisions.
06/01/1996This report provides an industry example in the planning and execution of a research project using feature-oriented domain analysis (FODA).
03/15/1996This paper summarizes a taxonomic survey of ADLs that is in progress. This paper summarizes a taxonomic survey of ADLs that is in progress. Preliminary results allow conclusions to be drawn about what constitutes an ADL, and how contemporary ADLs differ.
03/01/1996This paper describes the Gadfly, an approach for developing narrowly-focused, reusable domain models that can be integrated and (re)used to aid in the process of top-down system comprehension.
02/01/1996This report summarizes software architecture for an intended audience of mid to senior level management.
01/01/1996This position paper first presents a set of requirements that an ideal tool for architectural design and analysis, and then presents a tool—called SAAMtool—that meets most, but not all, of these requirements.
01/01/1996This 1996 report identifies a set of promising lines of research related to software architecture and architecture-based system development.
12/01/1995This report describes efforts to develop a unifying approach for reasoning about multiple software quality attributes.
11/15/1995This whitepaper provides a conceptual overview of component-based software development (CBSD) and discusses how CBSD is changing the way large software systems are developed.
09/15/1995This paper presents Modechart, a specification language for hard-real-time embedded computer systems developed at the University of Texas at Austin. It presents the Modechart paradigm as an example of a fruitful trend for ADL research.
07/01/1995This paper gives a brief overview of the underlying technologies of the Simplex architecture, which was developed to support safe and reliable online upgrade of hardware and software components.
04/14/1995This paper presents a method for analyzing systems for nonfunctional qualities from the perspective of their software architecture and applies this method to the field of Internet information systems (IISs).
04/14/1995This paper discusses the approach taken in a pilot study to uncover the correlation, if any, between architectural influences and architectural decisions in large-scale, software-intensive development projects.
04/14/1995This 1995 whitepaper provides an overview of Architecture description languages (ADLs), an emerging notation for software architecture models.
03/01/1995This paper presents a case study in assessing the maintainability of a large, software intensive system. The techniques used are described, and their strengths and weaknesses discussed.
12/01/1994System designers use two primary ways of defining software architecture; this paper explains why neither alternative is adequate.
11/15/1994The increasing importance of software in systems is also driving the software architecture renaissance. This article provides a brief overview of some important architecture related efforts.
11/01/1994This whitepaper was presented at the Workshop on Software Architecture, USC Center for Software Engineering, Los Angeles, 1994, by Paul Clements.
01/01/1994This paper provides an introduction to the emerging field of software architecture.
08/01/1993This paper presents the structural modeling approach, an application framework and development process for the construction of flight simulators.
03/01/1993This report documents an analysis of the army movement control domain performed by the SEI and a team of experts from the army.
02/01/1992The "software architecture" level of software design was the subject of a course taught at the SEI in 1992. This report presents the motivation for the course, the content and structure of the current version, and plans for improving the next version.
01/01/1992Kang et al present a reuse-based software development methodology developed by the Software Engineering Institute that is meant to identify the applicability of reusable resources.
11/01/1990The 1990 report describes a multi-dimensional design space that classifies system architectures.
11/01/1990This 1990 report establishes methods for performing a domain analysis and describes the products of the domain analysis process.
11/01/1990This report describes the architecture of user interface systems, using a design space that identifies the key architectural choices and classifies the available alternatives.
06/01/1990This 1990 document presents a bibliography of references on domain analysis.
09/01/1988This report presents a perspective to software reuse in the context of "ideal" development capabilities, which is intended to lead to a reuse strategy for software development.
For more information
Email: info@sei.cmu.edu
Call: 412-268-2358