SIT773 - Software Requirements and Analysis: Requirements Report

This report addresses the requirements for an e-commerce platform based on the Leckie's Choice (LC) case study. It meticulously identifies both functional and non-functional requirements. Functional requirements include a distributed database system for real-time updates, a client-server architecture, a user-friendly interface, and 'and/or/if' functionality to limit promotional item purchases for non-registered users. It also covers search and filtering features, and a user credentials management system. Non-functional requirements emphasize customization of user interfaces for accessibility and the need for robust system performance and scalability. The report references relevant academic sources to support the identified requirements, providing a comprehensive analysis of the software needs.

Identifying and documenting requirements

The requirements are identified following software development principles (Rainford, 2019)and
includes both the non functional and functional requirements (Eriksson, 2015)
Functional requirements
A distributed database system- The system will be database driven and requires a distributed
database (Woodland, 2019) so that any interaction or action on one aspect, such as item selection
and purchase automatically updates all related information, such as stock levels.
Client-server system- The database driven website has a relational database management system as
the back end with a front end for customers to use
User interface- a well designed, responsive, and easy to use user interface with multiple operating
and browser systems compatibility
And/ or/ if functionality in the database- the system will have a database with and/ if/ or
functionalities so that non registered users, for example, cannot purchase more than five
promotional items (Robertson and Robertson, 2013).
Search and filtering feature- The system should enable users to search for items by name, brand, or
use and get a list of results displayed in thumbnails. They should also be able to filter their searches
using various parameters including promotions, price, size, type to further customize their searches.
User credentials management system- The system and ts database must provide users with a front
end portal to either register (for new users) or log in for registered users using provided
authentication measures and this information is stored in the distributed database and can be
updated.
Non-functional requirements
Customization of user interfaces- The system should enable user to change settings such as font size
and appearance (brightness) for those with visual impairments.
Performance and scalability- System performance should not degrade by more than 10% when
multiple users are logged in (Pathak, 2019).

References
Eriksson, U. (2015). Functional Requirements vs Non Functional Requirements. [online] ReQtest.
Available at: https://reqtest.com/requirements-blog/functional-vs-non-functional-requirements/
[Accessed 31 Aug. 2019].
Pathak, S. (2019). 4 Must-Have Technical Requirements for an eCommerce Website - Bagisto.
[online] Bagisto. Available at: https://bagisto.com/en/technical-requirements-for-an-ecommerce-
website/ [Accessed 31 Aug. 2019].
Rainford, M. (2019). Developing Website Requirements - (Functional vs. Non-Functional) -
New2HTML. [online] New2HTML. Available at: http://www.new2html.com/website/developing-
website-requirements-functional-vs-non-functional/ [Accessed 31 Aug. 2019].
Robertson, S. and Robertson, J. (2013). Mastering the requirements process. 1st ed. Upper Saddle
River, New Jersey: Addison-Wesley.
Woodland, C. (2019). 14 Ecommerce Website Requirements for 2019: Does Your Ecommerce
Platform Have What Your Customers Need?. [online] Hitachi Solutions. Available at:
https://us.hitachi-solutions.com/blog/ecommerce-website-requirements/ [Accessed 31 Aug. 2019].