Again Updated Proposal, AwaisBitf18m053, Abdur Rehman, Bitf18m011, Muhammad Faizan Bitf18m031, Ehtisham Ul HaqBitf18m038
Again Updated Proposal, AwaisBitf18m053, Abdur Rehman, Bitf18m011, Muhammad Faizan Bitf18m031, Ehtisham Ul HaqBitf18m038
Freelance Marketplace
Project Overview:
Project Title: Freelance Marketplace
Project Goal: Provides an online platform for sellers to offer services to buyers
worldwide.
Objectives:
Sr.# Objectives
1 Facilitate buyers to find freelancers and see their details for their work
2 Facilitate sellers to earn money through their passionate skills at home
3 Secured communication panel will be provided for discussion among buyers
and sellers
4 Keep track of orders and deadlines and its status
5 Provide a secure pricing system
6 Enable admin to handle all things at platform
Project Success criteria:
1) System has no flaws in it
2) Communication panel working
3) Buyer interface
4) Seller interface
5) Admin interface
Assumptions, Risks and Obstacles: We assume that customers are already familiar with
this kind of system before.
Objectives:
Enable sellers to earn money by selling their skills at home
Enable buyers to hire sellers for their work
Keep track of orders and deadlines
Provide secure communication panel
Handle pricing procedure securely
Enable admin to handle all things at platform
Problem Statement:
Following is the order management problem statement of Greed Wood Company for the
management of the customer’s order at a global level.
Supplier Department Requirements
Order Management
Only registered customer could place order for goods. So a customer must be able to register
himself to the system by requesting for registration. There should have to be two types of
registration process, normal and privileged. Customer should provide his personal,
organizational, authorizer and payment details in the registration request process. All the
requests are to be viewed by the customer account administrator (CA). CA could accept,
reject and temporarily waive the requests on the basis of credentials provided. If admin
accept the registration request, a login information (Password, Id & role) should be assigned
and mailed to the corresponding customer. Similarly customer could also request for the
updating of his record. He could request for different types of updating e.g. updating of his
personal/shipping details, or upgrading of his status from registered to privileged customer, or
updating of his payment methodology. Customer could also view his details for verification
purposes and similarly CA could search any customer detail and could also view the whole
list of currently registered customers.
Both registered and privileged customers could order for goods. Customer places an order by
providing his ID and other order related details A complete order must contain personal
details of the customer, shipping information, product list along with product quantity and
payment details. Customer could make payment either through cash or through a credit card.
Accordingly invoice should be generated, and user should be given the option to finally place
the order and in the end confirmation receipt must be given to the customer. Invoice contains
the list of complete product along with their pricing details. It also contains discounts, sales
tax and total pricing details. User could also view the status of their orders by providing the
Order Number. Privileged customers could also place the request for the updating of their
orders if the orders are not shipped. They could place request for the updating of shipping
address and product quantity only. Similarly the privileged customer could also place the
request for the cancellation of the order. But all these updating and cancellation requests are
to be viewed by the Order Administrator in order to accept, reject, or waive them.
Action List mechanism should be adopted for better notification/messaging services,
business interaction and control. An action event should be generated for a corresponding
administrator when a request is placed for updating of orders or customer details etc. These
actions could be generated by the Order Operator or through the updating process. Similarly
on the other hand corresponding administrator could view his Action List containing different
actions, and correspondingly process these pending actions. Similarly when the action
processing is completed or if the action is just a notification message then administrator could
delete these actions from the action list. Actions List configuration should be done by System
Admin, who could add new action events and delete any current event from the system.
Shipping Department ships the corresponding orders.
Exclusions:
Graphical user interface is available only in English language.
Without login system no one can sell or buy services.
Limited to HTTPS/HTTP.
No withdraw money system
Application Architecture:
Buyers
Backend
(MySQL,
Frontend
Admin (Html, CSS,
JavaScript)
Sellers
Gantt chart: