Mekelle University

Mekelle Institute of Technology

OOSE Documentation Project 2019

Group Names
Nam
e: Id:
MIT/UR/1032/
1) Bruh Tesheme 10
Mengstu MIT/UR/1093/
2) Hadush 10
Submitted to: Instructor Gebrehiwot MIT/UR/1047/ Mezgebe
Mehari (Mercy) 3) Tesfay 10
Yohanes MIT/UR/1001
4) Mesfun 0/10

1|14
 Online Shopping System
Requirements Analysis Document (RAD)

1 Introduction
Introduction this document is the design report for a web-based Shopping
Mall. This is mainly about ‘how to do’ and also will help provide an insight to
the whole system design and implementation of the online Shopping Mall.
This software has the following three main components:
1. Implement the different types of user – Administrator, Customer and
Vendors.
2. Implement shopping cart for checkout and payment procedures.
3. Management of products and orders. This design document mainly consists
of State Machine/ Activity Flow Diagrams, Class Design, Internal Data
Structures, Architectural design, User Interface and Testing. The main
purposes of this design document are listed below.
1. Precise understanding of the requirements and constraints related with the
programming language, and User Interface.
2. System decomposition into manageable units or modules.
3. Abstraction of the system implementation with the help of classes.
4. Provide a basic outline of the User Interface of the online shopping
System.

1.1 Purpose of the system:

Online shopping is systems which can be make a market within different
places. It reduces the distance-time and transportation efforts of merchants and other
stakeholders and it can be access/ available at any time which the customer can need.

The purpose of this project is to create a functional website for people to be able to
both buy and sell goods. Users of this website will be able to create an account which
will supply them with an easy to use interface in order to both purchase items listed by
other users and sell items to other users. The basic requirements state that the users
will be able to securely register and manage their profiles.

2|14
 1.2 Scope of the system
For this project we want to define what will be done such that the final
product meets expectations. With this in mind, the following are the parts that will
be completed:

2 Secure registration and profile management facilities for customers • Browsing

through the e-Mall to see the items that are there in each category of products
like Apparel, Kitchen Accessories, Bath Accessories, Food, etc.
3 Adequate searching mechanisms for easy and quick access to particular
products and services

3.1.1 Payment mechanism and gateway for all popular credit cards, checks and
other relevant payment options.

4 We will create a shopping cart so that the customers can save their items and
checkout later with the entire shopping cart. A sorting mechanism for products
in each category such as: most purchased, price from low to high, and newly
listed.

1.3 Objectives and success criteria

5 The main objectives of Online Shopping are:
6 Selling products within technology aid.

7 Delivering Products within the countries of the world.

8 Exporting Different Goods and services to the worldwide customers.

9 Compute services and advertise goods that are available.

10 Create Opportunity for all men’s.

11 Success Criteria’s

12 Success in development and requirement analyzing phase.

13 Get a best satisfaction from customers for the system.

1.4 Definitions, Acronyms and Abbreviations

14 DB – Database.
15 RAD – Rapid Applications Development.
16
3|14
 1.5 References
http://krex.kstate.edu/dspace/bitstream/2097/1109/1/ChaitanyaMittapelli2008.pdf

http://www.ietymec.org/papers/N12.pdf

http://osmlite.googlecode.com/files/OSM_SRS_v0.1.dochttp://osmlite.googlecod
e.com/files/OSM_SRS_v0.1.doc

http://www.it.iitb.ac.in/~kamlesh/Page/Reports/oos-project-report.pdf

http://www.scribd.com/doc/15442179/Shopping-Cart-Software-RequirementHYPERLINK

1.6 Overview
Online Shopping System will provide easy access to consumers to products from
different vendors without having to walk into the particular stores. It will also help
vendors by reaching out to more and more customers through internet. It will be a win-
win situation for all. The software will be designed to be easy to use with very good and
intuitive CHI (Computer Human Interface) and reliability. It will be available to customers
and vendors round the clock.

The remaining sections of this document provide a general description, including

characteristics of the users of this project, the product's hardware, and the functional
and data requirements of the product. General description of the project is discussed in
section 2 of this document.

Section 3 gives the functional requirements, data requirements and constraints and
assumptions made while designing the E-Store. It also gives the user viewpoint of
product. Section 3 also gives the specific requirements of the product. Section 3 also
discusses the external interface requirements and gives detailed description of
functional requirements. Section 4 is for supporting information

