Business or Mission Analysis

The starting point of engineering any system-of-interest (SoI) is understanding the socio-economic and technological context in which potential problems or opportunities reside. The enterprise strategic goals and stakeholders’ needs, expectations, and requirements represent the problem or the opportunity from the viewpoint of users, acquirers, and customers.

Mission analysis (MA) is often performed iteratively with stakeholder needs and requirements generation to better understand the problem (or opportunity) space, as well as the solution space. The execution of this process enables a systems engineer to then establish a set of stakeholder requirements for a potential SoI, or other solution, that could provide a capability or service needed by the acquirer, the users, and the other stakeholders in a defined environment.

MA is part of the larger set of concept definition activities - the phase of systems engineering in which the problem space and the needs of the stakeholders are closely examined; this occurs before any formal definition of the (SoI) is developed. In fact, the activities of concept definition determine whether the enterprise strategic goals and stakeholder needs will be addressed by a new system, a change to an existing system, a service, an operational change or some other solution. Mission analysis focuses on the identification of the primary purpose(s) of the solution, while stakeholder needs and requirements definition explores what capabilities stakeholders desire and may include some detail on the performance of certain aspects of the solution.

Purpose and Definition

The purpose of MA is to understand a mission/market problem or opportunity, analyze the solution space, and initiate the life cycle of a potential solution that could address the problem or take advantage of an opportunity. MA is a type of strategic or operations analysis related to needs, capability gaps, or opportunities and solutions that can be applied to any organization that evolves its strategy for its business objectives.

MA, in some domains called market analysis or business analysis, is the identification, characterization, and assessment of an operational problem or opportunity within an enterprise. The definition of a mission need in a problem space frames the solution, both in terms of the direct application to the mission or business function, and in terms of the context for the resulting solution.

MA is used to define needed (or desired) operational actions, not hardware/software functions; that is, it is focused on defining the problem space, not the solution space. It characterizes the operational need in terms of mission description/provisions and the environment/context, together with the proposed enterprise concept of operations (ConOps) and operational scenarios. The primary products of MA are the revised ConOps of the enterprise, the operational concept, the operational scenarios for the mission, and the context in which the solution will exist.

MA may include mathematical analysis, modeling, simulation, visualization, and other analytical tools to characterize the intended mission and determine how to best achieve the needs/objectives. MA evaluates alternative approaches to determine which best supports the stakeholder needs (among both materiel and non-materiel solution alternatives, also known as product solutions and service/operational solutions). Thus, MA defines the problem space and analyzes the solution space alternatives using quality attribute constraints driven by the enterprise objectives.

Principles and Concepts

Mission Analysis and Concept of Operations

MA and the ConOps are broadly used in U.S. defense and aerospace organizations to analyze and define how a system is intended to operate, as well as how the major operations or operational scenarios are intended to be performed. They take into account the strategic, operational, and tactical aspects of the identified scenarios.

In order to determine appropriate technical solutions for evolving enterprise capabilities, systems engineering (SE) leaders interact with enterprise leaders and operations analysts to understand

• the enterprise ConOps and future mission, business, and operational (MBO) objectives;
• the characterization of the operational concept and objectives (i.e., constraints, mission or operational scenarios, tasks, resources, risks, assumptions, and related missions or operations); and
• how specific missions or operations are currently conducted and what gaps exist in those areas.

They then conceptually explore and select from alternative candidate solutions. This interaction ensures a full understanding of both the problem space and the solution space. The alternative candidate solutions can include a wide range of approaches to address the need, as well as variants for an approach to optimize specific characteristics (e.g., using a different distribution of satellite orbit parameters to maximize coverage or events while minimizing the number of satellites). Analysis, modeling and simulation, and trade studies are employed to select alternative approaches (NDIA 2010).

The ConOps, at the organization level, addresses the leadership's intended way of operating the organization. It may refer to the use of one or more systems (as black boxes) to forward the organization's goals and objectives. The ConOps document describes the organization's assumptions or intent in regard to an overall operation or series of operations within the business in regards to the system to be developed, existing systems, and possible future systems. This document is frequently embodied in long-range strategic plans and annual operational plans. The ConOps document serves as a basis for the organization to direct the overall characteristics of future business and systems. (ISO/IEC 2011)

