JewelsmithFinalProjectRev2 (1)

Jewelsmith’s Work Order
Management System

1
Table of Contents
I. Project Proposal ...........................................................................................2
II. System Proposal ...........................................................................................5
Executive Summary.........................................................................................................6
As-Is System Description...............................................................................................7
Evaluation of the Current System.................................................................................9
To-Be System Concept ................................................................................................11
Analysis Models.............................................................................................................12
Functional Model: Use-Case Diagram ..................................................................14
Functional Model: Use-Case Descriptions ...........................................................15
Functional Model: Activity Diagram .......................................................................25
Structural Model: Class Diagram ...........................................................................26
Structural Model: CRC Cards .................................................................................28
Behavioral Model: State Chart Diagram ...............................................................34
III. System Specification for Jewelsmith .............................................................35
Summary of Design Strategy .......................................................................................35
Physical Architecture Layer .........................................................................................40
Relationship Diagram ...................................................................................................41
Interface Design ............................................................................................................42
Design Standards..........................................................................................................42
Navigation Design.....................................................................................................42
Windows Navigation Diagram.................................................................................43
Input/Output Design .................................................................................................44
Main Menu User Interface.......................................................................................44
Data and File Specifications ........................................................................................50
Database Tables ...........................................................................................................50
IV. Conclusion .................................................................................................52

2
Project Proposal
1. Business Application
i. Business name and project sponsor:
Jewelsmith, Sue Strebe (Business Owner)
ii. Description of product(s)/service(s) of the business:
Jewelry Retail Sales, Jewelry Repair Services, Custom Jewelry
Fabrication
iii. Classification of the industry of which the business is a part:
Retail, Jeweler
iv. Business need:
The Limitations of the Current System Restricts Work Order History,
● Track work orders from initiation to work in process through
completion
○ Add, Assign, Update, Review, and Complete Work Orders
● Invoice Management
● Maintain Work Order History
● Work Order Pricing Management
v. Functional business system(s) to be addressed by the project:
Automation of current work order management system and invoicing of
services.
● Add, Assign, Update, Review, and Close Work Orders
● Invoice Management

3
● Maintain Work Order History and Backups
● Pricing Management
2. System Profile
i. Define business application(s):
Goal: Automate Current Workflow System
Business Objectives:
Work Order Creation
● Get client information
● Get clients item and item information
● Estimate for repair
Work Order Assignment
● Jeweler
● To Outside Vendor
Review of Work Completed
● Check for errors/completeness
Invoice Client
● Contact Client
● Collect Payment for Services Rendered
● Close Invoice/Close Work Order
ii. Identify clients and support for them:
● Owner: Create Pricing Structure, Review Work Orders.
● Clerk: Work Order Creation, Assign Work Order, Work Order
Retrieval, Create Invoice, and Close Work Order.

4
● Jeweler: Receive Work Order, Record Work Order Details, Return
to Clerk.
iii. Describe the system’s current technology:
Manual, carbon-copy envelope system tracks work orders through the
business.
Minimal paper filing to track work order history.
Customer is contacted for item Pick up.
Invoice is handwritten upon customer arrival, and approval of Work done.

5
System Proposal
1. Executive Summary
2. As-Is System Description
3. Evaluation of the Current System
i. Requirements Analysis Strategy(ies)
ii. Requirements Analysis Technique(s)
4. To-Be System Concept
i. Proposed objectives for new system + constraints
ii. Planning assumptions
iii. Project scope
5. Analysis Models
i. Functional models
ii. Structural models
iii. Behavioral models

6
Executive Summary
Jewelsmith is a family owned and operated jewelry store located in Tempe, AZ.
Established in 1973, this small business sells retail and custom jewelry, as well as
offering services such as jewelry cleaning, repairs, and restoration. The focus of this
project is to automate, and bring up to date, the current system of how work orders are
handled by the business.
The current system at Jewelsmith primarily relies on manual entries using carbon
copies to create work orders and entry logs to record customer information and work
order numbers. These log entries are stored in a filing cabinet while the carbon copy
work orders are shredded once the work order has been completed. Customer
information is the only data stored on a computer using an antiquated computer with out
of date software. There are a total of three computers with no network connection, each
operating on a different operating system. None of these computers are currently being
used to manage work orders, resulting in a paper-based document management
system.
Formula 1 Consulting met with Jewelsmith’s business owner, Sue Strebe, and
employees, Patricia Berney and Bridgette Martin. Formula One Consulting evaluated
the current work order system using document analysis, interviews, and observation.
The Owner agreed, a new system to manage work orders would be very beneficial to
her business. Formula 1 Consulting will take this input and information and create a new
work order system that is automated and easy to use for Jewelsmith and its employees.

