Requirement Gathering PT1

Analysis Phase

Requirements

What is a requirements?

Focuses on what must the system do, or characteristics it must have

Determining requirements?
  • Goal is to convert high level bussness requirements into detail requirements that can be implemented
  • Best determined by analyst and customers together
  • Best to make changes no than later
Problems that may cause bad requirements?
  • May not have access to the users
  • Specifications may be lacking
  • Not knowing the requirements at the start
  • Verification and validation of requirements may be hard

What is a Requirements Report?
  • List of function and non functional requirements (prioritised tho not always necessary)
  • Defines the scope
  • Provides info needed in other stages development
  • Verification from the user
Requirements Report example

What is a Function requirement

A process or data the system must do or contain.

process oriented information oriented

What is a non-functional requirement

Behavioural features the system must have (security, usability, speed)

operational performance security cultural political

BEST way do distinguish between the two is, function is anything to do with data for a process anything else in non functional