This technical note defines intellectual property (IP) and insider theft of IP, gives a snapshot of the insiders involved in these cases, summarizes some of the cases, and provides recommendations for mitigating the risk of similar incidents of insider threat.
05/10/2013This information sheet describes the SOA Migration, Adoption, and Reuse Technique (SMART), its benefits, and the SMART "family members."
05/09/2013This Software Assurance Competency Model helps create a foundation for assessing and advancing the capability of software assurance professionals.
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
05/30/2012This report describes the first CERT RMM Users Group (RUG) Workshop Series and relays the experiences of participating members and CERT staff.
05/03/2012This report presents an example of an enterprise architectural pattern, Increased Monitoring for Intellectual Property (IP) Theft by Departing Insiders, to help organizations plan, prepare, and implement a means to mitigate the risk of insider theft of IP.
05/01/2012This report details the CERT Program's Source Code Analysis Laboratory (SCALe), a proof-of-concept demonstration that software systems can be conformance tested against secure coding standards, and provides an analysis of selected software systems.
05/01/2012This technical report describes the Insider Threat Security Reference Architecture (ITSRA), an enterprise-wide solution to the threat to organizations from its own insiders. The ITSRA draws from existing best practices and standards as well as from analysis of real insider threat cases to provide actionable guidance for organizations to improve their posture against the insider threat.
04/25/2012This presentation introduces the STRategic Ecosystem Analysis Method (STREAM), which uses the architecture construct of a view to reduce model complexity.
03/27/2012This technical note maps CERT® Resilience Management Model (CERT®-RMM) process areas to certain National Institute of Standards and Technology (NIST) special publications in the 800 series.
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.
03/05/2012This paper gives substance and explicit meaning to the terms trust and trustworthy as they relate to automated systems and to embedded systems in particular.
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?
02/27/2012The SEI has developed the Mission Risk Diagnostic (MRD) to assess risk in interactively complex, socio-technical systems across the life cycle and supply chain.
02/16/2012This white paper describes an approach for deriving measures of software security from well-established and commonly used standard practices for information security.
02/13/2012This report presents the foundational concepts of a risk-based approach for software security measurement and analysis and provides an overview of the IMAF and the MRD.
01/27/2012This January 2012 webinar discusses SEI efforts to improve acquisition program staff decision making in order to reduce program cost, schedule, and quality failures.
01/27/2012The Insider Threat Center at CERT, which has been researching insider threats since 2001, has built an extensive library and comprehensive database containing more than 700 actual cases of insider cyber crimes. This presentation will describe findings from our analysis of three primary types of insider cyber crimes: IT sabotage, theft of information, and fraud. All CERT insider threat research focuses on both the technical and behavioral aspects of actual compromises.
01/26/2012This book describes CERT’s findings in practical terms, offering specific guidance and countermeasures that can be immediately applied by senior officials within any organization.
01/20/2012This report defines malicious insiders and organized crime and provides a snapshot of who malicious insiders are, what and how they strike, and why.
12/30/2011This research demonstrated the effectiveness of various statistical techniques for discovering quantitative data anomalies.
12/30/2011The method of quantifying uncertainty described in this report synthesizes scenario building, Bayesian Belief Network (BBN) modeling and Monte Carlo simulation into an estimation method that quantifies uncertainties, allows subjective inputs, visually depicts influential relationships among program change drivers and outputs, and assists with the explicit description and documentation underlying an estimate.
12/30/2011The information in this report is intended to help program managers reason about actions they may need to take to adapt and comply with the Section 804 NDAA for 2010 and associated guidance.
12/21/2011This technical note, which builds on two previous reports, describes how implementation-level processes can provide the necessary context for identifying and defining measures of operational resilience.
10/31/2011This technical note addresses some of the key issues that either must be understood to ease the adoption of Agile or are seen as potential barriers to adoption of Agile in the DoD acquisition context.
10/11/2011This technical note presents an insider threat pattern on how organizations can combat insider theft of intellectual property. The technical note describes how to use the centralized log storage and indexing engine Splunk to detect malicious insider behavior on a network.
10/05/2011This technical note focuses on software acquisition and development practices related to the evaluation of products before, during, and after implementation. From engagements with numerous DoD acquisition programs, it has been observed that a number of recurring issues reduce the effectiveness of how software-reliant products are evaluated. An acquisition effort consists of identifying the customer’s needs, selecting or developing a product that is responsive to those needs, and then evaluating the product to determine if it properly addresses the identified needs. This technical note describes the Product Evaluation (verification, validation, and certification) process including test, reviews, and formal methods. It also makes the argument that Product Evaluation should not be deferred until after a product has been built, but should begin as soon as the customer’s needs have been identified and should continue throughout the acquisition effort
09/30/2011The CERT Research Report highlights our accomplishments and activities in successfully executing our research strategy.
09/16/2011This book is the first comprehensive compilation of code-level requirements for building secure systems in JAVA. Organized by CERT’s software security experts, it covers every facet of secure software coding with Java 7 SE and Java 6 SE.
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/18/2011How to Sell Process Improvement
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.
08/10/2011Because of the anonymity provided by networked devices, our families are more likely to be attacked, be victims of theft, be subjected to inappropriate people or materials, or become involved unknowingly in illegal activities over a networked device than they are in person. This document discusses various dangers to be aware of and safeguards to reduce the risk of these dangers.
07/26/2011In this report, Resilient Enterprise Management (REM) team members suggest a set of top ten strategic measures for managing operational resilience. These measures derive from high-level objectives of the ORM system defined in the CERT® Resilience Management Model, Version 1.1 (CERT®-RMM).
07/20/2011This report describes standard noncommercial software licensing alternatives as defined by U.S. government and Department of Defense (DoD) regulations. It also suggests an approach for objectively identifying agency needs for license rights and the appropriate license type for systems with noncommercial computer software or as standalone software in the DoD environment.
06/07/2011A one-page brochure about the SEI's hands-on software architecture course.
06/02/2011This report presents research about insider theft of intellectual property.
04/29/2011This report describes the November 2010 Trusted Computing in Embedded Systems Workshop held at Carnegie Mellon University.
04/21/2011This document, first in the Best Practices for National Cyber Security series, provides information that interested organizations and governments can use to develop a national incident management capability.
03/31/2011This report, the third volume in the Software Assurance Curriculum Project sponsored by the U.S. Department of Homeland Security, provides sample syllabi for the nine core courses in the Master of Software Assurance Reference Curriculum.
03/24/2011Presented at SEPG North America 2011 on Thursday, March 24
03/24/2011Presented at SEPG North America 2011 on Thursday, March 24
02/28/2011This report explores the interdependencies among common language, business goals, and soft-ware architecture as the basis for a common framework for conducting evaluations of software technical solutions.
02/25/2011This 2011 report presents the findings of an SEI study that have been implemented in a system for malware analysis and improved capabilities for behavior computation in other applications.
02/18/2011This report provides an overview of techniques employed by malicious insiders to steal intellectual property, including the types of assets targeted and the methods used to remove the information from a victim organization’s control. The report closes with a brief discussion of mitigating factors and strategic items that an organization should consider when defending against insider attacks on intellectual property.
02/08/2011This report provides detection and prevention methods to counter an approach that a focused attacker would need to take in order to breach an organization through web-based protocols.
01/28/2011This information sheet describes the Architecture Tradeoff Analysis Method (ATAM.)
01/17/2011This technical note examines the Trusted Platform Module, which arose from work related to the Independent Research and Development project "Trusted Computing in Extreme Adversarial Environments: Using Trusted Hardware as a Foundation for Cyber Security."
01/14/2011This 2011 report seeks to demonstrate how a method for modeling previous insider crimes can create informed candidate technical controls and indicators.
01/11/2011This 2010 report considers current practices in software supply chain analysis and suggests foundational practices that can reduce risk in the supply chain.
12/31/2010This report provides guidance for appraisers and appraisal teams unfamiliar with TSP+ when conducting SCAMPI appraisals within organizations that use TSP+ as a foundational practice.
12/31/2010This 2010 report describes the (AIM which helps an organization to implement high-performance, high-quality CMMI practices much more quickly than industry norms.
12/31/2010This 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/30/2010This book discusses the importance of knowledge work to the success of modern organizations and explains the necessary steps for reshaping the way in which software development is conducted.
12/28/2010The Source Code Analysis Laboratory (SCALe) tests software applications for conformance to one of the CERT® secure coding standards. Though SCALe can be used in various capacities, it is particularly significant for conformance testing of energy delivery systems because of their critical importance.
12/28/2010This report presents a taxonomy of operational cyber security risks. This report discusses the harmonization of the taxonomy with other risk and security activities.
12/17/2010This report synthesizes presentations, discussions, and outcomes from the "Beyond Technology Readiness Levels for Software" workshop from August 2010.
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/12/2010This book presents best practices for managing the security and survivability of people, information, technology, and facilities. It integrates these into a unified CMM that encompasses security, business continuity, and IT operations.
11/11/2010This report explores the value of enhancing typical strategic planning techniques with the CSF method and scenario planning.
11/09/2010This 35-minute software architecture modeling demonstration describes an approach for virtual integration in system development.
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.
10/05/2010In this webinar Greg Porter and Randy Trzeciak, discuss the effects of the new regulations on the health-care industry and some of the essential elements that healthcare technology executives should consider in order to secure patient information and systems from external threats. As well as, the increasing risks of insider threat within organizations, the key factors influencing an insider's decision to act, the technical and non-technical indicators and precursors of malicious acts, and the countermeasures that could improve the survivability and resiliency of the organization. (1 hr:31 mins)
09/30/2010This report describes key elements in systems thinking, provides an introduction to general systems archetypes, and applies these concepts to the software acquisition domain.
09/30/2010This report documents ideas and recommendations for improving the overall acquisition process and presents the actions taken by project managers in several programs to develop, staff, and obtain approval for their systems.
09/30/2010This report provides suggestions for documenting service-oriented architecture-based systems based on the Views & Beyond (V&B) software documentation approach.
09/30/2010This book provides the most complete and current guidance on how to capture a software architecture in a commonly understandable form.
09/29/2010This 2010 report begins a dialogue and establishes a foundation for measuring and analyzing operational resilience.
09/22/2010Greg Porter and Randy Trzeciak provide some essential elements that healthcare technology executives should consider in order to secure patient information and systems from external threats.
08/31/2010This report contains a master of software assurance curriculum that educational institutions can use to create a degree program or track.
08/31/2010This report focuses on an undergraduate curriculum specialization for software assurance.
08/31/2010This 2010 report is a guidebook for conducting a Measurement and Analysis Infrastructure Diagnostic (MAID) evaluation.
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.
08/18/2010This report details a framework that documents best practices for risk management and an approach for evaluating a program’s risk management practice in relation to this framework.
07/30/2010This 2010 report explores how the SQUARE process can be adapted for privacy requirements engineering in software development.
07/28/2010Rich Caralli, architect of CERT’s Resilience Management Model (CERT RMM), will describe how an organization can use the RMM to transform its operational resilience.
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 document -- first in the Best Practices for National Cyber Security Series - provides insight that interested organizations and governments can use to begin to develop a national incident management capability.
06/30/2010This 2010 report describes results from two recent studies conducted by the SEI to survey the measurement and analysis activities of software systems development organizations.
06/30/2010This report synthesizes presentations and discussions from a 2010 workshop to discuss product line practices and operational accomplishments.
06/29/2010In this webinar, Robert W. Stoddard and David Zubrow summarize critical lessons learned from several large corporations in both the content and delivery of Six Sigma training.
06/17/2010This 2010 report explores the questions: Can Agile be used in the DoD environment? If so, how?
06/16/2010This webinar will discuss an ongoing SEI effort to develop an approach for assessing software supply chains and identifying the associated software assurance risks. (48 mins)
06/07/2010This report examines how data rights issues were addressed in the TSAT program, reviews additional concerns posed by the use of commercial software in the TSAT program’s Space Segment, and reviews data rights concerns for software incorporated in the GPS program.
06/07/2010The CERT Oracle Secure Coding Standard for Java provides guidelines for secure coding in the Java programming language. This report documents the portion of those Java guidelines that are related to concurrency.
06/04/2010This report describes a managed string library for the C programming language.
06/01/2010Description of a framework (Survivability Analysis Framework) used to examine the elements of an operational process and evaluate the survivability and effectiveness of the linkage among roles, dependencies, constraints, and risks to achieve critical operational capabilities.
05/25/2010In this 2010 paper, Grady Campbell - delivered at the 7th Acquisition Research Symposium - argues that a new approach to acquisition is needed that recognizes that hiding uncertainty is detrimental to success.
05/25/2010presentation given at the 7th Annual Acquisition Research SymposiumNaval Postgraduate School, Monterey, CA, May 2010
05/21/2010This report presents the CERT-RMM, an approach to managing operational resilience in complex, risk-evolving environments.
05/20/2010A method for identifying network behavior that my be a sign of coming internet-wide attacks is presented.
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.
05/14/2010This white paper is an executive overview of the business value in harmonizing process improvement efforts when multiple improvement technologies, models and standards are in use. It proceeds with an overview of a harmonization approach that reaches from strategy to tactics and connects enterprise and discipline specific improvement.
05/04/2010one hour overview presented as a DoD and NDIA System-of-Systems Engineering Collaborator’s Information Exchange (SoSECIE) Webinar on May 18, 2010
05/04/2010Keynote presentation by Donald Firesmith at SESS’10, as part of the 32nd ACM/IEEE International Conference on Software Engineering (ISCE’2010) in Cape Town, South Africa.
05/04/2010presentation given at the 22nd Annual Systems and Software Technology Conference (SSTC 2010) in Salt Lake City, Utah on April 26-29, 2010.
05/04/2010presentation given at the 32nd International Conference on Software Engineering 4 May 2010
04/30/2010presentation given by William Novak and Ray Williams at the 2010 Systems and Software Technology Conference (SSTC) on April 29, 2010
04/30/2010In this 2010 presentation, Michael Bandor and Suzanne Garcia-Miller focus on software issues and shortfalls observed during the DoD Technology Readiness Assessment (TRA) processes.
04/30/2010Bryce Meyer and James Wessel provide a 10-step method for planning/assessing software performance, allowing for respective improvement of architecture and test processes.
04/30/2010James Wessel focuses on software measurement practices that Army acquisition organizations find useful for software issue identification, tracking, and active control of programs.
04/30/2010Terry Roberts addresses why R&D in cyber and software engineering is different, how to research the federal lab landscape for opportunities, and how focus our R&D initiatives.
04/06/2010presentation made by Patricia Oberndorf Thomas Merendino, & Soumya Simanta at the at the Systems and Software Technology Conference, Salt Lake City, UT, April 26, 2010
04/06/2010presentation made by Patricia Oberndorf & Carol Sledge at the Systems and Software Technology Conference, Salt Lake City, UT, April 27, 2010
04/06/2010This presentation was given by Patricia Oberndorf and Carol A. Sledge of the Software Engineering Institute (SEI) on April 6, 2010 at the IEEE Systems Conference in San Diego, CA.
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.
01/18/2010When problems are detected in programs, everyone needs to listen and work together towards a solution. Shooting the messenger only delays the process, and hurts program morale.
01/12/2010The Process Improvement in Multimodel Environments (PrIME) project will span a breadth of topics that are needed for an organization to be successful with process improvement in multimodel environments. The project will concentrate on several subsets of models and standards that are commonly used in industry, such as Six Sigma, CMMI®, Lean, and Agile methods.
12/31/2009Criteria and standards to certify an organization as a COE are presented in this Carnegie Mellon Software Engineering Institute preliminary report.
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
11/17/2009This report explores the lack of agreement among SCAMPI Lead Appraisers about what “artifact quality” means in the SCAMPI process context.
11/17/2009This report explores the lack of agreement among SCAMPI Lead Appraisers about what “process quality” means in the SCAMPI process context.
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.
10/15/2009This April 2009 whitepaper focuses on the problems of underspending, which can result in funds being shifted from one acquisition program to another.
10/15/2009When time and budget are tight, it's tempting to follow the "happy path" in testing. But be careful: it may be a path that brings your program great unhappiness.
09/30/2009This 2009 report contains a series of observations and their associated lessons learned from a large, multi-segment, software-intensive system.
08/24/2009The Personal Software Process (PSP) body of knowledge (BOK) contained in this report provides guidance to software professionals who are interested in using proven-effective, disciplined methods to improve their personal software development process.
08/13/2009Led by Robert Seacord, the Secure Coding Initiative (SCI) within CERT works with software developers and software development organizations to eliminate vulnerabilities resulting from coding errors before software becomes operational. SCI is developing secure coding standards for commonly used programming languages such as C, C++, and Java. These standards can be used to improve and assess the security and overall quality of software through training, automated analysis, code review, and other processes. (59 mins)
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.
08/01/2009Being Your Own Boss—Part IV: Being a Victim
07/10/2009This SEI report describes the results of a joint effort to build a business case using high maturity measurement approaches that require limited measurement effort.
07/10/2009People CMM (Version 2)
06/30/2009This paper explores how continued use of the acquisition roadmaps opens up the potential for running into program pitfalls (programmatic IEDs) that aren’t acknowledged on the map at hand.
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.
06/01/2009This report summarizes the findings of a study conducted for the Army to find and describe software measurement practices that are being used successfully.
06/01/2009The 2009 report defines and communicates software engineering and management events necessary to support the successful acquisition of software-intensive systems.
04/23/2009This April 2009 whitepaper is one in a short series of acquisition failures. This paper focuses on the problems of underspending, which can result in funds being shifted from one program to another.
04/23/2009Planning for a long development period doesn't always solve acquisition scheduling problems. Sometimes it makes them worse.
04/21/2009This paper discusses the application of assurance cases as a means of building confidence that the software design of a complex system of systems will actually meet the operational objectives set forth in the project’s top-level requirements.
04/20/2009Donald Firesmith of the SEI presented a one-day tutorial in the Method Framework for Engineering Systems Architectures (MFESA) at the 2009 SSTC in April 2009.
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/24/2009This presentation was given by Joe Wickless of the Software Engineering Institute (SEI) in March 2010 at SEPG North America 2009, held in San Jose, CA.
03/23/2009Tutorial: The Method-Framework for Engineering System Architectures (MFESA). Delivered by Donald Firesmith at the IEEE International Systems Conference, March 23-26, 2009.
03/23/2009This March 2009 presentation, An Innovative Requirements Solution, was presented by Ira Monarch, Dennis Goldenson, and Robert W. Stoddard at SEPG North America 2009.
03/23/2009This brief tutorial of the Method Framework for Engineering System Architecture was delivered in March 2009 at the IEEE International Systems Conference by Donald Firesmith.
03/06/2009When projects attempt to please too many customers, complexity mounts, schedules slip, costs expand ... and no one is happy.
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)
03/01/2009This 2009 SEI report describes a set of secure design patterns, which are meant to eliminate the accidental insertion of vulnerabilities into code.
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.
02/01/2009This 2009 report contains results from a survey of high maturity organizations conducted by the Software Engineering Institute (SEI) in 2008.
01/01/2009This 2009 document describes the tenets of high-fidelity e-learning, describes how VTE reflects these, and summarizes how organizations have used and are using VTE.
12/10/2008A tutorial on the Method Framework for Engineering System Architectures (MFESA) delivered at ICSSEA 2008 on December 10, 2008.
12/01/2008This survey quantifies the relationship between the application of Systems Engineering (SE) best practices to projects and programs, and the performance of those projects and programs.
11/18/2008A 2008 video presenting an overview of the SEPG conference.
11/15/2008Presentation by Kenneth Nidiffer, Director of Strategic Plans for Government Programs (SEI), from the 8th Annual CMMI Technology Conference and User Group, November 2008.
11/12/2008A presentation made by Rick Barbour and Barbara Tyson at the 8th Annual CMMI Technology and Users Conference in November 2008. The Last Phase of Process Change - Deployment
11/01/2008This report describes common errors in measurement and analysis, and discusses the need for a criterion-based assessment method that allows organizations to evaluate their measurement programs.
10/18/2008Kenneth Nidiffer delivered this presentation at the 11th Annual Systems Engineering Conference in October 2008.
10/14/2008This book documents the first official release of the CERT C Secure Coding Standard, which itemizes those coding errors that are the root causes of software vulnerabilities in C.
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.
10/10/2008Presented: October 2008
09/22/2008Applying more pressure on staff can temporarily increase productivity, but burnout soon sets in.
09/22/2008From the Acquisition Support Program, one in a series of short papers on acquisition patterns of failure. Acquisition Archetype: Underbidding the Contract
09/17/2008presented at SOAPL 2008: Service-Oriented Architectures and Software Product Lines - Putting Both Together, Limerick, Ireland, September 8-12, 2008
09/08/2008Renewing the Product Line Vision was presented by Brady Campbell (SEI) at the 12th International Software Product Line Conference in September 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.
08/01/2008How Mexico is Doing It
08/01/2008The purpose of this 2008 document is to preview a core set of activities and outputs that define a MAAP assessment.
07/18/2008In this presentation, currently available strategic and tactical methods for multi-model improvement are presented. (1 hr:9 mins)
07/01/2008Presented: July 2008
06/11/2008In this podcast, Brian Gallagher, former director of the Acquisition Support Program at the SEI, discusses what business leaders need to know when acquiring or purchasing software, along with implications for security.
06/04/2008presentation from the Second Annual Systems Engineering Conference of the National Reconnaissance Office on June 4, 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/2008A Specification for Software Project Performance Measures
06/01/2008Building More Secure Software
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.
06/01/2008This report describes a study to evaluate the efficacy of the CERT Secure Coding Standards and source code analysis tools in improving the quality and security of commercial software projects.
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.
05/08/2008case study presented at the Hard Questions for Process Improvement in Multimodel Environments Workshop on May 8, 2008
05/08/2008opening remarks from the Hard Questions for Process Improvement in Multimodel Environments Workshop on May 8, 2008
05/08/2008"Breakout Session -- Strategy Rounds 1 and 2" presentation from the Hard Questions for Process Improvement in Multimodel Environments Workshop on May 8, 2008
05/08/2008"Breakout Session -- Architecture" presentation from the Hard Questions for Process Improvement in Multimodel Environments Workshop on May 8, 2008
05/08/2008"Breakout Session Output -- Implementation Issues" presentation from the Hard Questions for Process Improvement in Multimodel Environments Workshop on May 8, 2008
05/08/2008"Breakout Session -- Technology Relationships" presentation from the Hard Questions for Process Improvement in Multimodel Environments Workshop on May 8, 2008
05/08/2008summary of the SEI approach of harmonizing multiple models, presented at the Hard Questions for Process Improvement in Multimodel Environments Workshop on May 8, 2008
05/08/2008This white paper is the first in a five-part series dedicated to examining problems organizations encounter when operating in multimodel environments and the current process improvement approaches such organizations need to consider.
05/08/2008white paper that was presented at the Hard Questions for Process Improvement in Multimodel Environments Workshop on May 8, 2008
05/05/2008A system designer faces several challenges when specifying security for distributed computing environments or migrating systems to a new execution platform.
05/01/2008In this paper, the authors present analytical techniques to model and validate security protocols for enforcing confidentiality and integrity.
05/01/2008With this book, you can select from a number of sound practices likely to increase the security and dependability of your software, both during its development and its operation.
05/01/2008This 2008 report describes how SQUARE can be incorporated in standard life-cycle models for security-critical projects.
05/01/2008An SEI team built an analysis framework to evaluate the quality of the linkage among roles, dependencies, constraints, and risks for critical technology capabilities in the face of change. This report outlines the team's progress.
05/01/2008This presentation was given by Linda Levine and Bill Novak of the SEI’s Acquisition Support Program at the IEEE Systems Conference in April 2008.
04/01/2008Making SIMPLE Decisions about Software Product Lines
03/20/2008Presented in September 2008 by Robert Stoddard.
03/20/2008Presented by Dennis Goldenson and Bob Stoddard in March 2008.
03/20/2008Presented in September 2008 by Robert Stoddard.
03/12/2008Presented by Don Firesmith on March 12, 2008
03/10/2008All hands on deck helps put out the immediate blazes threatening projects, but falling into a routine of constant firefighting is not the way to guide a project across the finish line.
03/04/2008Everyone intends the best in project-driven marriages of PMOs and contractors, but good intentions can't overcome the hostility generated by loss of trust and squabbles in poorly developed relationships.
03/04/2008Some programs take on a life of their own--privileged, and woven into an organization's existence. But when "sacred cow" projects begin to go wrong, that privilege and protection makes fixing them even more difficult.
03/01/2008Cyber Attack Scenarios Test Responses
03/01/2008Being Your Own Boss—Part V: Building Trust
03/01/2008This technical note describes the adaptation of the Mission Diagnostic (MD) necessary for a customer and the lessons we learned from its use.
03/01/2008This 2008 document describes the core set of activities and outputs that defines mission diagnostic protocol (MDP).
03/01/2008This 2008 report provides a quick evaluation of the potential for success of an organization’s computer security or cyber-security incident management capability (IMC).
03/01/2008This paper was presented at the Hard Questions for Process Improvement in Multimodel Environments Workshop on May 8, 2008. This white paper is the third in a five-part series dedicated to examining problems organizations encounter when operating in multimodel environments and the current process improvement approaches such organizations need to consider.
03/01/2008This paper was presented at the Hard Questions for Process Improvement in Multimodel Environments Workshop on May 8, 2008. This white paper is the third in a five-part series dedicated to examining problems organizations encounter when operating in multimodel environments and the current process improvement approaches such organizations need to consider.
03/01/2008This paper was presented at the Hard Questions for Process Improvement in Multimodel Environments Workshop on May 8, 2008. This white paper is the third in a five-part series dedicated to examining problems organizations encounter when operating in multimodel environments and the current process improvement approaches such organizations need to consider.
02/01/2008Tackling the Growing Botnet Threat
02/01/2008This report presents findings of a study of RTSCE software-intensive systems issues and develop recommendations for effectively dealing with those issues.
01/01/2008Performance Improvement: It’s a Small World After All
01/01/2008Resources for Getting Started with Software Product Lines
12/25/2007The tools compared in this discussion, the Unified Modeling Language (UML) and the Architecture Analysis and Design Language (AADL), facilitate the modeling of software architecture and provide elements to understand it.
12/01/2007This 2007 document is a draft in progress of a technology vision and roadmap to improve the ability of the DoD and industry to deliver needed SiS capability in a timely, cost-effective, and predictable manner.
12/01/2007This report extends the quality concepts first articulated in "A Software Quality Framework (SQF)" developed in the early 1980s for the DoD by Baker and colleagues.
11/01/2007presented at the CMMI Technology Conference, November 2007
11/01/2007This survey quantifies the relationship between the application of systems engineering best practices to projects and the performance of those projects.
10/25/2007From the Acquisition Support Program, one in a series of short papers on acquisition patterns of failure.
10/01/2007The SLA BOK identifies the competencies needed to carry out the method requirements and guidelines detailed in the MDD (Method Definition Document).
10/01/2007This 2007 report presents a COTS and Reusable Software Management Plan that can serve as a guide for how to manage multiple COTS and other reusable software components in complex systems.
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 2007 implementation guide, geared toward senior leaders, provides prescriptive guidance for creating and sustaining an enterprise security governance program.
09/01/2007This 2007 report describes SQUARE, and outlines other methods used for identifying security requirements and compares them with SQUARE.
09/01/2007This document summarizes the content shared at the 2007 SEPG conference and identifies several subsequent steps underway toward strengthening those ties.
09/01/2007This 2007 report describes an extension to the C programming language to introduce the notion of ranged integers, that is, integer types with a defined range of values.
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.
08/01/2007Spider-Man 3 Developers to Discuss Process-Improvement Experience in SEPG Keynote
07/01/2007Mitigating the Risk of Using Service-Oriented Architectures
07/01/2007Lessons Learned about Software Architecture
07/01/2007This report discusses how AADL can be used to model system families and configurations of system and component variants.
06/01/2007Being Your Own Boss—Part III: Knowledge Work
06/01/2007Survivability Challenges for Systems of Systems
06/01/2007A presentation with audio
05/31/2007Full day tutorial presented in May 2007
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/2007OCTAVE Allegro Speeds Up the Risk Assessment Process
05/01/2007ArchE-the Architecture Expert
05/01/2007Being Your Own Boss—Part II: The Autocratic Manager
05/01/2007Software Product Lines FAQs Part VI: Using Software Product Lines with Other Approaches
05/01/2007This 2007 report highlights the design considerations and requirements for OCTAVE Allegro based on field experience with existing OCTAVE methods.
05/01/2007This document presents metrics to provide a baseline or benchmark of incident management practices.
05/01/2007This report explores the transformation of the disciplines of security and business continuity into processes designed to support and sustain operational resiliency.
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.
05/01/2007This technical report describes how to use +SAFE to appraise an organization's capability in developing, sustaining, maintaining, and managing safety-critical products.
04/19/2007Coming Soon: A New Version of the SEI's Framework for Software Product Line Practice
04/01/2007Computer Forensics for Business Leaders: A Primer
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/22/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/2007Being Your Own Boss—Part I: The Ideal Job
03/01/2007Presented: March 2007
03/01/2007This 2007 report provides an overview of the concepts and foundations of MOSAIC, a suite of advanced, risk-based analysis methods for assessing complex, distributed programs, processes, and information-technology systems.
03/01/2007This report presents an overview of CERT progress in developing a system dynamics model of organizations’ typical use of change and access controls to support IT operations.
03/01/2007This 2006 report describes the MERIT insider threat model and simulation results.
03/01/2007Four studies from 2006 that explore an issue relevant to the survivability of networks which are systems of systems.
02/27/2007presentation given at the 6th IEEE International Conference on COTS-Based Software Systems (ICCBSS) 2007, Alberta, Canada (February-March 2007)
02/01/2007SEI Publishes Framework for Software Process Research
02/01/2007Large-Scale Work – Part VII: Process Discipline
02/01/2007Protecting Against Insider Threat
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/19/2007Learn to use the SAE AADL Standard Model-Based Engineering with SAE AADL
01/12/2007The SAE AADL is an international standard for predictable model-based engineering of real-time and embedded computer systems.
01/01/2007Large-Scale Work–Part VI: The Process
01/01/2007FAQs Part 5: Getting Started
12/01/2006This book brings 27 leaders from academia and industry together to study the implications of both plausible future scenarios and existing process research.
12/01/2006This report examines the psychological, technical, organizational, and contextual factors thought to contribute to espionage and insider sabotage against critical IT systems.
12/01/2006This report revises the steps of the Attribute-Driven Design (ADD) method and offers practical guidelines for carrying out each step.
10/27/2006A tutorial presented by Donald Firesmith at the 9th Annual Systems Engineering Conference, October 23-27, 2006, in San Diego, California.
10/26/2006presentation made at International Council on Systems Engineering (INCOSE) 2007, San Diego, June 24-29, 2007
10/26/2006Presented: March 2007
10/26/2006Presentation by Donald Firesmith (SEI) on QUASAR, V3.0 (February 2008).
10/26/2006Presented: March 2007
10/26/2006Presented: May 2006
10/26/2006Presentation by Brian Gallagher, Director, Acquisition Support Program (SEI) on acquisition support. Provides a number of real-world examples relevant to the defense industry.
10/26/2006Presented: March 2007
10/26/2006Presentation by Brian Gallagher which discusses acquisition archetypes and how they can be used to detect acquisition problems in an organization (April 2008).
10/26/2006Presentation by Neal London, Dr. Carl Sunshine, and Dr. Charles Hammons on using the TSAT approach to service identification, classification, and definition (October 2006).
10/26/2006Presented by Donald Firesmith at SEPG 2006.
10/26/2006presentation given at the 6th IEEE International Conference on COTS-Based Software Systems (ICCBSS) 2007, Alberta, Canada (February-March 2007)
10/26/2006Presented: October 2006
10/26/2006presentation made at the SEPG 2006 symposium, March 6-9, 2006, Nashville, Tennessee
10/26/2006Presented: September 2007
10/26/2006Presented: June 2006
10/26/2006Presented: October 2006
10/26/2006In this 2007 presentation, Brian Gallagher discusses the state of acquisition support and offers advice for better implementing acquisition support programs in an organization.
10/26/2006Peter Capell (SEI) discusses QUASAR, a method of assessing system architecture, and MFESA, a method framework that enables the development of system-specific architecture (2008).
10/26/2006presentation given at the 2007 SEPG Conference, March 2007, Austin, Texas
10/26/2006This SEI presentation – “Using System Archetypes to Identify Failure Patterns in Acquisition” – was delivered by Diane Gibson, Linda Levine, and William E. Novak on May 2, 2006.
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/2006Materials from the 2006 Defense-in-Depth Foundational Curriculum course are useful for system administrators and IT security personnel who would like to step up to the management level.
09/01/2006This 2006 report describes methods for selecting candidate commercial off-the-shelf packages for further evaluation, possible methods for evaluation, and other factors besides requirements to be considered.
09/01/2006This 2006 report contains an example that illustrates the critical importance of recognizing the need for evolutionary design changes in secure and survivable systems.
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.
08/01/2006This presentation on best practices in software architecture was delivered by Paul C. Clements of the Software Engineering Institute (SEI) on July 26, 2006.
07/01/2006This 2006 handbook documents the QUASAR (QUality Assessment of System ARchitectures) method for assessing the quality of the architecture of a software-intensive system.
07/01/2006CERT Launches Secure Coding Standards Web Site
06/13/2006This book isn't an official guide to best practice, and it certainly isn't a textbook. But in a kind of off-beat way, it's an entertaining yet insightful look at some of the things that can really happen in software acquisition.
06/01/2006This 2006 report presents definitions of IDR and FDR, their context in the acquisition life cycle, a comparison of engineering emphasis during IDR and FDR, IDR and FDR pre- and post-conditions, and IDR and FDR criteria and how to apply it.
06/01/2006Governance Issues for a Service-Oriented Architecture
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/31/2006presentation delivered at the Systems & Software Technology Conference (SSTC): Transforming: Business, Security, Warfighting, in Salt Lake City, Utah, 1-4 May 2006
05/31/2006presentation delivered at the Systems & Software Technology Conference (SSTC): Transforming: Business, Security, Warfighting, in Salt Lake City, Utah, 1-4 May 2006
05/31/2006presentation delivered at the Systems & Software Technology Conference (SSTC): Transforming: Business, Security, Warfighting, in Salt Lake City, Utah, 1-4 May 2006
05/01/2006Specifications for Managed Strings
05/01/2006This 2006 report outlines a method for applying the PROxy Based Estimation (PROBE) technique to Structured Query Language (SQL).
05/01/2006This report, published in 2006, discusses questions about sustaining new and legacy systems; the report presents definitions, related issues, future considerations, and recommendations for sustaining software-intensive systems.
05/01/2006This document describes how the Operationally Critical Threat, Asset, and Vulnerability Evaluation (OCTAVE) method has been used and tailored to fit a wide range of organizational risk assessment needs.
05/01/2006Large-Scale Work–Part V: Building Team Ownership
05/01/2006Security Matters [2006 | 05]
05/01/2006Quality Attributes and Service-Oriented Architectures
05/01/2006Meet Ricky & Stick
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/10/2006Whether you are considering the Team Software Process (TSP) or are actively implementing it, this book provides invaluable examples, guidelines, and suggestions you need to get started as a team coach.
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 2006 report explores the questions, "What constitutes risk?" and "What factors put operational missions at risk?"
04/01/2006This report, published in 2006, describes the fundamental elements and benefits of a process approach to security and operational resiliency and provides a notional view of a framework for process improvement.
04/01/2006This report examines selected aspects of autonomic computing and explores some of the strengths and weaknesses of that technology.
04/01/2006This 2006 report presents an approach to detecting scans against, or passing through, very large networks.
04/01/2006FAQs Part 4: Product Lines in the Context of Acquisition
03/09/2006In this 2006 presentation, Brian Gallagher, Director of the Software Engineering Institute’s (SEI) Acquisition Support Program (ASP) provides an overview of the ASP.
03/07/2006Presented at SEPG 2006 by Stuart Feldman, Vice President, Computer Science, IBM Research
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/01/2006This 2006 report presents an analysis of what is meant by scalability and a description of factors to be considered when assessing the potential for system scalability.
03/01/2006Strategic Architecting
03/01/2006Presented: March 2006
03/01/2006Initiative Advocates Building Security In from the Start
03/01/2006This report describes the results of a preliminary investigation into measures for software architecture.
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.
02/01/2006Security Changes Everything
02/01/2006New CERT “Virtual Training Environment” Provides Online Information Security Education
02/01/2006How Much Security Is Enough?
01/02/2006Presented: January 2006
01/01/2006Three Perspectives of Service-Oriented Architectures
01/01/2006FAQs Part 3: Exploring the Issues More Deeply
01/01/2006This 2006 report includes papers from the Proceedings of the First International Research Workshop for Process Improvement in Small Settings workshop, and presents conclusions and next steps for process improvement in small settings.
12/01/2005This 2005 handbook presents guidance for acquisition planning and strategy topics in a condensed form, and references the primary resources available for each topic.
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.
12/01/2005This report describes the results of a controlled experiment that was performed to compare traditional manual methods of comprehension with automated behavior computation using an FX prototype.
11/17/2005Presented: November 2005
11/01/2005Presented: November 2005
11/01/2005This 2005 report presents the Security Quality Requirements (SQUARE) Methodology for eliciting and prioritizing security requirements in software development projects
11/01/2005This 2008 report includes an overview of the First Workshop on Service-Oriented Architectures and Product Lines, workshop position papers, and more.
11/01/2005This report briefly describes these potential software vulnerabilities in Java version 5.
09/27/2005Presented: November 2005
09/12/2005The OPEN Process Framework (or OPF) is an appropriate focused requirements engineering method (REM) that facilitates the search for a mechanism that will support the flexible creation of a number of tailored REMs from a single base.
09/09/2005This book identified a number of root causes for exploited software vulnerabilities and encourages programmers to adopt security best practices that can help prevent current and future attacks on vulnerable systems.
09/02/2005Presented: September 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 2005 report describes a disciplined method and a related automated tool that can be used for the analysis of natural language requirements documents.
09/01/2005This 2005 report presents the concepts and underlying theories behind the Mission Assurance Analysis Protocol (MAAP), highlights results from early piloting of the technique, and outlines future research directions.
09/01/2005This note describes an ARL implementation of two usability scenarios: displaying progress feedback and allowing cancel.
09/01/2005This 2005 report attempts to fill in these gaps in knowledge and experience by presenting an overview of the operational diagnostic life cycle of a system.
09/01/2005This report presents a taxonomy-based method for identifying and classifying risks to operational aspects of an enterprise.
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.
09/01/2005This report describes efforts by the SEI to increase the capacity of institutions of higher education to offer IA and IS courses, to expand existing IA and IS offerings, and to include IA and IS topics and perspectives in other courses.
08/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 2005 report summarizes FX research and development and investigates the impact of FX on software engineering.
07/01/2005This 2005 report provides an overview of a generic FPGA firmware design process and identifies the resulting work products that may be suitable for reuse in future development efforts.
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
06/01/2005This 2005 report examines governance thinking, principles, and approaches and applies them to the subject of enterprise security.
06/01/2005This 2005 report describes IAP, a documented and repeatable process for developing consistent asset profiles.
06/01/2005This 2004 report outlines the ITS, a study of insider incidents to examine actual cases identified through public reporting or as a computer fraud case investigated by the Secret Service.
05/21/2005In this MPEC 2005 presentation, Donald Firesmith of the Software Engineering Institute (SEI) discusses how to achieve quality requirements with reusable software.
05/11/2005Presented: May 2005
05/02/2005Presented: May 2005
05/01/2005What are the drivers for the burgeoning interest in agile methods? Have these drivers stimulated a similar rethinking on other fronts? What have we discovered? In this 2005 paper, the author takes a reflective stance in order to look at these larger issues and patterns.
05/01/2005This paper addresses the problems associated with a lack of a clear security taxonomy by identifying four different types of security-related requirements, providing them with clear definitions, and placing them within an organizing hierarchical taxonomy.
05/01/2005This position paper argues that a successful COTS evaluation process should be based on the principles of method engineering (ME).
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/2005Large-Scale Work–Part IV: The Management System
04/01/2005Large-Scale Work—Part III: The People
04/01/2005The Components of Software Architecture Design and Analysis
04/01/2005FAQs Part 2: Are Product Lines Right for My Organization?
04/01/2005Secure Coding in C and C++: C-Style Strings
04/01/2005New CERT Course and Handbook Detail Electronic Detective Work
04/01/2005Governing for Security: Protect Stakeholder Interests
04/01/2005Social Security Administration Reaps Rewards of Process Improvement
04/01/2005Keynote presentation slides from SEPG 2005 by Watts Humphrey
04/01/2005Debugging the Healthcare System by Dan S. Drawbaugh, CIO, University of Pittsburgh Medical Center (UPMC)
04/01/2005Keynote speech at SEPG 2005 gy Miles Lewitt, Vice President, Intuit Corporation
04/01/2005This video is a recording of the slides presented with the keynote speech at SEPG 2005.
04/01/2005Keynote Speech by Watts S. Humphrey. SEPG 2005
04/01/2005This 2005 technical note provides guidance and procedures for performing robustness testing as part of DoD or federal acquisition programs that have a software component.
03/01/2005Large-Scale Work—Part II: The Project
03/01/2005Analyzing the Reuse Potential of Migrating Legacy Components to a Service-Oriented Architecture
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/2005Shifting Perspective to Achieve and Sustain Enterprise Security
03/01/2005Writing the Book on Process Improvement: An Interview with Watts Humphrey
03/01/2005Using Product Line Analysis to Get Started With Software Product Lines
03/01/2005This 2005 report documents the ways in which the organizational and project management environment for system development can support or reject improved quality requirements elicitation mechanisms.
03/01/2005This 2005 report summarizes discussions and presentations from the Seventh Department of Defense (DoD) Product Line Practice Workshop.
03/01/2005This 2004 report describes the history and experiences of the process improvement initiatives that transformed the AMS Australia organization.
02/01/2005Large-Scale Work—Part I: The Organization
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/2005Governing for Enterprise Security: Security is a Requirement of Being in Business
02/01/2005Watts Humphrey provides information about the benefits of process improvement, as well as examples of organizations that could have used process improvement more effectively.
02/01/2005New Curriculum Fosters Adoption of Software Product Line Practices
02/01/2005Software Acquisition Survival Skills: Helping the DoD and Government Program Offices Improve Acquisition of Software and Systems
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.
02/01/2005This 2005 report includes the draft interpretation guide used for four mini-appraisal pilots and the final enterprise-wide Class A appraisal at Tata Consultancy Services (TCS).
01/01/2005Internet Denial of Service sheds light on a complex form of computer attack that impacts the confidentiality, integrity, and availability of millions of computers worldwide.
01/01/2005Presented: January 2005
01/01/2005A Personal Quality Strategy
01/01/2005Integrating Architecture Methods: The Case of Extreme Programming
01/01/2005Presented: January 2005
01/01/2005Presented: January 2005
01/01/2005A presentation about software acquisition made in January 2005 by Mary Catherine Ward and Joseph P. Elm
01/01/2005Presented: January 2005
01/01/2005Presented: January 2005
01/01/2005Presented: January 2005
01/01/2005Presented: January 2005
01/01/2005Pas de Deux: Making the Two-Part Organization Work
01/01/2005An Introduction to Governing for Enterprise Security
01/01/2005An Adoption Roadmap for Software Product Line Practice
01/01/2005University Hubs Help SEI Spread Information Assurance Curricula and Methods
01/01/2005Enterprise Security Management: Refocusing Security’s Role
01/01/2005This 2004 report provides the detailed guidelines for conducting an OCTAVE-S evaluation.
01/01/2005This 2005 report proposes a classification scheme that uses attribute-value pairs to provide a multidimensional view of vulnerabilities.
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.
12/01/2004This 2004 report itemizes characteristics of common approaches to security that limit effectiveness and success.
11/17/2004Presented: November 2004
11/17/2004Presented: November 2004
11/01/2004Presented: November 2004
11/01/2004This 2004 report describes a general framework for hierarchical cost/benefit analysis aimed at providing acceptable estimations for small companies in their information security improvement projects.
10/01/2004This 2004 technical note describes ways for applying Q methodology, a research method with a proven history for illuminating agreement and differences among individual and group perceptions, to assist software engineering processes.
10/01/2004This report presents a prototype best practice model for performing incident management processes and functions.
09/28/2004This paper describes a taxonomy of these different kinds of safety-related requirements, and clearly and briefly defines and describes each of the above categories of safety-related requirements.
09/01/2004Principles of CASE Tool Integration describes concepts, models, and guidelines for understanding CASE tool integration and analyzes in-depth the CASE tool integration problem.
09/01/2004Analyses of more than 1350 findings drawn from 663 Software CMM appraisals suggest several areas where both managers and engineers would benefit from better guidance about the proper use of measurement and analysis.
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 SEI has constructed a tentative "roadmap" for personnel involved in the systems and software acquisition community. This report describes the characteristics that determine whether a risk diagnostic method qualifies for the roadmap.
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 describes the critical success factor method and presents various theories and experience in applying it to enterprise security management.
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.
05/26/2004Social networks play a key role in the adoption and diffusion of software process improvement as a networked technology. This panel addressed actual examples of SPI networks and identified key characteristics of and roles in these emergent networks.
05/26/2004This paper summarizes the scope of patent protection in the European Union, the United States, and Japan. In doing so, it examines the patentability of computer software as inventions allowed under E.U. and U.S. patent law.
05/14/2004This book details software engineering from the perspective of those involved in the software development process: individuals, teams, customers, and the organization.
05/01/2004Presented: May 2004
05/01/2004This 2004 report describes a way to think about enterprise networks and is intended to aid system administrators so that they can more easily see how technology supports the enterprise’s mission.
05/01/2004This report documents the Self-Assessment Tool for Engineering Environments (SAT-EE) and the Self-Assessment Tool for Engineering Tool Capabilities (SAT-ETC).
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/2004Benchmarking for Improvement in Army Acquisition
03/01/2004The Quality Attitude
03/01/2004This report details Wipro's process improvement activities and evolution of processes and systems over a period of time.
03/01/2004Integrating Architecture Methods: The Case of the Rational Unified Process
03/01/2004Marathon Man
03/01/2004Install and Use Those Anti-Virus Programs
03/01/2004Making the Use of the DoDAF Easier for DoD Organizations
03/01/2004This report analyzes a survey that covered four areas of the acquisition system: the acquirer's environment, the developer's environment, communication between the acquirer and developer, and external factors that could affect the acquisition system.
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.
03/01/2004This handbook helps technical staff members who are charged with administering and securing information systems and networks.
02/01/2004CERT/CC Instrumental in National Security Effort
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/2004The Goal of Computer Security or What's Yours is Yours Until You Say Otherwise!
02/01/2004This report describes the process of architecture reconstruction using the Dali architecture reconstruction workbench.
02/01/2004This 2004 paper documents some of the challenges and risks facing programs or organizations trying to help small manufacturing enterprises (SMEs).
01/28/2004A presentation made during the 2004 SIS Conference: Improving Acquisition through COTS Risk Identification.
01/28/2004This 2004 presentation on Software Acquisition Process Improvement was delivered by Donald R. Beyron, Debra Borden (NAVAIR), Gerry Imai (STSC), and John Kennedy (MITRE).
01/28/2004This 2004 presentation on reconsidering the role of systems engineering in DoD software problems was delivered by Grady Campell of the Software Engineering Institute (SEI).
01/28/2004“Acquisition Modeling: The Key to Managing Acquisition Complexity?” was delivered at the 3rd OSD Conference on the Acquisition of Software-Intensive Systems in January 2004.
01/28/2004This 2004 presentation was delivered at the 3rd OSD Conference on the Acquisition of Software Intensive Systems by Richard J. Adams and others of the Aerospace Corporation.
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004A presentation in January 2004 to survey the U.S. railroad industry to benchmark best practices in the acquisition of software-intensive systems.
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/27/2004This 2004 presentation on Guidelines for Acquisition Planning was delivered by Cecilia A. Albert and three others of the Software Engineering Institute (SEI).
01/27/2004In this 2004 presentation, Barry Boehm of the University of California (Los Angeles) discusses early warning indicators in the acquisition of software-intensive systems.
01/27/2004This 2004 presentation on iterative RFP project management was delivered by Chris Armstrong and Bobbi Underbakke of Adaptive Team Collaboration (ADC).
01/01/2004Presented: January 2004
01/01/2004Presented: January 2004
01/01/2004Defective Software Works
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
01/01/2004What is a Distributed Denial of Service (DDoS) Attack and What Can I Do About It?
01/01/2004This paper outlines a successful effort to apply COTS-based engineering principles to a software acquisition by various groups at the SEI.
12/01/2003Some Programming Principles: People
12/01/20033rd International Conference on COTS-Based Software Systems
12/01/2003CERT's Function Extraction Project: Exploring Program Behavior for Security Analysis
12/01/2003Integrating Analysis and Design Methods for the Software Life Cycle
12/01/2003It Takes Two
12/01/2003There IS an Intruder in My Computer—What Now?
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.
12/01/2003This 2003 report describes different organizational models for implementing incident handling capabilities, including each model's advantages and disadvantages and the kinds of incident management services that best fit with it.
11/01/2003This 2003 report examines the OSEK OS, OSEK COM, and OSEK OIL specifications from the perspective of a real-time application developer.
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 2003 report provides an objective study of the state of the practice of incident response, based on information about how CSIRTs around the world are operating.
10/01/2003This report describes the newly revised QAW (Quality Attribute Workshop) and describes potential uses of the refined scenarios generated during it.
09/12/2003presentation from RE'2003 RHAS'03 Workshop, September 12, 2003
09/01/2003Rethinking the Software Life Cycle
09/01/2003presentation from RE'2003 RHAS'03 Workshop, September 12, 2003
09/01/2003The Man with the Plan
09/01/2003Use Care When Reading Email with Attachments
09/01/2003Some Programming Principles: Projects
09/01/2003This 2003 report describes the current state of requirements engineering for survivable systems--systems that are able to complete their mission in a timely manner, even if significant portions are compromised by attack or accident.
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 report describes the development of an approach to reduce the number of program failures attributable to COTS software: the COTS Usage Risk Evaluation (CURE).
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.
09/01/2003A system cannot have high assurance if it has poor security, and thus, requirements for high assurance systems will logically include security requirement as well as availability, reliability, and robustness requirements.
08/01/2003Acquisition Support Program Director answers the question: What is the SEI's long-term strategy for cross-functional integration across the various SEI competencies.
07/01/2003This 2003 report defines key factors to consider in taking an incremental approach to fielding a product line.
07/01/2003This 2003 report documents a recent investigation which characterized the technical and programmatic risks in reusing significant quantities of legacy Ada code in a new system.
07/01/2003This 2003 report focuses on international law related to cybercrime, international information security standards, and software liability issues as they relate to information security for critical infrastructure applications.
06/01/2003What's the Difference Between Product Line Scope and Product Line Requirements?
06/01/2003Use Care When Downloading and Installing Programs
06/01/2003Second International Conference on COTS-Based Software Systems
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/19/2003The AADL standard will include a UML profile useful for avionics, space, automotive, robotics and other real-time concurrent processing domains including safety critical applications.
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.
04/01/2003This 2003 document provides guidance on forming and operating a CSIRT, and helps an organization to define and document the nature and scope of a computer security incident handling service, which is the core service of a CSIRT.
03/01/2003Assumption Management
03/01/2003Components As Products
03/01/2003Can You Prove It?
03/01/2003OCTAVE Users Forum: Helping to Build a Community of Practice
03/01/2003The Acquisition Support Program
03/01/2003Some Programming Principles: Products
03/01/2003Some Programming Principles—Requirements
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.
02/03/2003Presented: February 2003
02/01/2003This report summarizes research on Flow Structures and describes the application of their function-theoretic mathematical foundations to the problem of program behavior calculation.
01/29/2003This January 2003 presentation – “SA-CMM in a Large Complex Program” – was delivered by Lloyd Anderson and Hugh Gray at a Software Engineering Institute (SEI) conference in Washington, D.C.
01/29/2003This presentation was delivered by Jonathan D. Addelston at the Conference on the Acquisition of Software Intensive Systems on January 29, 2003.
01/28/2003This 2003 presentation on reducing system acquisition risk with software architecture analysis and evaluation was delivered by J.K. Bergey, Matt Fisher, and Lawrence G. Jones of the Software Engineering Institute (SEI).
01/28/2003This page contains the keynote presentation by Claude M. Bolton at the Acquisition of Software-Intensive Systems Conference, held from January 28-30, 2003.
01/28/2003In this 2003 presentation, V. Basili and Barry Boehm provide an overview of complex systems of systems, discussing the software benefits, risks, and strategies associated with them.
01/28/2003Presented: January 2003
01/28/2003presentation at the Conference on the Acquisition of Software-Intensive Systems, January 28-30, 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003presentation at the Conference on the Acquisition of Software-Intensive Systems, January 28-30, 2003
01/28/2003presentation at the Acquisition of Software-Intensive Systems Conference, January 28, 2003, in Arlington, Virginia
01/28/2003Presented: January 2003
01/28/2003presentation from the Acquisition of Software-Intensive Systems Conference, January 28-30, 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003presentation from the Acquisition of Software-Intensive Systems Conference, January 28-30, 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003presentation from the Acquisition of Software-Intensive Systems Conference, January 28-30, 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003IPresented: January 2003
01/28/2003Presentation by Dr. Dave Thombs, Pricing & Forecasting Group (PFG), made on January 2003.
01/28/2003Presented: January 2003
01/28/2003This presentation on the experiences and lessons learned in applying the Tri-Service Assessment Initiative Process was delivered by William Bail of MITRE on January 28, 2003.
01/28/2003This 2003 presentation was delivered by Charles R. Armstrong of the Customs Modernization Office at the Conference on the Acquisition of Software-Intensive Systems.
01/27/2003This 2003 presentation was delivered by Melanie Benhoff of Integrity Applications, Inc., in which she presents a number of lessons learned on cooperative government/industry appraisals.
01/26/2003“They Keep Moving the Cheese: A Framework for the Evolutionary Acquisition of Large Software Intensive Systems” was delivered by Cecilia Albert and Lisa Brownsword in 2003.
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/2003The practices recommended in this 2003 report provide organizations with the guidance necessary to knowledgeably engage MSSPs, so they can make informed use of such services.
01/01/2003Presented: January 2003
01/01/2003This presentation provides an overview of the SCAMPI appraisal method.
12/01/2002Managing Risks in Modernizing Legacy Systems
12/01/2002SEI Hosts Software Product Line Conference
12/01/2002OCTAVE Developers Reach Out to Smaller Organizations with OCTAVE-S
12/01/2002E Pluribus Unum
12/01/2002Installing and Using a Firewall Program
12/01/2002Learning from Hardware: Design and Quality
12/01/2002This 2002 report describes the results of explorations into the use of simulation in examining Internet survivability.
12/01/2002This 2002 report provides information to help guide decisions about when COTS products are an appropriate solution—and when they are not.
12/01/2002This report, published in 2002, details the responsibilities that a system must implement to support command cancellation.
11/01/2002This 2002 document is the first release of a full description of the EPIC framework along with its activities and artifacts.
10/01/2002This 2002 report explains survivability concepts, describes a software development life-cycle model for survivability, and illustrates techniques to support survivability goals.
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.
10/01/2002This 2002 report presents abstraction techniques that can be used to build essential models of system behavior in the context of MBV and details a methodology for creating state machine models using those techniques.
10/01/2002The CBAM (Cost Benefit Analysis Method) extends the ATAM framework to elicit and model costs, benefits, and uncertainty.
09/02/2002This report summarizes the results of the CMMI Workshop held May 7-8, 2002.
09/01/2002The Evolution of Quality Attribute Workshops as an Architecture-Evaluation Technique
09/01/2002New Book Helps Organizations Take Charge of Information Security
09/01/2002Software Architecture Book Provides Practical Guidance about Documentation
09/01/2002Carnegie Mellon Educates Next Generation of Information-Security Experts
09/01/2002Product Lines Are Everywhere
09/01/2002File Cabinets and Pig Latin: Guards for Information Assets
09/01/2002Learning from Hardware: Planning
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 report outlines the early results of an approach to support software migration planning that focused on deriving actionable plans for focus areas that were identified in an initial increment of an overall migration plan.
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 summarizes MBV and outlines the responsibilities of engineers engaged in Model-Based Verification.
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.
07/09/2002This book provides organizations with a systematic way to evaluate and manage their information security risks through the use of the OCTAVE approach.
07/01/2002This 2002 paper reports on the study of the Industry/University group (a subgroup of the Working Group on Software Engineering Education and Training) to investigate active collaborations between companies and universities in which non-software professionals and practitioners who lack formal software education are reeducated to become software engineers.
06/01/2002Aligning Business Models, Business Architectures, and IT Architectures
06/01/2002CERT/CC and Secret Service Collaborate on Security
06/01/2002Preventing Security-Related Defects
06/01/2002Is There an Intruder in My Computer?
06/01/2002Surviving Failure
06/01/2002This report provides guidance for documenting the interfaces to software elements.
06/01/2002This 2002 report describes Flow-Service-Quality (FSQ) engineering, an emerging technology for management, acquisition, analysis, development, evolution, and operation of large-scale, network-centric systems.
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 report focuses is on the use of Earned Value in the context of a COTS-Based System (CBS).
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/2002The Internet—Friend or Foe?
03/01/2002The Future of Software Engineering: V
03/01/2002This 2002 report outlines details of past and current architecture reconstruction work on several systems at Nokia.
03/01/2002This 2002 version of the SA-CMM incorporates change requests that have been received, as well as the results of lessons learned from conducting appraisals and from the use of Version 1.02.
01/01/2002This report presents a basic set of guidelines to facilitate the generation of expected properties in the context of Model-Based Verification.
01/01/2002This report describes ways to document the behavior of systems, subsystems, and components of software architecture.
12/20/2001Watts S. Humphrey shows corporate executives and senior managers how to gain control of a software operation and to transform it into a professional businesslike function.
12/01/2001TransPlant: Helping Organizations to Make the Transition
12/01/2001The Internet Security Alliance: Leadership in Information Security
12/01/2001Attack Scenarios: How to Get There from Here
12/01/2001The Future of Software Engineering: IV
12/01/2001This technical note provides guidance for the analysis activity that occurs during the interpretation of results produced by model-checking tools.
12/01/2001This paper describes a risk-mitigation framework for deciding when and how COTS components can be used to build survivable systems.
12/01/2001This special report provides a bibliography of books, articles, and other literature concerning the PSP and TSP methodologies.
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.
11/01/2001This 2001 report describes lessons learned at several organizations that have implemented measurement programs using the Goal-Driven Software Measurement methodology.
10/03/2001This paper discusses the understanding of quality attributes and their application to the design of a software architecture.
10/01/2001This 2001 document describes the processes, activities, artifacts, and deliverables associated with an Engineering Practice Investigation of MBV.
10/01/2001This report provides guidance for defining the scope, formalism, and perspective for applying MBV, a systematic approach to finding defects in software requirements, designs, or code.
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/2001This 2001 report describes a pattern-based approach to facilitate claim generation.
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/2001Everyone's a System Administrator
09/01/2001The Future of Software Engineering: III
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.
08/01/2001This report presents the results of a workshop on real-time systems engineering. The workshop was held as part of the SEI Symposium in Washington, DC, during September 2000.
07/10/2001Presentation from July 2001 on the IDEAL model, an organizational improvement model that serves as a roadmap for initiating, planning, and implementing improvement actions.
06/07/2001This book puts CERT practices and implementations in book form, and offers step-by-step guidance for protecting systems and networks against malicious and inadvertent compromise.
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/2001Securing Information Assets
06/01/2001CERT System and Network Security Practices
06/01/2001The Future of Software Engineering: II
06/01/2001This 2001 paper contains observations, recurring themes, trends, and lessons learned about systems development as derived from real-time/mission-critical programs that have been reviewed over the last three years.
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/2001DoD Instruction 5000.2 introduced innovations throughout the acquisition cycle. To address this, a workshop was held September 2000. This 2001 report summarizes the workshop and presents its recommendations.
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/2001Intrusion Detection Systems
03/01/2001Pursue Better Software, Not Absolution for Defective Products
03/01/2001How the FBI Investigates Computer Crime
03/01/2001The Future of Software Engineering: I
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 2000 paper discusses a model-based architectural approach for improving predictability of performance in embedded real-time systems.
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.
10/01/2000The Simplex Architecture facilitates the building of dependable and upgradable real-time systems. Before using the technology, potential users want to know more about the costs of adopting the Simplex paradigm compared to the benefits of using it. This paper examines Simplex performance and the costs associated with its use.
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.
08/01/2000The SEI surveyed senior acquisition managers about the performance of their organizations, especially on skills and competencies, and issues surrounding the training needed to develop them. The results of the survey are presented in this report.
06/01/2000Quality Attribute Workshop
06/01/2000Cybersleuthing: Means, Motive, and Opportunity
06/01/2000Moving the Goal Posts
05/01/2000This 2000 report describes experiences with modeling the liquid hydrogen subsystem of the space shuttle.
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/2000Countering the Threat of Internet Denial of Service Attacks
03/01/2000A Practical Approach to Improving Pilots
03/01/2000Software Engineering Measurement and Analysis
03/01/2000Removing Roadblocks to Cyber Defense
03/01/2000Survivability Blends Computer Security With Business Risk Management
03/01/2000Survivability Blends Computer Security
03/01/2000Making the Tactical Case for Process Improvement
03/01/2000Justifying a Process Improvement Proposal
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/07/1999A presentation by Watts Humphrey
12/01/1999Software Architecture Evaluation in the DoD Systems Acquisition Context
12/01/1999Protecting Critical Systems in Unbounded Networks
12/01/1999Making the Strategic Case for Process Improvement
11/01/1999This book examines the various stages in the life cycle of a real-world software project in order to aid managers and developers with executing their own projects through CMM.
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.
10/01/1999This report provides guidelines for implementing a software acquisition risk management program that satisfies the goals of the ARM KPA of the SA-CMM.
09/01/1999The Net Effects of Product Lines
09/01/1999The Perils and Joys of Reconstructing Architectures
09/01/1999Eight Key Factors for Successful Technology Collaborations
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
09/01/1999From Y2K to Security Improvement: A Critical Transition
09/01/1999From Y2K to Security Improvement: A Critical Transition
09/01/1999Getting Management Support for Process Improvement
08/01/1999This 1999 report provides guidelines for an organization that is developing a CONOPS document.
08/01/1999This report describes an approach to using Simplex to construct a COTS-based computer system capable of coordinated real-time motion control in a hostile communications environment.
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/1999Delivering on the Promise of Process Improvement
06/01/1999Introduction: Checking In on a Process Improvement Revolution
06/01/1999Using Scenarios in Architecture Evaluations
06/01/1999Software Strategy for Technology Collaborations
06/01/1999Were You Ready for the Melissa Virus?
06/01/1999Doing Disciplined Work
06/01/1999This report presents a description of architecture-centric system development.
04/01/1999Bugs or Defects?
04/01/1999This is an introductory report on the use of model-based verification techniques within software development and upgrade practices.
03/01/1999Analyzing Quality Attributes
03/01/1999Avoiding the Trial-by-Fire Approach to Security Incidents
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/1998What Messages Are You Sending to Vendors?
12/01/1998Representing Software Architecture
12/01/1998Interview with Richard D. Pethia
12/01/1998Security of the Internet
11/01/1998This report presents the results of a study on the practice issues involved in using the Symbolic Model Verifier (SMV) for model checking software systems.
09/01/1998Your Date or Mine?
09/01/1998Are Software Architects Like Building Architects?
09/01/1998Security Matters – Doesn't It?
09/01/1998This 1998 report outlines the technological foundations of model-based verification for engineering software system upgrades.
08/01/1998This 1998 report explores the translation of MetaH into ACME.
07/01/1998This 1998 document discusses rationale behind the need for the Software Acquisition Improvement Framework (SAIF), the elements constituting the SAIF, and the intended operational usage of the SAIF.
06/15/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 report addresses the use of different technologies and an architectural tradeoff approach on a typical En Route system problem.
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.
02/10/1998This book shows you how to develop a preventive culture of disciplined software process improvement within an organization in order to control the quality of its software products.
01/01/1998In this report, we describe the application of an off-the-shelf ORB to two real-time model problems.
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.
08/01/1997This 1997 report contains a software acquisition process maturity questionnaire, intended for those interested in learning about and performing software acquisition process appraisals.
08/01/1997This report describes the results of the Workshop on the State of the Practice in Dependably Upgrading Critical Systems held April 16-17, 1997 at the Software Engineering Institute.
07/01/1997This 1997 report presents a perspective on research in fault tolerance as it relates to dependability in software-based systems and attempts to describe the current state of, and outline future directions for, this broad research field.
06/01/1997This 1997 report synthesizes the presentations and discussions from the 1996 SEI Product Line Practice Workshop.
05/01/1997This column is the last in a series about estimating. This column describes some data on how the PROBE method that is described in these articles has helped engineers make better estimates and do better work.
05/01/1997This report describes a few principles for analyzing a software architecture to determine if it exhibits certain quality attributes.
04/01/1997This column is the tenth in a series about estimating. This column concludes the discussion of how object-oriented techniques can help you estimate and plan your work.
03/03/1997This column is the ninth in a series about estimating. This column continues the discussion of how object-oriented techniques can help you to estimate and plan your work.
02/03/1997This column is the eighth in a series about estimating. This column continues the discussion of how to make software estimates.
01/02/1997This column is the seventh in a series about estimating. This column continues the discussion of how to make software estimates.
01/01/1997This report details the results of two workshops on software architecture evaluation, held at the SEI in 1996.
12/02/1996This column is the sixth in a series about estimating. It continues the discussion of how to make size estimates.
12/01/1996This 1996 version of the SA-CMM incorporates the results of lessons learned from the use of Version 1.0.
11/01/1996Drawing on the author's extensive experience as a senior manager of software development at IBM, this book describes proven techniques for managing technical professionals.
11/01/1996This column is the fifth in a series about estimating. It continues the discussion of how to make size estimates.
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.
10/01/1996This column is the fourth in a series about estimating. It continues the discussion of how to make size estimates.
09/02/1996This is the second of a series of columns on software project estimating. It discusses program size and it provides a general background for all the columns to follow.
07/01/1996This column starts a series on estimating. In this first column, Watts Humphrey talks about why one should make estimates and then briefly discusses the elements of estimating.
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.
03/01/1996This 1996 whitepaper explores how an organization can gain credibility by realistically planning work based on historical performance.
02/01/1996As systems have performance requirements, sometimes dominant and explicit, and other times subordinate and implicit. Despite the pervasiveness and importance of performance requirements, performance problems persist. To help us understand why, we sponsored a workshop in performance engineering and conducted some structured interviews with software contractors. This report summarizes our observations.
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.
09/01/1995This 1995 paper reviews the rate monotonic scheduling theory, examines the architectural requirements for the use of the theory, and provides an application example.
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.
06/01/1995This report presents a paradigm for object-oriented implementation of flight simulators. It is a result of work on the ADA Simulator Validation Program (ASV) carried out by members of the technical staff at the SEI.
05/01/1995This 1994 report discusses the results of a DISA pilot effort to assess the issues involved in implementing a software measurement program across multiple sites and projects.
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 report helps instructors teach rate monotonic analysis (RMA) to graduate and undergraduate software, computer, and electrical engineering students.
01/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.
12/01/1993This 1993 proposes a taxonomy of the coordination mechanisms for the synchronization and communication of concurrent processes.
12/01/1993This 1993 report provides examples of an organization struggling to establish a software measurement program in order to help other organizations with setting up their own programs.
10/01/1993This report provides an overview of two standards that are used for data specification and representation in distributed systems.
08/01/1993This paper presents the structural modeling approach, an application framework and development process for the construction of flight simulators.
06/01/1993Many systems are deemed safety-critical and these systems are increasingly dependent on software. Much has been written in the literature with respect to system and software safety. This report summarizes some of that literature and outlines the development of safety-critical software. Techniques for hazard identification and analysis are discussed. Further, techniques for the development of safety-critical software are mentioned. A partly annotated bibliography of literature concludes the report.
04/01/1993This 1993 paper describes the use of generalized rate monotonic scheduling theory for the design and analysis of a distributed real-time system.
03/01/1993This 1993 module introduces formal specification of concurrent software and verification of the consistency between concurrent programs and their specifications.
06/01/1992This report documents an analysis of the army movement control domain performed by the SEI and a team of experts from the army.
02/01/1992This report presents a set of tests for checking whether an ADA runtime system properly supports certain rate monotonic scheduling algorithms, specifically, the basic inheritance and priority ceiling protocols.
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.
02/01/1992This document provides vocabulary, discusses system failure, describes mechanisms for making systems fault tolerant, and provides rules for developing fault tolerant systems.
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.
12/01/1991This 1991 report presents a design specification method that treats a software architecture as a set of runtime entities.
10/01/1991This 1991 report summarizes workshop discussions about state of the practice in fault tolerant systems and barriers to the deployment of fault tolerant systems.
09/01/1991The purpose of this paper is to introduce a sporadic server algorithm that can be implemented as an application-level task, and that can be used when no runtime or operating system level implementation of the sporadic server is available.
07/01/1991This 1991 report explores issues related to the use of database management technology in support of real-time systems programming.
03/01/1991In this report, we review important decisions in the development of RMA. Our experience indicates that technology transition considerations should be embedded in the process of technology development from the start, rather than as an afterthought.
12/01/1990This 1990 report informally specifies the general functions, data interactions, and timing constraints for an avionics mission control computer system typical of those found in some existing U.S. Navy/Marine Corps aircraft.
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.
07/01/1990This paper illustrates how to build a mathematical model of the schedulability of a real-time system, taking into consideration such factors as preemption, synchronization, non-preemptibility, interrupts, and process idle time.
06/01/1990Boeing Military Airplanes and The Wichita State University became co-acceptors of a copy of DARK for the purpose of demonstrating a port to a 68000-based distributed architecture. This report describes the experiences in accomplishing the port.
06/01/1990This 1990 report describes the results obtained by running Version 1.0 of the Hartstone benchmark, an ADA implementation of one of the requirements, on a number of compiler/target processor combinations.
06/01/1990This 1990 document presents a bibliography of references on domain analysis.
05/01/1990This 1990 paper presents the data structures and algorithms for implementing sporadic servers in real-time systems programmed in ADA.
12/01/1989This report describes the evaluation of four methods for the specification of system and software requirements for time-critical systems.
09/01/1989This 1989 report presents techniques for controlling devices with Ada and several Ada tasking paradigms for managing concurrency.
06/01/1989This 1989 paper defines the operational concept for a series of benchmark requirements to be used to test the ability of a system to handle hard real-time applications.
04/01/1989This 1989 report examines a priority-driven, two-phase lock protocol called the read- or write-priority ceiling protocol.
04/01/1989This 1989 report reviews important results of a priority-based scheduling theory and discusses implications for the Ada tasking model.
04/01/1989This 1989 paper presents a high-level design for implementing the basic priority inheritance and priority ceiling protocols in an ADA runtime system.
04/01/1989A real-time system consists of both aperiodic and periodic tasks. Periodic tasks have regular arrival times and hard deadlines. Aperiodic tasks have irregular arrival times and either soft or hard deadlines. In this paper, we present a new algorithm, the Sporadic Server algorithm, that greatly improves response times for soft-deadline aperiodic tasks and can guarantee hard deadlines for both periodic and aperiodic tasks. The operation of the Sporadic Server algorithm, its performance, and schedulability analysis are discussed and compared with previous, published aperiodic service algorithms.
02/01/1989This 1989 report describes a new design for the Durra runtime environment that addresses these two issues.
01/01/1989This landmark book introduces the author's methods, now commonly practiced in industry, for improving software development and maintenance processes.
12/01/1988This curriculum module provides an overview needed to understand in-depth curriculum modules in the verification and validation area.
12/01/1988This 1988 module introduces formal verification of programs, dealing primarily with proofs of sequential programs, but also with consistency proofs for data types and deduction of particular behaviors of programs from their specifications. This module introduces formal verification of programs, dealing primarily with proofs of sequential programs, but also with consistency proofs for data types and deduction of particular behaviors of programs from their specifications.
11/01/1988This 1988 report reviews results of a priority-based scheduling theory, illustrates its applications with examples, discusses its implications for the Ada tasking model, and suggests workarounds.
11/01/1988This 1988 report discusses a protocol for accomplishing mode change in the context of a priority-driven preemptive scheduling environment.
10/01/1988This 1988 report defines the functional and performance requirements for the inertial navigation system simulator that interfaces with the ECS simulator.
10/01/1988This 1988 document defines the functional and performance requirements for the ECS simulator that interfaces with the inertial navigation system simulator.
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.
03/01/1988This paper discusses real-time design issues that arise when using the priority ceiling protocol for real-time systems.
03/01/1988The priority ceiling protocol is a new technique that addresses the priority inversion problem. Under the priority ceiling protocol, a high priority task can be blocked at most once by a lower priority task. This paper, written in 1988, defines how to apply the protocol to Ada.
12/01/1987This 1987 report addresses issues and questions related to the use of ADA for embedded systems applications.
12/01/1987This 1987 survey provides a summary description of some of the major Ada benchmarks currently available and an evaluation of their applicability to the Real-Time Embedded Systems Testbed Project at the SEI.
12/01/1987This paper considers a class of objects, called incrementally mutable objects, that are intermediate between mutable and immutable objects.
12/01/1987This report summarizes the history, goals, and conclusions of the prototype real-time monitor development effort.
12/01/1987This technical report provides an overview of the results produced in the first year of the ADA Embedded Systems Testbed Project (through September 30, 1987).
12/01/1987This report documents the results obtained from running Ada performance benchmarks on a DEC VAXELN MicroVAX II using the DEC VAXELN Ada compiler.
11/01/1987The purpose of this paper is to provide the reader with some technical information and observations ADA source code, and measurement results based on experimentation with respect to developing a real-time periodic task dispatcher in ADA.
11/01/1987The requirements imposed by flight simulators and good software engineering practice on Ada systems force software engineers to seek new solutions to the problem of monitoring executing software. This report examines some of these requirements and, based on these requirements, defines a subset for implementation as a prototype real-time monitor (RTM).
11/01/1987This 1987 report defines the user interface to the prototype real-time monitor (RTM).
11/01/1987The requirements imposed by flight simulators and good software engineering practice on Ada systems force software engineers to seek new solutions to the problem of monitoring executing software. This report examines some of these requirements and, based on these requirements, defines a subset for implementation as a prototype real-time monitor (RTM).
11/01/1987This report documents the ADA code of the prototype real-time monitor (RTM).
11/01/1987This report lists criteria used in five aspects of the project: hardware configuration, software configuration, real-time application, ADA real-time experiments, and benchmarking and instrumentation techniques.
10/01/1987This report describes the results of implementing an interrupt handler totally in ADA for a MicroVAX II/VAXELN 2.3 target system, the VAXELN 1.1 ADA compiler, and a KWV11-C programmable real-time clock.
06/01/1987This 1987 report offers several recommendations for achieving a balanced policy as to government funded software, privately funded software, and mixed funding software that will meet the mission needs of the DoD while enabling contractors to protect their proprietary interests, and commercialize their software products.
01/01/1987This 1987 report summarizes the significant technical and managerial considerations that affect the maintenance and enhancement of software.
12/01/1986This 1986 report presents a notation and a methodology for specifying the functional and timing behavior of real-time applications for a heterogeneous machine.
09/01/1986This report 1986 recommends regulatory strategies for addressing difficulties the DoD has experienced with respect to legal issues related to software acquisitions.
04/01/1986For more information
Email: info@sei.cmu.edu
Call: 412-268-2358