7
As-Is System Description
The current system at Jewelsmith for taking in Work Orders relies entirely on
handwritten carbon copy paper envelopes and several paper filing logs. The current
system handles the Work Order intake process, and allows employees to track the
Work Order through the business process.
The carbon copy envelopes serve the purpose of recording pertinent data about
the Client, Item, and Work Order.
 Client: Name, Address, Phone Number, and Email
 Item: Item Description
 Work Order: Work Order Instructions, Parts Needed, Estimate Given
The paper filing log serves the purpose of maintaining a consolidated history of
past Work Orders. It also can be helpful in looking up if a Work Order has been
completed or not. There is a regular Work Order log which stores details such as: Date
In, Customer Name, Item, Work Order Description, and Phone Number. There is also a
separate log for managing Work Orders relating to Watch Repairs that are outsourced.
This log stores the Date the item gets dropped off, the Date it returns, the Client Name,
and the Item Description (in this case, the Brand Name of the watch).

8
Through Interviews, Observation Analysis, and Document Analysis, we
determined the business process of managing the Work Orders to be:
1. Client requests repair for an Item.
2. Clerk inspects the Item.
3. Clerk outlines work to be done and provides Estimate, if possible.
4. If accepted, Clerk collects Client Information on carbon copy envelope.
5. Customer receives the top copy of the envelope as a receipt.
6. Clerk enters Work Order information in the Log.
7. Clerks assigns Work Order as follows:
a. If done in house, the Work Order goes into the Inbox.
b. If outsourced, the Work Order gets another associated envelope
and is assigned to appropriate outside vendor.
8. Upon completion of the Work Order, it’s placed in the Out Box.
9. Clerk picks Work Orders up from the Done Box and records the Date Out
on the Log.
10.The Client is then notified by Phone Call that the Work Order is complete.
11.Client is Invoiced upon returning to the Store to pick up their Item.
12.Once the customer reviews and accepts the work done, payment is
collected.
13.The paper envelope is destroyed after Item is picked up.

9
Evaluation of the Current System
The primary Analysis Strategy that we chose to employ for Jewelsmith’s Work
Order Management System is Business Process Automation (BPA). We feel that using
BPA would result in a significant improvement over the current system.
Through the Problem Analysis Techniques, we were able to identify several
areas that could be improved/automated. During our initial requirements gathering
interviews with the Staff at Jewelsmith, we identified the current problems and
limitations within the problem domain. Using information collected during these
interviews, process observation, and document analysis we have determined
several issues that could be improved using an automated cohesive system.
ProblemAnalysis
1. There is very limited data stored about the Work Orders.
a. This is a problem because there's no record of the work
order details, or the estimate given, which makes it difficult should an
Employee need to look back at the history of a Client's work order.
2. There is very limited data stored about the History of Work Orders.
a. Without the ability to look up a Work Order history, the
business is limited in the data they can pull up. Should a
Client have a problem with a past work order, this presents a
problem because there is not an easy or accurate way to
pull of this information to resolve the Client's issue.
3. All records are handwritten and kept in one physical file folder.

10
a. Keeping everything in one folder could be prone to loss of
data quite easily should the file folder
4. There is no system in place to retrieve the Work Order records once
completed.
a. This leads to a slow Client response time should a Client
need to check back on a Work Order for any reason.
5. Work Order envelope system is destroyed at the end of every week, which
contains the Work Order details.
a. This is a problem because all of the information relating to that
Work Order is destroyed. The details of a Work Order are very
important; the business would benefit from storing all this
information for future use. This protect the business in the
case that a Client later has a complaint about work done,
needs to check what ring size they are or had their rings sized
to, or wants to re-order an item.

