MOBILE SHOP

MANAGEMENT SYSTEM
Group 4

GROUP MEMBERS:
(LEADER) ABDULRAHMAN MOHAMMED MOSAIBAH-20192231
AHMED EBRAHIM AHMED-20197531
ALHASSAN AHMED SHARIF-20192869
HASAN EBRAHIM HASAN-20197562
 Index

Index………….…………………………………………….1

Problem Definition……...………………………………….2

System Description……………………..………..…………3-7

Software Process Model and

Description of Software Process Model……………………8

Functional Requirements…………………………………...9,10

Non-Functional Requirements……………………………...11,12

1|Page
 Problem Definition

We choose a Mobile Shop Management System to provide a system to

manage the mobile shop and make it easier and faster for the staff and
the manager, that have 5 main components which help the system to
be more maintainable and it will be more manageable to contain the
system.

2|Page
 System Description

The objective is to define a small mobile shop's system for Sales and
purchase of mobiles, where the detail of purchasing of mobiles of
different models at which price is stored and in which price the mobiles
are sold to the customers, both details are stored for the query for any
mobile handsets.
In start we introduce a form to request for the menu which holds
several options for available sales and offers. This is the start for all
other forms which are connected to it by a simple connection.
During purchase, We request for the model-id or name of the product.
This form accepts Mobile mode-id or name to either store or use this
form to help you find that same model-id. If it exists then you can
modify or complaint about it if not you can add it.
After adding the Mobile model-id, you have to add the all features that
are available in that Mobile. This form helps to add features of Mobile
through the available list of features. This form also helps to change or
remove the features of the Mobile.
If there is a time were it is needed to store and retrieve the information
about the supplier, we created a solution that helps you to store
supplier id and its basic information.
When purchasing the Mobile handsets, customer information is
required and we will save it to customer detail form. This information
will be later used in statistic research.

3|Page
Access levels:
Not anyone can access the add mobile form or the manager supplier
information. There are certain levels on the system, these levels decide
what information or features you can access in the system. There are 3
levels in our system and will be displayed in a chevron list.

Can access all features

Manager Able to manage the whole system

Can access almost all features

Employee Able to add/delete some information

Has access on some features(Customer features)

Customer Can only manage his info and cart.

4|Page
 Mobile Shop Management System

Help Transactions Reports Details Exit

About Employee Customer

Details Details

Customer Employee Product Purchase Dealer

Report Report Report Report Report

Purchase Attendance Bill Salary

Details Details Details Details

5|Page
  Details:
1) Customer & Employee(Staff) Details:
 Personal information about both customer and employees will be
saved here, Like:
 Full Name
 Age
 Gender
 Address
 ……………Etc.

6|Page
  Reports:
1) Customer & Employee(Staff) Reports(feedback):
 Any thing that a customer or an employee want to talk about with
the Manager(Owner) of the shop, Like:
 Positive or negative feedback about products
 Any complains
 Ideas to improve the shops workspace
 ……………Etc.

2) Product Report(Info.):
 All available products that are ready to be sold with additional
information, Like:
 Product name
 Brand name
 Available quantity
 Device specs like: Ram, Size , Display resolution,…..
 ……………Etc.

3) Purchased Report:
 Every time a product is bought its name and price will be saved in a
table with the total items sold and price ready to be displayed when
needed

4) Dealer Report:
 All products bought from the dealer will be saved in a report with
there prices and will be sent to the “Product Report” section to be
displayed with a change of prices for profit.

7|Page
  Transactions:
1) Purchase Details(Cart):
 Any items that a costumer tries to buy will go directly to his cart were
he can complete his purchase and manage his cart with features like:
 Being able to add or delete products
 Can use discount codes If available
 Can choose to either get the product from the store or get it
delivered
 ……………Etc.

2) Attendance Details:
 This is the attendance information for employees where they will
prove that they came to work :
 The employee will be marked as on-time ,late or absent and his
salary will be affected differently by each
 The employee will be marked as on-time if he had a sick-leave
 If the employee worked over time he will be payed for it
 ……………Etc.

3) Bill Details:
 All the store bills(fees) will be saved here and removed if payed, bills
like:
 Electricity bills
 Water bills
 Store rent
 ……………Etc.

4) Salary Details:
 All Staff(Employees) members salaries will be here with changes if
occurred with reason :
 Every staff member can only view his salary
 Will get a bonus if the employee was the employee of the week
 ……………Etc.

8|Page
 Software Process Model

The Concurrent Development Model is called as Concurrent Model.

We have chosen this model because it contains some features that
make it distinct from other models:
 This model is applicable to all types of software development
processes.
 It gives immediate feedback from testing.
 It is easy for understanding and use.
 It provides an accurate picture of the current state of a project.

Description of Software Process Model

A large portion of the fruitful programming out there includes a

progression of periods of improvement, for example, necessities
gathering and prototyping, that are assembled to build up the product.
These stages are discrete and regularly performed simultaneously.
Frequently there is an entwining between the stages, which makes it
unavoidable to re-visitation of the prior stages to roll out certain
improvements as indicated by the outcomes got in the later stages. This
sort of a model, wherein various stages are performed simultaneously,
can be instituted as a simultaneous model.

9|Page
 Functional Requirements

 Login
o Simple two step login system
 Admin Login
 Sales person Login
 Administrator Dashboard
o Admin can control whole system easily
o Admin can add/delete sales person, Edit, update, delete,
generate barcode etc.
o Admin show payment option.

 Sales person Role

o Sell Products
o Stock Products
o Delivery Receipt
o Payment Process
o Accept Refunds Products

 Payment process
o Only Cash Payments
o Paid Vat

10 | P a g e
 o Get Discounts

 Barcode
o Generate Barcode
o Print Barcode Level
o Barcode Scanner

 Refunds Process
o Accept Refund Products
o Cash back

 Reports Module
o View Sales Reports
o View Transaction Reports
o View Refunds Reports
o Daily/Weekly/Monthly/Yearly Reports

 Database

11 | P a g e
 Non-Functional Requirements

Reliability
 The following requirements describe the expected reliability of
the Operational Interface
o The Operational Interface shall have a Mean Time Between
Failures of no less than 17 days
Availability
 The following requirements indicate the expected availability of
the Operational Interface.
o The system shall be available 99.5% of the time
Security
 All users of the system shall login using some form of unique
identification (e.g., username and password)
 All login attempts shall be done so in a secure manner (e.g.,
encrypted passwords)
 Each user shall either be trusted or not trusted.
Maintainability
 The following requirements increase the maintainability of the
Operational Interface software.

12 | P a g e
 o All source code and development related documents shall
be controlled under a version control system
o All source code shall adhere to an agreed upon and well-
defined set of coding standards for each development
language used.
o A standard naming convention for classes, variables and
packages shall be agreed upon and adhered to.
Portability
 Hardware
 Operating Systems
 Since the software must run on several popular hardware
platforms and the goal is to achieve a Reasonable level of
platform independence.
 The system shall be compatible with the Microsoft Windows
Operating System (Vista, Windows 7/8/10, XP or greater).
Usability
 The system’s user interface intuitive, easy to use and provide an
overall positive user experience.

13 | P a g e