SAD_del3

SILK THREADS CASE STUDY 2015

TechMac Computing Solutions

OCTOBER 16, 2015 MARK ORLANDO

SHERIDAN COLLEGE

GROUP MEMBERS

SAMEED AHMED BAQAI

ALIN KAKOOZ

SIMRAN KAUR

SYED ZAIDI

DONALD MACKENZIE

ELLEN MACKENZIE

ANDREW MACKENZIE

CAMERON MACKENZIE

JOHN MACKENZIE

TECHMAC COMPUTING SOLUTIONS 1

1430 Trafalgar Rd,

Oakville, ON L6H 2L1

[email protected]

Silk Threads

Brampton, ON M4V 24P

Dear Mr. Mackenzie,

Our company TechMac Computing Solutions has been working for your family business, Silk

Threads and we will provide you with best and latest technology to your new system. We have

studied the system and explained its details diagrammatically.

Please review the following changes proposed for the new system:

Context Diagram

This diagram shows the boundaries of the system and entities interacting with it. It

represents the data flow between the system and the different entities.

Use Case Diagram

This diagram represents the interaction between users and the system. It shows the roles

played by actors.

Intermediate Use Case Narratives

It is a detailed explanation about the flow of events for the actors and the roles played by

them, which relates to the scenario.

Domain Class Diagram

The domain class diagram is a logical diagram that shows the objects with their

attributes.

The changes proposed for the new system will help you to improve your system. Our goal is to

provide you the best services. Please review the report and give your valuable feedback.

Sincerely,

TechMac Computing Solutions

mailto:[email protected]


Executive Summary

This report provides an analysis of the potential and current profitability, liquidness of Silk

Threads Company. In particular, comparative performance is poor in the areas of profit margins,

liquidity and budget and inventory management. Diagrammatical representation would help

explain different processes that should be carried out for improvement.

The report finds the prospects of the company in its current position are not positive. Thus,

demonstration of the requirements to increase profit is necessary.

Their firm needs an impeccable and secure system which would remove time consuming

processes.


Table of Contents

Executive Summary ........................................................................................................................ 2

Table of Contents ............................................................................................................................ 3

Introduction ..................................................................................................................................... 4

Context Diagram ............................................................................................................................. 5

Use Case Diagram........................................................................................................................... 7

Intermediate Use Case Narratives ................................................................................................... 9

1. Backup System ................................................................................................................................................. 9

2. Order Items ..................................................................................................................................................... 10

3. Compose Invoices .......................................................................................................................................... 11

4. Ship Items ....................................................................................................................................................... 12

Domain Class Diagram ................................................................................................................. 13

Recommendations ......................................................................................................................... 15


Introduction

Silk Threads is a privately owned enterprise established in 1985 at Brampton, Ontario. It is ran

by Donald and Ellen Mackenzie and their three sons, Andrew, Cameron and John.

Silk Threads has a wide selection of the men’s and women’s apparel items such as T-shirts, golf

shirts, and caps. Their business provides promotional items to various organizations: companies,

governmental agencies and school boards. Recently they have added engraving of plaques and

awards, in plastic, wood and metal. The company is known for its personalization of the products

they sell. This is done through embroidery and engraving.

The report discusses about the data flow and processes that would make their business efficient.

Also, various entities who are a part of processes are identified.

Requirements for the latest system include:

Use of context diagram

Creating use case and intermediate use case narratives

Creating domain class diagram.


Context Diagram

The following context diagram represents the data flow between the external entities. The central

core system is the Silk Threads System. The external entities identified are:

Customer

Warehouse

Vendor

Financial Institution

When a customer has to place an order, firstly he/she needs to set up an account. Customer

details and their financial details are required by the system in order to set up an account. After

an order has been placed, 50% of payment is must be deposited by customer either by debit or

credit card. Customer can include details about the personalization of their product. Also, system

checks if there is any repeat customer, then the discount is given.

An inventory check is done in the warehouse to make sure that inventory is updated or timely

ordered. A shipping confirmation and backorder is sent by warehouse employees to the system.

A purchase order is placed to vendor(s) which includes details of the company and vendor.

Vendor then, returns the packing list, invoice and the shipped items to system. A credit check is

done and response is given by the financial institution. Then, sales tax is calculated and

submitted to government.


Context Diagram

Figure 1


Use Case Diagram

The following Use Case diagram depicts four actors and the actors are:

Owner

IT technician

Shipping & Receiving manager

