MERU UNIVERSITY OF SCIENCE AND TECHNOLOGY

SCHOOL OF COMPUTING AND INFORMATICS

DEPARTMENT OF COMPUTER SCIENCE

Requirements Specification document

Project title: ONLINE HORTICUTURAL MARKETING AND INFORMATION SYSTEM

Group: BCS Group 10 Supervisor: Mr. Samson Munialo

Group Members:

1. VICTOR MACHARIA- CT201/0071/16

2. NGENO VICTOR - CT201/0039/16

3. VANET KEMUMA - CT201/0055/16

4. MERCY BORE - CT201/0036/16

5. IRENE GERTRAY NAMALE - CT201/0052/16

6. SUSAN MUTISO - CT201/1006/16

1. Introduction

1.1 Purpose of the document

The purpose of this document is to present a detailed description of the online horticultural marketing
information System. It will explain the purpose and features of the system, the interfaces of the system, what the system
will do and the conceptual database design.

1.2. Scope of the Project

This software system will be an online horticultural marketing information System for use within Muranga,
Kirinyaga, Kiambu, Embu and Nyeri counties in the central part of Kenya. This system will be designed to assist
horticultural farmers in selling and purchasing these products, which would otherwise have to be done by middlemen.
By making it easy for the buyer and seller to access a common market the system increases the efficiency of the
marketing process and consequently results in high productivity.

More specifically, this system is designed to allow a buyer to browse for available products, order and make
payments. Similarly, it makes it easy for the seller to supply his or her products and get paid on time. The software will
facilitate up to date relevant information on horticultural products as well as market situation.

2.Overview

The remaining sections of this document provide a general description including the product's hardware and data
requirements of the product. Section 3 gives the specific requirements which includes functional and non-functional
requirements. In addition, it also describes external interface requirements for the systems as well as user classes and
characteristics .It also gives the conceptual database requirement for the system.

3. Specific Requirements
3.1 Functional Requirements
 I. The system shall allow non registered member to freely browse available items.
II. The system shall allow access to general information as well as give feedback features to non-
registered member.
III. The system shall allow the non- registered member to sign up and subsequently register membership
as a buyer/seller account.
IV. The system shall provide login/logout facility for only registered members.
V. The system shall allow a buyer to order and make payments for a product.
VI. The system shall make it easy for the buyer/seller to view/print their transaction statement
VII. The system shall provide for messaging facility to both the buyer and seller for communication
purpose
VIII. The system shall always display current products available alongside their prices
IX. The system shall make it easy for the buyer/seller to pay ,withdraw or check their account balances
X. The system shall allow generation of periodic/on-demand report by the administrator

3.2 External Interface Requirements

3.2.1 User Interfaces

3.2.1.1 Input Forms

a) Buyer Registration form:
The buyer fills in his/her details as per the buyer such as personal details, location details etc.
b) Seller Registration form:
The seller fills in his/her details as per the seller such as personal details, horticultural niche etc.
c) Login form:
Allows registered seller/buyer to access their accounts by providing login credentials.
d) Contact us form:
Allows a user to reach the admin.
e) Messages form:

The buyer or seller can read/send personalized messages to the system admin.
 f) Order form:

The buyer orders the selected item by providing order details.

g) Supply item form:

The seller provide product details and wait for picking.
h) Add new Products form:

The admin add new supplied products

3.2.1.2 Reports
a) Buyer/Seller transaction reports
The seller/buyer views/prints detailed payments/purchases receipts and statements
b) General reports
The admin can generate a full report of the number of sellers/buyers, all purchases or supplies as
well as any other relevant information.

3.2.2 Hardware Interfaces

i. Laptop/Desktop PC
 core i3 processor
 4GB RAM

 500GB HDD

Purpose of this pc is to allow buyer and seller to access all the system services.
ii. Smartphone/ Tablet
It acts as an alternative to the laptop/ desktop PC.
iii. Display Unit /Screen Resolution(240*240)
 This unit is for displaying the web pages such as home page, order page etc.

iv. Laser Printer

Simply this device is for printing reports.

v. Wi-Fi router

Wi-Fi router is used to for internetworking operations and data transmission from pc’s to sever.

