The difference between functional and non-functional requirements is that:

	Functional requirements, focus on the business uses of the system and functions the users carry out; and non-functional requirements focus on technology constraints and performance goals
	Functional requirements are concerned with Domain Layer logic, and non-functional requirements are concerned with presentation layer logic
	Functional requirements are concerned with Internal Stakeholders, and non-functional requirements are concerned with external stakeholders
	Functional requirements are gathered through interviews and questionnaires, and non-functional requirements are gathered through researching vendor solutions and observation.

To identify classes for the system, analysts can use two techniques. Those are:

	Association Technique and Verbal Phrase technique
	User Goal Technique and Event Decomposition Technique
	Brainstorming Technique and noun technique
	Data Entity technique and Generalization technique

In UML notation the includes relationship connects two use cases. The use case that is "included" use case is the one which _______ .

	cannot be determined
	is connected to the head of an arrow
	is connected to the tail of an arrow
	is not connected to an actor

All of the following are reasons to use models in Systems Analysis and Design except:

	Reducing complexity by abstraction
	Communicating with other development team members and stakeholders
	Document what was done for future maintenance/enhancement
	Enhance the quality of information gathered