4. Approach

4.3. Non-Functional Requirements

The non-functional requirements specify how the system should behave and it is typically responsible for the definition of the overall qualities or attributes of the application. It places restrictions on the product being developed, its process, and specifies external constraints that the product must meet.

The following non-functional requirements were established within the context of this application:

  • Availability – the application should be always available in order to allow that top management query the data and draw conclusions when appropriate. It is considered especially critical the availability on weekdays;
  • Performance – the application must offer short response times, i.e., the information must be available within few seconds since it is requested a spreadsheet update with data from the DW;
  • Usability – the organization of information in the decision-cube should be logical and intuitive in order to be simple, fast and easily interpreted and perceived by its users. It is intended that a user through a brief training of 5 minutes, should be able to use all the application functionality in less than 15 minutes;
  • Security – the access to information that the solution provides to the end user should only be allowed to grant rights, in particular, to the staff of Administration and Financial Department. The access must be read only.

The portability was not considered as a mandatory non-functional requirement for this project, because users will interact with the system using only desktop interfaces.