Order Management System

Gregory BarrettKen Browning

Hiroshige Matsuno

Team3: Order Management System Sponsor:Aviation Learning, Inc. Goal:Create an n-tier, client-server

system that will track the product and order information necessary for product support and to be able to enter this information in a manner that follows the processes used to fulfill a product order.

Glossary of Terms Order: Record of purchase of one or more base products or

companion kits at a single time. Contains customer information, invoice number, and one or more order details. Also contains shipment information once an order has been shipped.

Order Detail: Line item contained in an order. Minimally contains product ID and version information. Also stores registration information for registered products.

Base Product: Instructional materials pertaining to airplane maintenance. A base product may be ordered independently of any other product or service.

Glossary of Terms cont. Companion Kit: Package of supplemental materials, pertaining

to a base product. Companion kit purchase are usually linked to the purchase of a base product. One base product may have zero or more companion kits associated with it.

Voucher: Unique identifier assigned to an order detail at time of order, for appropriate products. Upon successful completion of a course of study proscribed by a given product, the customer can request a certificate using this number.

  Certificate: Certificate of completion. Acknowledges that an

individual has successfully completed a course of study proscribed by a product.

Data Base Description The purpose of the database is to track the

necessary product information and to be able to enter this information in a manner that follows the processes used to fulfill a product order.

Microsoft Access 2000 database using specified

fields, tables and relationships

Data Base Relationship

Order tableField Names Constraint Data Type Description

OrderID Primary Key AutoNumber Database generated unique identifierInvoiceNumber Char(50) In-house generated unique identifierCustomerID Char(50) Unique identifier of the customer making the purchaseOrderDate Required Date/Time Date the order was placedPONumber Char(50) Customer generated unique identifierNotes Memo User-specified notes about the orderShipDate Date/Time Date the order was shipped. NULL if the order has not been shipped yetShipEmployee Char(50) The name of the employee who shipped the orderShipingMethod Char(50) The shipping method usedShipTrackingNum Char(50) The tracking number of the shipmentShipName Char(50) Shipping address informationShipCompany Char(50) Shipping address informationShipAddress Char(50) Shipping address informationShipCity Char(50) Shipping address informationShipState Char(50) Shipping address informationShipZip Char(50) Shipping address informationShipCountry Char(50) Shipping address informationShipPhone Char(50) Shipping address information

Order Detail OrderDetailI D Primary Key AutoNumberDatabase generated unique identifier

OrderI D Required (FK)Number Foreign key to Orders.OrderI D - the parent order

ProductI D Required (FK)Number Foreign key to Products.ProductI D - the product that was ordered

VersionSent Char(50) The version of the product that the customer was sent

Price Currency How much the customer was charged for the product

DiskSerial Char(50) The serial number of the disk that was sent. Generated when the disk is created

LicenseKey Char(50) The license key for the product ordered. Generated at order time by an external program

LicenseTerm Char(50) The term that was purchased measured in days

ExpirationDate Date/ Time The date when the license will expire

RegName Char(50) I nformation returned on the registration card

RegCompany Char(50) I nformation returned on the registration card

RegAddress Char(50) I nformation returned on the registration card

RegCity Char(50) I nformation returned on the registration card

RegState Char(50) I nformation returned on the registration card

RegZip Char(50) I nformation returned on the registration card

RegCountry Char(50) I nformation returned on the registration card

RegPhone Char(50) I nformation returned on the registration card

RegFax Char(50) I nformation returned on the registration card

RegEMail Char(50) I nformation returned on the registration card

RegLocation Char(50) I nformation returned on the registration card

RegAMTs Char(50) I nformation returned on the registration card

RegCompType Char(50) I nformation returned on the registration card

RegI nternet Char(50) I nformation returned on the registration card

TechSupportNotes Memo Technical support notes

Products & Product Term & Shipping Method

ProductsProductID Primary KeyNumber In-house generated unique identifier

BaseProductID NumberFor companion kits: foreign key toProducts.ProductID - For base products: NULL

ProductNameAlternate KeyChar(100)The name of the productPrice Currency Default price for the productVersion Char(50) Current version being shipped

HasVouchers True/ FalseSpecifies if vouchers should be generated for ordersof this product

ProductTerm

ProductID CK(1,1) - (FK)NumberComposite key member - Foreign key toProducts.ProductID

Term CK(1,2)Number Composite key member - Number of days for termPrice Currency Default price for this term

ShippingMethod

Method Primary KeyChar(50)Name of the shipping method (i.e. FedEx Two-dayAir)

Vouchers

VoucherID Primary Key NumberSystem generated, random number and uniqueidentifier

OrderDetailID FK Number Foreign key to OrderDetails.OrderDetailIDVoucherRecDate Date/ Time Date the voucher was received back

VoucherShipDate Date/ TimeDate the voucher was processed and returned tocustomer

