Week 8: Identifying Needs and Establishing Requirements.

Now, what are requirements?

• Statement about an intended product that specifies what it should do or how it should perform.
• Specific, unambiguous & as clear as possible.
• Must know how to tell when they have been fulfilled.

Types of requirement:

in software engineering

• Functional: What they should do.
• Non-Functional: What are the constraints there are on the system and its development

in Interaction Design

• Functional: Capture what the product should do
• Data: Capture the accuracy and value the amounts of the required data
• Environmental: Circumstances in which interactive product will be expected to operate
• User characteristics: Capture the characteristics of the intended user group
• Usability goals: How well the users can perform
• User experience goals: The perceptions of the others

4 Characteristics of Environmental Requirements:

• Physical: How much lighting, noise and dust is expected in the operational environment.
• Social: Social aspect of the interaction design - collaboration and coordination
• Organizational: How good is the user support likely to be, how easily it can be obtained and are there facilities/ resources for training.
• Technical: What technologies will the product run on or need to be compatible with and what technological limitations might be relevant.

4 Main Principles:

1. Context
2. Partnership
3. Interpretation
4. Focus

Stakeholder: Everybody's who is involve in the design production.