3
The Great Mind Challenge - Project Scenario Template Note: Already filled information should not be changed 1. Name of the Project Order Management System (OMS) 2. Objective/ Vision Objective of this project is to manage/process through web, the orders already placed by a customer either through company website or over phone. Order goes through various phases till it finally reaches the customer. At any point of time customer himself can check the status of the order online or over phone with the reference number he got while placing the order. Note1 : This is a complete back office management for the order 'status' only. Shoping cart (Estore) and money transaction can be part-2 Note2 : Order status cycle should be : New → Ordered → Picked → Packed → Out for Shipment → Shipped → Accepted/Returned → Closed/Reordered/Refunded 3. Users of the System A. Administrator B. Customer C. Operator/System User D. Stores operator / Picker E. Packer F. Shipper 4. Functional Requirements (Atleast Eight) i. Administrator should be able to add/edit users give roles and permissions. ii. Operator/System user should be able to update all orders based on authorization key iii. Stores operator/Picker should be able to see all the stores order records but should be able to modify only status of items to be picked iv. Packer should be able to see all the picked order records but should be able to modify only status of items assigned to be packed by him. v. Shipper should be able to see all the packed order records but should be able to modify only status of items assigned to be Shipped by him vi. Customer should be able to login to estore and check the status of exactly where is his order. vii. Customer should be able to return the order if its damaged viii. Normal order status cycle should be : New → Ordered → Picked → Packed → Out for Shipment → Shipped → Accepted/Returned → Closed/Reordered/Refunded ix. Estore and Order tracking for customer is on Internet and all other operations are on itranet x. Shipper will call operator and update about shipped status or he comes back to store and updates it online.

OMS Order Management System

Embed Size (px)

Citation preview

Page 1: OMS Order Management System

The Great Mind Challenge - Project Scenario Template

Note: Already filled information should not be changed

1.Name of the Project

Order Management System (OMS)

2. Objective/ Vision

Objective of this project is to manage/process through web, the orders already placed by a customer either through company website or over phone. Order goes through various phases till it finally reaches the customer. At any point of time customer himself can check the status of the order online or over phone with the reference number he got while placing the order.

Note1 : This is a complete back office management for the order 'status' only. Shoping cart (Estore) and money transaction can be part-2

Note2 : Order status cycle should be : New → Ordered → Picked → Packed → Out for Shipment → Shipped → Accepted/Returned → Closed/Reordered/Re-funded

3.Users of the Sys-tem

A. AdministratorB. CustomerC. Operator/System UserD. Stores operator / PickerE. PackerF. Shipper

4.Functional Re-quirements(Atleast Eight)

i. Administrator should be able to add/edit users give roles and permissions. ii. Operator/System user should be able to update all orders based on authoriza-tion keyiii. Stores operator/Picker should be able to see all the stores order records but should be able to modify only status of items to be picked iv. Packer should be able to see all the picked order records but should be able to modify only status of items assigned to be packed by him.v. Shipper should be able to see all the packed order records but should be able to modify only status of items assigned to be Shipped by himvi. Customer should be able to login to estore and check the status of exactly where is his order. vii. Customer should be able to return the order if its damagedviii. Normal order status cycle should be : New → Ordered → Picked → Packed → Out for Shipment → Shipped → Accepted/Returned → Closed/Reordered/Re-fundedix. Estore and Order tracking for customer is on Internet and all other operations are on itranetx. Shipper will call operator and update about shipped status or he comes back to store and updates it online.

5.Non-functional re-quirements (Atleast Four)

i. Secure access of confidential data (user’s details). SSL can be used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak time

iv. Flexible service based architecture will be highly desirable for future ex-tension

6. Optional features None

7. User interface pri-orities

A. Professional look and feel

B. Use of AJAX atleast with all registration forms

C. Browser testing and support for IE, and Firefox.

D. Use of Graphical tool like JASPER to show strategic data to admin

Page 2: OMS Order Management System

E. Reports exportable in .XLS, .PDF or any other desirable format

8. Reports Admin should be able to get reports on daily, weekly, monthly, quarterly etc for different status, price or any other criteria

9.Other important is-sues

None

10. Team Size 2 – 4

11.Technologies to be used

UML, JSP, J2EE, XML X-Forms, AJAX, Web-services, SOA

12. Tools to be Used Lotus Form Designer/Eclipse/RAD

WebSphere Portal/ WAS, Webservices/SOA

DB2 Express C

13.Final Deliverable must include

A. Online or offline help to above said users, Application deployment execu-tive and developer

B. Application archive ( .war/.ear ) with source code

C. Database backup and DDL Script

D. Complete Source code

14.Advantages of using pureXML?

15. Pictorial Representa-tion