Software Engineering

8.2.1 
Identify operational concepts
The operational concept for the software product must be documented to describe 
the characteristics of a proposed software product from the viewpoint of an individ-
ual who will use the product. It is used to communicate the software characteristics 
to all stakeholders. Concepts of operation descriptions usually address the following:
1. 
Statement of the goals and objectives of the software product.
2. 
Mission statement that expresses the set of services the product provides.
3. 
Strategies, policies, and constraints affecting the product.
4. 
Organizations, activities, and interactions among participants and stakeholders.
5. 
Clear statement of responsibilities associated with product development and 
sustainment.
6. 
Process identification for distributing, training, and sustainment of the product.
7. 
Milestone decision definitions and authorities.
During software requirements definition, the operational or business process should 
be modeled to understand the operational activity flows, control flows, and data flows 
among the elements of the computational environment, associated applications, data-
bases, and users. The operational concept should identify operational threads for each 
type of transaction that the software application will have to support.
During architecture definition, the operational concepts should address the user 
interactions associated with installation, operation, distribution, training, and sup-
port of the product.