Faculty of Information Technology

Department of Software Engineering

SYSTEM PROPOSAL

Eyes Shopping(E.S)

Date: 7/6/2021

Prepared by :

1. Zaid Mohammad
2. Firas Salah
3. Junied Khaled
4. Alaa aldeen

Supervised by:
<Aysh Alhroob>
Table of Contents
1 OVERVIEW........................................................................................................................................................2
1.1 PURPOSE, SCOPE AND OBJECTIVES...................................................................................................................3
2 SYSTEM REQUEST..........................................................................................................................................4
2.1 PROJECT SPONSOR....................................................................................ERROR! BOOKMARK NOT DEFINED.
2.2 BUSINESS NEED.................................................................................................................................................4
2.3 BUSINESS REQUIREMENTS.................................................................................................................................4
2.4 BUSINESS VALUE...............................................................................................................................................4
2.5 SPECIAL ISSUES.................................................................................................................................................4
3 FEASIBILITY ANALYSIS................................................................................................................................5
3.1 TECHNICAL FEASIBILITY...................................................................................................................................5
3.2 ECONOMIC FEASIBILITY....................................................................................................................................5
3.3 ORGANIZATIONAL FEASIBILITY........................................................................................................................5
4 WORK PLAN AND GANTT CHART..............................................................................................................6
5 REQUIREMENT DEFINITION.....................................................................................................................10
6 FUNCTIONAL MODELS................................................................................................................................11
7 STRUCTURAM MODELS..............................................................................................................................14
8 BEHAVIORAL MODELS...............................................................................................................................17

2
1 OVERVIEW

1.1 Purpose, Scope and Objectives

Purpose: The purpose of this project is to facilitate the process and to spread the culture
of buying and selling products online, collecting shops in one location that facilitates
access to them at any time and any place, and to let the customer have multiple ways of
paying.

Scope: The scope of this project includes all shops and their products are accessible to
phones and tablets with either Android or IOS, and also accessible to laptops and pc’s.

Objectives: The main objective of this project is to expand the circle of buying and
selling merchandise online, to make it easier for the customer to fulfil his own needs in
less time, effort, money, and to provide the seller with more space to sell products and
gain customers without the need of opening multiple branches, and all of that is done by
providing the customer and the store owner an environment for buying and selling
products that is easier and faster to use compared to other traditional ways.

3
2 SYSTEM REQUEST

2.1 Project sponsor: Golden Sun Company (G.S.C),Amman, Mecca St,

Mecca towers complex, ZIP code (11953), Phone Number((06)-5520307).

2.2 Business need: The need for this project is that it will increase the
percentage of profits for the seller, to make it easier for the customer to access
the product easily, and reduce traffic crises that the world is witnessing today.

2.3 Business requirements

