Introduction

• A requirement is something the product must do or a quality that the product must have.-
• Requirements specifications can include prototypes, screenshots and other media.
• When written, they should be clear, unambiguous, and framed so that it will be possible to test whether the requirement has been met in the final system.

Types of requirements:

• Functional requirements – what the system must do
• Non-functional requirements – qualities that the system must have
  • can affect the acceptability, sales, or usage
  • cover different aspects of design (e.g., usability, UX, performance, maintainability, security, cultural acceptability, legal restrictions)
• How the technology will meet the requirements is not specified (this comes later during the design activity)

Prioritizing requirements: MosCoW Rules

• Must have – fundamental requirements; these determine the minimum viable product (MVP)
• Should have – “if time permits”
• Could have – lesser importance
• Want to have but Won’t have – can wait until next development cycle

Query techniques

Focus groups

Focus groups are:

• Group discussions, lasting approximately one-two hours, chaired by moderator
• Widely used in market research and new product design
• It can collect opinions of proposed development or views on current practice.