FACULTY OF COMPUTING AND INFORMATION MANAGEMENT

BACHELOR OF BUSINESS IN IFORMATION TECHNOLOGY

BBIT 03107: BUSINESS PROJECT

ONLINE RETAILER SOFTWARE

SYSTEM REQUIREMENT SPECIFICATIONS DOCUMENT

BY
MUNGAI KAGECHU
21/02480

SUBMITTED IN PARTIAL FULFILMENT FOR

THE REQUIREMENTS FOR THE AWARD OF A DEGREE IN BACHELOR OF
BUSINESS IN INFORMATION TECHNOLOGY

SUPERVISOR: FRED OMONDI

Contents
1. Introduction.............................................................................................................................................3
1.1 Purpose..................................................................................................................................................3
1.2 Intended Audience................................................................................................................................3
1.3 Scope.....................................................................................................................................................3
2. Overall Description..................................................................................................................................3
2.1 Product Perspective...............................................................................................................................3
2.2 Product Specifications...........................................................................................................................4
2.3 User classes and traits...........................................................................................................................4
2.4 Operating environment.........................................................................................................................5
2.5 Design and implementation constraints................................................................................................5
2.6 Assumptions and Dependencies............................................................................................................6
3. System Elements.....................................................................................................................................6
3.1 Description and importance of the log-in page.....................................................................................6
3.2 Home page............................................................................................................................................6
3.3 Priority and Database Description.........................................................................................................7
4. Requirements for External Interfaces......................................................................................................8
4.1 User Interfaces......................................................................................................................................8
4.2 Hardware Interfaces..............................................................................................................................8
4.3 Software Interfaces...............................................................................................................................8
4.4 Communications Interfaces...................................................................................................................8
5. Requirements that aren't necessary........................................................................................................8
5.1 Performance specifications...................................................................................................................8
5.2 Requirements for safety........................................................................................................................9
5.3 Security conditions................................................................................................................................9
1. Introduction
1.1 Purpose
This document's goal is to provide a comprehensive overview of the online store
software. The paper will also describe the software's functions, user interfaces,
scope (what the system is allowed to do and what it is not allowed to do),
operating restrictions, and response to external incentives. The system's
developers and end users are both supposed to use the document.

1.2 Intended Audience

The following people are among the system's target market:
i. Burooj Retail Store Administrator
ii. Their clients
Before taking any action, those involved in this project should read this
document.

1.3 Scope
Customers can add or remove products from their cart as needed using this
method. It enables online product marketing, distribution, and sales. Stock
records will be kept, making easy product monitoring possible. Employees will
sign in and out of the application in a different part.

2. Overall Description
2.1 Product Perspective
This method offers a simple way for customers to purchase products without
physically visiting a store, as well as for store owners to sell products. This
suggested method can be used by any inexperienced users and does not require
any technical skills in the field of computers or a high level of education, although
it will be helpful if the user has this understanding.
 2.2 Product Specifications
There are three ways to access the system: Administrator, Customer, and
Employee.

i. Burooj Retail's administrator is in charge of overseeing the Online

Retailer. The administrator's job is to add new products, offer price tags,
assign quantities, and update and track the registered stock data in the
system. The system will also enable profile updates for the
administrator. He will also have access to staff attendance data.
ii. Customer: The customer can purchase goods from the company and
make the necessary payments. The administrator will enter all customer
information into the system's database in order to easily maintain track
of the stock.
iii. Employees will be able to sign in and out of work by logging in.

2.3 User classes and traits

Administrator: The manager of Burooj Retail will be the sole administrator of this
system for online retailers.
The administrator will be in charge of entering all information about the
enterprise's stock into the system. These aspects include adding a new product,
updating and tracking the system's registered stock, allocating the proper
amounts to the products, and supplying a price tag.

Login

Inventory
Info
Administrator

Add &
Delete
Products

Update
Employee
Info. On
Info
Products
Customers
There may be numerous users who become clients.
Customers will have the ability to post and read product reviews, as well as add
items to their shopping carts.