These notions are also used in industrial sectors, such as aviation administrations and aeronautic transportation, health care systems, space, etc., with adapted definitions and/or terms, such as operational concepts, usage concepts and/or technological concepts. For example, “mission analysis” is the term used to describe the mathematical analysis of satellite orbits performed to determine how best to achieve the objectives of a space mission (ESA 2008).

In commercial sectors, MA is often primarily performed as market analysis. Wikipedia defines market analysis as a process that:

. . . studies the attractiveness and the dynamics of a special market within a special industry. It is part of the industry analysis and this in turn of the global environmental analysis. Through all these analyses, the chances, strengths, weaknesses, and risks of a company can be identified. Finally, with the help of a Strengths, Weaknesses, Opportunities, and Threats (SWOT) analysis, adequate business strategies of a company will be defined. The market analysis is also known as a documented investigation of a market that is used to inform a firm's planning activities, particularly around decisions of inventory, purchase, work force expansion/contraction, facility expansion, purchases of capital equipment, promotional activities, and many other aspects of a company. (Wikipedia Contributors, 2012)

Anywhere these notions are used, it is evident that they are based on fundamental concepts, such as the operational mode (or state of the system), scenario (of actions), the enterprise level ConOps and the system level operational concepts, functions, etc. For more explanations about the ConOps and operational concept, refer to Systems and Software Engineering - Requirements Engineering (ISO/IEC 2011); useful information can be found in Annex A, "System Operational Concept", and Annex B, "Concept of Operations" (ISO/IEC 2011).

Mission Analysis as Part of Enterprise Strategy Development

Periodically, most enterprises re-evaluate their strategy with respect to their mission, vision, and positioning to accomplish their goals. Figure 1 shows the interactions of the enterprise strategy development and the concept definition, including MA and stakeholder needs and requirements that are involved in an iterative manner to fully develop the strategy and define future capabilities and solutions.

Figure 1. Enterprise Strategy and Concept Development (Roedler 2012). Used with permission of Garry Roedler. All other rights are reserved by the copyright owner.

As the enterprise evolves the strategy, it is essential to conduct the supporting MA or strategic analysis for each element of the enterprise to determine readiness to achieve future objectives. This analysis examines the current state to identify any problems or opportunities related to the objective achievement and aids the enterprise in fully understanding and defining the problem space. The analysis examines the external environment and interfaces in search of impacts and trends, as well as the internal enterprise to gauge its capabilities and value stream gaps. Additionally, a strengths, weaknesses, opportunities, and threats (SWOT) analysis may be performed. As the problem space is defined, the stakeholder needs are defined and transformed into stakeholder requirements that define the solutions needed. These requirements include those that address customer and mission needs, the future state of core processes and capabilities of the enterprise, and the enablers to support performance of those processes and capabilities. Finally, MA is engaged again to examine the solution space. Candidate solutions that span the potential solution space are identified, from simple operational changes to various system developments or modifications. Various techniques are applied to analyze the candidates, understand their feasibility and value, and select the best alternative.

Process Approach

Activities of the Process

It is necessary to perform the following major activities and tasks during the MA process:

1. Review and understand the enterprise mission, vision, and ConOps.
2. Identify and define any gaps and opportunities related to future evolution of the strategy:
   1. Examine the current state to identify any problems or opportunities related to the objective achievement, including any deficiencies of the existing system.
   2. Analyze the context of the actual political, economic, social, technological, environmental, and legal (PESTAL) factors, while studying sensitive factors such as cost and effectiveness, security and safety improvement, performance improvement or lack of existing systems, market opportunities, regulation changes, users' dissatisfaction, etc. External, internal, and SWOT analysis should be included as well. For the technological considerations, an appropriate architectural framework representation, such as the U.S. Department of Defense Architecture Framework (DoDAF) operations view (DoD 2010), the Zachman Framework (Rows1 and 2) (Zachman 2008), and The Open Group Architecture Framework (TOGAF) Architecture Development Method (ADM) (The Open Group 2010) Phases A and B should be included within the concept definition when performing mission analysis and stakeholders needs and requirements.
   3. Define any mission, business, and/or operational problem or opportunity, as well as its context, and any key parameters, without focusing on a solution.
