TCC125/05 Software Development Models: E-shop Online System Report

This report presents a Software Requirements Specification (SRS) document for an E-shop online system, designed to facilitate online product sales. The report begins with an introduction outlining the purpose, scope, and target audience of the system. It then provides an overall description of the product, detailing cart management, order details, and customer management functionalities. The report includes a comprehensive requirements analysis, specifying interface, functional, and non-functional requirements. The data model section provides use case and data flow diagrams, along with a data dictionary. The document concludes with software and hardware requirements, planning details using the waterfall model, and a discussion of the system's successful implementation. This report is a detailed outline of the entire software development lifecycle for the E-shop online system.

Running head: SOFTWARE DEVELOPMENT
SOFTWARE DEVELOPMENT
Name of the Student
Name of the University
Author Note

1SOFTWARE DEVELOPMENT
1. Introduction
a. Purpose
The main purpose of this report is to discuss the development of E-shop Online System. It is
developed to provide several products from different brands to the customers. The document
includes the design and modelling of the planned system along with the structure and
functionalities of the system.
b. Document Conventions
c. Target Audience
This project is based on design and development of an online system that provides products to
the customers who register on the website. The targeted audiences are the people who prefers
online shopping over offline using electronic devices. It has been implemented considering the
basic features of E-commerce website exists around the world (Pogorelova et al., 2016). It will
be useful for the customers and save their time.
d. Project Scope
The main scope of the project is to enable the purchasing of the products for the people. The
company has the aim to successfully implement the project and provide the business to the
customers. They have goals set to achieve a market share around the world.
2. Overall Description
a. Product Perspective
 Cart Management:

2SOFTWARE DEVELOPMENT
It is consisting of product selection from the website and adding them into cart for
purchasing multiple products. It stores the product, quantity and price of the each unit to
calculate the final amount value of the cart (Jagtap & Hanchate, 2017).
 Order Details:
In includes order number, customer details, products ordered, quantity and delivery
address of the products. The information is stored in the database to manage the
operations of the system.
 Customer management:
It manages the registered customer of the system along with their basic details.
Customers can also save their payment details for fast checkouts (Wang, Cavusoglu &
Deng, 2016). Customers are identified with their Customer ID.
b. Product Functionalities
The major features of the product is that customer can register and login in the system to search
and purchase products. The products can be searched using keywords and tags. Multiple
products can be purchased with the help of the cart management system (Mall, 2018). Lastly the
user can make payment of the total cart value to complete the purchase.
c. Constraints and Assumptions
Constraints:
1. SQL commands for search query on website.
2. Implementation of cloud based centralized database for backend.
3. The database schema for optimized queries.
Assumptions:

3SOFTWARE DEVELOPMENT
1. A request for change delivery address, update password and cancellation of the order in
appropriate situations by the customer.
2. Calculation of the total value of the cart including the taxes and delivery charges.
It has been assumed that the above assumptions are single and separate transactions and used in
th development of the website.
3. Specific Requirements Analysis
a. Interface Requirement
The interface is a web based interaction between the user and the system. For the front end,
languages such as HTML, CSS and PHP. The framework uses forms and clicks for input
validation. The system uses backend as JavaScript and SQL database. The layout used for the
webpages are grid based column layout (Bonastre & Granollers, 2014). The interface
communicates with the user, from the registration process till the payment.
b. Functional Requirement
Functional requirement of the E-shop online system can be listed below:
i. The users and admins register and log into the system to use main features of the website.
ii. The user can search for the products using keywords.
iii. The user can check the availability of the product based on the location or delivery
address.
iv. The user can raise concerns regarding any issues to the admin such as forgot password,
delivery address change, update profile or cancellation of the order etc.
v. The user can select the products and add them into their cart.

4SOFTWARE DEVELOPMENT
vi. The user can update and view the cart.
vii. The user can proceed to checkout from the cart.
viii. The user can make payments and update profile details.
ix. The admin can also update their profile.
x. The admin can solve the queries of the customer.
xi. The system is able to check stock level of the products and generate monthly report of the
expenditure and revenue of the inventory and online shop.
c. Non- Functional Requirement
Non-functional requirements are the secondary requirements that do not define the system,
however; essential for operations of the system. Some of the non-functional requirements of the
developed system are given below:
a. The system is available 24x7 to the customers.
b. The system has high capacity to handle large number of users instantly.
c. The system is easily learnable for the new users.
d. The system has high end security in form of password authentication of users and
encrypted information in the database.
e. The system has high usability that has the main aim as providing products to its
customers.

