Non-Functional requirements (Mobile)

This document presents the list of standard test environments. Specific test environments for the project should be discussed and approved by the client at the start of the project. Test environments are defined based on the market, target audience, and project specifics.

Localization requirements should describe things that need to be taken into account regarding language changes, such as national standards and metrics, text directions, and etc. Also, a source of translations for texts, videos, images and audio wich must be localized should be included.

• availability and provision of translation;
• interaction of the translation with the interface;
• comparability to regional standards (phone number formats, emails, etc.);
• interaction with possible user languages.

Additional Security requirements must be agreed with the client, developers, and QA:

• Company Admin is responsible for Mobile App content which is generated via the admin panel;

• Super Admin (MobiDev representative) users are able to fully control the whole system including other companies Admins.

• Data Storage security
• Encryption

Usability can describe (if needed due to the project specifics):

1. Compliance with Web Content Accessibility Guidelines (WCAG)
2. Сhanging font sizes are supported by the application (depends on the target audience).
3. How fast is it for users to complete the main actions once they see the interface?
   • Users should have usage instruction for each key business flow.
4. How quickly users can reach their goals?
   • It is possible to create a new task from the main dashboard in less than 5 clicks;
5. Can users return to the interface after some time and start efficiently working with it right away?
6. How often do users make mistakes?
   • The error rate of users submitting their payment details at the checkout page mustn’t exceed 10 percent.
7. Is the design pleasant to use?

Keeping that in mind, you must make these requirements measurable.

Additional Availability requirements must be agreed with the client, developers:

• The system may be available 98 percent of the time during a month.
• The system may be available from Mon to Fri in a time range (1 p.m. - 22 p.m.)
• The part of the system may be available from Mon to Fri in a time range (1 p.m. - 22 p.m.)

Performance requirements must be agreed with the client, developers, and QA:

• The first app launch should take no longer than 2 seconds;
• The app should be responsive with a reaction on the tap less than 300 ms; 
• Maximum response time 3sec;
• Average response time 1 sec;
• Battery Time while using an app;
• maximum/average simultaneous users;
• total number of users;
• Average throughput and the peak number of concurrent active users per device and OS;
• maximum/average actions per time (orders, pays, etc.);

Performance requirements should be added if it has an influence on the main business flow. For example:
1) quiz (quick questions answering is the main part of business logic).
2) aggressive marketing and SEO promotion are planned as a killer feature. (performance one of the important things for perfect SEO).

Reliability requirements must be agreed with the client, developers, and QA:

• The application should not crash in case of a call, application hiding (application going to background), issues with an Internet connection, transfer from wi-fi to mobile Internet, etc.
• Probability percentage, time; (Defined as the probability of a system or system element performing its intended function under stated conditions without failure for a given period of time)
• The number of critical failures, time;
• Mean time between failures;
• Data safety in negative cases;

Expandability and flexibility must be agreed with the client, developers, and QA. The requirements can describe (if needed due to the project specifics):

• Mobile App  should be Expandable for a growing:

  • number of users;

  • maximum/average simultaneous users;
  • number of specified entities (products, items, orders, requests, etc.);
  • add a new location (localization growth);

• Mobile App should be flexible for further converting (integration) into another project.

Legal and Regulatory Requirements should describe (if needed due to the project specifics):

• PCI DSS compatibility;
• HIPAA compatibility;
• Compatibility with any other local/domain law.
• Compliance with software security standards:
  • NIST
  • MISRA-C

 It must be agreed with the client developers and QA.

Requirements for accurate must be agreed with the client, developers, and QA. The requirements can describe (if needed due to the project specifics):

• Location accuracy;
• Barometer accuracy;
• Pedometer accuracy, etc.

Third-Party Services should list (if needed due to the project specifics):

• Payment systems;
• Integrated video/audio/ streaming services;
• Third-Party devices and its software;
• Single sign-on;
• chats;
• etc.

 It must be agreed with the client and developers.