John K. Bergey

Software Engineering Institute

Publications by John K. Bergey

Architecture-Centric Procurement

April 30, 2013 • Presentation

John K. Bergey Lawrence G. Jones

A presentation from the ninth annual SATURN conference, held in Minneapolis, MN, April 29 - May 3, 2013.
read
A Framework for Software Product Line Practice, Version 5.0

December 31, 2012 • White Paper

Linda M. Northrop Reed Little John McGregor

This document describes the activities and practices in which an organization must be competent before it can benefit from fielding a product line of software systems.
read
Supporting the Use of CERT Secure Coding Standards in DoD Acquisitions

July 01, 2012 • Technical Note

Timothy Morrow Robert C. Seacord John K. Bergey

In this report, the authors provide guidance for helping DoD acquisition programs address software security in acquisitions.
read
Exploring Acquisition Strategies for Adopting a Software Product Line

August 25, 2010 • White Paper

John K. Bergey Lawrence G. Jones

Some 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.
read
Software Product Lines: Report of the 2010 U.S. Army Software Product Line Workshop

June 01, 2010 • Technical Report

John K. Bergey Gary Chastek Sholom G. Cohen

This report synthesizes presentations and discussions from a 2010 workshop to discuss product line practices and operational accomplishments.
read
System of Systems Architecture Centric Acquisition

May 18, 2010 • Presentation

John K. Bergey Michael J. Gagliardi William G. Wood

This tutorial presentation describes the SEI's system of systems architectural engagements and how they can be applied within programs and organizations to improve acquisition success.
read
Implementing Secure Coding Standards in a System Acquisition

December 04, 2009 • Presentation

John K. Bergey Timothy Morrow

In this December 2009 presentation, John Bergey and Tim Morrow explore how required secure coding standards can be specified and integrated in a system acquisition.
read
A Proactive Means for Incorporating a Software Architecture Evaluation in a DoD System Acquisition

July 01, 2009 • Technical Note

John K. Bergey

This technical note provides guidance on how to contractually incorporate architecture evaluations in an acquisition.
read
The Impact of Conducting ATAM Evaluations on Army Programs (SATURN 2009)

April 27, 2009 • Presentation

John K. Bergey Stephen Blanchette, Jr.Mark H. Klein

This presentation describes the results of a study of the impact of software architecture practices conducted with Army programs.
read
Impact of Army Architecture Evaluations

April 01, 2009 • Special Report

Robert Nord John K. Bergey Stephen Blanchette, Jr.

This 2009 report describes the results of a study of the impact that the ATAM evaluations and QAWs had on Army programs.
read
Software Product Lines: Report of the 2009 U.S. Army Software Product Line Workshop

April 01, 2009 • Technical Report

John K. Bergey Sholom G. Cohen Patrick Donohoe

This report is a synthesis of the presentations and discussions that took place during the 2009 U.S. Army Software Product Line Workshop.
read
U.S. Army Workshop on Exploring Enterprise, System of Systems, System, and Software Architectures

March 01, 2009 • Technical Report

John K. Bergey Stephen Blanchette, Jr.Paul C. Clements

This report confirms that various architectural genres enjoy more commonalities than differences. Each one has its own important knowledge base, and openness among the various architectural tasks within an organization is growing in importance.
read
Overview of a Proactive Software Product Line Acquisition Approach

February 12, 2009 • Presentation

John K. Bergey

Presented at the SEI Army Software Product Line Workshop, February 12, 2009
read
Progress Toward an Organic Software Architecture Capability in the U.S. Army

June 01, 2007 • Technical Report

Stephen Blanchette, Jr.John K. Bergey

This 2007 report describes the Software Architecture Initiative of the Army Strategic Software Improvement Program.
read
A Comparison of Requirements Specification Methods from a Software Architecture Perspective

August 01, 2006 • Technical Report

Len Bass John K. Bergey Paul C. Clements

In this report, five methods for the elicitation and expression of requirements are evaluated with respect to their ability to capture architecturally significant requirements.
read
A Comparison of Requirements Specification Methods from a Software Architecture Perspective (SATURN 2006)

April 25, 2006 • Presentation

Ipek Ozkaya Len Bass John K. Bergey

Ipek Ozkaya talks about an approach developed by Fergus O'Brien that is used to assess how well different requirement specification methods serve an architect's goals and needs.
read
Product Line Acquisition in a DoD Organizational Guidance for Decision Makers

March 01, 2006 • Technical Note

John K. Bergey Sholom G. Cohen