Customer

This diagram demonstrates the new ordering system for Silk Threads. The Backup System is an

important part of new system. The IT Technician will be hired and is responsible for it. Then,

owner and the customers will interact with the Order Items. Items are ordered online. Owners

deal with Compose Invoices with new application software. Lastly, ship items involve the

customer and the Shipping & Receiving manager which includes invoice and delivery.


Use Case Diagram

Figure 2


Intermediate Use Case Narratives

1. Backup System

Use Case Name: Backup System

Scenario Maintain operating system

Triggering Event: System is outdated and needs tune up for software to run properly.

Brief Description: When the system is outdated, an IT Technician comes in to back-up the system, performs

update on the operating system, Retest all applications, tune up, and prepares it back for

usage.

Actors: IT Technician , Owner

Related Use Cases: Includes: Order Items, Compose Invoices

Stakeholders: IT Department: To provide a full maintenance and tune up.

Owner: To inform the IT Technician that systems are outdated.

Preconditions Computer Systems must exist.

System must be outdated and not running properly.

Post-conditions: The technician must be contacted

Files must be backed up before any operations performed on the system.

Flow of Events: Actor System

1. Owner calls the IT Technician for

maintenance.

2. IT Technician confirms the request.

3. IT Technician backs up all the files

before performing anything.

4. IT Technician starts performing updates

on all of the software on the system.

5. Once updated, IT Technician tests each

application to make sure it runs

properly.

6. Repeat step 3 again to replace the old

update.

7. IT Technician runs final inspection of

the whole operating system.

8. IT Technician gives the green light to

inform owner that the operation is done.

9. Owner informs the workers that systems

are all updated and ready for use.

3.1. Cloud storage is in effect saving all

files on the cloud.

4.1 System is responding to the technician

updates and starts receiving.

5.1 System executes applications.

6.1 Cloud storage is in effect again to take

in the new backup.

Exception

Conditions:

1.1 If technician is not available, then business will run on cloud storage until systems are

updated.

3.1 If cloud backup fails, then technician will back up the files to external hard drive.

4.1 If update fails, then temporary system will be setup and ran once issue is solved.

5.1 If application fails to start then it is reinstalled and retested.


2. Order Items

Use Case Name: Order Items

Scenario Creates new order online

Triggering Event: Customer adds an item to cart on the website.

Brief Description: Customer adds item to cart, the website stores it in customer cart list, then customer checks out, a

list of the items is made and website requests customer information’s, customer inputs it and website verifies it then requests the payment information, once payment is successful, a receipt is

displayed for the customer and saved in the company systems.

Actors: Customer

Related Use Cases: Includes: Compose invoices, ship items.

Stakeholders: Sales department: to make sure products are updated on the websites

Shipping department: to ensure items are shipped to correct address

Preconditions Customer must exist.

Products and Inventory must exist for requested products.

Post-conditions: Order list must be created

Order transaction must be created to very payment

Stock level must be updated on the website to notify customer if product is in stock or not.


1. Customer browses through the

website and adds items to cart

2. Shopping cart list is updated

every time a product is added

by the customer.

3. Customer checks out

4. Customer inputs the

information and proceeds.

5. Customer inputs the payment

information

6. Customer reviews the final

order list and total amount and

submits the order.

7. Once payment is successful, a

receipt is printed out for the

customer.

1.1 Servers are running and communicating with

customer computer to display the website contents.

2.1 Website is refreshed by the servers.

3.1 Servers receive the final cart list and send it to the

customer computer.

6.1 Servers communicates with customer’s bank account to withdraw the money

7.1 Servers notify the customer computer that payment

is successful and displays a receipt on their computer.

Exception

Conditions:

5.1 If information is invalid, it will ask the customer to input valid information.

7.1 If payment information is not valid then it would ask customer to input valid payment

information.

9.1 In case receipt is not shown, another copy will be sent to the customer email.


3. Compose Invoices

Use Case Name: Compose Invoices

Scenario Create new invoices of each order

Triggering Event: Once a customer places an order, this event is triggered.

Brief Description: Customer places an order through the website, the owner composes the invoice using

QuickBooks once he receives the final information from the order details created by the website.

Actors: Owner

Related Use Cases: Includes: Order Items

Stakeholders: Shipping department: they receive the invoice and ships the product

Preconditions Customers must exist.

Orders must exist.

Post-conditions: Website must be running perfectly on the right speed.

Servers should be updated.