3.2.3 Software Interfaces

a. Back-End

• PHP- It is most popular and widely used server side scripting language since it is open source
and very simple to use
• MySQL server - Database connectivity and management

• Wamp server- To execute server scripts

• Adobe XD CC - Logo and other designing such as User interfaces

• Visual Studio Code – code editor for front end scripting languages

b. Front-End

• OS – Windows 7/8/8.1/10 or Android OS- Very user friendly and common OSs

• Web browser- viewing web pages.

3.2.4 Communications Interfaces

• NIC (Network Interface Card) - It is a computer hardware component that allows a computer to connect to a
network. NICs may be used for both wired and wireless connections.
 • CAT 5/6 network cable- for high signal integrity

• TCP/IP protocol- Internet service provider to access and share information over the Internet
• ISP Simcard- To allow access to the internet as an alternative to the Wi-Fi router.

• Ethernet Communications Interface- Ethernet is a frame-based computer network technology for local area
networks (LANs)
• Ubiquitous- easy to set up and easy to use. Low cost and high data transmission rates.

3.3 Logical Database Requirements

i. Sellers’ table- stores seller information.
ii. Product table – contains available product details.
iii. Product_category table –contains product categories such as flowers, vegetables etc.
iv. Orders table – keeps track of all purchase transactions
v. Sales table - keeps track of all sales transactions
vi. Buyer_account table – contains the account details of the buyer
vii. seller_account table – contains the account details of the seller
viii. Message table- keeps track of all the messages

3.4 Non-functional Requirements

3.4.1 Performance Requirements

• Response time-The system will give responses within 5 seconds after checking the product information and
other information.
• Capacity-The system must support 100 people at a time

• User interface- User interface screen will response within 5 seconds.

3.4.2 Safety Requirements
If there is extensive damage to a wide portion of the database due to catastrophic failure, such as a disk crash,
the recovery method restores a past copy of the database that was backed up to archival storage and reconstructs a more
current state by reapplying or redoing the operations of committed transactions from the backed up log, up to the time
of failure.

3.4.3 Security Requirements

All the administrative and data entry operations have unique logins so that the system can filter who is loging in
to system at a particular time.

3.4.4 Software Quality Attributes

 Availability: The system shall be available all the time.

 Correctness: A bug free software which fulfill the correct need/requirements of the client.
 Maintainability: The ability to maintain ,modify information and update/ fix problems of the system
 Usability: software can be used again and again without distortion.

 Accessibility: Administrator and many other users can access the system but the access level is controlled for
each user according to their work scope.

 Accuracy: The reliability on the information/output. The outcome can be depended upon.

4. User Classes and Characteristics

● Admin

Admin has the full access to the system which means he is able to manage any activity with regard to the
system. He is the highest privileged user who can access to the system.

Key functions
 ✓ Manage users

✓ Generate reports

✓ Resolve payment issues

✓ Remove/suspend users

✓ Update system information

✓ Add/ remove products

✓ Verify seller items

● Seller

Interacts with the systems most often to provide details of ready products .

Key functions

✓ Supply products

● Buyer

Interacts with the systems most often to purchase products supplied by sellers

Key functions

✓ Make purchases
 Min03. (10)/19/3: Development of an SRS Document:

04.1: Division of word and task completion:

The literature review section was done in 3 phases each taking

TASK CONCERNED DURATION

1. Introduction MERCY BORE 2 days
1.1 Purpose of the document
1.2 Scope of the project
2. Overview
3.Specific Requirements NGENO VICTOR 3 days
3.1 Functional Requirements
3.2 External Interfaces
3.2.1 User Interface
3.2.2 Hardware Interface
3.2.3 Software Interface
3.2.4 Communication Interface
3.3 Conceptual Database requirement
3.4 Non-functional requirements KEMUMA VANET 3 days
3.4.1 Performance requirements
3.4.2 Safety requirements
3.4.3 Security requirements
3.4.4 Software quality attributes
4. User Classes and Characteristics
Verification, discussion and conclusion of the SRS document All Members 3 hrs

04.2: Challenges encountered:

1. Understanding abstract user requirements and using them to come up with a model of requirements.
2. Time constraints especially when analyzing interfaces and database tables.