11
To-Be System Concept
The new system that we will develop for Jewelsmith will automate their current Work
Order system. The system will replace the manual filing system consisting of written
paper logs which also reduces the need for filing cabinets. Some items from the old
system can be integrated into the new system which in turn will help keep costs down
for the client.
Customer information is currently stored on existing business software, Jewelry
Shopkeeper. Some of the existing items of the old system will remain in place as they
still serve other functions to the current business operations, plus, this will help keep
costs down. These items include:
 Jewelry Shopkeeper business software.
 Small paper envelopes with Preassigned Work Order numbers with written
customer information to store jewelry in.
After converting the old system to a new automated system, record keeping will
become more efficient and reduce errors.

12
Analysis Models
Now that we have gone over the as-is system this next section will go over the
outline of the to-be system. The outlines of the Analysis Models will describe how the
to-be system will operate. The set of models will break down the data and the
procedures necessary to support the business process.
i. Functional Models: Use-Case Diagram, Use-Case Description, Activity
Diagram
The Use-Case Diagram will give you a visual representation of how
the Employee's, Client's, and Use-Cases will interact with one another.
The Use-Case Descriptions will outline specific steps and also
show relationships between Use-Cases.
The Activity Diagram shows the flow of the activities from the Use-
Cases independent of the classes.
ii. Structural Models Attached: Class Diagram, CRC Cards
Structural Modeling formally depicts objects that are used and
created by a system. The Class Diagrams breaks down the data as it represents
templates for objects to be created within the system. Their attributes represent a
pieces of data relevant to the description of the class, and methods within those classes
define the actions necessary within the business process.
iii. Behavioral Models Attached: State Chart Diagram

13
This dynamic model will show the different states an object will
pass through in response to a specific activity or event. In this model, the Work Order is
depicted as it passes through different states within the system.

14
Functional Model: Use-Case Diagram

15
Functional Model: Use-Case Descriptions
Use Case Description
Use Case Name: Add Client ID Number: JS-UC1 Importance Level: High
Primary Actor: New Client Use Case Type: Detail, Essential
Stakeholders and Interests:
Employee - wants to input Client’s information into database
Client - wants to utilize business services
Brief Description:
This use case describes how a New Client is created in the system.
Trigger: New Client requests work order
Type: External
Relationships:
Association: New Client
Include:
Extend:
Generalization:
Normal Flow of Events:
1. Client requests Work Order from Employee
2. Employee checks if Client is in the system.
a. Client is in the System: Exit Add Client Use-Case.
b. Client is not in the System: Employee collects Client Information.
2. Employee executes Create Work Order Use-Case
Subflows:
Alternate/Exceptional Flows:

16
Use Case Name: Update Client ID Number: JS-UC2 Importance Level: High
Primary Actor: Existing Client Use Case Type: Detail, Essential
Employee - wants up to date information for Client in the database
Client - wants to make changes to their information in the database
Brief Description:
This use case describes how an Employee updates information for a Client in the
Database.
Trigger: Existing Client places work order
Type: External
Relationships:
Association: Existing Client
Include:
Extend:
Generalization:
1. Existing Client provides updated information pertaining for the Client such
as: Name, Address, Phone Number, etc.
2. Employee updates Existing Client’s information in system.
3. Verbal confirmation is given to the Client.
Subflows:

17
Use Case Name: Add Employee ID Number: JS-UC3 Importance Level: High
Primary Actor: New Employee Use Case Type: Detail, Essential
Employee - wants to add employees to the system.
Brief Description:
Describes how an Employee will add a New Employee to the system.
Trigger: Employee hires/contracts with a New Employee.
Type: External
Relationships:
Association: New Employee
Include: Update Employee
Extend:
Generalization:
1. Employee collects New Employee information such as: Name, Address, City,
State, Zip, Phone, Email, etc.
2. Employee adds New Employee to the system.
3. New Employee is assigned an Employee ID.
Subflows:
3a. If New Employee already exists, transaction aborted.

18
Use Case Name: Update Employee ID Number: JS-UC4 Importance Level: High
Primary Actor: Employee Use Case Type: Detail, Essential
Employee - needs to update their information within the system.
Brief Description:
Describes how an employee's information will be updated within the system.
Trigger: The Employee needs to make essential changes to their existing Employee
Information.
Type: External
Relationships:
Association: Employee
Include:
Extend:
Generalization:
1. The Employee information changes are submitted to the Business Owner.
This includes any changes in regards to Employee's Name, Address, Phone
Numbers, Email Address, etc.
2. Business Owner makes correct changes to the Employee’s information.
3. Business Owner gives verbal confirmation of successful Employee Updates.
Subflows:
2a. If Employee doesn't already exist in the system, execute Add New Employee
use-case.

