|
TABLE OF CONTENTS
USER REQUIREMENTS 4
ERD 6
Class & Use Case Diagrams 6
Summary 8
Use Case Diagram for Sell Product 11
Use Case Diagram for Ship / Receive Product 12
Use Case Diagram for Purchase Stock 12
Use Case Diagram for Purchase Stock 13
References 14
Introduction
The Monkey’s Music Store has been selling musical instruments in Reno, Nevada for three years. ... Through the usage of UML modeling the initial database is designed to include the following tables:
· Customers: This table will contain the constant data for Monkey’s customer base, and will include the customer ID primary key, Customer Name, address, phone number, and email fields
· Orders: This table will contain the information regarding stock orders that are pending from vendors. ...
Class & Use Case Diagrams
The Class Diagram for the Music Store Inventory Database System will include all of the entities that we discovered through our observation. ...
For our Customer Class Diagram, we will have the data of Customer ID, Name, Address, Phone Number, and Email address. ... For the Salesperson Class Diagram, we will have the data of Salesperson ID, Name, Address, Phone number, Pay rate, and Bank account. ...
For the Product Class Diagram, we will have the data of Product ID, On-hand quantity, Warehouse location, Item Price, and Item Cost. ... For the Purchasing Class Diagram, we will have the data of Purchasing ID, the Minimum quantity, and the maximum quantity. ...
For the Vendor Class Diagram, we will have the data of Vendor ID, Name, Address, Phone, Fax, and Contact. ... For the Sale Class Diagram we will have the data of Sales ID, Clock, Quantity purchased, and Vendor warranty. ...
From these class diagrams we will be able to create our objects for our database program and have all of the necessary information to complete all processes from contacting vendors, receiving products, contacting customers, and making the final sale.
The use case diagrams included in the inventory database model are sell product, ship and receive product, and purchase stock. ... These use cases provide high level view that represent the goals needed in the rolls of selling inventory, buying inventory, shipping and receiving inventory, and maintaining data in the system. The purpose of these use case diagrams is to provide an overview of system usage requirements, and communicate the scope of the modeled project.
Relationships included in the diagrams are: Associations: the associations is used to display the link between the actors and uses.
Approximate Word count = 1964
Approximate Pages = 7.9
(250 words per page double spaced)
|
|
