253
Integration in Systems Engineering Context
as much about knowing the constraints and limitations of the boundary conditions and boundaries as it is appreciating the uses of the product or service. It is also as much about the functions as it is about knowing what
decisions the users expect to make after they put the product or service into
operation. In order of importance, the defining characteristics of the problem
can be expressed by (1) the decisions that the users will make either because
the product or service exists or because in anticipation of the working with
the product or service; (2) the limitations imposed by the physical, functional,
and behavioral boundaries; (3) the constraints of cost, facilities, and other
nonlabor issues and resources; (4) the implications of thinking in systems
about the future of the proposed product or service; and (5) the revised needs
of the key stakeholders, as determined after the stakeholders have examined
and discussed the trade-offs imposed by the previous three items listed.
Scope of a Problem
Within the boundedness of the problem, the scope of the expected development work can help define how much of the long-term solution will be delivered in the first tranche of value. The determination of the scope of the work
can be expressed by (1) the limitations imposed by the total development
costs, the deliverable functions, design and architected performance(s), and
the levels of quality expressed as the losses to achieve the deliverable system
performances; (2) the constraints imposed by the development schedule, systems engineering skills, and management skills; (3) and the degree of integration. The scope issues are a constant reminder that development uncovers
many issues that were not envisioned at the beginning of the project. Since
both boundary discussions and scope issues are contractual by their nature,
the discussions with key stakeholders are a convenient, albeit proper means
to deal with such issues.
Nature of a Problem
An example that points out the specific nature of a problem is that faced
when the project is on a tight schedule and a wrong decision in the beginning days of work becomes expensive to correct later and co-opts the schedule with undue additional work. Your mathematicians describe a means of
evaluating two conceptual designs developed for a project in the first week
of work. Both designs seem to address the needs of the customer and appear
workable to the engineers. However, there is no consensus or rationale for a
consensus that favors one design over the other as the designs are only representative of a set of vague requirements from the customer. The designer
has inferred much and liberally made decisions to eliminate uncertainties.
Early designs are conceptual in nature and lack the refinements that are
reflected in later-stage design. The schedule of this project is compressed
more than the systems engineers found comfortable, but acceded to their
Integration in Systems Engineering Context
as much about knowing the constraints and limitations of the boundary conditions and boundaries as it is appreciating the uses of the product or service. It is also as much about the functions as it is about knowing what
decisions the users expect to make after they put the product or service into
operation. In order of importance, the defining characteristics of the problem
can be expressed by (1) the decisions that the users will make either because
the product or service exists or because in anticipation of the working with
the product or service; (2) the limitations imposed by the physical, functional,
and behavioral boundaries; (3) the constraints of cost, facilities, and other
nonlabor issues and resources; (4) the implications of thinking in systems
about the future of the proposed product or service; and (5) the revised needs
of the key stakeholders, as determined after the stakeholders have examined
and discussed the trade-offs imposed by the previous three items listed.
Scope of a Problem
Within the boundedness of the problem, the scope of the expected development work can help define how much of the long-term solution will be delivered in the first tranche of value. The determination of the scope of the work
can be expressed by (1) the limitations imposed by the total development
costs, the deliverable functions, design and architected performance(s), and
the levels of quality expressed as the losses to achieve the deliverable system
performances; (2) the constraints imposed by the development schedule, systems engineering skills, and management skills; (3) and the degree of integration. The scope issues are a constant reminder that development uncovers
many issues that were not envisioned at the beginning of the project. Since
both boundary discussions and scope issues are contractual by their nature,
the discussions with key stakeholders are a convenient, albeit proper means
to deal with such issues.
Nature of a Problem
An example that points out the specific nature of a problem is that faced
when the project is on a tight schedule and a wrong decision in the beginning days of work becomes expensive to correct later and co-opts the schedule with undue additional work. Your mathematicians describe a means of
evaluating two conceptual designs developed for a project in the first week
of work. Both designs seem to address the needs of the customer and appear
workable to the engineers. However, there is no consensus or rationale for a
consensus that favors one design over the other as the designs are only representative of a set of vague requirements from the customer. The designer
has inferred much and liberally made decisions to eliminate uncertainties.
Early designs are conceptual in nature and lack the refinements that are
reflected in later-stage design. The schedule of this project is compressed
more than the systems engineers found comfortable, but acceded to their