What must the new product be able to do? This is the question answered during the requirements phase.
        The first step in achieving some agreement on the answer to this question is to analyze the client's
        current situation. Example: A PC manufacturer wants a new operating ystem. The first step is to evaluate
        the current system and analyze carefully why it is unsatisfactory.
        A commonly held misconception is that during this phase a developer must determine what the client wants.
        The real objective is to determine what the client needs.
        Sometimes the problems lie in poor communication. Problems of this type can be solved by building a
        rapid prototype.

	Requirements Analysis Techniques
	Rapid Prototyping
	Human Factors
	Rapid Prototyping as a Specification Technique
	Reusing the Rapid Prototype
	Other Uses of Rapid Prototyping
	Management Implications of the Rapid Prototyping Model
	Experiences with Rapid Prototyping
	Joint Application Design (JAD)
	Comparison of Requirements Analysis Techniques
	Testing during the Requirements Phase
	CASE Tools for the Requirements Phase
	Metrics for the Requirements Phase
	Object-Oriented Requirements?

NOTE:  A detailed case study is presented in Part 2 of Classical and Object-Oriented Software Engineering with UML and C++, by Stephen R. Schach. The source code for the case study can be obtained on the World Wide Web at www.mhhe.com/engcs/compsci/schach