Difference between revisions of "Business or Mission Analysis"

From SEBoK
Jump to: navigation, search
Line 1: Line 1:
Introductory Paragraph(s)
+
==4.1 Introduction, Definition and Purpose of Stakeholder Requirements
 +
'''Introduction''' - The starting point of engineering a system is the definition of the problem to be solved. The stakeholders’ requirements represent the view of the users, acquirers, and customers of the problem. An important set of activities has to be performed to establish a set of stakeholders’ requirements for a system that can provide the services needed by the acquirer, the users, and the other stakeholders in a defined environment. This section provides knowledge about the notions of needs, expectations, stakeholders’ requirements, concept of operations, and the related systems engineering activities and methods. The set of Stakeholder Requirements represents one of the major outcomes of these activities. For better understanding of this chapter, it is recommended that you read sections '''3.3.3.1''' and '''3.3.3.2''' first.
 +
 
 +
'''Definition and Purpose''' - An initial presentation of stakeholders’ intention is not necessarily a requirement, since it has not been defined, analyzed, or determined to be feasible. This intention is distinguished from a requirement as being (stakeholder) needs, goals or objectives. The distinction between requirements and needs is related to which system is concerned; for example, a requirement for a system may be allocated to a software element of the system, viewed as needs by the supplier of this software element, and further elaborated as (a) requirement(s) for this software element.
 +
 
 +
An important aspect of engineering is “requirements engineering.” Some activities gathered under this term include:
 +
*the capture of the needs, goals, and objectives of the various stakeholders;
 +
*the preliminary identification of the engineering elements of this system-of-interest in terms of purpose, expected mission, services or operations, objectives, exchanges, and physical links with the objects of its context of use;
 +
*the enrichment of the needs through the analysis of these first engineering elements of the system, in particular what is called the “mission analysis”;
 +
*the transformation of these needs into clear, concise, and verifiable Stakeholders’ Requirements applicable to the system-of-interest;
 +
*the analysis and translation of the Stakeholders’ Requirements into a set of System Requirements (see section  '''3.3.5''').
 +
 
 +
Requirements engineering is performed in an iterative manner with the other life cycle processes and recursively through the system design hierarchy.
 +
 
 +
 
  
 
====Article Discussion====
 
====Article Discussion====

Revision as of 19:24, 4 June 2011

==4.1 Introduction, Definition and Purpose of Stakeholder Requirements Introduction - The starting point of engineering a system is the definition of the problem to be solved. The stakeholders’ requirements represent the view of the users, acquirers, and customers of the problem. An important set of activities has to be performed to establish a set of stakeholders’ requirements for a system that can provide the services needed by the acquirer, the users, and the other stakeholders in a defined environment. This section provides knowledge about the notions of needs, expectations, stakeholders’ requirements, concept of operations, and the related systems engineering activities and methods. The set of Stakeholder Requirements represents one of the major outcomes of these activities. For better understanding of this chapter, it is recommended that you read sections 3.3.3.1 and 3.3.3.2 first.

Definition and Purpose - An initial presentation of stakeholders’ intention is not necessarily a requirement, since it has not been defined, analyzed, or determined to be feasible. This intention is distinguished from a requirement as being (stakeholder) needs, goals or objectives. The distinction between requirements and needs is related to which system is concerned; for example, a requirement for a system may be allocated to a software element of the system, viewed as needs by the supplier of this software element, and further elaborated as (a) requirement(s) for this software element.

An important aspect of engineering is “requirements engineering.” Some activities gathered under this term include:

  • the capture of the needs, goals, and objectives of the various stakeholders;
  • the preliminary identification of the engineering elements of this system-of-interest in terms of purpose, expected mission, services or operations, objectives, exchanges, and physical links with the objects of its context of use;
  • the enrichment of the needs through the analysis of these first engineering elements of the system, in particular what is called the “mission analysis”;
  • the transformation of these needs into clear, concise, and verifiable Stakeholders’ Requirements applicable to the system-of-interest;
  • the analysis and translation of the Stakeholders’ Requirements into a set of System Requirements (see section 3.3.5).

Requirements engineering is performed in an iterative manner with the other life cycle processes and recursively through the system design hierarchy.


Article Discussion

[Go to discussion page]