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 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. | |
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 | |
Analyzing Enterprise JavaBeans Systems Using Quality Attribute Design Primitives |
|
Analyzing Enterprise JavaBeans Systems Using Quality Attribute Design Primitives | |
Analyzing Quality Attributes |
|
Analyzing Quality Attributes | |
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 | |
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. | |
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 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 | |
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 | |
Best of Three Worlds: Combining QAW, MDRE, and GA, The |
|
Presented: April 2006 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
Deriving Architectural Tactics: A Step Toward Methodical Architectural Design |
|
Deriving Architectural Tactics: A Step Toward Methodical Architectural Design | |
Design and Analysis Principles for Software Architecture |
|
Presented: January 2004 | |
Discovering Architectures from Running Systems: Lessons Learned |
|
Discovering Architectures from Running Systems: Lessons Learned | |
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 | |
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 | |
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 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). | |
Features of Architecture Description Languages |
|
Features of Architecture Description Languages | |
Formal Methods in Describing Architectures |
|
Formal Methods in Describing Architectures | |
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 | |
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 | |
Global Software Development Working Session |
|
SATURN 2006 Working Session. | |
Global Software Development Working Session (SATURN 2006) |
|
Presented: April 2006 | |
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. | |
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 | |
Leadership and Management in Software Architecture Leadership and Management in Software Architecture |
|
Leadership and Management in Software Architecture Leadership and Management in Software Architecture | |
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 | |
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 | |
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. | |
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 | |
Perils and Joys of Reconstructing Architectures, The |
|
The Perils and Joys of Reconstructing Architectures | |
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 | |
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 | |
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 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 | |
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 | |
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 | |
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 | |
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 | |
Scenario-Based Analysis of Software Architecture |
|
Scenario-Based Analysis of Software Architecture | |
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. | |
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 | |
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 | |
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, | |
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 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 | |
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 | |
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 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 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 | |
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 | |
Working Session: Software Architecture Competence |
|
presentation made by Paul Clements at the SATURN 2007 Working Session "Architecture Competence," May 15, 2007 | |
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 | |
Email: info@sei.cmu.edu
Call: 412-268-2358