Page 146 -

ChaPter 4 • InformatIon GatherInG: InteraCtIve methods 113

®
HypeRCAse expeRienCe 4.1

“Well, I did warn you that things aren’t always smooth here hyPeRcase Questions
at MRE. By now you’ve met many of our key employees and 1. Using the interview questions posed in HyperCase, give
are starting to understand the ‘lay of the land.’ Who would have five examples of open-ended questions and five examples of
thought that some innocent decisions about systems, like whether closed questions. Explain why your examples are correctly
to purchase a COMTEX or Shiroma, would cause such hostility? classified as either open-ended or closed question types.
Well, live and learn, I always say. At least now you’ll know what 2. List three probing questions that are part of the Daniel Hill
you’re up against when you have to start recommending software interview. In particular, what did you learn by following up
and hardware! on the questions you asked Daniel?
“It’s funny that not all questions are created equal. I myself 3. List three probing questions that are part of the Snowden
favor asking open-ended questions, but when I have to answer Evans interview. In particular, what did you learn by follow-
them, it is not always easy.” ing up on the questions you asked Snowden?

Figure 4.HC1
Pointing to a question in HyperCase will reveal an answer.

Accomplishing a Structured Analysis of Project Activities
IBM recommends that the JAD sessions examine these points in the proposed systems project:
planning, receiving, receipt processing/tracking, monitoring and assigning, processing, record-
ing, sending, and evaluating. For each topic, the questions who, what, how, where, and why
should also be asked and answered. Clearly, ad hoc interactive systems such as decision support
systems and other types of systems dependent on decision-maker style (including prototype sys-
tems) are not as easily analyzed with the structured approach of JAD.
As the analyst involved with the JAD sessions, you should receive the notes of the
scribe and prepare a specifications document based on what happened at the meeting.
Systematically present the management objectives as well as the scope and boundaries of the
project. Specifics of the system, including details on screen and report layouts, should also
be included.