In our project, we will be developing an online shopping system for all of our
stakeholders. There will be two sets of stakeholders:

External stakeholders and internal stakeholders.

17 External-stakeholders: consist of suppliers, banks, governments, deliverers,

shareholders, investors, and customers. The primary requirement is the case with which
they can find, transport, and purchase needed items.
18 Internal stakeholders consist of employees, marketers, managers, owners, and
developers. Their primary requirement may be profit, both short and long-term. For
these reasons, each group of stakeholders will want the website to emphasize high-
margin item. Managers, another group of stakeholders, will require the application to
track visitors. The application’s developers are stakeholders too: They may want to use
new development technology to keep up to date.

4|14
19 Technologies to be used
20 MS Project - Project management software which is used to develop plans, assign
resources, and create time lines.
21 MongoDB– Database Management System.
22 Visual Studio code- Implementation

2. Current System
You can visit, sell and Buy at an online. We encourage merchants to do this so they can
get a sense of the system behavior and logic to get and sell access to their goods.

3. Proposed System
Online shopping eliminates hundreds, if not thousands, of individuals who
seem to have decided to shop on the same day.

3.1 Functional Requirements

3.1.1 for Users:
Basic Account features are required for both Customers and Sellers. This includes

23 Registering
24 Login
25 Forgot/change passwords

26 “Account Details” section containing contact details

27 Browse and Search:

28 User should be able to browse through the entire items list by modifying certain
selection criteria's such as: Item category, Price range selection, Item/Seller Rating
based selection

29 In addition to providing the above mentioned search feature, user should also be
able to search for a particular product

30 This is applicable to all stakeholders (Guests, Customers, Sellers and Administrators)

31 Shopping:

32 Add / remove items to their shopping cart/list

33 Customer should have the option to buy desired item(s) sold by one or more sellers.
34 Customer will have access to finalize product lists of items she wishes to buy and
make the final payment

5|14
35 The website should support all popular credit cards and make sure that the
transaction happens securely
36 History

 Shopping history: List of items previously shopped

 Item View history: List of recently viewed items

 Search history: Recent search criteria used by a customer.

3.1.2 for Sellers

 Account Setting

 The requirements specified in the Accounts section in user requirements

 Shop installation request

 Sellers should get authorization from Administrator before selling products/installing

shop(s) in the mall.

 Transaction history

 Status of all the transactions for a seller.

3.1.3 for Administrators

 Account Setting

 Authorizing shop installation requests

 Updating product information

 Monitoring transactions and keeping track of its status

 Update Seller/Customer/transaction information (In case of system errors/complaints)

3.2 Non-functional Requirements

In systems engineering and requirements engineering, a non-functional
requirement (NFR) is a requirement that specifies criteria that can be used to judge the
operation of a system, rather than specific behaviors.

They are contrasted with functional requirements that define specific behavior or
functions.

Examples are:

37 Usability-easy and accessible for user.

 Performance – for example Response Time, Throughput, Utilization,
Static Volumetric.
 Scalability.
 Capacity.
6|14
  Availability.
 Reliability.
 Recoverability.
 Maintainability.
 Security.

3.2.1 Usability
For maintaining the robustness of the system and for the safety of customers and
vendors, we will ensure following in the project:

 Overall system quality should be good and it should be a smooth experience for both
vendors and customers.

 The system should be easy to maintain. We will be using object oriented programming
techniques.

 The system will remain up at all times. The hardware and software should be robust
and will be tested extensively

3.3.2 Reliability
 Customers and vendors details will be secure from outside intruders.

 Safe payment gateways will be used and all the security checks will be made to ensure
a safe deal.

3.3.3 Performance
The product shall be based on web and has to be run from a web server.
The product shall take initial load time depending on internet connection strength which
also depends on the media from which the product is run. The performance shall depend
upon hardware components of the client/customer.

As there are many ways to measure the performance of online shopping in a competitive
market, the main objective is to satisfy the customers. To measure the performance of
the online shopping needs to measure the customer’s satisfaction on the basis of quality,
cost, service level, Delivery and availability, risks involves security, information available
and delivery time.

3.3.4 Security
The system shall use secure sockets in all transactions that include any confidential
customer information. The system shall automatically log out all customers after a period
of inactivity.
The system shall confirm all transactions with the customer’s web browser. The system
shall not leave any cookies on the customer’s computer containing the user’s password.
The system shall not leave any cookies on the customer’s computer containing any of
the user’s confidential information.

