Order Management System

Master of Computer Application

Object Oriented Programming Using C++
Submitted to
LOVELY PROFESSIONAL
UNIVERSITY PHAGWARA, PUNJAB

From 01/11/2022 to 08/12/2022

SUBMITTED BY:

Name- Rohit Kumar ((12219614)

Name- Vaibhav Sikka ((12205374) Submitted to:
Name- Md Aquib (12215525
12215525) Prince Arora

Section – DOC 12 Designation

Roll No – 54
Roll No –55
Roll No – 56
 TO WHOM SO EVERY MAY CONCERN

I, Rohit kumar, Vaibhav Sikka, Md Aquib, 12219614,

12205374, 12215525, of the student, hereby declare
that the work done by me on “Order management
system” from 01/11/2022 to 08/12/2022, Lovely
professional University, Phagwara, Punjab, is a record
of original work for the partial fulfillment of the
requirements for the award of the degree, Master of
Computer Application.

Name of the Student (Registration Number)

Rohit Kumar
Vaibhav Sikka
Md Aquib
(12219614, 12205374, 12215525)
Dated: - 08/11/2022
Page 2
Table of conTenTs

Sr.No. Title PageNo.

01. Acknowledgement by student

02. Profile of the Problem
03. Existing System (If any)

04. Introduction to existing system

05. Scope of existing system
06. DFD for present system
07. Future scope of the existing system
08. Problem analysis
09. Product definition of new system
10. Feasibility study for new system
11. Project planning for new system
12. Software Requirement Analysis
13. Introduction
14. General Description
15. Specific Requirements
16. Design (of new system)
17. System Design for new system
18. Design Notations for new system
19. Detailed Design of new system
20. Flow Charts for new system
21. DFD for new system
22. ER Diagram of new system (Database)
23. User Interfaces used in system (GUI)
24. Bibliography/References

Page 3
 Acknowledgement

Deepest thanks to our mentor Mr. Prince Arora Sir for guiding
and correcting various documents of mine with attention and
care. He has taken pain to go through the paper and make
necessary corrections as and when needed. We would also thank
our Institution and our faculty members without whom this
project would have been a distant reality. We also extend our
heartfelt thanks to our family and well-wishers.

[Rohit Kumar, Vaibhav Sikka, Md Aquib]

[12219614, 12205374, 12215525]
[Date of Submission: - 08/12/2022]

Page 4
TITle of THe PRoJecT
Order Management system

Page 5
 Profile of the problem
There are some problems in order management
software:
1) Missing Integration: The real power comes in
integration of across of all channels.
2) Lost two-way sync: When any lost jibe, user never
pass the data in inventory, all prices, and photos from
singular systems.
3) Slow Agree: The order management software at less
rate is riddle with some error which render to mistake
shipping listing facts.
4) Weak Documentations: They expect the users to
find out the solutions the system’s of problem with
own.
5) Un-responsive Customer Service: As a customer
you want your issues address the possible.
6) On-boarding Process: Better order management
system has forthright reverse action.
7) Insufficient Features: While a meet your need miss
an essential feature you may experience to different
system in future.

Page 6
 Introduction to existing system

1. They can be described as process for the group,

action and fulfillment of sequence that happens
in the running of a business.
2. In the past order management relied on time-
consume process like manually update static
spreadsheets.
3. Order management software is put in place to
enable operators to manage and track orders
that come from various fulfillment points and
arrive through distribution channels.
4. The aim of OMS is to deliver outcome to
consumer as soon as possible.

Page 7
Scope of existing system

This project will

ill consist of creating the tool for
automate order purchase, sale, pay payment and
an
receipt. This project wwilll fulfill the requirement of
inventory and lededger system.
ystem. It will generate the
Page 8
reports about inventory and ledger to control
inventory flow and party ledger.

The main goal of OMS is to ensure consistent

availability of supplies for consumers. Thus, OMS is
direct toward owner of small to large stores and
stock managers who are responsible of maintaining
sufficient goods on hand in a retail or
manufacturing business.

Page 9
DFD for present system
Zero Level DFD:

