252
Engineering Systems Integration
general systems design developed, a concept of operations presented, a highlevel architecture presented, and perhaps an initial feasibility study must be
completed. In this manner, the extent of the problem domain can be compared within the nested problem space to assure that the correct problem
domain is identified. Nested problems require the most analysis and care to
discern the actual problem and the nature of the problem.
If the discussion with the stakeholder(s) indicates a hierarchical problem,
then the systems engineer needs to identify the root (or top-level) problem in
the hierarchy. Asking the question why at each level of the hierarchy exposes
the next higher level of the problem set. For example, why do I have a problem arriving at work at 8:00 a.m.? (I do not get up early enough to avoid the
traffic.) From this point, the questioning can (and should) proceed in any
number of directions. Why do I not get up earlier? (I stay up too late and I
need 8 h of sleep.) This question and answer suggest that the problem might
be related to trying to accomplish too much or taking too long to complete
certain tasks. The problem could be phrased as taking too much time to complete tasks delays the start of required sleep, thereby causing me to be late to work.
The solution sets are plentiful:
Objective (1): Eliminate some of the previous day’s activities, and go to
bed earlier.
Objective (2): Learn to complete the work faster.
Objective (3): Train to get by on less sleep.
Objective (4): Get help with the tasks.
Objective (5): Negotiate with the boss to have some tasks completed
by others.
Objective (6): Some of the tasks are irrelevant; do not even start them.
Objective (7): Change jobs.
And further, why is there so much traffic when I want to commute by
bicycle? (Everyone needs to be at work at 8:00 a.m. as this is the current
schedule for all the business in the area.) This question and answer suggest
that the problem might be to encourage public transportation, lobby for bicycle lanes, work from home, or go to the beach (or fishing) and work outdoors.
What problem domain is important enough for the stakeholders to reach
consensus? Defining the problem is itself problematic. Identifying a symptom and offering a palliative solution are quickly revealed as eye candy.
Considered analysis upfront avoids false starts to the effect that the real
problem is discovered after exposing the sham during reviews.
Characteristics of a Problem
Identifying the problem is as much about understanding the context of the
problem as it is about knowing what the stakeholders believe they need. It is
Engineering Systems Integration
general systems design developed, a concept of operations presented, a highlevel architecture presented, and perhaps an initial feasibility study must be
completed. In this manner, the extent of the problem domain can be compared within the nested problem space to assure that the correct problem
domain is identified. Nested problems require the most analysis and care to
discern the actual problem and the nature of the problem.
If the discussion with the stakeholder(s) indicates a hierarchical problem,
then the systems engineer needs to identify the root (or top-level) problem in
the hierarchy. Asking the question why at each level of the hierarchy exposes
the next higher level of the problem set. For example, why do I have a problem arriving at work at 8:00 a.m.? (I do not get up early enough to avoid the
traffic.) From this point, the questioning can (and should) proceed in any
number of directions. Why do I not get up earlier? (I stay up too late and I
need 8 h of sleep.) This question and answer suggest that the problem might
be related to trying to accomplish too much or taking too long to complete
certain tasks. The problem could be phrased as taking too much time to complete tasks delays the start of required sleep, thereby causing me to be late to work.
The solution sets are plentiful:
Objective (1): Eliminate some of the previous day’s activities, and go to
bed earlier.
Objective (2): Learn to complete the work faster.
Objective (3): Train to get by on less sleep.
Objective (4): Get help with the tasks.
Objective (5): Negotiate with the boss to have some tasks completed
by others.
Objective (6): Some of the tasks are irrelevant; do not even start them.
Objective (7): Change jobs.
And further, why is there so much traffic when I want to commute by
bicycle? (Everyone needs to be at work at 8:00 a.m. as this is the current
schedule for all the business in the area.) This question and answer suggest
that the problem might be to encourage public transportation, lobby for bicycle lanes, work from home, or go to the beach (or fishing) and work outdoors.
What problem domain is important enough for the stakeholders to reach
consensus? Defining the problem is itself problematic. Identifying a symptom and offering a palliative solution are quickly revealed as eye candy.
Considered analysis upfront avoids false starts to the effect that the real
problem is discovered after exposing the sham during reviews.
Characteristics of a Problem
Identifying the problem is as much about understanding the context of the
problem as it is about knowing what the stakeholders believe they need. It is