19
Use Case Name: Create Work Order ID Number: JS-UC5 Importance Level: High
Primary Actor: Existing Client Use Case Type: Detail, Essential
Client – Wants to request a new work order
Brief Description: This Use Case describes how an employee wants to create a new
work order for a client.
Trigger: Client requests work on any item whether it be a custom piece or a repair
Type: External
Relationships:
Include: Assign Work Order, Review Work Order, Invoice Client
Extend: Track Work Order
Generalization:
1. Employee inspects Client's item for possible work and/or parts needed for
the Work Order.
2. Employee outlines work needed with the Client.
4. Employee provides estimate.
5. Client agrees with Work Order details.
6. Client provides Employee with his/her contact information.
7. Employee searches for Client in system.
8. System generates Work Order and prints Invoice.
9. Employee invokes Assign Work Order Use Case.
10. Employee reviews Work Order upon completion.
Subflows:
4a. Estimate cannot be given at the time; Client will be contacted at a
later time.
4b. Employee deems item unrepairable, exit Use Case
5a. Client cancels request and transaction is aborted.
7a. Employee invokes Add Client Use-Case.

20
Use Case Name: Assign Work Order ID Number: JS-UC6 Importance Level: High
Employee – Wants to assign work order to appropriate repair person
Brief Description: This Use Case describes how an existing employee assigns the
work order for the customer’s item to a repair person.
Trigger: Employee creates work order
Type: External
Relationships:
Association:
Include:
Extend:
Generalization:
1. Employee inspects Work Order for Parts Needed.
2. Employee assigns repair person to Work Order.
3. Employee delivers Work Order to Repair Person.
Subflows:
2b. No repair parts in stock, item on hold for parts to come in
3a. Employee assigns custom piece order to Jeweler
3b. Jeweler requests Work Order reassigned to Outside Vendor

21
Use Case Name: Track Work Order ID Number: JS-UC7 Importance Level: High
Employee – Wants to be able to look up the status of a Work Order
Client – Wants to know the status of their Work Order
Brief Description: This use case describes how an Employee tracks the progress of a
Work Order for an Existing Client.
Trigger: Employee or Client requests the status of Work Order.
Type: External
Relationships:
Association: Existing Client, Employee
Include:
Extend:
Generalization:
1. Employee looks up Existing Client Work Order within the system.
2. Employee takes note of the Work Order Status, ensuring that it’s on track
for completion.
Subflows:
2b. Employee notifies Existing Client of Work Order Status.
1b. Employee looks up a Work Order that has already been completed and picked
up.

22
Use Case Name: Review Work Order ID Number: JS-UC8 Importance Level: High
Employee – Wants to ensure the accuracy of a Work Order
Brief Description: This use case describes how Employees will review Work Orders.
Trigger: Work Order is completed by Jeweler/Vendor.
Type: External
Relationships:
Association:
Include:
Extend:
Generalization:
1. Employee receives completed Work Order.
2. Employee compares Work Order description to work done.
3. If Work Order description does not match the work done the item is sent
back to the jeweler/vendor for completion.
Subflows:

23
Use Case Name: Invoice Client ID Number: JS-UC9 Importance Level: High
Employee – Wants to get paid by Client for Work Order
Client – Wants to pick up Work Order item
Brief Description: This use case describes how an Employee invoices the Client for a
Work Order.
Trigger: The Work Order Complete and ready for delivery to Client.
Type: External
Relationships:
Association:
Include:
Extend:
Generalization:
1. Work Order is reviewed by Employee and Client at time of delivery.
2. Employee produces Invoice based on Work Order details.
3. Client pays Invoice in full.
4. Employee delivers finished item and receipt to Client.
Subflows:
3b. If payment cannot be delivered by Client then item is withheld until
payment is made.
1a. Client and/or Employee send Work Order back for further refinement.
3a. Client makes payment arrangements, or layaway plan.

