A systems engineering approach to dating and relationships
Figure 1 shows the steps and the position of the stakeholder requirements and system requirements in the engineering cycle.
Using enterprise-level life cycle concepts (see Business or Mission Analysis for details) as guidance, stakeholders are led through a structured process to elicit stakeholder needs (in the form of a refined set of system-level life-cycle concepts).
(Created for SEBo K)The degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or master-subordinate relationship to one another (IEEE 1233-1998 (R2002) IEEE Guide for Developing System Requirements Specifications, 3.1.9) The purpose of the Stakeholder Needs and Requirements definition activities are to elicit a set of clear and concise needs related to a new or changed mission for an enterprise (see mission analysis (MA) for information relevant to identifying and defining the mission or operation), and to transform these stakeholder needs into verifiable stakeholder requirements.
Stakeholders may well begin with desires, and expectations that may contain vague, ambiguous statements that are difficult to use for SE activities.
As an example, a need or an expectation such as, to easily manoeuvre a car in order to park, will be transformed in a set of (1b) The stakeholder needs and requirements definition process identifies stakeholders, or stakeholder classes, involved with the system throughout its life cycle, and their needs.
(ISO/IEC/IEEE,2015) to a statement such as, increase the driviability of the car, decrease the effort for handling, assist the piloting, protect the coachwork against shocks or scratch, etc.