3. Examine and evaluate the solution space.
   1. Identify the main stakeholders (customers, users, administrations, regulations, etc.).
   2. Identify high level operational modes or states, or potential use cases.
   3. Identify candidate solutions that span the potential solution space, from simple operational changes to various system developments or modifications. Identify existing systems, products, and services that may address the need for operational or functional modifications. Deduce what potential expected services may be needed. The SoI is a potential and not yet existing product, service or enterprise. Additionally, the solution could be an operational change or a change to an existing product or service.
4. Perform appropriate modeling, simulation, and analytical techniques to understand the feasibility and value of the alternative candidate solutions. Model or simulate operational scenarios from these services and use cases, and enrich them through reviews with stakeholders and subject matter experts.
5. Define basic operational concept or market strategy, and/or business models.
   1. From previous modeled operational scenarios and operational modes, deduce and express the usage of operational concepts, or technical concepts.
   2. Collect and enrich needs, expectations, scenarios, and constraints.
   3. Validate the mission of any potential SoI in the context of any proposed market strategy or business model.
6. Evaluate the set of alternatives and select the best alternative.
   1. Perform a trade study of the alternatives to discriminate between the alternatives.
7. Provide feedback on feasibility, market factors, and alternatives for use in completion of the enterprise strategy and further actions.

Mission Analysis Artifacts

This process may create several artifacts, such as

• recommendations for revisions to the enterprise ConOps;
• preliminary operational concept document or inputs;
• mission analysis and definition reports;
• system analysis artifacts (e.g., use case diagrams, context diagrams, sequence/activity diagrams, functional flow block diagrams);
• trade study results (alternatives analysis); and
• market study/analysis reports.

Methods and Modeling Techniques

MA uses several techniques, such as

• use case analysis;
• operational analysis;
• functional analysis;
• technical documentation review;
• trade studies;
• modeling;
• simulation;
• prototyping;
• workshops, interviews, and questionnaires;
• market competitive assessments;
• benchmarking; and
• organizational analysis techniques (e.g., strengths, weaknesses, opportunities, threats (SWOT analysis), and product portfolios).

Practical Considerations

Major pitfalls encountered with mission analysis and marketing analysis are presented in Table 1.

Table 1. Major Pitfalls for Mission Analysis. (SEBoK Original)

Pitfall	Description
Wrong level of system addressed	When delineating the boundaries of the SoI and defining the mission and purpose of the system at the very beginning of systems engineering, a classic mistake is to place the system-of-interest at the wrong level of abstraction. The level of abstraction can be too high or too low (sitting respectively in the upper-system or in a sub-system). This is the consequence of the principle stating that a system is always included in a larger system and of confusing the purpose and the mission of the SoI.
Operational modes or scenarios missing	In commercial products or systems, the lack or insufficient description of operational modes and scenarios (how the SoI will be used, in which situations, etc.) is often encountered.

Proven practices with mission analysis and marketing analysis are presented in Table 2.

Table 2. Mission Analysis Proven Practices. (SEBoK Original)

Practice	Description
Models of operational scenarios	Using modeling techniques as indicated in sections above for operational scenarios in any kind of SoI (including commercial systems).
Models of the context	Consider the context of use as a system and force oneself to use modeling techniques for main aspects of the context (functional, behavioral, physical, etc.).

References

Works Cited

DoD. 2010. DoD Architecture Framework, version 2.02. Arlington, VA: U.S. Department of Defense. Accessed August 29, 2012. Available at: http://dodcio.defense.gov/Portals/0/Documents/DODAF/DoDAF_v2-02_web.pdf.

ESA. 2008. Mission Analysis: Towards a European Harmonization. Paris, France: European Space Agency. Accessed August 29, 2012. Available at: http://www.esa.int/esapub/bulletin/bulletin134/bul134b_schoenmaekers.pdf.

IEEE. 1998. Guide for Information Technology – System Definition – Concept of Operations (ConOps) Document. Piscataway, NJ, USA: Institute of Electrical and Electronics Engineers, IEEE 1362:1998.

ISO/IEC/IEEE. 2011. Systems and software engineering -- Life cycle processes -- Requirements engineering Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC), Institute of Electrical and Electronics Engineers.ISO/IEC/IEEE 29148:2011

ISO/IEC/IEEE. 2008. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC), Institute of Electrical and Electronics Engineers. ISO/IEC/IEEE 15288:2008 (E).

ISO/IEC/IEEE. 2011. Systems and Software Engineering - Requirements Engineering. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission/ Institute of Electrical and Electronics Engineers (IEEE), (IEC), ISO/IEC/IEEE 29148.