24
Use Case Name: Adjust Pricing
Structure
ID Number: JS-UC10 Importance Level: High
Employee – Wants to manage pricing of work orders/invoices.
Brief Description: This use case describes how an Employee updates the pricing on a
Work Order.
Trigger: Owner changes prices of goods/services in the ever changing prices of the
open marketplace.
Type: Temporal
Relationships:
Include:
Extend:
Generalization:
1. Employee searches system for goods/services to update.
2. Employee updates costing of goods and services according to change in
market.
3. Pricing structure for Work Orders/Invoices is now updated and the business
can continue to turn a profit.
Subflows:

25
Functional Model: Activity Diagram
The Work Order Activity Diagram describes the process flow between Use
Cases, from creation to close of the Work Order between the Client and the Employee.

26
The Work Order flow itself is a pretty smooth system, with very little decision activity or
alternate process flow, as depicted in the diagram.
Structural Model: Class Diagram
The Work Order Class Diagram on the next page breaks down each class in
detail, listing it’s attributes and the way the classes interact with one another. The
diagram begins with a Person, the Parent Class, which is made up of two Child
Classes, the Client and the Employee. The relationship between the Client and
Employee create an Association Class, the Work Order. From the Work Order, two
Concrete Classes are formed, the Invoice and the Vendor. This model will become the
foundation for forming relationships in the new automated system.

28
Structural Model: CRC Cards
CRC Cards
Class Name: Person
ID: JSC-01
Class Type (Abstract, Concrete,
Domain): Abstract
Brief Description: Any person
in the system.
Associated Use Cases: N/A
UC
#
Responsibilities Collaborators (classes)
N/A N/A
CRC card (back side)
Attributes Relationships with other classes
Last Name Generalization (is a):
First Name
Email
Phone Aggregation/Composition (has parts):
Address
Association:

29
CRC card (front side)
Class Name: Client
ID: JSC-02
Domain): Concrete, Domain
Brief Description: A Person
wants to place a Work Order.
Associated Use Cases: 2
UC
#
Provide personal contact
information
Work Order
Pay Invoice
Create Client
Update Client
LastName Generalization (is a):
FirstName Person
Address
City Aggregation/Composition (has parts):
State
ZipCode
HomePhone Association: Work Order

30
Class Name: Employee
ID: JSC-03
Brief Description: A Person
Employed at the store. Handles
Work Order completion.
UC
#
Invoice client Client
Assign Work Order Work Order
Track Work Order Work Order
Review Work Order Work Order
Add Employee Employee
Update Employee Employee
Create Pricing Structure Employee
Employee ID Generalization (is a):
Position Person
Aggregation/Composition (has parts):
Association: Work Order

31
Class Name: Work Order
ID: JSC-04
Brief Description: An item or
service to be completed by
Employee.
UC
#
Create Work Order Employee
Assign Work Order Client
Track Work Order
Review Work Order
Cancel Work Order
workOrderID Generalization (is a):
clientID
receivedDate
estimatedDueDate Aggregation/Composition (has parts):
workToBeDone
estimate
status Association: Employee, Client
assignedToEmployee
employeeID
assignedToVendor
vendorID

32
Class Name: Vendor
ID: JSC-05
Brief Description: An item for
repair assigned to Vendor by
Employee
Associated Use Cases:
UC
#
Employee
vendorID Generalization (is a):
businessName
contactFirstName
contactLastName Aggregation/Composition (has parts):
address
city
state Association: Work Order
zipCode
businessPhone
email

33
Class Name: Invoice
ID: JSC-06
Brief Description: An item for
repair assigned to Vendor by
Employee
Associated Use Cases:
UC
#
PayInvoice Employee, Client
invoiceID Generalization (is a):
invoiceDate
clientID
descriptionOfWorkOrder Aggregation/Composition (has parts):
workOrderID
finalCost
Association: Work Order

34
Behavioral Model: State Chart Diagram