Inventory level must be updated and kept track of.


1. Owner prints the order details created by

the website.

2. Owner opens the software QuickBooks

and enters the order information.

3. Once all information is in the software,

Owner reviews the order details and

make sure everything is copied correctly.

4. Owner makes final notes on the

QuickBooks to thank the customer for

shopping and to keep in touch.

5. Owner prints out the invoice

6. Owner sends the invoice to shipping

department.

7. Owner sends the invoice to the customer

as well.

1.1 Servers send the customer order details to

the printer

3.1 Information is stored to the cloud storage.

5.1 Computer system sends the invoice to the

printer to be printed.

6.1 Invoice is forwarded to shipping

department via Internet.

Exception

Conditions:

1.1 In case order details don’t print, owner can manually copy it from the website to the software

2.1 If software doesn’t run, then owner will call IT support or write out the invoice manually.

5.1 If invoice doesn’t print out properly, owner has to call IT department or write it on paper.

6.1 If invoice fails to send, then it will be delivered manually.


4. Ship Items

Use Case Name: Ship Items

Scenario Products ship to customers

Triggering Event: Once a verified invoice is received by Owner, product will be shipped

Brief Description: Order is placed by the customer, then invoice is composed by owner and then sent to the shipping

department, one of the employees processes the invoice and ships the product to the customer.

Actors: Shipping & Receiving manager , Customer

Related Use Cases: Includes: Compose invoices.

Stakeholders: Shipping departments: to verify the invoice information and process it.

Inventory department: to update the inventory levels as it decreases/increases.

Preconditions Customer must exist.

Invoice must exist to ship.

Post conditions: Owner must have each invoice ready to send to shipping department.

Order details must be verified by the owner.


1. Shipping manager receives the invoice

from owner or receives a package from

customer in case of refunds or

replacement.

2. Shipping manager reads and verifies the

invoice.

3. Shipping manager prepares the product

and package it.

4. Shipping manager prints out the shipping

label and apply it on the package.

5. Shipping manager checks the package

one more time to avoid any mistakes.

6. Shipping manager sends out the package

to the customer with automated tracking

number.

1.1 System will have it accessible for the

shipping manager once the owner uploads it.

4.1 The system automatically prepares a

formatted label to be applied on the package

6.1 Computer automatically creates a tracking

number and applies it to the shipping invoice

so customers can keep track of it.

Exception

Conditions:

2.1 If invoice is invalid or has a type, Manager will send it back to the Owner to fix the mistake.

5.1 If there are any issues, then Manager will redo the work.

6.1 If tracking number is not working then Manager will use the computer to create another one.



The diagram shows the relationship between different entities and it represents the attributes of

objects.

Association Relationship:

1. Customer-Web services: customer uses web services, 0 to many multiplicity on

both side.

2. Account-Payment: account used for payments, Account can have 0 to many

payment where else a single payment is associated with one account

3. Order-Payment: order used for payments. An order can have many payment

where else a single payment is associated to one order

4. Employee-Inventory System Check: employee uses Inventory System Check.

employee can check only one Inventory system where else a system can be

checked by 1 or many employees

5. Inventory System Check-Inventory: Inventory System Check uses Inventory.

Both have only 1 multiplicity

6. Order-Inventory: order uses Inventory for an item. An inventory can have 0 or 1

order where else order uses one inventory

Composition Relationship:

1. Customer-Account: customer has an account: account has one customer and

customer can only use one account

2. Account-Order: account has an order. Account can have many orders where else

one order is associated with one account only.


3. Account-Shipping cart: account has a cart. Both have only 1 multiplicity

4. Shipping cart-Product: shipping cart has product. A cart can have 1 or many

products where else product has only one cart

Figure 3



Recommendations

The proposed changes for the new system will help the client to understand who does what work.

Also, the data flow and roles played by each person will make the system manageable.

The client is recommended to adopt these changes to as to increase revenue and better

understanding of each person’s role.

The next steps could be:

Increase in profit margins

Reduction in costs

Improvement in customer service

Fast delivery of the ordered items


Group Member name

(printed)

Deliverable section(s)

completed

Member Signature

Sameed Ahmed Baqai Domain Class diagram

Alin Kakooz Intermediate Use Case

narrative

Simran Kaur Documentation

(Introduction, Executive

Summary, Cover page,

Table of Contents), Context

diagram, Recommendation

Syed Zaidi Use case diagram

Documents

SAD_del3