Complete the crossword, then click on "Check" to check your answer. If you are stuck, you can click on "Hint" to get a free letter. Click on a number in the grid to see the clue or clues for that number.

			1						2		3
	4
5														6	7
											8
9				10
			11										12
	13							14
				15
											16
		17

 Check 

Across: 2. A single action step performed by a single stakeholder and is the smallest part of the business processes. 5. Subdivision of the major project deliverables into smaller, more manageable (granular) components until the deliverables are defined in sufficient detail to support future project activities (such as planning, executing, monitoring & controlling, and closing). 6. A structured process in which users, managers, and analysts work together for several days in a series of intensive meetings to specify or review system requirements 8. Something that occurs at a specific time and place, can be precisely identified, and must be remembered by the system 9. An individual or organization that can influence a project, or can be affected by a project, in some way. 11. A description prepared and endorsed by members of the organization that typically answers these questions: What do we do? For whom do we do it? How do we go about it? 13. The person who makes detailed notes of the happenings at a Join Application Design session. 14. An activity that the system performs, usually in response to a request by a user 15. The boundary between the computerized portion of the application and the users who operate the application but are part of the total system 17. Characteristics of the deliverable, described in ordinary, non-technical language that is understandable to the customer (a type of requirement).

Down: 1. Represents major participants in a process, typically separating different organizations. 3. The totality of the outputs, outcomes, and benefits and the work required to produce them. 4. A term that describes a naturally occurring association between specific things, sometimes called an association 7. In a UML Use Case diagram, an external agent; a person or group that interacts with the system by supplying or receiving data 10. An activity within requirements development that identifies sources for requirements and then uses requirement gathering techniques (e.g., interviews, prototypes, facilitated workshops, documentation studies) to gather requirements from those sources. 12. A set of defined ad-hoc or sequenced collaborative activities (processes) performed in a repeatable fashion by an organization. 16. A standard set of model constructs and notations defined by the Object Management Group