Kaplan, R.S. and Norton, D.P. 2008. “Developing the Strategy: Vision, Value Gaps, and Analysis”, Balanced Scorecard Report. Cambridge, MA, USA: Harvard Business School Publishing, Jan-Feb 2008.

Kohda, T., M. Wada, and K. Inoue. 1994. "A simple method for phased mission analysis." Reliability Engineering & System Safety 45(3): 299-309.

NDIA. 2010. “Mission Analysis Committee Charter”. Website of the National Defense Industrial Association, Systems Engineering Division, Mission Analysis Committee. Accessed August 29, 2012. Available at: http://www.ndia.org/Divisions/Divisions/SystemsEngineering/Documents/Committees/Mission%20Analysis%20Committee/Mission%20Analysis%20Committee%20Charter.pdf.

Shupp, J.K., “The Mission Analysis Discipline: Bringing focus to the fuzziness about Attaining Good Architectures”, Proceedings of INCOSE 13th International Symposium, July 2003.

The Open Group. 2011. TOGAF, version 9.1. Hogeweg, The Netherlands: Van Haren Publishing. Accessed August 29, 2012. Available at: https://www2.opengroup.org/ogsys/jsp/publications/PublicationDetails.jsp?catalogno=g116.

Wikipedia contributors, "Market analysis," Wikipedia, The Free Encyclopedia, http://en.wikipedia.org/w/index.php?title=Market_analysis&oldid=508583878 (accessed August 29, 2012).

Zachman, J. 2008. "John Zachman's Concise Definition of The Zachman Framework™ (online)". Zachman International Enterprise Architecture. Accessed August 29, 2012. Available at: http://www.zachman.com/about-the-zachman-framework.

Primary References

ISO/IEC/IEEE. 2008. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electronical Commission (IEC), Institute of Electrical and Electronics Engineers. ISO/IEC/IEEE 15288:2008 (E).

ISO/IEC/IEEE. 2011. Systems and Software Engineering - Requirements Engineering. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission/ Institute of Electrical and Electronics Engineers (IEEE), (IEC), ISO/IEC/IEEE 29148.

INCOSE. 2011. INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities. Version 3.2.1. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2003-002-03.2.1.

Lamsweerde, A. van. 2009. Requirements Engineering: From System Goals to UML Models to Software Specifications. New York, NY, USA: Wiley.

Additional References

Center for Quality Management. 1993. "Special Issue on Kano's Methods for Understanding Customer Defined Quality." Center for Quality Management Journal 2(4) (Fall 1993).

Faisandier, A. 2012. Systems Opportunities and Requirements. Belberaud, France: Sinergy'Com.

Freeman, R. "Chapter 27: Achieving Strategic Aims: Moving Toward a Process Based Military Enterprise," in Handbook of Military Industrial Engineering. A.B. Badiru and M.U. Thomas (eds). Boca Raton, FL, USA: Taylor & Francis Group, CRC Press.

IEEE. 1998. Guide for Information Technology – System Definition – Concept of Operations (ConOps) Document. Piscataway, NJ, USA: Institute of Electrical and Electronics Engineers, IEEE 1362:1998.

Hull, M.E.C., K. Jackson, A.J.J. Dick. 2010. Systems Engineering. 3rd ed. London, UK: Springer.

Kano, N. 1984. "Attractive Quality and Must-Be Quality." Quality JSQC 14(2) (October 1984).

Kohda, T., M. Wada, and K. Inoue. 1994. "A Simple Method for Phased Mission Analysis." Reliability Engineering & System Safety. 45(3): 299-309.

Marca, D. A. and C. L. McGowan. 1987. "SADT: Structured analysis and design techniques," in Software Engineering. New York, NY: McGraw-Hill.

MITRE. 2011. "Concept Development." Systems Engineering Guide. Accessed 9 March 2012 at [[1]].

MITRE. 2011. "Requirements Engineering." Systems Engineering Guide. Accessed 9 March 2012 at [[2]].

MITRE. 2011. "Stakeholder Assessment and Management." Systems Engineering Guide. Accessed 9 March 2012 at [[3]].

---

< Previous Article | Parent Article | Next Article > SEBoK v. 1.9.1 released 30 September 2018

SEBoK Discussion

Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.

If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.

blog comments powered by Disqus