Page 10
We have to elaborate the high level process of
OMS. It’s a basic overview of the whole OMS and
process being analyze model. It should be easily
understood by a wide audience, including
purchasing, company and confirmation order in
zero level DFD of OMS.
Process flow of OMS:-
1)Manage the order
2)Manage the product
3)Manage the company
4)Manage the invoice
5)Manage the payment

Page 11
First Level DFD:

The system is divided into 2 processes each of the

deals with one or more of the data the flow from
external agents which together provide all of the
functionality of OMS as a whole.

Page 12
Main entities:-
1)Process order record and generate all order.
2)Process product record and generate all products.
3)Process company record and generate all
company.
4)Process customer record and generate all
customers.
5)Process confirm order record and generate all
confirm order.
6)Process invoice record and generate all invoice.

7)Process payment record and generate all

payment.

Page 13
Second Level DFD:
DFD:-

It may require more functionality of OMS to reach

the necessary level of detail about the OMS
functionality.
Functionality:-
1)Admin login system all functionality.
2)Admin can view the all records.
3)Admin can manage all the details.
4)Admin can also generate all report
report.

Page 14
 Problem analysis

There are some problems with OMS are as

follows:-
1. Incomplete Integrations:-
The true OMS come from integration of info
across a multimedia of channel.
2. Missing Bi-directional:-
When OMS missed and cannot use by pass
certain the data such as money & photos
from particular system.
3. Slow Sync:-
Some OMS at a slow rate riddled with some
technical error to translate to shipping or the
inventory data.
4. Weak Documentation:-
It does expect that all users should find out
solution to most system on their own.
5. Unresponsive Customer Services:-
As a customer what they want exact issue
address the soonest possible.

Page 15
 6. Complicate Process:-
While this process may have many step
should be clear out that expect are clear.
7. Insufficient Features:-
If a tool an OMS has so many feature then it
can be somewhat frustrated to use.
8. New Feature:-
If you use to provide who’s OMS roll out new
feature slow feature slow or not at all it is a
strong indicate the system.
9. No support for barcode scan:-
These translate to another system and
another place where things went wrong.
10. No action on request feature:-
Even if the feature would twice or thrice your
business it may not important to provide the
users.
11. Zero Support for Multi Package Order:-
In some instance the system might detect them as
order which slow down the process the order.

Page 16
 Software Requirement Analysis

 Integration
 Inventory
 Customers
 Products
 Order
 Payment

Page 17
 Specific Requirements

1. Multiple Customers:-
 The fore most requirements are the need to
locate more than the customers.
 This information about different customers
impact the whole business process the require
order and pricing management & the forecasts
that demand analysis.

Page 18
 This is actually kind of important and unique to
the organization that we are working with or at
least vendor that sell through distributors or
through extended value chains.
2. Complex ship terms:-
 In the technology industry it is normal to
use the ship accounts of your customers
and the customer shipping terms instead
of your own.
 Ship term and condition may include
specific customer requirements
depending on the ship from or ship to
locations shipment weight and the need
for re shippers.
 Therefore, the challenge part is how to
collect and capture the ship term for
these complex extended value chains.
3. Flexible Price Model:-
 This pushes a requires for different price
model and term for the same ship-to
customer for the same product based on
who the end buyer is.
Page 19
4. Booking Matrices:-
 It means that production is often outside
of the direct control of the internal
operations team.
 Therefore, they need to finalize
commitment dates and meet is based on
their plan.
5. After sale Tracks:-
 The need to track inventory after the sale is
the 5th significant requirement.
 For example, the stock may go to a hub, a
VMI storage facility or a distribution
channel.
 However, you still need to integrate point
of sale data to show the inventory status or
record the pulls from inventory when there
is a system consumes the stock.

Page 20
 Flowcharts’ for New System

There are mainly 5 types creating a flow chart

are as followss:-
1. Choose an intuitive software
2. Be Consistent
3. Space out elements
Page 21
 4. Use decision symbols
5. Use trigger words

Reference

 Wikipedia
 https://projectworlds.in/free-projects/php-
projects/food-ordering-system-project-in-
php/
 https://www.javatpoint.com
 https://www.python.org/
 https://www.tutorialspoint/

 REFERENCE BOOKS

Page 22
Page 23