Establishing Requirments

Four basic activities in Interaction Design:

1. Identifying users, their needs and requirements

2. Developing alternative designs

3. Building versions of the designs

4. Evaluating designs

What is Requirements Analysis?

Requirements analysis is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed.

Requirements analysis is taken at the early stage of development life cycle in traditional methodologies where it will take place in iterative cycles. Requirements analysis is initially taken place after feasibility study and requirements gathering to  identify and distinguish essential user requirements in order to build the development path. once the requirements are gathered , they will be analysed and organised according to following categories;

Functional

• What the system should do
• Historically the main focus of requirements activities

Non-functional

• memory size
• response time

Data

• What kinds of data need to be stored?
• How will they be stored   

Why establish requirements for a mobile app?

Establishing requirements for mobile applications is important because it helps to understand and justify user needs and also it can be related to data. 


The Volere Requirements Specification Template

The Volere Requirements Specification Template is intended for use as a basis 
      for your requirements specifications. The template provides sections for each 
      of the requirements types appropriate to today's software systems.

Requirements types according to Volere Requirements Specification Template;
  

    Functional requirements are the fundamental or essential subject matter of  the product. They describe what the product has to do or what processing  actions it is to take. 

   Nonfunctional requirements are the properties that the functions must have, such as performance and usability. Do not be deterred by the unfortunate type name (we use it because it is the most common way of referring to these types of requirements)—these requirements are as important as the functional requirements for the product’s success.

   Project constraints are restrictions on the product due to the budget or the time available to build the product.

    Design constraints impose restrictions on how the product must be designed. For example, it might have to be implemented in the hand-held device being given to major customers, or it might have to use the existing servers and desktop computers, or any other hardware, software,or business practice. Project drivers are the business-related forces. For example, the purpose of the project is a project driver, as are all of the stakeholders each for different reasons.

    Project issues define the conditions under which the project will be done. Our reason for including them as part of the requirements is to present a coherent.