You are on page 1of 3

List of functional and nonfunctional

requirements
This list of requirements has been organized using The Volere Requirements
Specification Template (Robertson, 2007).

Framework
Development of a tablet application (iPad) from an interactive digital magazine for a
men's footwear brand.

The interactive digital magazine is part of Khepry brand marketing strategy and aims to
add value to the brand, attract and retain potential customers.

The target audience are men of 35 years with interest in fashion.

Non-Functional Requirements (NFR)


The application should:

(Look & Feel)

NFR 1. Be responsive - adaptable (progressive visual content and design) in


different conditions and devices;
NFR 2. Be consistent with the Khepry brand identity;
NFR 3. Look luxurious.

(Usability)

NFR 4. Be easy to use by beginners and advanced users;


NFR 5. Possessing afordances of the interaction elements according to current
standards; (quality of an element to enable the user to identify its functionality
intuitively)
NFR 6. Have a clear and explicit navigation taking into account the usability
heuristics discussed in the chapter;
NFR 7. Use language familiar to the primary audience;

(Accessibility)

NFR 8. Take into account readers with myopia (guarantee accessibility or


assistive functionalities);

1
(Performance)

NFR 9. Provide responses / interaction at a suitable system response time


(maximum 1 seconds);

(Safety)

NFR 10. Be secure (confidentiality, privacy and security of user data);

(Operational and Environment)

NFR 11. Have a good reading outdoors (sunlight);


NFR 12. Have the possibility of being used in offline mode;
NFR 13. Be able to resume reading at the point where you last stopped;
NFR 14. Run on IOS system;

(Cultural)

NFR 15. Be developed in English;

Functional Requirements (NFR)


The application should:

(Contents)

FR 1. Have a "fast reading" area (only titles, pictorial images and headlines);
FR 2. Allow select content to "read later";
FR 3. Have a research area of authors and creators;
FR 4. To have an area of information dissemination on the footwear brand
and the magazine;
FR 5. Possess an area with the library or "digital banking".
FR 6. Have a content page, an editorial, a glossary, a fact sheet and a
contributor’s page for each issue.
FR 7. Have a profile area;
FR 8. There is an area with content selected for "read later";
FR 9. Delete content from the "read later" area after being read (or when
selected a second time);
FR 10. Have an area with information about the author of the article (at the
end of each article);
FR 11. Allow to see large-scale images and zoom;
FR 12. Possess a "favored" content area;

(Management)

FR 13. Possess an area of creation of personal accounts, authentication and


recovery of accounts or passwords;

2
(Communication and social interaction tools)

FR 14. Allowing "follow" authors and creators;


FR 15. Allow "favorite" content;
FR 16. Know how many times each article was "favored";
FR 17. Allow sharing of content on social networks;
FR 18. To have links to the social networks of the authors, the Khepry brand
and the magazine itself;
FR 19. Receive notifications when a "tracked" author or creator is published.

(Brand specific)

FR 20. Allow a link to the site where the specific shoe (which is in the image) is
sold;

References
Robertson, S. R. J. (2007). The volere requirements specification template. New York:
The Atlantic Systems Guild Limited.

You might also like