5SOFTWARE DEVELOPMENT
4. Data Model and Description
a. Use Case Model
Figure 1: Use case Model
Source: created by author

6SOFTWARE DEVELOPMENT
b. Data Flow Model
Figure 2: Data Flow Model
Source: created by author

7SOFTWARE DEVELOPMENT
c. Data Dictionary
Customer
Attributes Data type Size Key
Username varchar 10 Primary key
Password varchar 50
Name varchar 50
Address varchar 100
PhoneNumber Int 10
Email varchar 50
Order
Attributes Data type Size Key
OrderID varchar 10 Primary key
Date Date
ProductID varchar 10 Foreign Key
Quantity Int 10
Amount Decimal (8,2)
CustomerUsername varchar 10 Foreign Key
Admin
Attributes Data type Size Key
Username varchar 10 Primary key

8SOFTWARE DEVELOPMENT
Password varchar 50
Name varchar 50
Contact Int 10
Email varchar 50
Address varchar 100
Query
Attributes Data type Size Key
TicketNumber Int 10 Primary key
Date Date
Description varchar 250
Type varchar 50
CustomerUsername varchar 10 Foreign Key
Solution varchar 250
AdminUsername varchar 10 Foreign Key
Products
Attributes Data type Size Key
ProductID varchar 10 Primary key
Type varchar 50
Name varchar 50
Description varchar 100

9SOFTWARE DEVELOPMENT
UnitCost Decimal (8,2)
BrandID varchar 10 Foreign Key
Brand
Attributes Data type Size Key
BrandID varchar 10 Primary key
Name varchar 50
Description varchar 100
Rating Decimal (2,1)
Payment
Attributes Data type Size Key
PaymentID varchar 10 Primary key
PaymentType varchar 50
CardNumber Int 16
OrderID varchar 10 Foreign Key
5. Software and Hardware Requirements
Software requirements:
i Browser
ii operating system (Windows 7 or higher)
iii Microsoft .Net Framework v4.6.1 (or higher)
iv Internet Information Services

10SOFTWARE DEVELOPMENT
Hardware Requirements:
i Processor (2 GHz minimum)
ii Memory (4GB or higher)
iii Hard Disk (50 GB or higher)
6. Planning
a. Process Model
The process model for the E-shop online development is based on six phases of software
development life cycle. The model used for the development is waterfall model (Andry & Loisa,
2016). The process model of the entire development is shown in the figure below.

11SOFTWARE DEVELOPMENT
Figure 3: Process Model of development
Source: created by author
7. Conclusion
The waterfall mode is widely used framework for software development. The
development is done phase by phase. The E-shop online system is developed based on this
model. The main functionality of the system is successfully designed and implemented with the
help of UML use case diagram, front end and backend coding. The data dictionary successfully
represents the structure of the backend database. Lastly the data flow diagram represents the flow
of data for each of the processes identified. Hence, it can be said that the development of the E-
shop online system is successfully completed.

12SOFTWARE DEVELOPMENT
8. References
Andry, J. F., & Loisa, J. (2016). The e-Commerce Potential for Home-Based Businesses: A Case
Study. Jurnal Ilmiah Fifo, 8(2), 139-146.
Bonastre, L., & Granollers, T. (2014, March). A set of heuristics for user experience evaluation
in e-commerce websites. In 7th International Conference on Advances in Computer-
Human Interactions (pp. 27-34). IARIA.
Jagtap, S. S., & Hanchate, D. B. (2017). Development of Android Based Mobile App for
PrestaShop eCommerce Shopping Cart (ALC). International Research Journal of
Engineering and Technology (IRJET), 4(07), 2249-2254.
Mall, R. (2018). Fundamentals of software engineering. PHI Learning Pvt. Ltd..
Pogorelova, E., Yakhneeva, I., Agafonova, A., & Prokubovskaya, A. (2016). Marketing Mix for
E-commerce. International journal of environmental & science education, 11(14), 6744-
6759.
Wang, S., Cavusoglu, H., & Deng, Z. (2016). Early mover advantage in e-commerce platforms
with low entry barriers: The role of customer relationship management
capabilities. Information & Management, 53(2), 197-206.