Page 324 -

CHAPTER 11 ANALYSIS CONCEPTS AND PRINCIPLES 295

partitioned, and representations that depict the essence of requirements and, later,
implementation detail, are developed.
In many cases, it is not possible to completely specify a problem at an early stage.
Prototyping offers an alternative approach that results in an executable model of the
software from which requirements can be refined. To properly conduct prototyping
special tools and techniques are required.
The Software Requirements Specification is developed as a consequence of analy-
sis. Review is essential to ensure that the developer and the customer have the same
perception of the system. Unfortunately, even with the best of methods, the problem
is that the problem keeps changing.

REFERENCES

[AKA90] Akao, Y., ed., Quality Function Deployment: Integrating Customer Require-
ments in Product Design (translated by G. Mazur), Productivity Press, 1990.
[AND92] Andriole, S., Rapid Application Prototyping, QED, 1992.
[BAL86] Balzer, R. and N. Goodman, "Principles of Good Specification and Their
Implications for Specification Languages," in Software Specification Techniques (Gehani,
N. and A. McGetrick, eds.), Addison-Wesley, 1986, pp. 25–39.
[BOA84] Boar, B., Application Prototyping, Wiley-Interscience,1984.
[BOS91] Bossert, J.L., Quality Function Deployment: A Practitioner’s Approach, ASQC
Press, 1991.
[CUR85] Curtis, B., Human Factors in Software Development, IEEE Computer Society
Press, 1985.
[DAV93] Davis, A., Software Requirements: Objects, Functions and States, Prentice-
Hall, 1993.
[DAV95a] Davis, A., 201 Principles of Software Development, McGraw-Hill, 1995.
[DAV95b] Davis, A., “Software Prototyping,” in Advances in Computers, volume 40,
Academic Press, 1995.
[GAU89] Gause, D.C. and G.M. Weinberg, Exploring Requirements: Quality Before
Design, Dorset House, 1989.
[HOL95] Holtzblatt, K. and E. Carmel (eds.), “Requirements Gathering: The Human
Factor,” special issue of CACM, vol. 38, no. 5, May 1995.
[JAC92] Jacobson, I., Object-Oriented Software Engineering, Addison-Wesley, 1992.
[JOR89] Jordan, P.W., et al., "Software Storming: Combining Rapid Prototyping and
Knowledge Engineering,” IEEE Computer, vol. 22, no. 5, May 1989, pp. 39–50.
[REI94] Reifer, D.J., “Requirements Engineering,” in Encyclopedia of Software Engi-
neering (J.J. Marciniak, ed.), Wiley, 1994, pp. 1043–1054.
[TAN89] Tanik, M.M. and R.T. Yeh (eds.), "Rapid Prototyping in Software Develop-
ment," special issue of IEEE Computer, vol. 22, no. 5, May 1989.
[WYD96] Wyder, T., “Capturing Requirements with Use-Cases,” Software Development,
February 1996, pp. 37–40.