248
Engineering Systems Integration
have thought the word was clear, inferred meaning from context, guessed, or
ignored the word’s meaning and follow along with the discussion to take
away what could be gleaned. The problem may manifest itself later when
the word is used in a different or mistaken manner and a part is built that
does not pass a test or meet a requirement (whether or not the part(s) passed
their tests). Analyzing the part’s failure might focus on various aspects of the
design of the part, the building of the part, the testing or test set-up, milestone
reviews and oversight, or some aspect(s) of communications. The consequence of a failed test means rework and analysis, which adds to schedule
and costs. If these difficulties are assumed to be part of development, and
taken into account when determining budgets and schedules for deliveries,
then there is no problem. A problem only exists when there is a difference
between what can be done and what you need to do, and you do not know
how to achieve what needs to be done. Defining the problem is a process
“. . . which transforms an indeterminate situation into a pattern of factual
data . . .” (Hall 1962).
Defining the Problem
A problem is devised in relation to a need or want of a solution that accomplishes something that cannot be done due to some objective reason(s), that is,
availability, technology, science, opportunity, resources, or desire. A problem
is relative to circumstances, meaning a problem for one person may not be a
problem for someone else. Problems are relative. Therefore, systems engineers (and others) who aspire to find a set of solutions to a problem must be
mindful that there are problems great and small. Great problems demand an
apt consideration of the problem space, that is, the problems that exist in
association with other problems. Such association might be thought of as a
nesting of problems (mix of heterarchical and hierarchical relations), a strict
hierarchy of problems, or an affinity of like-kind problems.
Nested Problems
Nested problems are problems within problems with a relation to the other
problems through an abstraction. The relation between the problems is
amorphous, having more to do with the abstraction that categorizes the
problem than the relation between individual problems. Nested problems
are typically related to some abstract object, whether physical or intellectual.
An example of a nested problem within the domain of physical objects is that
of a house. The abstraction of the house could be considered as a shelter or
living environment. As a shelter, the house (with its myriad of functions that
support “to shelter”) and the boundary of house are well beyond the physical
Engineering Systems Integration
have thought the word was clear, inferred meaning from context, guessed, or
ignored the word’s meaning and follow along with the discussion to take
away what could be gleaned. The problem may manifest itself later when
the word is used in a different or mistaken manner and a part is built that
does not pass a test or meet a requirement (whether or not the part(s) passed
their tests). Analyzing the part’s failure might focus on various aspects of the
design of the part, the building of the part, the testing or test set-up, milestone
reviews and oversight, or some aspect(s) of communications. The consequence of a failed test means rework and analysis, which adds to schedule
and costs. If these difficulties are assumed to be part of development, and
taken into account when determining budgets and schedules for deliveries,
then there is no problem. A problem only exists when there is a difference
between what can be done and what you need to do, and you do not know
how to achieve what needs to be done. Defining the problem is a process
“. . . which transforms an indeterminate situation into a pattern of factual
data . . .” (Hall 1962).
Defining the Problem
A problem is devised in relation to a need or want of a solution that accomplishes something that cannot be done due to some objective reason(s), that is,
availability, technology, science, opportunity, resources, or desire. A problem
is relative to circumstances, meaning a problem for one person may not be a
problem for someone else. Problems are relative. Therefore, systems engineers (and others) who aspire to find a set of solutions to a problem must be
mindful that there are problems great and small. Great problems demand an
apt consideration of the problem space, that is, the problems that exist in
association with other problems. Such association might be thought of as a
nesting of problems (mix of heterarchical and hierarchical relations), a strict
hierarchy of problems, or an affinity of like-kind problems.
Nested Problems
Nested problems are problems within problems with a relation to the other
problems through an abstraction. The relation between the problems is
amorphous, having more to do with the abstraction that categorizes the
problem than the relation between individual problems. Nested problems
are typically related to some abstract object, whether physical or intellectual.
An example of a nested problem within the domain of physical objects is that
of a house. The abstraction of the house could be considered as a shelter or
living environment. As a shelter, the house (with its myriad of functions that
support “to shelter”) and the boundary of house are well beyond the physical