Order Management System Gregory Barrett Ken 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 table

Order Detail

Products & Product Term & Shipping Method

Vouchers

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

PresentationT ier UI-Centric Tier Data-centric Tier Load() Fetch() Edit BeginEdit() Save ApplyEdit() Save() Load Data Services Tier