7|14
3.3.5 Design and Implementation
In order to create good software, design constraints and other contingencies need to be
addressed. In this section we will enumerate any and all considerations that must be
made when creating this project.

 Must be coded efficiently enough to run well on provided server hardware

 Client side code and/or web pages must be able to run efficiently on low end hardware

 The database will be created and maintained in a way that makes it of reasonable
and manageable size.

Class diagrams and activity Diagrams provide a schematic representation of the

various classes used and design flow respectively.

The diagrams were prepared using UML diagram tool. The Consolidated Activity
diagram provides a model to visualize the flow in the system as a whole. The class
diagrams also hold the data structures that would be used and also their data types.
The System will be implemented using NodeJs as the programming language.
MongoDB database will be used to store vital user, product and order information.

3.3.6 Interface
There are many types of interfaces as such supported by the E-Store software system
namely;
 User Interface,
 Software Interface and
 Hardware Interface.
 The protocol used shall be HTTP.
 The Port number used will be 80.
 There shall be logical address of the system in IPv4 format.

3.3.6.1 User Interfaces

8|14
The user interface for the software shall be compatible to any browser. The user
interface shall be implemented using any tool or software package like Java Applet.
3.10.2 Hardware Interfaces
Since the application must run over the internet, all the hardware shall require to
connect internet will be hardware interface for the system.
3.10.3 Software Interfaces
1. The system shall communicate with the Configuration to identify all the available
components to configure the product.
2. The system shall communicate with the content manager to get the product
specifications, offerings and promotions.
3. The system shall communicate with bill Pay system to identify available payment
methods, validate the payments and process payment.
4. The system shall communicate to credit management system for handling financing
options & with CRM system to provide support and with Sales system for order
management.

3.4 System Models

System Model After carefully analyzing the requirements and functionality of the web
application, I had two important diagrams by the end of the analysis phase. They are the
ER diagram and data flow diagram which were the basis for finding out entities and
relationships between them, the flow of information.

ER Diagram

UML Component Diagram

Data Flow Diagrams

9|14
3.4.2 Use Case Models
Use cases and activity flow
Activity Flow associated with the system administrator

Activity Flow associated with a shop owner

10|14
 Activity Flow associated with a registered user

Use case Models are usually referred to as Behavioral Methods used to describe a
set of actions (use cases) that some system or systems (subject) should or can
perform in collaboration with one or more external users of the system (actors).
Each use case should provide some observable and valuable result to the actors or
other stakeholders of the system.

11|14
Use case model

3.4.3 Object Model

12|14
 3.4.3.1 Data Dictionary

Entity Name Entity Description

Column_Na Column_Descripti Data Type Length Primary Unique Nullab
me on Key le

ID This is the user Varchar 50 True False False

or customer id
to sell or buy
items.

PayPal PayPal is the Int 50 False False True

Account No. account type
you pay online

Phone No. The phone Int 15 False False false

number of a
customer

3.4.3.2 Class Diagrams

 The purpose of the diagram is to introduce some common terms, "dictionary" for
online shopping – Customer, Web User, Account, Shopping Cart, Product, Order,
Payment, etc.
 It could be used as a common ground between business analysts and software
developers.
 Each customer has unique id and is linked to exactly one account. Account owns
shopping cart and orders. Customer could register as a web user to be able to buy
items online. Customer is not required to be a web user because purchases could also
be made by phone or by ordering from catalogues. Web user has login name which
also serves as unique id. Web user could be in several states - new, active, temporary
blocked, or banned, and be linked to a shopping cart. Shopping cart belongs to
account.
13|14
3.4.4 Dynamic Model
Dynamic Model for online shopping, may resides to Customer searching or
browsing items add or remove items from shopping cart, do checkout.

4) Glossary
The application can be used for any E-commerce application. It is easy to use, since it
uses the GUI provided in the user dialog. User friendly screens are provided. The
application is easy to use and interactive making online shopping a recreational activity
for users. The ‘Online Shopping’ is designed to provide a web based application that
would make searching, viewing and selection of a product easier. The search engine
provides an easy and convenient way to search for products where a user can search for
a product interactively and the search engine would refine the products available based
on the user’s input. The user can then view the complete specification of each product.
They can also view the product reviews and also write their own reviews. Use of Ajax
components make the application interactive and prevent annoying post backs.

14|14