Sample Selection from IEEE Software Engineering Standards and Examples: Guide for Implementing a Software Concept of Operations (ConOps) Document
3.2 Concept Analysis
Concept analysis (ConOps analysis) is the process of analyzing a problem domain and an operational environment for the purpose of specifying the characteristics of a proposed system from the users' perspective. The traditional system development process emphasizes functionality with little concern for how that functionality will be used. ConOps analysis emphasizes an integrated view of a system and its operational characteristics, rather than focusing on individual functions or pieces of a system. A major goal of ConOps analysis is to avoid development of a system in which each individual function meets its specifications, but the system as a whole fails to meet the users' needs. This can occur if the development team has analyzed parts of the overall systems individually, without focusing on how the those parts must function together to provide the users with a useful and workable system.
ConOps analysis, which should be the first step taken in the overall system development process, identifies the various classes of users and modes of operations and provides users with a mechanism for defining their needs and desires. ConOps analysis is also useful to surface different user's (and user groups) needs and viewpoints and in allowing the buyer (or multiple buyers) to state their requirements for the proposed system. This process is essential to the success of the subsequent system development effort. Users have an opportunity to express their needs and desires, but they are also required to state which of those needs are essential, which are desirable, and which are optional. In addition, they must prioritize those needs that are desirable and optional. "Prioritized user needs provide the basis for establishing an incremental development process and for making tradeoffs among operational needs, schedule, and budget" [Fairley, Bjorke, & Thayer, 1994].
ConOps analysis stimulates a thorough examination of the users' needs and visions and the buyer's requirements by obligating them to analyze how the system must operate to meet those needs, visions, and requirements. ConOps analysis also helps to clarify and resolve vague and conflicting needs, expectations, and opinions by reconciling divergent views. When several user groups (or buyer groups) have conflicting needs, expectations, or viewpoints, ConOps analysis can aid in building consensus. In some cases, it may be determined that no single system can satisfy all of the divergent needs and desires of multiple user groups and buyer agencies. If that should be the case, it is beneficial to make that determination as early in the development process as possible. The potential cost of acknowledging that one system is not sufficient late in the project's lifecycle can be devastating to the project.
ConOps analysis is an iterative process that should involve various people. The analysis group should include representatives from the user, buyer, and developer organizations plus any other appropriate parties such as training and operational support. When a development organization has not been selected at the time of ConOps analysis, the developer role may be filled by in-house experts or by consultants.
The results of concept analysis are recorded in the ConOps document which serves as a checklist to guide the conceptual analysis process and provides the foundation for all subsequent system development activities (analysis, design, implementation, and validation). The ConOps document should say everything about the system that the users and buyer need to communicate to those who will develop the system.
The ConOps document should be repeatedly reviewed and revised until all involved parties agree on the resulting document. This iterative process helps bring to the surface many viewpoints, needs, wants, and scenarios that might otherwise be overlooked (e.g., scenarios for handling exceptional situations).
Purchase, Product Description, Author Bios, Table of Contents