259
Integration in Systems Engineering Context
Characterizing the Need
In developing a theory of integration, three needs arise: first, the salient factors
(e.g., assumptions, independent and dependent variables, measures, and measurement) need to be identified, classified, and categorized; second, a model
must be posed that relates the facts, based on certain specified assumptions; and
third, the hallmarks of explanation and prediction must be laid out. Each of the
three needs address several problems. For every problem there may be multiple
needs. A need is a condition requiring relief. A need needs to be resolved and
managed. Needs have characteristics that distinguish them from wants. Needs
map to the intentions of stakeholders through the stated or unstated wants.
Stakeholders have need(s) and want(s). The systems engineer differentiates
needs from wants by reflecting the needs in the design and architecture baselines, weighing whether needs or wants are disguised and miscategorized.
A need has measurable requirements. Systems engineers define needs for
developing the product or services, while the program manager satisfies the
needs to support the project. The user of the new product or service defines
their needs. Users have needs. A need can be for an object’s properties, traits,
or attributes. The systems engineer’s role is to assure that all objects are
appropriately specified, that is, the need(s) are met.
Stakeholders
The word “stakeholder,” one who has a stake in the outcome, is most typically
an entity (a person either acting alone or representing an organization) who can
influence the conceptualization or funding of the development project, or the
product’s or service’s acceptance, operations, or disposal. A stakeholder is anyone who significantly affects or is affected by decision-making activity the
influences the product or service. In a broader sense, it is someone with an interest or concern, and specifically someone at risk due to the product or service.
Stakeholders have needs, as such it is important to capture their needs so
that the systems engineer can incorporate, acknowledge, or choose to ignore
specific requirements. Discovering stakeholders early in the development
work is less disruptive than later. Identifying and analyzing the needs of
stakeholders is referred to stakeholder analysis.
Stakeholder analysis is a methodology for identifying stakeholders and
analyzing their underlying value and interests in the system. The methodology involves several processes and tools that cater to discovering types,
significance, and value of stakeholders. At risk are the consequences of not
uncovering the current and potential future interests and objectives of
affected parties. Conjugate benefits include (1) a better appreciation of the
complexity of the system and the undertaking; (2) understanding of the
Integration in Systems Engineering Context
Characterizing the Need
In developing a theory of integration, three needs arise: first, the salient factors
(e.g., assumptions, independent and dependent variables, measures, and measurement) need to be identified, classified, and categorized; second, a model
must be posed that relates the facts, based on certain specified assumptions; and
third, the hallmarks of explanation and prediction must be laid out. Each of the
three needs address several problems. For every problem there may be multiple
needs. A need is a condition requiring relief. A need needs to be resolved and
managed. Needs have characteristics that distinguish them from wants. Needs
map to the intentions of stakeholders through the stated or unstated wants.
Stakeholders have need(s) and want(s). The systems engineer differentiates
needs from wants by reflecting the needs in the design and architecture baselines, weighing whether needs or wants are disguised and miscategorized.
A need has measurable requirements. Systems engineers define needs for
developing the product or services, while the program manager satisfies the
needs to support the project. The user of the new product or service defines
their needs. Users have needs. A need can be for an object’s properties, traits,
or attributes. The systems engineer’s role is to assure that all objects are
appropriately specified, that is, the need(s) are met.
Stakeholders
The word “stakeholder,” one who has a stake in the outcome, is most typically
an entity (a person either acting alone or representing an organization) who can
influence the conceptualization or funding of the development project, or the
product’s or service’s acceptance, operations, or disposal. A stakeholder is anyone who significantly affects or is affected by decision-making activity the
influences the product or service. In a broader sense, it is someone with an interest or concern, and specifically someone at risk due to the product or service.
Stakeholders have needs, as such it is important to capture their needs so
that the systems engineer can incorporate, acknowledge, or choose to ignore
specific requirements. Discovering stakeholders early in the development
work is less disruptive than later. Identifying and analyzing the needs of
stakeholders is referred to stakeholder analysis.
Stakeholder analysis is a methodology for identifying stakeholders and
analyzing their underlying value and interests in the system. The methodology involves several processes and tools that cater to discovering types,
significance, and value of stakeholders. At risk are the consequences of not
uncovering the current and potential future interests and objectives of
affected parties. Conjugate benefits include (1) a better appreciation of the
complexity of the system and the undertaking; (2) understanding of the