1) A special page can be created for the customer.
2) A special seller page can be created.
3) The possibility of delivery to all governorates.
4) Serves all operating systems from android and IOS.
5) The website can be reached through any search engines.
6) Available for all ages.
7) There is the possibility of paying directly upon receipt or paying
online(Visa, PayPal, Master Card, Debit Card, Smart Card(.

2.4 Business value: This project will increase the percentage of sale in
stores by about 30% of the percentage of sale, and it will save the customer the
task of going to the market and searching for the product he wants and will
reduce about 40% of traffic crises.

2.5 Special issues: If the seller has enough knowledge to use the
application and to display his products successfully.

4
3 FEASIBILITY ANALYSIS

3.1 Technical feasibility

When it comes to software development capability, it is possible to us (the

developers of the application) to develop such a project. The server capabilities,
it needs to be dual intel Xeon processors and has 64 gigabytes of RAM and 20
Terabytes of storage. When it comes to hardware capabilities that the sponsor
has, it meets the requirements to be able to run the application.

There will be two types of payment, either by cash when the customer receives
the his/her order, or through paying online using visa card, master card.

3.2 Economic Feasibility

Costs: The project needs office equipment that costs 4200 JD, the development
team that consists of 8 developers salary is in total 4000 JD per month, 10
computers that costs 6000 JD, two servers that cost 5000 JD each, 5 printers
that cost 500 JD, internet connection subscription of type fiber optic that costs
50 JD per month, the cost of marketing this project is 1000 JD per month,
workplace rent is 300 JD per month, the cost of the website domain is 10 JD, the
cost of publishing the project as an app in app store costs 40 JD, and publishing
it on google play costs 30 JD, which makes the capital cost 26,130 JD, and the
total monthly cost would be 5350 JD. According to the customer, it’s feasible.

Benefits: there are two sources of income, one from the stores, and the other is
from the delivery men. The company takes 15 percent commission of each order
that the store gets through the app, and takes 25 percent from the money that
the delivery man gets out of each order. And the sponsor will regain the capital
cost in 4 years.

3.3 Organizational Feasibility

The application will be very user friendly which means the customers wouldn’t
find any difficulties in dealing with the application which means that customers
don’t need any training, plus whenever the application is installed or accessed
through the website by the customer, a quick guide of the app or the website
would appear for only the first time which guarantee that the customer would
face as less problems as possible when using the app or the website.

The Delivery man would use an app that has a different control panel that gives
him the needed information to get the customer’s order, such as the store
location, the order number, and the customer’s information. Delivery men don’t
need any training since the application has a quick guide that’s shows enough
on how to use it.

The store uses the same application that the customer uses, but when the store
signs up an account, the store would choose “A store” option so that the
application makes an account that suits the store needs. The store’s employee
that is responsible of administrating the account needs training on how to add,
remove, update, etc. products.

5
4 WORK PLAN and GANTT CHART

4.1 The Project Work Plan

Goal 1: Feasibility Study
Data Source
Expected and Person/Area
Key Action Steps Timeline Comments
Outcome Evaluation Responsible
Methodology
Have a
To determine the Final weekly review
economical, From:1/5/2021 feasibility for the status
organizational, and Firas Open
Till: 11/5/2021 analysis of the
technical feasibility. form. feasibility
study.
To make sure that the To get the Open, Task
stakeholders would be approval or dependent
From:12/5/2021
satisfied with the final denial of Not required Firas on the
Till: 14/5/2021
product by reviewing continuing previous
the feasibility study. the project. task
Goal 2: Requirement Elicitation
Data Source
Expected and Person/Area
Key Action Steps Timeline Comments
Outcome Evaluation Responsible
Methodology
Have a
To have
To gather information weekly report
enough
from the stakeholders from the
information
through(Questionnaire person
From:15/5/2021 of the
s and meetings)so that responsible of Firas Open
Till: 15/8/2021 wanted
the requirements of the this phase, on
functions
system can be what’s the
etc. in the
determined. status of this
final product.
task.
To summarize the Have a daily
system requirements status report
Open, Task
based on the To have the on what’s the
dependent
information gathered From:16/8/2021 requirement status of the
Firas on the
from the questionnaire Till: 15/9/2021 s of the summarizatio
previous
and meetings that were system. n of the
task
held with the system
stakeholders.. requirements.
Goal 3: Requirements Analysis
Data Source
Expected and Person/Area
Key Action Steps Timeline Comments
Outcome Evaluation Responsible
Methodology
To analyze and From:22/5/2021 The final To have a Junied Open
determine the needs or Till: 15/9/2021 requirement weekly report
conditions to meet for s of the that shows
the project, taking system. the stage of
account of the possibly studying and
conflicting determining
requirements of the the system
various stakeholders. requirements.
That includes
documenting,
validating and

6
Goal 1: Feasibility Study
managing system
requirements.
To have a
Finalizing the system A form that
daily report of Open, Task
requirements and summarizes
the dependent
making a summarized From:16/9/2021 the final
requirements Junied on the
report of the Till: 15/10/2021 requirement
that are going previous
requirements. s of the
to be written task.
system.
on the form.
Goal 4: Software Design
Data Source
Expected and Person/Area
Key Action Steps Timeline Comments
Outcome Evaluation Responsible
Methodology
Developing a design
A weekly
strategy which first
A form that status report
clarifies who is going to
contains the that contains
program the Frm:16/10/2021
System the state of Zaid Open
application, then Till: 30/11/2021
specification the system
specify how the
s specifications
program will work and
form.
look.
To have the project A response
plan, system from the
specifications, and project
feasibility analysis sponsor and Open, Task
reexamined and the approval dependent
From:1/12/2021
revised by the project committee Not required Zaid on the
Till: 16/12/2021
sponsor and approval on previous
committee which would continuing task
give a final decision of the project
continuing or or
terminating the project terminating it
Goal 5: Software Implementation
Data Source
Expected and Person/Area
Key Action Steps Timeline Comments
Outcome Evaluation Responsible
Methodology

To
A weekly
The programming team implement
status report
takes the system Frm:16/12/2021 the project
that contains Alaa+Junied Open
requirements and start Till: 1/2/2022 and turn it to
the state of
to program the system. a software
the task.
program.

Goal 6: Software V&V (Validation and Verification)

Data Source
Expected and Person/Area
Key Action Steps Timeline Comments
Outcome Evaluation Responsible
Methodology
Checking that the From:30/5/2021 To validate A monthly Alaa+Junied Open,
software system Till: 21/2/2022 and verify the report that Task
meets specifications project contains the dependent

7
 Goal 1: Feasibility Study
through out
the tasks
from the
result of
and requirements so feasibility on the
verifying and
that it fulfills its study phase previous
validating
intended purpose. till the tasks
each task.
software
implementati
on phase.
Goal 7: Software Deployment
Data Source
Expected and Person/Area
Key Action Steps Timeline Comments
Outcome Evaluation Responsible
Methodology
The final The feedback
The system is
product is out of the
deployed, and it’s From:22/2/2022
for the customers on Alaa+Junied Open
public for the people Till: 21/3/2022
customers to the
to use. use. application.
Goal 8: Documentation
Data Source
Expected and Person/Area
Key Action Steps Timeline Comments
Outcome Evaluation Responsible
Methodology
To document
To document the To have a
each goal on Open,
final document ALL people
process of each how it was Task
after each that are
phase starting from From:22/5/2021 done. dependent
phase that responsible
the requirements Till: 21/2/2022 Starting from on the
documents of the
analysis phase till the the first goal previous
the process of phases.
software v&v phase . till the sixth tasks
the goal.
goal.

4.2 The Project Gantt Chart

DURATIO
DESCRIPTION Responsibility START DATE END DATE N
14-May-
Feasibility Study Firas 1-May-21 13
21
Requirement Elicitation Firas 15-May-21 15-Sep- 120

8
 21
Requirement Analysis Junied 22-May-21 15-Oct-21 143
16-Dec-
Software Design Zaid 16-Oct-21
21
60
Software
Alaa+Junied 16-Dec-21 2-Jan-22 16
Implementation
21-Feb-
Software V&V Alaa+Junied 30-May-21
22
261
21-Mar-
Software Deployment Alaa+Junied 22-Feb-22
22
29
21-Feb-
Documentation All 22-May-21
22
269

1-May-21 20-Jun-21 9-Aug-21 28-Sep-21 17-Nov-21 6-Jan-22 25-Feb-22 16-Apr-22

Fesability Study ; 13

Requirement Elicitation ; 120

Requirement Analysis ; 143

Software Design ; 60

Software Implementation ; 16

Software V&V ; 261

Software Deployment ; 29

Documentation ; 269

START DATE DURATION Responsibility

9
5 REQUIREMENT DEFINITION

5.1 Functional Requirement

Customer requirements:
A. Enter customer first and last name.
B. Enter a residence location.
C. Enter product quantity.
D. Search for the product name.
E. View product
F. Cancel order
G. Add product to cart
H. Remove product from cart
I. Search for the store name.
J. Enter the phone number.
K. Can choose a different type of payment method in every order.
L. Make an order
Seller requirements:
A. Store location.
B. Store phone number.
C. The type of products it display.
D. The price of the product.
E. The quantity of the product that a custtomer can order.
F. A picture of the product.
G. Receive orders.
H. Send orders
Delivery man requirements:
A. Enter the vehicle number.
B. Enter a copy of the driver’s license.
C. Enter the driver’s name.
D. The ability to access the store location and the customer location.
E. Enter the phone number.
F. Delivery man residence place.

5.2 Non-Functional Requirement

1) Linking the website with the application.
2) Website and application response speed is 5 milliseconds.
3) Both the application and website are available 24/7.
4) You must sign in to your account using an email and a password to
enter the store’s page as a customer or the customer’s page as a store
owner.
5) You can choose more than one currency to pay with.
6) Both the application and the website are associated with government
agencies in order to protect users information.
Questionnaire Link:
https://docs.google.com/forms/d/1uy9CCO_Ckk5UQGFhxmavfWrl5sJ_D0hIBrsf1jBCc3I/
edit