35
System Specification for Jewelsmith
Summary of Design Strategy
Jewelsmith will receive a custom developed system that will be designed to meet
their needs. The current staff has limited technical skills and a custom built system is
the best option because it gives Jewelsmith an easy to read, navigate, and update the
database system. After searching for a prebuilt system the level of complexity and
technical knowledge is going to be overwhelming for the Jewelsmith staff. Jewelsmith
has no in-house expertise to develop and maintain this system; this project will be
outsourced to Formula 1 Consulting. The time frame for completing this project is
flexible, this approach will allow Jewelsmith to have all of the functionality that is
necessary according to technical skills of the staff.
This document will outline the design details and specifications for the to-be
system for Jewelsmith’s Work Order Management System.
Physical Architecture Design
This section will address the specific software and hardware requirements and
design that will be in place. It includes software dispersion on the devices as well as the
network connections in the system.
Relationship Diagram
The relationship diagram will show how the Class Diagram from the System
Proposal has evolved to establish relationships between the tables necessary to
construct this system.

36
Interface Design
This section will cover the design specifications put in place for the human-
computer interaction. It will include Designs Standards and Windows Navigation
Diagram.
Input/Output Design
This section will show prototypes of the Forms and Main Menu that the user will
use to navigate and operate throughout the system.
Data and File specifications
These data and file specifications outlines the tables, fields, data types, and a
short description of each field.
By the end of this document, you will understand the detailed design for the To-
Be system for Jewelsmith.

37
Physical Architecture Design
The new system will run on Microsoft Access 2016 and allow Jewelsmith to input
customer work orders, manage customer information, and invoice customers through a
Client Based Network consisting of 3 desktop computers and a networked printer.
The database will be stored in two locations: the first will physically be stored and
accessed through the network on the Manager’s Office PC (see diagram), and second
by utilizing Microsoft Office 365 Cloud file storage as a backup.
Operating System
 All 3 computers will run Windows 10 (needs to be purchased by owner)
Microsoft will continue to be supporting Windows 10 for the next decade.
Software
 Microsoft Office 365 License for three desktop computers (needs to be
purchased by owner)
 Avast Security Software 2016 for three desktop computers
Our database has been created using Microsoft Access which will be supported
by Microsoft for years to come. It will also allow for access to the other Microsoft
products like Outlook and Word. Avast is a free antimalware program to be
hosted on each client on the network.
Hardware
 Dell Inspiron 3650 Desktop Computer (needs to be purchased by owner)
 Intel Core i-5 processor
 16GB RAM

38
 1 TB Hard Drive
The Dell 3650 Desktop Computer is a small form factor machine that will
fit nicely with in the limited desk space of the store.
Network
 Client Based
 Century Link DSL Internet
 NETGEAR - N900 Router/Firewall
This Client based system will house all of the graphical and processing power that is
needed to exceed the work demands. The Current ISP is Century Link and provides
enough bandwidth to handle the workload. In order for all of the clients to talk with one
another, we recommended the NETGEAR N900. The N900 is a robust router with
integrated firewall that has Wi-Fi capability should the owner choose to go to a wireless
network in the future.
Security Access
 Administrator - Business Owner – Sue Strebe
o Will have primary access to all systems.
 User Account(s) – Employees
o Will have user access set to enter data, run reports only.
Security is a strong factor to consider for this project due to its high end retail
nature. Jewelsmith’s current location already have physical access controls in
place that are sufficient for the business need. To further secure the information
on the PC’s, the hard drives will be encrypted with Bit Locker (supported by and

39
part of Windows 10), user access lists, Windows Defender, Windows Firewall,
and Avast antimalware.
As part of the security measures put in place, users will only be allowed to
access the data contained in the forms. Users will not be able to access data
stored directly in the tables.

40
Physical Architecture Layer
This diagram depicts the network topography.

41
Relationship Diagram
The Relationship Diagram is based upon the Class Diagram from the System
Proposal. The relationships have expanded to include Invoices and Vendors tables
which will fulfill the main functions of the to be Work Order Management System.
The relationships above can be broken down into individual relationships as
shown in the table below:
Table Primary Key Relationship Table Foreign Key
Clients ClientID One to Many WorkOrders ClientID
Clients ClientID One to Many Invoices ClientID
WorkOrders WorkOrderID One to Many Invoices WorkOrderID
Employees EmployeeID One to Many WorkOrders EmployeeID
Vendors VendorID One to Many WorkOrders VendorID

