Mobile Shop Management System Documentation
Mobile Shop Management System Documentation
Mobile Shop Management System Documentation
“MOBILE SHOPPING”
A PROJECT SUBMITTED TO
HNB GARHWAL UNIVERSITY , SRINAGAR
(UTTARAKHAND )
IN PARTIAL FULFILLMENT FOR THE AWARD OF THE
DEGREE OF
BACHELOR OF SCIENCE
IN
INFORMATION
TECHNOLOGY BATCH 2014-
17
Submitted by submitted to :
SHILKI ( 3330717) Mr. Abhijeet
Kumar WAIKHOM UMARJIT SINGH ( 3330721)
HOD (IT)
Dated:………………..
M IOK0-P
SHILKI
WAIKHOM UMARJIT SINGH
That the above statement made by the candidate are correct to
the best of my knowledge .
SHILKI
WAIKHOM UMARJIT SINGH
ACKNOWLEDGEMENT
I take this opportunity to express a deep sense of gratitude towards my project guide
Mr.Abhijeet Kumar Department of Computer Science and information technology for
providing excellent guidance, encouragement and inspiration throughout my thesis work. His
intelligible
conversations, patient listening and friendly behaviour encouraged me to work with
enthusiasm and honesty. I am really thankful to him for accepting me to work under his
guidance and including within me knowledge, values and principles that will help me to
shape up my life.
I would also like to thank all the members of Bachelor of Computer science and
Information Technology , Beehive college of Advanced Studies Dehradun, for their valuable
support, encouragement and cooperative
attitude during the thesis work.
Good ideas generate from open discussions. I have spent good times with my colleagues at
college campus discussing various issues of this work.
At this point of time it is necessary to express my limitless love and respect to my family
whose support, encouragement and motivation kept me focused towards my goal and has lead
to the completion of this work.
SHILKI
WAIKHOM UMARJIT SINGH
INDEX
Sr.No. Title
1 Preliminary Investigation
Organizational Overview
Description Of System
Limitations Of Present System
Proposed System & its Advantage
Feasibility Study
Stakeholders
Gantt Chart
2 System Analysis
Fact Findings
Event Table
Use Case Diagram
Entity Relationship Diagram
Activity Diagram
Class Diagram
Object Diagram
Sequence Diagram
Collaboration Diagram
State Diagram
3 System Design
Converting ERD to Tables
Relationship Diagram
Component Diagram
Package Diagram
Deployment Diagram
System Flow Chart
Structure Chart
4 System Coding
Menu Tree
List of Tables with Attributes & Constraints
Program Description with naming Conventions
Program Listing
Validations
Test Cases, Test Data, Test
Results Screen Layouts & Report
Layouts
5 System Implementation & Uploading
6 Future Enhancement
7 References & Bibliography
Chapter 1
Preliminary Investigation
Organizational Overview
Organizational Chart
Mobile
Store
Management
System
Employee
Supplier Customer
Description of System
files and folders. They use to keep the record of product sold, Customers,
complaints.
Preparing report is very time consuming and tedious task. For searching
task.
Limitations Of Present System
❖ Lack of security.
Proposed System
Theproposedsystem
iscomputerizedandhasbeen
developedusingadvancelanguagetherefore
itgivesmorefacilitiesthan
presentsystem.Itprovidesquickaccesstoan
ydata.Inthissystem user
havetoenterthedataonlyonceandthenitgetl
inkedwithallfiles.This
reducestheworkloadofuseranditisalsoati
mesavingprocess.
TheinformationaboutanySub
scribercanbeeasily
retrieved.Thesystem
maintainsallrecordseasy.
Advantages of Proposed System:
Input Processing
Output
Systems Life Cycle
▪ Problem Definition
▪ Systems analysis
▪ Feasibility study
▪ Systems design
▪ Updating
▪ Testing
▪ Implementation
▪ Maintenance
System Analysis
System analysis is a logical process; the objective of this phase is not actually to
solve the problem but to determine what must be done to solve the problem. The
basic objective of the analysis stage is to develop the logical model of the
system using tools such as the data flow diagram and elementary data
description of the elementary algorithm. The logical model is Subject to review
by both the management and the user who agree that the model does in fact
reflect what should be done to solve the problem.
Project Overview
Product prospective
It will be able to manage information about different tutorial in more user
friendly way. This system will manage tutorial information at various pages.
User ID and password has been given to all the field in admin accounts so
that they can enter their see by these information to login from admin and.
User Interface
▪ User will have to select the options form the given menu.
▪ Buttons will be used to insert, delete, clear and modify the data.
Processor
Memory
Hard Disk
CD-ROM
Keyboard
Monitor
Mouse
FEASIBILITYSTUDY
This phase implies on the primary job of recognizing the problem. In this stage
we define what the problem is and study the various inputs and outputs of the
system. Recognizing the demands of the system and clearly defining the system
must be the output of this phase of software development life cycle.
The output of the preliminary investigation phase is the input to this phase. This
stage aims at analytical conclusions of developer. This phase implies at
analyzing whether it is feasible on the part of programmer and for the user to
build the system. The feasibility study is done in terms of resources such as
economy, time etc. Moreover system requirements are also interpreted from the
user and deductions are made.
A feasibility study determines whether the proposed solution is feasible based
on the priorities of the requirements of the organization. A feasibility study
culminates in a feasibility report that recommends a solution. It helps you to
evaluate the cost-effectiveness of a proposed system.
The feasibility study is carried out to test if the proposed system is worth being
implemented. Given unlimited resources and infinite time, all projects are
feasible.
After performing a Preliminary Investigation, gathering and interpreting data
and details concerning the project, a Feasibility Check is done which involves a
series of steps to check the Technical, Financial and Operational feasibilities.
During this phase, various solutions to the existing problems were examined.
For each of these solutions the Cost and Benefits were the major criteria to be
examined before deciding on any of the proposed systems.
These Solutions would provide coverage of the following:
ECONOMIC FEASIBILITY:
Economic feasibility can be established by cost /benefit analysis of
the project while considering both the direct as well as the indirect
cost against the tangible benefits. In software system intangible
benefits are visible at the start & hence a system analyst must try to
convert such intangible benefits into measurable derivatives of such
benefits.
OPERATIONAL FEASIBILITY:
Operation feasibility is a measure of how people feel about the system.
Operational Feasibility criteria measure the urgency of the problem or the
acceptability of a solution. Operational Feasibility is dependent upon
determining human resources for the project. It refers to projecting whether the
system will operate and be used once it is installed.
If the ultimate users are comfortable with the present system and they see no
problem with its continuance, then resistance to its operation will be zero.
Behaviorally also the proposed system is feasible. A particular application may
be technically and but may fail to produce the forecasted benefits, because the
company is not able to get it to work. For the system, it is not necessary that the
user must be a computer expert, but any computer operator given a little bit of
knowledge and training can easily operate.
Our Project is operationally feasible since there is no need for special training of
staff member and whatever little instructing on this system is required can be
done so quite easily and quickly as it is essentially This project is being
developed keeping in mind the general people who one have very little
knowledge of computer operation, but can easily access their required
database and other related information. The redundancies can be decreased to
a large extent as the system will be fully automated.
1) TECHNICAL FEASIBILITY:
It is related to the software and equipment specified in the design for
implementing a new system. Technical feasibility is a study of function,
performance and constraints that may affect the ability to achieve an acceptable
system. During technical analysis, the analyst evaluates the technical merits of
the system, at the same time collecting additional information about
performance, reliability, maintainability and productivity. Technical feasibility
is frequently the most difficult areas to assess.
The main technical issue raised during feasibility is the existence of
necessary technology and whether the proposed equipment has the capacity to
hold required data. The technical guarantee of accuracy, reliability, ease and
data were also investigated
It involves ensuring that the system responds to user queries and is efficient,
reliable, accurate and easy to use. Since we have the excellent network setup
which is supported and excellent configuration of servers with 80 GB hard disk
and 512 MB RAM, it satisfies the performance requirement.
ECONOMIC FEASIBILITY
The cost will be in terms of utilization of resources leading to the cost to the
company. Since our cost of project is our efforts, which is obviously less than
the long-term gain for the company, the project should be made.
Internet Information Service is required for running code . Since the front end
used in this system is in HTML and in ASP.NET ,server is needed to execute
the code
TESTING
AND
IMPLEMENT
ATION
TESTING AND IMPLEMENTATION
Objectives of Testing:
This section introduces the concept of testing and how important is, for the
successful implementation of the project. Different phases of testing are
described along with the level of testing incorporated in this particular project.
Testing is vital to the success of any system. Testing is done at different stages
within the phase. System testing makes a logical assumption that if all phases of
the system are correct, the goals will be achieved successfully. Inadequate
testing at all leads to errors that may come up after a long time when correction
would be extremely difficult. Another objective of testing is its utility as a user-
oriented vehicle before implementation. The testing of the system was done on
both artificial and live data.
Typically, the project team includes a mix of testers and developers who work
closely together, with the overall QA processes being monitored by the project
managers.
Testing principles
Design Integration
Condition Testing
It is based upon the consideration that in the software code, a variable is at some
stage created, and subsequently may have its value changed or used in a
controlling expression several times before being destroyed. If only locally
declared Boolean used in control conditions are considered then an examination
of the sources code will indicate the place in the source code where the variable
is created, places where it is given a value is used as a part of a control
expression and the place where it is destroyed.
This approach to testing requires all possible feasible lifecycles of the variable
to be covered whilst the module is under test.
Unit Testing
The purpose of this phase is to test the individual units of the developing
software component. This phase is recursive and is to be repeated, as many as
there are, levels of testing. In the DGLW project, each individual form has been
tested using techniques of testing namely: Client side testing using JavaScript.
Each individual form has been validated so that user enters only valid data at
every time.
Functional Testing:
This is done for each module / sub module of the system. Functional testing
serve as a means of validating whether the functionality of the system Confers
the original user requirement i.e. does the module do what it was supposed to
do? Separate schedules were made for functional testing. It involves preparation
of the test data, writing of test cases, testing for conformance to test cases and
preparation of bugs listing for non-conformities.
System Testing:
System testing is done when the entire system has been fully integrated.
The purpose of the system testing is to test how the different modules
interact with each other and whether the entire system provides the
functionality that was expected.
a) Program Testing
b) String Testing
c) System Testing
d) System Documentation
Level 1
Level 2
Level 1 Testing (Alpha Testing)
At this level a test data is prepared for testing. Project leaders test the system on
this test data keeping the following points into consideration:
● Exception handling
Here the testing is done on the live database. If errors are detected then it is sent
back to LEVEL 1 for modification otherwise it is passed on to LEVEL 3.
This is the level at which the system actually becomes live and implemented for
the use of END USERS.
A forced system failure is induced to test a backup recovery procedure for file
integrity. Inaccurate data are entered to see how the system responds in terms of
error detection and protection. Related to file integrity is a test to demonstrate
that data and programs are secure from unauthorized access.
The usability test verifies the user-friendly nature of the system. This relates to
normal operating and error-handling procedures.
Quality Assurance
Proper documentation is must for mainframe of any software. Apart from In-
line documentation while coding. Help coding, help files corresponding to each
program were prepared so as to tackle the person-dependency of the existing
system.
Feasibility Of Study
1. Software Specification:-
Software requirements for this system are as listed follows:
❖ FRONTEND : PHP
❖ BACKEND : MY SQL
❖ Processor : i3
❖ RAM : 2 GB RAM .
HTML
CSS
JavaScript
php
PHP is an acronym for "PHP: Hypertext Preprocessor"
PHP is a widely-used, open source scripting language
PHP scripts are executed on the server
PHP is free to download and use
With PHP you are not limited to output HTML. You can output images, PDF files,
and even Flash movies. You can also output any text, such as XHTML and XML.
Why PHP?
PHP runs on various platforms (Windows, Linux, Unix, Mac OS X, etc.)
PHP is compatible with almost all servers used today (Apache, IIS, etc.)
PHP supports a wide range of databases
PHP is free. Download it from the official PHP resource: www.php.net
PHP is easy to learn and runs efficiently on the server side
What Do I Need?
To start using PHP, you can:
Just create some .php files, place them in your web directory, and the server will
automatically parse them for you.
You do not need to compile anything or install any extra tools.
Comments in PHP
A comment in PHP code is a line that is not read/executed as part of the program.
Its only purpose is to be read by someone who is looking at the code.
The best things in using PHP are that it is extremely simple for a
newcomer, but offers many advanced features for a professional
programmer. Don't be afraid reading the long list of PHP's features. You
can jump in, in a short time, and start writing simple scripts in a few
hours.
PHP has received criticism due to lacking native Unicode support at the core
language level, instead only supporting byte strings. In 2005, a project headed by
Andrei Zmievski was initiated to bring native Unicode support throughout PHP,
by embedding the International Components for Unicode (ICU) library,
and
representing text strings as UTF-16 internally.Since this would cause major
changes both to the internals of the language and to user code, it was planned to
release this as version 6.0 of the language, along with other major features then in
development.
Stakeholders
1. Project Developers :-
Project Developers is one who develops software for customer. In
my project I am the first stakeholder i.e. Project Developer.
2. Project customer :-
Project Customer is one who pays for the developed software.
4. Project Testers
Project Testers are those who test the software.
Gantt Chart
Project Finalizati on
10/06/2 17/06/20
011 11
Investiga tion of system requirem ent
18/06/2 25/06/20
011 11
System Analysis
27/06/2 14/8/201
011 1
System Design
15/8/20 28/9/201
11 1
Coding
Interface Coding
29/09/2 15/10/20
011 11
Database Connecti vity
16/10/2 30/10/20
011 11
Validatio n Coding
31/10/2 15/11/20
011 11
Report Coding
17/11/2 31/12/20
011 11
Impleme ntation
Develope r Testing
5/12/20 12/12/20
11 11
Client Testing
13/12/2 22/12/20
011 11
User Testing
25/12/2 29/12/20
011 11
Project Delivery
30/12/2 05/1/201
011 2
Project Report Submissi on
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
Project Report Hard Copy Checking
12/1/201 WEEK
8/1/201
2 2
Project Submissi on
13/1/20 18/1/201
12 2
Chapter 2
System Analysis
Fact Findings
Introduction
The Current System is the manual one, hence is not speedy, accurate,
efficient as well as time consuming. An essential part of the system analysis,
which enables the developer to understand & the system correctly. It is
undertaken to obtain details of the system. To understand the physical flow of
the information through the current system. Collect various information through
various fact finding techniques. Identify the procedural difficulties experienced
by the user. Study the bottlenecks find out the redundant work being performed
in the system.
1. Interviews
Information was obtained from the employees at the organization by
interviewing them at the location and time convention both.
2. Document Searching
An extensive study of existing document an official correspondence
was done to understand the present working status of organization.
SR
NO EVENT TRIGGER SOURCE ACTIVITY RESPONSE DESTINATION
Supplier:-
Supplier Admin
Search supplier
Product:-
Admin
Display product details
Stock:-
Customer:-
Customer Admin
Search customer
Order:-
Places an
Order
Create a new
order
Lookup for
order details
Update order
record
Customer Admin
Delete order
record
Bill:-
Places new
Bill
Create a new
Bill
Display Bill
Bill
Mobile Shop
System
Bill
Employee
Product Supplier
Salary
Activity Diagram
Customer
Check availability
No
Yes Supplier
Enter product information
Product
Add product
Enter order
Give payment
Calculate total
Generate Bill
Class Diagram
Customer Supplier
+Cust_id:Number +Supp_no:Number
+Cust_name:Text +Supp_name:Text
+Cust_add:Text +Supp_add:Text
+Cust_ph:Number +Suppt_ph:Number
+Cust_email:Text
+Insert () +Insert ()
+Update () +Update ()
+Delete () +Delete ()
+New () +New ()
1..* 1..*
1..* 1..*
Employee Bill
+Bill_no:Number
+Emp_id:Number +Order_no:Number
+Emp_name:Text +Cust_no:Number
+Emp_add:Text +Prod_name:Text
+Emp_ph:Number +Total:Number
+Insert () Stock
+Insert ()
+Update ()
+Update ()
+Delete ()
+Delete () +Prod_id:Number
+New ()
+New () +Prod_name:Text
+Prod_qty:Number
1 1..*
1
1..* 1..* +Insert()
Order Product +Update()
+Delete()
+Order_no:Number +Prod_no:Number
+Date:Date/Time +Prod_name:Text +New()
+Cust_name:Text +Prod_info:Text
+Prod_name:Text 1 1..* +MRP:Number
+Total:Number 1..*
+Insert () +Insert ()
+Update () +Update ()
+Delete () +Delete ()
+New () +New ()
Object Diagram
: Customer : Supplier
+Cust_id:Number +Supp_no:Number
+Cust_name:Text +Supp_name:Text
+Cust_add:Text +Supp_add:Text
+Cust_ph:Number +Suppt_ph:Number
+Cust_email:Text
+Insert () +Insert ()
+Update () +Update ()
+Delete () +Delete ()
+New () +New ()
1..* 1..*
1..* 1..*
: Employee : Bill
+Bill_no:Number
+Emp_id:Number +Order_no:Number
+Emp_name:Text +Cust_no:Number
+Emp_add:Text +Prod_name:Text
+Emp_ph:Number +Total:Number
+Insert () : Stock
+Insert ()
+Update ()
+Update ()
+Delete ()
+Delete () +Prod_id:Number
+New ()
+New () +Prod_name:Text
+Prod_qty:Number
1 1..*
1
1..* 1..* +Insert()
: Order : Product +Update()
+Delete()
+Order_no:Number +Prod_no:Number
+New()
+Date:Date/Time +Prod_name:Text
+Cust_name:Text +Prod_info:Text :Stock
::OEmrderplo
+Prod_name:Text
1 1..* ::PBrilolduct
+MRP:Number
yee +Bill_no:Number 1..*
+Total:Number
+Order_no:Number +P+Orrod_no:der_no:N +Prod_id:Number
+E+Dmatp_ie:Dd:at Numumbeber r +Prod_name:Text
+Insert () +Insert ()
Ne/uTmimbeer +P+Crusod_nat_nom:Ne +Prod_qty:Number
+Update () +Update
+E+Cmusp_nat_namm u:Tmebextr()
+Delete () +Delete ()
ee::TTeextxt +P+Prrod_iod_nnafmo
+New () +New ()
:eT:eTxtext
+E+Prmod_np_add:ame +Insert()
T:eTxtext +M+ToRtaPl::NNu +Update()
+Update () +Update ()
+Delete () +Delete () +Delete()
+New () +New () +New()
Sequence Diagram
Supplier:-
Create Supplier:
Admin
Update Supplier:
System
Supplier Admin
Delete Supplier:
System
Admin
Product:-
Create Product:
Admin
Update Product:
System
Admin
Delete Product:
System
Admin
Stock:-
Create Stock:
Admin
Update Stock:
Admin
Delete Stock:
System
Admin
Customer:-
Create Customer:
System
New Customer created
Customer Admin
Update Customer:
System
Customer Admin
Delete Customer:
System
Admin
Order:-
Create Order:
System
New Order created
Customer Admin
Update Order:
Customer Admin
Delete Order:
System
Admin
Bill:-
Create Bill:
Admin
Delete Delete:
System
Admin
Employee:-
Create Employee:
Admin
Update Employee:
System
Employee Admin
Delete Employee:
System
Admin
Collaboration Diagram
Customer
1. Customer enquiry
6. Get order
9. Generate receipt
11. Order
Supplier
State Diagram
Login
Idle
Customer enter
Customer enquiry
Mobile available
End
Check details
Pay bill
Paying bill
Generate receipt
Generating receipt
Chapter 3
System Design
Converting ERD to Tables
5 Salary This table is use store ,retrieve and information about the
employee salary.
The field are e_id, e_fname,e_mname,e_lname, e_add,
e_contact, msalary, advance.
Supplier.vb
Stock.vb
Order.vb
Nokia Mobile
Bill.vb
Shop System
Customer.vb Emp.vb
Salary.vb
Order.vb
Component Diagram
Package Diagram
Connection Admin
Form Availability
PC <<device>>
XP
Cust.vb Mobdetails.vb
Database
Transaction.vb
Server Order.vb
<<device>>
Emp.vb Bill.vb
Emp.vb
Printer
System flow
Mobile details
Price Mobile
Paid details
Paid
System Coding
Menu Tree
Customer information
Main
Mobile Details
Customer information
MDI Form
Employee
Mobile Details
Transaction Transaction
Mobile Bill
Reports
Supplier Report
Utility Calculator
About Us Help
Exit
Table List
1. Table name:-Cust_info
Sr.N Field Name Datatype Constraints Size Description
1 c_no Integer Primary key Stores the customer code
2 cname Varchar 10 Stores the customer name
3 cadd Varchar 10 Stores the customer address
2. Table name:-Employee
Sr. Field Name Datatype Constraints Size Description
No.
1 E_id Integer Primary key Stores the employee code
2 E_fname Varchar 15 Stores the employee name
4. Table name:-Order
Sr. Field Name Datatype Constraints Size Description
1 c_no Integer Foreign key Stores the customer code
2 c_name Varchar 15 Stores the customer name
3 c_add Varchar 15 Stores the customer address
4 contactno Bigint Stores the customer contact
no
5 email varchar 20 Stores the customer email
6 o_no Integer Stores the order no
7 p_no integer Stores the product no
8 P_name Varchar 15 Stores the product name
9 P_q ty Integer Stores the product quantity
10 P_mrp integer Stores the product prize
NO FORM PURPOSE
NAME
1 Loding.frm This form display the title of system name
of organization & copyright of the system
To display crystal
CryRpt CrystalReport report.
1. Access control:-
System gives access by valid password.
2. Input control:-
System validates every textbox. It allows textual values for fields like customer name.
It also validates some numeric data only for fields like phone no.
4. Range control:-
In Order Transaction the system checks whether quantity given by the user is not
more than the available product.
Chapter 6
Future Enhancement
Future Enhancement
Conclusion
System helps to store all the data about the customer order in computer
and there is no need to do paper work.
Publication : Murach
Book name : Mastering php 2016