VoucherShipEmployee Char(50) Name of employee who shipped the voucherVoucherShipMethod Char(50) Shipping method used to send the voucherVoucherTrackingNumber Char(50) Tracking number of shipmentVoucherName Char(50) Voucher shipping address informationVoucherCompany Char(50) Voucher shipping address informationVoucherAddress Char(50) Voucher shipping address informationVoucherCity Char(50) Voucher shipping address informationVoucherState Char(50) Voucher shipping address informationVoucherZip Char(50) Voucher shipping address informationVoucherCountry Char(50) Voucher shipping address informationVoucherPhone Char(50) Voucher shipping address informationVoucherFax Char(50) Voucher shipping address information

OMS Description of Screens

Use Case 1: User enters new order 

User Action System Response

1. User starts OMS software and chooses Create Order menu item.

System displays Create Order form.

2. User enters order information and clicks Add Product button.

System displays Order Detail sub form.

3. User enters product information and clicks Print Registration Card button.

Registration card is printed containing product and license information.

4. User clicks OK button. Order Detail sub from disappears. Details of the added product appear in the Order Details list box.

5. User clicks OK button on Create Order form. Order information is committed to database. Create Order form disappears.

Assumptions: All order information is entered correctly. User has a printer attached to the local machine. Alternatives: Steps 2-4 may be repeated as needed.

 

Use Case 2: User ships existing order

User Action System Response

1. User starts OMS software and chooses Ship Order menu item.

System displays Ship Order form. Invoice Number, Customer ID, Name, and Company fields are automatically populated with information from the oldest unshipped order.

2. User enters shipping information and clicks OK button.

Information is committed to database. Ship Order form disappears.

 

Assumptions: Shipping information is entered correctly. Alternatives: User can edit Invoice Number field. Changing the value will load order information from the specified order.

Use Case 3: User enters registration information

User Action System Response

1. User loads OMS software and chooses Register Product menu item.

System prompts user to enter License Key for the product to be registered.

2. User enters License Key value and clicks OK button.

System displays Order Registration form. Invoice Number, Customer ID, Company, Product ID, Serial Number, and License Key fields are automatically populated with information for the order.

3. User enters registration information and clicks OK button.

Information is committed to database. Order Registration form disappears.

 Assumptions: License Key provided is valid. Registration information is entered correctly.

 Use Case 4: User registers voucher

User Action System Response

1. User loads OMS software and chooses Register Voucher menu item.

System prompts user to enter Voucher ID for the voucher to be registered.

2. User enters Voucher ID value and clicks OK button.

System displays Voucher Registration form. Values for Voucher ID, Invoice Number, Customer ID, Company, Product ID, Serial Number, and License Key are automatically populated with information for the voucher.

3. User enters voucher registration information and clicks OK button.

Information is committed to database. Voucher Registration form disappears.

 

Assumptions: Voucher ID provided is valid and assigned. Registration information is entered correctly.

Use Case 4: User ships certificate

User Action System Response

1. User opens OMS program and selects Ship Certificate menu item.

System prompts user for Voucher ID of the voucher to be redeemed.

2. User starts OMS software and chooses Ship Certificate menu item.

System displays Certificate Shipping form. Fields for Voucher ID, Invoice Number, Customer ID, Company, Product ID, Serial Number, License Key, and Voucher Company are automatically populated from database.

3. User enters certificate shipping information and clicks OK button.

Information is committed to database. Certificate Shipping form disappears.

 Assumptions: Voucher ID entered is valid and assigned. Shipping information is entered correctly.

 Use Case 5: User enters technical support information

User Action System Response

1. User opens OMS program and selects Technical Support menu item.

System prompts user to search using one of the following methods: Customer ID, Ship Company, Serial Number, or License Key.

2. User selects search method and enters appropriate value.

System displays Technical Support form. Fields for Invoice Number, Customer ID, Order Date, Purchase Order Number, Ship Name, Ship Company, Product Name, product ID, Serial Number, Version Sent, License Term, License Key, and Expiration Date are automatically populated from database.

3. User enters technical support information and clicks OK button.

Information is committed to database. Technical Support from disappears.

 Assumptions: Search information entered is valid. 

Use Case 6: User creates vouchers

User Action System Response

1. User opens OMS software and selects Create Vouchers menu item.

System displays Create Vouchers dialog box.

2. User enters the number of vouchers to create, and clicks Generate and Print Vouchers button.

System generates specified number of random, unique 6-digit Voucher ID numbers, writes them to the database, and prints Voucher Slips, two per standard letter-sized page.

 Assumptions: System is able to generate a sufficient number of ID numbers.

Class Diagram

UI-centric

Class Diagram

Data-centric

PresentationTier

UI-Centric Tier

Data-centric Tier

Load()Fetch()

Edit BeginEdit()

Save

ApplyEdit()

Save()

Load

Data Services Tier