This 2006 report chronicles the decisions a program manager might face in considering the adoption of a product line approach.
read
Software Product Lines: Experience from the Eighth DoD Software Product Line Workshop

November 01, 2005 • Technical Report

John K. Bergey Sholom G. Cohen Patrick Donohoe

This 2005 report summarizes the discussions from a 2005 PLP workshop in which participants shared DoD product line practices, experiences, and issues and discussed ways in which specific product line practices are accomplished within the DoD.
read
Using the SEI Architecture Tradeoff Analysis Method to Evaluate WIN-T: A Case Study

September 01, 2005 • Technical Note

Paul C. Clements John K. Bergey Dave Mason

This report describes the application of the SEI ATAM (Architecture Tradeoff Analysis Method) to the U.S. Army's Warfighter Information Network-Tactical (WIN-T) system.
read
The U.S. Army's Common Avionics Architecture System (CAAS) Product Line: A Case Study

September 01, 2005 • Technical Report

Paul C. Clements John K. Bergey

This report offers a case study of organizations that have adopted a software product line approach for developing a family of software-intensive systems.
read
Software Product Lines: Experiences from the Seventh DoD Software Product Line Workshop

March 01, 2005 • Technical Report

John K. Bergey Sholom G. Cohen Patrick Donohoe

This 2005 report summarizes discussions and presentations from the Seventh Department of Defense (DoD) Product Line Practice Workshop.
read
Software Architecture in DoD Acquisition: An Approach and Language for a Software Development Plan

February 01, 2005 • Technical Note

John K. Bergey Paul C. Clements

This report discusses the Software Development Plan (SDP), providing an example approach and corresponding SDP language that enable software architecture to play a central role in the technical and organizational management of a software development effort.
read
Software Architecture in DoD Acquisition: A Reference Standard for a Software Architecture Document

February 01, 2005 • Technical Note

John K. Bergey Paul C. Clements

This report provides a reference standard for a Software Architecture Document (SAD). Acquisition organizations can use this to acquire documentation needed for communicating the architecture design and conducting software architecture evaluations.
read
Results of SEI Independent Research and Development Projects and Report on Emerging Technologies and Technology Trends (FY 2004)

October 01, 2004 • Technical Report

John K. Bergey Edwin J. Morris Jeannine Siviy

This report describes the IR&D projects that were conducted during fiscal year 2004 (October 2003 through September 2004).
read
Software Product Lines: Experiences from the Sixth DoD Software Product Line Workshop

March 01, 2004 • Technical Note

John K. Bergey Sholom G. Cohen Lawrence G. Jones

This 2004 report summarizes the presentations and discussions from the Sixth Department of Defense (DoD) Product Line Practice Workshop in September 2003.
read
Fifth DoD Product Line Practice Workshop Report

June 01, 2003 • Technical Report

John K. Bergey Sholom G. Cohen Matt Fisher

This 2003 document summarizes the presentations and discussions from the Fifth Department of Defense (DoD) Product Line Practice Workshop, held in August 2002.
read
An Application of an Iterative Approach to DoD Software Migration Planning

September 01, 2002 • Technical Note

John K. Bergey Liam O'Brien Dennis B. Smith

This 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.
read
Use of the Architecture Tradeoff Analysis Method (ATAM) in Source Selection of Software-Intensive Systems

June 01, 2002 • Technical Note

John K. Bergey Matt Fisher Lawrence G. Jones

This report explains the role of software architecture evaluation in a source selection and describes the contractual elements that are needed to support its use.
read
Use of Quality Attribute Workshops (QAWs) in Source Selection for a DoD System Acquisition: A Case Study

June 01, 2002 • Technical Note

John K. Bergey William G. Wood

This case study outlines how a DoD organization used architecture analysis and evaluation in a major system acquisition to reduce program risk.
read
Army Workshop on Lessons Learned from Software Upgrade Programs

November 01, 2001 • Special Report

John K. Bergey Matt Fisher Caroline P. Graettinger

This report summarizes the results of the SEI-sponsored Software Upgrade Workshop for Legacy Systems at the Redstone Arsenal on June 5-7, 2001.
read
Fourth DoD Product Line Practice Workshop Report

October 01, 2001 • Technical Report

John K. Bergey Albert Soule Sholom G. Cohen

The report summarizes the workshop presentations and discussions from the Fourth Department of Defense (DoD) Software Product Line Practice Workshop, held in March 2001.
read
Use of the ATAM in the Acquisition of Software-Intensive Systems

September 01, 2001 • Technical Note

John K. Bergey Matt Fisher

