Page 325 -

296 PART THREE CONVENTIONAL METHODS FOR SOFTWARE ENGINEERING

[ZAH90] Zahniser, R.A., "Building Software in Groups," American Programmer, vol.
3, nos. 7–8, July-August 1990.
[ZUL92] Zultner, R., “Quality Function Deployment for Software: Satisfying Cus-
tomers,” American Programmer, February 1992, pp. 28–41.

PROBLEMS AND POINTS TO PONDER

11.1. Software requirements analysis is unquestionably the most communication-
intensive step in the software process. Why does the communication path frequently
break down?
11.2. There are frequently severe political repercussions when software require-
ments analysis (and/or system analysis) begins. For example, workers may feel that
job security is threatened by a new automated system. What causes such problems?
Can the analysis task be conducted so that politics is minimized?

11.3. Discuss your perceptions of the ideal training and background for a systems
analyst.

11.4. Throughout this chapter we refer to the "customer." Describe the "customer"
for information systems developers, for builders of computer-based products, for sys-
tems builders. Be careful here, there may be more to this problem than you first imag-
ine!
11.5. Develop a facilitated application specification techniques "kit." The kit should
include a set of guidelines for conducting a FAST meeting and materials that can be
used to facilitate the creation of lists and any other items that might help in defining
requirements.
11.6. Your instructor will divide the class into groups of four or six students. Half of
the group will play the role of the marketing department and half will take on the role
of software engineering. Your job is to define requirements for the SafeHome secu-
rity system described in this chapter. Conduct a FAST meeting using the guidelines
presented in this chapter.
11.7. Is it fair to say that a Preliminary User's Manual is a form of prototype? Explain
your answer.
11.8. Analyze the information domain for SafeHome. Represent (using any notation
that seems appropriate) information flow in the system, information content, and any
information structure that is relevant.
11.9. Partition the functional domain for SafeHome. First perform horizontal parti-
tioning; then perform vertical partitioning.
11.10. Create essential and implementation representations of the SafeHome
system.