10
6 FUNCTIONAL MODELS

Buying a product Activity Diagram

11
Product purchase Use case diagram

Seller use case diagram

12
 Search for a product Use case Description
Use case Number: UC-01
Use case Name: Search for a product
Actor(s): Customer
Maturity: High
Summary: This use case is started by the customer. It provides the capability for the actor to search for a
product.

Basic course of Events: Actor Action System Response

1. This use case is started when a 2. The system starts to search in the database
customer wants to search for a product. for products that have a similar name and or
description to what the actor typed in.
4. The Actor then looks for the exact
product that he/she wants or redo the 3. The system displays a list of products
process. names and pictures that have any similarity to
what the actor typed in the search box.
Alternate Paths: No alternate paths

Exception Paths: No exception paths

Extension Points: No extension points

Triggers: The customer would like to search for a certain product.

Assumptions: The customer is aware of the steps required to search for a product

Preconditions: The system is functioning properly.

Post Conditions: The actor decides whether the results have what he/she were looking for or not.

Reference – Business Rules: See Business Rules sections 6.8.1 and 6.3.1

Reference – Risks: See Risks List section: 2.5

Author(s): Firas Salah
Date: 01-05-21

7 STRUCTURAM MODELS
CRC Cards
Class Name: Seller ID: 2 Type: High
Description: An individual that sells a product for customers Associated Use Cases: 2

Responsibilities Collaborators

13
 Add a product

Delete a product

Edit page

Send order

Receive order

Attributes:
Name

Phone

Address

Product type

Relationships:

Generalization: person

Aggregation:

Other Associations: store, order

Class Name: Customer ID: 1 Type: High

Description: An individual that buys a product from a seller Associated Use Cases: 2

Responsibilities Collaborators

search for a product

edit profile

view product

cancel order order

14
 add to cart

remove product

choose payment method payment method

search for store name

login

Sign up

make order order

Attributes:
Name

Phone

Address

Relationships:

Generalization: person
Aggregation:
Other Associations: order, payment method

Class diagram

15
Object diagram

8 BEHAVIORAL MODELS
Sequence diagram (Buy a product)

16
17