This report discusses the role of software architecture evaluations in a system acquisition and describes the contractual elements that are needed to accommodate architecture evaluations in an acquisition. The report also provides an example of contractual language that incorporates the ATAM as a software architecture evaluation method in a system acquisition.
read
DoD Software Migration Planning

August 01, 2001 • Technical Note

John K. Bergey Liam O'Brien Dennis B. Smith

This 2001 report describes migration planning, identifies influencing factors, outlines a set of migration planning activities, and offers a set of guidelines for the migration planning process.
read
Options Analysis for Reengineering (OAR): A Method for Mining Legacy Assets

June 01, 2001 • Technical Note

John K. Bergey Liam O'Brien Dennis B. Smith

OAR is a systematic, architecture-centric, decision-making method for mining existing components for a product line or new software architecture.
read
Developing a Product Line Acquisition Strategy for a DoD Organization: A Case Study

April 01, 2001 • Technical Note

John K. Bergey Wolfhart B. Goethert

This 2001 report describes the approach a DoD organization used to develop alternative acquisition strategies and analyzes the pros and cons of each.
read
Using Quality Attribute Workshops to Evaluate Architectural Design Approaches in a Major System Acquisition: A Case Study

July 01, 2000 • Technical Note

John K. Bergey Mario R. Barbacci William G. Wood

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

May 01, 2000 • Technical Note

John K. Bergey Dennis B. Smith

This 2000 report outlines four basic steps that are required to successfully mine assets.
read
Guidelines for Using OAR Concepts in a DoD Product Line Acquisition Environment

March 01, 2000 • Technical Note

John K. Bergey Dennis B. Smith

This 2000 report provides guidance for DoD organizations for mining legacy systems to obtain core assets that will fit into a previously defined software architecture for a product line.
read
Basic Concepts of Product Line Practice for the DoD

February 01, 2000 • Technical Note

John K. Bergey Matt Fisher Brian P. Gallagher

This 2000 report provides background information to inform other reports in an SEI-published series of reports designed to provide concise and usable information about product line acquisition practices.
read
Second DoD Product Line Practice Workshop Report

October 01, 1999 • Technical Report

John K. Bergey Grady Campbell Paul C. Clements

This report synthesizes the workshop presentations and discussions of the Second DoD Product Line Practice Workshop, held in March 1999.
read
Software Architecture Evaluation with ATAM in the DoD System Acquisition Context

September 01, 1999 • Technical Note

John K. Bergey Matt Fisher Lawrence G. Jones

This report explains the basics of software architecture and software architecture evaluation in a system acquisition context.
read
DoD Legacy System Migration Guidelines

September 01, 1999 • Technical Note

John K. Bergey Dennis B. Smith Nelson W. Weiderman

This report provides a set of DoD legacy system migration guidelines.
read
Options Analysis for Reengineering (OAR): Issues and Conceptual Approach

September 01, 1999 • Technical Note

John K. Bergey Dennis B. Smith Nelson W. Weiderman

This 1999 report outlines the foundation of a structured and coherent method, based on the "horseshoe" model, that will help practitioners make appropriate reengineering choices.
read
The DoD Acquisition Environment and Software Product Lines

May 01, 1999 • Technical Note

John K. Bergey Matt Fisher Lawrence G. Jones

This technical note examines three key DoD acquisition policies and regulations, along with their implications for launching a product line.
read
Why Reengineering Projects Fail

April 01, 1999 • Technical Report

John K. Bergey Dennis B. Smith Scott R. Tilley (Florida Institute of Technoloy)

This 1999 report highlights some of the most important reasons for failures in reengineering efforts despite the best of intentions.
read
DoD Product Line Practice Workshop Report

May 01, 1998 • Technical Report

John K. Bergey Robert W. Krut, Jr.Paul C. Clements

This report synthesizes the 1998 product line workshop presentations and discussions that described selected product line practices and identified barriers and enablers to achieving these practices within the DoD.
read
Enterprise Framework for the Disciplined Evolution of Legacy Systems

October 01, 1997 • Technical Report

John K. Bergey Linda M. Northrop Dennis B. Smith

This 1997 report describes an enterprise framework that characterizes the global environment in which system evolution takes place and provides insight into the activities, processes, and work products that shape the evolution of legacy systems.
read
Proceedings of the First Annual Software Engineering Techniques Workshop, September 1994: Software Reengineering

September 01, 1994 • Special Report

L. Green John K. Bergey Giuseppe Lami

The 1995 workshop on software reengineering established a foundation for capturing the best practices within reengineering and resulted in a detailed outline for a reengineering best practices handbook.
read