42
Interface Design
Design Standards
The system will use a series of input forms with simple and consistent buttons to
navigate through the work order management system. Throughout Microsoft Access, all
the buttons and form layouts will generally have the same look (interface template)
making it easy for the Employees to learn and use.
Navigation Design
The layout of these forms will minimize user effort during data entry by having the layout
of the input boxes in the same order that they are collected for the Client, Work Order, or
Employee. This will also be achieved by providing a comfortable user experience and by using
consistent navigation controls through the system.

43
Windows Navigation Diagram
This navigation diagram represents the processes of the forms and windows of
the database system. The new system allows the user to input data in 3 clicks and
search for data in 4 clicks, minimizing the amount of time and effort in using the system.
The next section will demonstrate how the Windows Navigation Diagram will
transform into a User Interface pleasing to the eye, as well as easy to use and learn for
the Users.

44
Input/Output Design
The following pages of screenshots display the prototype forms that the
Employees will use to enter Client, Employee, Vendor, and Work Order information.
Main Menu User Interface

45
Client Form
Search Client Form

46
Employee Form
Search Employees Form

47
Vendor Form
Search Vendors Form

48
Work Order Form
Search Work Orders Form

49
Invoice Report (PDF)
All forms shown have been derived from database tables stored in the Database
Management System. The Data and File Specifications section will describe each table
in detail on how this data is to be stored.

50
Data and File Specifications
The following tables were derived from the Class Diagram represented in the
System Proposal. The classes identified will become the basis for developing the tables
in the DBMS. The attributes within those classes will become the fields for each table.
The following is a list of all of the database tables with a Field Name, Data Type,
and Description.
Database Tables
Client Field Table
Employee Field Table

51
Vendor Field Table
Work Order Field Table
Invoice Field Table

52
Conclusion
The newsystemforJewelsmith isdesignedtoprovide automation; alsomakingtaskseasierto
create,manage,and maintaintheirWorkOrderand Work OrderHistory.As you readin thisdocument,
we usedseveral analysismodelstodepicteveryaspect withinthe problemdomainandtounderstand
everytaskand itspurpose.The Use-Case Diagramdepictsthe mostimportantkeyactivitiesof the
businessprocessandhowtheyrelate toone another.The Use-Case Descriptionsgointodetail
describingeveryactionnecessarytocomplete thatparticularprocess. The ActivityDiagramisa visual
model allowingeasyunderstandingof the flow of activities forthe maintask(s) in thisSystem. The Class
Diagram identifiesthe necessaryobjects,attributes,andmethodsneededwithinthe problemdomain.
CRC Cards tie intothe ClassDiagramprovidingahigherlevel of detail aboutthe specificclasses. And
finally,the Behavioral State Diagram depictsthe changesinthe state of the mostimportantpart of this
system—the WorkOrder. We made sure the new systemintegratedall of these necessaryactivities,
parts,and functions.
Basedon the thoroughanalysiscoveredinthisdocument,the systemdesignedbyFormula1
Consultingwillmeetthe businessneedsof Jewelsmith’sWorkOrderManagementbyprovidingvalue to
the business.Such valuablebenefitsinclude anincrease inthe accuracyregardingWork Ordersand
Work Orderhistory. The Employeeswill easilybe able toenterClientsandWorkOrdersintothe System
usingthe newsystem. The Ownerwill have well documentedinformationinrelationtothe Client’s,the
repairscompleted,the WorkOrdertime-frame,andthe cost/pricespaidforthe services providedby
Jewelsmith.Havingthisinformationavailable,andbeingeasytolookup allowsthe businessOwnerto
make informeddecisionsregardingrepairpricing,andmore.Thisalsoallowsthe Ownertolookupany
previousWorkOrdershouldthere be aneedto doso (a mistake, abad job,price reference, WorkOrder
Details, etc.).Withthe currentsysteminplace,these tasksare toodifficult,andtake a lotof time.Our

53
newsystemwouldmake this processeasier,andtake muchlesstime. Forall of these reasons,we
believethissystemwouldbe adrasticimprovementoverwhat’scurrentlyinplace withinthe business.

JewelsmithFinalProjectRev2 (1)

Recommended

Recommended

More Related Content

Similar to JewelsmithFinalProjectRev2 (1)

Similar to JewelsmithFinalProjectRev2 (1) (20)

JewelsmithFinalProjectRev2 (1)