0 Items in Your Cart
Cart Summary
Shopping Cart Empty
  Search by keyword: Find
Previous |  ReadyNotes  | Next

Guide for Implementing a Software ConOps Document

RN0000005
List Price: $19.00
 
File Name: RN0000005

This ReadyNote is a guide to utilizing concept analysis and a Concept of Operations (ConOps) document. These are highly useful tools for facilitating the communication between those who need a software system and those who will design and implement the system. A good understanding of the users and their needs is crucial to all software projects, and concept analysis and a ConOps document can help with this step no matter how large or small, how complex or simple, the project is.

A Concept of Operations (ConOps) document describes, in the user's language and from the user's perspective, all of the key elements of a proposed system, including description of the problem domain, operational environment, use cases, and description of the system. The ConOps document serves as a bridge between the users and the system developers and the latter's technical requirements and specification documents.

The goal of this ConOps ReadyNote is to provide a practical guide to help the user to be more successful in software development projects via application of concept analysis and ConOps documents. This ReadyNote explains what a ConOps document is, when to use it, what the benefits are from using it, how to develop it, who should be involved, and a template for a ConOps document outlining what should be covered in each section. It also provides two examples of ConOps documents to help the reader better understand how to leverage ConOps documents for their projects.

Preface
Chapter 1: Introduction
1.1 Limitation of Current Software Engineering Methodologies
1.2 Concept Analysis and Concept of Operations (ConOps) Document
Chapter 2: Justifications for the ConOps
Chapter 3: The ConOps Process
3.1 The Roles of Users, Buyers, and Developers
3.2 Concept Analysis
3.3 The Concept of Operations (ConOps) Document
3.4 Roles for ConOps Documents
Chapter 4: Developing a Concept of Operations (ConOps) Document
4.1 Initiator - Recipient Modes
4.2 When Should the ConOps be Developed?
4.3 Who should Develop the ConOps Document?
4.4 How Should the ConOps Be Developed?
4.5 Recommended Format of A ConOps Document
4.6 Maintenance of A ConOps Document
Chapter 5: Conclusions
Chapter 6: Annotated ConOps Outline
Chapter 7: Example 1: Air Traffic Management Assistant
Chapter 8: Example 2: ConOps for the Community Assistance System
Chapter 9: ConOps: The Cryptex to Operational System Mission Success
References

Per Bjorke is a Director of Product Management in the Audience Analytics group at Yahoo! Inc. in Sunnyvale, California. He's responsible for the network web analytics solutions for Yahoo's world-wide business. Prior to Yahoo! he worked in product management at Actuate Corp., developing enterprise business intelligence products.

Bjorke is a principal author for a Standard for a Concept of Operations (ConOps) document (IEEE Std 1362-1998). He has an MS in Computer Science from California State University, Sacramento, and a BS in Computer Science from Gjovik College of Engineering, Norway.

Richard H. Thayer is a consultant in software engineering and project management, and a visiting senior researcher and lecturer at the University of Strathclyde, Glasgow, Scotland. In addition to 20 years as a professor of software engineering at California State University, Sacramento, Thayer served as a senior officer in the US Air Force. His Air Force experience included six years as a supervisor and technical lead of scientific programming groups, four years directing the US Air Force R&D program in computer science, and six years managing large data-processing organizations.

Thayer is a principal author for a Standard for a Concept of Operations (ConOps) document (IEEE Std 1362-1998) and a principal author of the Standard for Software Project Management Plans (IEEE Std 1058-1998). He has edited or coedited more than a dozen tutorial books, as well as over 40 technical papers and reports on software project management, software engineering, and software engineering standards. He has been an invited speaker at international software engineering conferences and workshops.