Search
Products

Customer
Write
Reviews

Add To
Cart

2.4 Operating environment

The computer of the business, which is connected to the database, will be used to
access the Online Retailer. To access the system's main database, the computer
must be a part of the enterprise's local area network (LAN).

2.5 Design and implementation constraints

This mechanism offers safety. The login form guards against unauthorized users
abusing the system. Only an authorized operator will be given the authority to
alter in accordance with the conditions. Its additionally trustworthy and fault
tolerant. The system created is built to deal with incorrect inputs. Since data loss
is a big problem, the system features a backup to prevent it. The user must be
well familiar with the programming language used to create the system.
2.6 Assumptions and Dependencies
 Users with access to the system should exercise caution when entering
records into the system because it is expected that they have a
rudimentary understanding of computers.
 The computer that will be utilized in this system is presumed to have a
suitable platform for running the software.
 We make the assumption that a single administrator will input all the data
and accurately record the values from forms and registers.

3. System Elements
3.1 Description and importance of the log-in page
This sign-in page is a feature with a medium level of priority. This is due to the
fact that it is here that the system user submits his or her information to gain
access to the system. The information consists of both the username and the
password.
Stimulus/Reaction
In order for the system to record the user's information in the computer, the
administrator will need to fill out the details on a blank text box that is being
constructed.
Functional specifications
These are its abilities:
1. Enter the user's login information
2. Analyze the data entered to determine whether the user's credentials are valid.

3.2 Home page

Definition and importance
A high importance feature is the home page. This is primarily due to the fact that
all information is presented and client records are disposed of using this feature.
Stimulus/Reaction
The home page serves a number of purposes:
Displaying the system's stock records, changing the user's login information, and
adding new stock information are all examples of this.
Functional specifications
These are its abilities:
1. Should be simple to customize
2. The system should respond quickly to newly entered data.
3. A clear display of the results information is required.

3.3 Priority and Database Description

The database, which keeps system data on the mainframe, is a high importance
feature.

Stimulus/Response
The database feature serves as the system's primary data storage. The database
functionality is made to take user commands and produce the necessary feedback
on the home page.
Functional specifications
1. The system needs to be secure enough to guard database data against
malfunction.
2. In order to prevent data loss, external disks must be used to store data as a
backup.

4. Requirements for External Interfaces

4.1 User Interfaces
• An intuitive graphic user interface (GUI) with useful frames and buttons
• Reports are produced in accordance with requirements

4.2 Hardware Interfaces

RAM: 4GB, HDD: 500GB, and operating system
OS Windows 10

4.3 Software Interfaces

Front end - Final Visual Basic 6.0
Back end - Ms. Access
When wrong data is entered into the modules, error messages will appear to let
the user know that the database cannot read the data because it is invalid.
Furthermore, the system will display a text box asking the user to provide all the
information when the user provides incomplete information and attempts to
submit the details for storage in the database.

4.4 Communications Interfaces

For the computer to access the system's central database, it must be a part of the
enterprise's local area network.

5. Requirements that aren't necessary

5.1 Performance specifications

Records can be updated and tracked easily. The prerequisites for the system's
performance characteristics are all listed below in a methodical order.
• Static specifications.
i. The system creates an underlying database that will reside at the same system,
and the administrative computer will have access to the front end.
ii. The system can only be used by one administrator in this instance and at this
period. However, the system can be expanded so that only a select number of
organization members have access to it.
• Dynamic specifications. These outline restrictions on the system's execution
characteristics. They typically cover response time and system-wide performance.
Now since the suggested program does not take into account these parameters, it
is sufficient provided reaction times are swift and transactions are completed
efficiently.

5.2 Requirements for safety

Information backup is necessary in the event that the data is changed or the
system crashes. External drives will be used for the backup. In order to prevent
the system from becoming vulnerable to attackers, the system will also require
regular updates.

5.3 Security conditions

The primary security is covered by the security requirements. Only the
administrator should manage the system, and only that person should generate
inventory or open new accounts.