5 - the requirements phase

5 - the requirements phase - The Requirement Phase...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
The Requirement Phase Requirements describe what the system is supposed to do using o Natural language o Diagrams o Other notation An important requirement of requirements is that they are understood by the customer/client for concept exploration/feedback/validation o Not too much technical jargon
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Elicitation Techniques Interviews o structured, planned, close-ended conversations o unstructured, encouraged to speak and brainstorm o in our case interview each other make sure you are all on the same page System/documentation inspection o Look at other similar systems to see if there is functionality that might want/need to incorporate Paper prototypes o Hand sketches of interface storyboard to determine scenarios Scenarios o A scenario is a way a user might use a target product to accomplish some objective o An easy way for the client to define functionality in an accessible way o Only major system functions should be explored/explained with scenarios. o
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 10/03/2011 for the course CSC 592 taught by Professor Staff during the Spring '11 term at Rhode Island.

Page1 / 4

5 - the requirements phase - The Requirement Phase...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online