CMGT/445: CASE STUDY: APPLIANCE WAREHOUSE – Application Implementation
Assignment Content
- Continue your work to support the development and implementation of the new Service Department for Appliance Warehouse.
Directions
In MindTap, review the Appliance Warehouse Case, and do the following:Read the Before You Begin Message and the Module 11 Appliance Warehouse Webmail Client Emails. Read the messages to help determine the tasks you must complete.
Review and analyze the weekly Appliance Warehouse case study content and resources.
Create a 2- to 3-page document (to submit in Blackboard) to support the Appliance Warehouse Service Plan that includes the following:
Testing Plan: Create a testing plan to manage the systems through QA standards. Include a testing plan for each part of the new service you’ve identified, such as, scheduling, invoicing, and reporting. For each part identified, include in your testing plan an action to be tested, along with an expected outcome.
Implementation Plan: Indicate whether you will use parallel, direct, phased, or pilot changeover strategies. Explain your reasoning. For Implementation recommendations, refer to section 11.9, “Installation,” in Ch. 11 of Systems Analysis and Design.
Training Plan: Indicate what a training plan would include for affected employees, such as appointment setters, technicians, management, and the parts department. Include a plan for all employees (or specific departments) affected by the new system implementation.
Submit your document.
urgentDue soonMindtap
Template Library/form_01_request-for-information-services.rtf
REQUEST FOR INFORMATION SERVICES
Date:
System enhancement:
Title:
Department:
Location:
New system:
E-mail:
REQUEST FOR:
URGENCY:
[ ] Correction of system error
[ ] Immediate attention required
[ ] System enhancement
[ ] Handle in normal priority sequence
[ ] New system
[ ] Defer until new system is developed
DESCRIPTION OF REQUESTED SYSTEMS SERVICES:
(ATTACH ADDITIONAL DOCUMENTS AS NECESSARY)
(To be completed by the Information Technology Department)
[ ] Approved
Assigned to IT contact person:
User:
Urgency code (1 low to 5 high):
[ ] Modified (see attached notes)
[ ] Rejected (see attached notes)
Date:
Action:
Template Library/form_02_preliminary-investigation-report.rtf
Note:
In MS Word 2010,
Click
Review – Restrict Editing – Stop Protection
and remove all highlighted material after completing the form
PRELIMINARY INVESTIGATION REPORT
Subject:
Date:
INTRODUCTION
[Provide a brief description of the system, the name of the person or group who performed the investigation, and the name of the person or group who initiated the investigation.]
SYSTEMS REQUEST SUMMARY
[Explain the basis of the systems request, including an explanation of major problems or opportunities mentioned in the request.]
PRELIMINARY INVESTIGATION FINDINGS
[Describe the results of the investigation, including the scope of the proposed project and the conclusions that were reached. Mention all significant findings, including the results of interviews and other fact-finding, and provide an estimate of current costs.]
RECOMMENDATIONS
[Present a specific recommendation for further action.]
TIME AND COST ESTIMATES
[Include an estimate of time and expenses necessary for additional IT department work. This should be quite specific for the next phase and should include a timetable and cost estimate for the entire project.]
EXPECTED BENEFITS
[Explain all tangible benefits, with specific dollar estimates, using a range if appropriate. Also mention any intangible benefits.]
Template Library/form_03_system-requirements-document.rtf
SYSTEM REQUIREMENTS DOCUMENT
·
Introduction
·
Summary
·
Findings
·
Recommendations
·
Time and Cost Estimates
·
Expected Benefits
·
Appendix
Template Library/form_04_system-design-specification.rtf
SYSTEM DESIGN SPECIFICATION
Management Summary
Template Library/form_05_systems-requirements-change-request.rtf
SYSTEM REQUIREMENTS CHANGE REQUEST
PRINT THE FOLLOWING INFORMATION:
NAME
DEPARTMENT
JOB TITLE
DESCRIPTION OF CHANGE:
REASON FOR CHANGE:
ATTACH ADDITIONAL INFORMATION AND DOCUMENTS AS NEEDED:
CHECK THIS BOX IF ATTACHMENTS ARE INCLUDED:
SIGNED _________________________________________________________ DATE __________________________
CONTROL NUMBER
DATE RECEIVED
TO BE COMPLETED BY THE PROJECT COORDINATOR:
IMPACT ANALYSIS:
Include an estimate of resources needed, with specific costs and timetables.
ACTION:
ACCEPT
DEFER UNTIL (DATE)
REJECT FOR THE FOLLOWING REASONS:
SIGNED ___________________________________________________________ DATE _____________________
Template Library/form_06_interview-documentation.rtf
INTERVIEW DOCUMENTATION
Name of System: Page
Date:
Prepared by:
Title:
Purpose:
Location:
Template Library/form_07_report-analysis.rtf
SYSTEM DOCUMENTATION
NAME OF SYSTEM
DATE
PAGE
of
ANALYST
PURPOSE OF DOCUMENTATION
FIELD
FIELD TYPE
FIELD LENGTH
Template Library/form_08_data-element-description.rtf
DATA DICTIONARY
DATA ELEMENT DESCRIPTION
SYSTEM
DATA ELEMENT
NAME
LABEL
ALTERNATE NAMES
TYPE AND LENGTH
OUTPUT FORMAT
DEFAULT VALUE
ACCEPTABLE VALUES
PROMPT/COLUMN HEADER
SOURCE
SECURITY
RESPONSIBLE USER
DERIVATION FORMULA
DESCRIPTION AND COMMENTS
Template Library/form_09_data-flow-description.rtf
DATA DICTIONARY
DATA FLOW DESCRIPTION
ID NAME
ALIAS
DESCRIPTION
ORIGIN DESTINATION
RECORD
VOLUME AND FREQUENCY
COMMENTS
Template Library/form_10_process-description.rtf
DATA DICTIONARY
PROCESS DESCRIPTION
SYSTEM
PROCESS
NAME
PROCESS
ID
INPUT DATA FLOWS
OUTPUT DATA FLOWS
PROCESS DESCRIPTION
Template Library/form_11_record-description.rtf
DATA DICTIONARY
RECORD DESCRIPTION
SYSTEM
RECORD
ID
RECORD
NAME
ALTERNATE NAMES
DEFINITION
RECORD DATA ELEMENTS
Template Library/form_12_data-store-description.rtf
DATA DICTIONARY
DATA STORE DESCRIPTION
LABEL
ENTRY TYPE
DESCRIPTION
ALIAS
COMPOSITION (ATTRIBUTES)
NOTES
LONG NAME
Template Library/form_13_external-entity-description.rtf
DATA DICTIONARY
EXTERNAL ENTITY DESCRIPTION
LABEL
ENTRY TYPE
DESCRIPTION
ALIAS
VALUES & MEANINGS
NOTES
LONG NAME
Template Library/form_14_program-documentation.rtf
SYSTEM DOCUMENTATION
NAME OF SYSTEM
DATE
PAGE
of
ANALYST
PURPOSE OF DOCUMENTATION
PROGRAM IDENTIFICATION
PURPOSE
FILES
– DATABASES – CLOUD REQUIREMENTS
WEB
PROCESSING REQUIREMENTS
AND RESOURCES
Template Library/form_15_npv_template.xls
NPV Template
Net Present Value (NPV) Template
Note:
Cells B12:H12 and B16:H16 contain formulas to multiply discount factors * benefit and cost values
Cells I12 and I16 contain adjusted cost and benefit totals
Cell C18 contains the calculation for net present value (NPV)
Year Year Year Year Year Year Year Total
0 1 2 3 4 5 6
Benefits
Factor
PV of Benefits – 0 – 0 – 0 – 0 – 0 – 0 – 0 – 0
Costs
Factor
PV of Costs – 0 – 0 – 0 – 0 – 0 – 0 – 0 – 0
Net Present Value: – 0
The formula in cell C18 will calculate NPV when values are entered in cells B10:H11 and B14:H15
Sheet2
Sheet3
Template Library/form_16_system-security-checklist.rtf
SYSTEM SECURITY CHECKLIST
·
Overview of
System S
ecurity
I
ssues and
C
oncerns
·
Analysis of Physical Security
·
Analysis of Network Security
·
Analysis of Application Security
·
Analysis of File Security
·
Analysis of User Security
·
Analysis of Cloud vulnerability, if any
·
Additional Comments and Recommendations
Template Library/form_17_payback-analysis-template.xls
Payback Analysis Template
Payback Analysis Template
Note: Cells C8:C14 and E8:E14 contain formulas to accumulate costs and benefits
Year Costs Cumulative Benefits Cumulative
Costs Benefits
0 – 0 – 0
1 – 0 – 0
2 – 0 – 0
3 – 0 – 0
4 – 0 – 0
5 – 0 – 0
6 – 0 – 0
Sheet2
Sheet3
Template Library/form_18_roi-template.xls
ROI Template
Return on Investment (ROI) Template
Note: Cells C8:C14 and E8:E14 contain formulas to accumulate costs and benefits
Cell C17 contains formula to calculate ROI
Year Costs Cumulative Benefits Cumulative
Costs Benefits
0 – 0 – 0
1 – 0 – 0
2 – 0 – 0
3 – 0 – 0
4 – 0 – 0
5 – 0 – 0
6 – 0 – 0
– 0 – 0
ROI: 0.0%
The formula in cell C17 will calculate ROI when values are entered in cells B8:B14 and D8:D14
Sheet2
Sheet3
Template Library/form_19_npv-template.xls
NPV Template
Net Present Value (NPV) Template
Note:
Cells B12:H12 and B16:H16 contain formulas to multiply discount factors * benefit and cost values
Cells I12 and I16 contain adjusted cost and benefit totals
Cell C18 contains the calculation for net present value (NPV)
Year Year Year Year Year Year Year Total
0 1 2 3 4 5 6
Benefits
Factor
PV of Benefits – 0 – 0 – 0 – 0 – 0 – 0 – 0 – 0
Costs
Factor
PV of Costs – 0 – 0 – 0 – 0 – 0 – 0 – 0 – 0
Net Present Value: – 0
The formula in cell C18 will calculate NPV when values are entered in cells B10:H11 and B14:H15
Sheet2
Sheet3
Resource Library/build-costs-and-durations.xlsx
Sheet1
Costs for in-house development Standard Development Times
As standard practice, use these costs for all in-house development. As standard practice, use these guidelines (assume 8 hours of work per day).
Cost per hour (for first year) Duration
Database Development $ 60 Database design 5 days
Web developers $ 75 Database build 10 days
App developers $ 75 Design of a report (web or app) 2 days
UX designers $ 60 Design of data entry page (web or app) 2 days
Business Analyst $ 50 Design of static text page (web or app) 1 day
Trainers $ 50 Build of a report (web or app) 1 day
Cybersecurity specialists $ 90 Build of data entry page (web or app) 1 day
System Admin $ 70 Build of static text page (web or app) 1 day
Connection to separate system or database (sys admin) 8 days
Analysis work (both web and app combined) 20 days
Training 5 days
Equipment: Cybersecurity work 10 days
Servers $ 2,500
Routers $ 200
Expected Monthly Maintenance:
Development (web or app) 2 days
System Admin 3 days
Training 1 day
Key:
Web or app = activity must be done for both web and app. Same amount of time required for each deliverable.
Both web and app = time given includes development for both of the web and app deliverables.
Resource Library/historical-analysis-phase-durations.xlsx
Sheet1
Analysis and Design task durations
Project name Year Task name Duration
Accounts Payable 2018
Interview process 5 days
Development of User Questionnaire 2 days
Identification of risks 1.5 days
DFD diagram 4 days
UML diagram 4 days
Layout of 1 report 4 hours
Layout of 1 user screen 2 hours
Testing plan 5 days
Implementation plan 3 days
Human Resources 2017
Interview process 4 days
Development of User Questionnaire 2 days
Identification of risks 1 day
DFD diagram 3.5 days
UML diagram 2 days
Layout of 1 report 2 hours
Layout of 1 user screen 4 hours
Testing plan 7 days
Implementation plan 3 days
Payroll 2019
Interview process 6 days
Development of User Questionnaire 1 day
Identification of risks 2 days
DFD diagram 4.5 days
UML diagram 5 days
Layout of 1 report 1 day
Layout of 1 user screen 4 hours
Testing plan 5 days
Implementation plan 3.5 days
Resource Library/jad-session x
JAD session excerpts
Alan Marks (store mgr): I am so excited to be launching this new service to our customers! It’s going to be great to not have to refer out customers to unknown service companies. Besides, if they can’t fix their own appliance, we might be able to convince them to visit the store to replace it.
Emily Johns (service manager): Yes, I agree! We need to work very closely with the parts department in order to get the service estimates out to the customer and get the parts for the repair quickly.
Meredith Parks (programmer): I think it would be a good idea to name our new service system. Any ideas?
Alan Marks (store mgr): Service Information System? SIS?
Emily Johns (service manager): Service Information Manager? SIM?
Meredith Parks (programmer): OK, let’s vote.
Meredith conducts a quick vote and all are agreed on SIM.
Maddox Farley (parts director): I’m a little worried about how this SIM will affect my inventory levels.
Meredith Parks (programmer): I need you to break this down a bit for me. Who is involved in this new process?
Emily Johns (service manager): We definitely have the customers, parts department, parts, technicians, appointment setters, and calendar.
Meredith Parks (programmer): OK, now we have our entities. What are the processes that will take place?
Alan Marks (store mgr): Well, we will need to generate estimates and final invoices.
Emily Johns (service manager): Right. And we’ll make appointments, order parts, assign technicians to appointments.
Meredith Parks (programmer): Anything else?
Emily Johns (service manager): A calendar should be able to be viewed or printed for each technician. Each technician needs their daily schedule of appointments at the beginning of each day.
Alan Marks (store mgr): I don’t think so. Payment will be accepted by the current cashier’s system.
Meredith Parks (programmer): OK.
Resource Library/organizational-staffing x
Appliance Warehouse staffing
Parts Department – purchasing, inventory control, sales
· Director: Maddox Farley
· Sales staff: Tyler Cummings, Steve Dawson, Amelia Warner
· Purchasing: Celia Martel, Joe Perez
· Inventory/warehouse: Ben Cooke, Melissa Benedict, Matt Jones
Appliance Sales – sales of new appliances in 4 departments
· Director: Sonia Lopez
· Large Kitchen Appliance department: Mike Nelson (manager), Jessica Scott, Rachel Evans, Justin Cooper
· Laundry Appliance department: Tina Turner (manager), Mackenzie Scott, James Wright
· Audio/Visual department: Samantha Campbell (manager), Tim Reynolds, Tracey Oliver
· Small Appliance department: Peter Parker (manager), Ken Howell, Marti Castillo
Service Department
· Service Manager: Emily Johns
· Technicians: Liam Henson, Mark Robles, Lee Wong
· Appointment setters: Lisa Shields, Jake Meyers
· Equipment and parts: Rhonda Patel
Storewide Cashiers:
· Manager: Abby Franklin
· Cashiers: Nancy Richards, Joy Vasquez, David Goodman, Paul Patton, Maria Nunez
Administrative roles:
· Owner (store manager reports to this role): Mae Roth
· Store Manager (all department heads and assistant manager report to this role): Alan Marks
· Store Assistant Manager (admin roles report to this assistant manager): Ali Miranda
· Admin Assistant to store manager: Tim Stafford
· Human Resources specialist: Joey Booker
· Accounting, payroll, accounts payable/receivable: Doug Dorsey, Tia Carey
· IT department: Carlie Davis (manager), Tony Barlett, Meredith Parks, you
Resource Library/results x
Questionnaire results
Results are ordered by importance. The top result (#1) is the most important to that group.
Most common features requested by appointment setters:
1. Reminder services calls/messages
2. See technician’s availability
3. Determination of discounts for customers
4. See availability of parts to schedule repair
5. View service history
Most common features requested by technicians:
1. Able to view own calendar
2. See availability of parts to schedule repair
3. Keep notes for each customer
4. Mobile access of scheduling
5. View service history
6. Reminder services calls/messages
Most common features requested by parts department:
1. Can pull inventory requests every two hours.
2. Database of requested parts.
Most common features requested by management:
1. Reporting by time period, type of appliance, brand
2. Determination of discounts for customers
3. Mobile access of scheduling
4. Routing and mapping of technician’s driving to appointments
5. See technician’s availability
6. Suggest preventative maintenance to customers
Resource Library/service-records-sample x
Service Records Sample
Date Called
Date of Service
Appliance type
Appliance serial number
Parts Needed
Technician assigned
Customer Name
Customer Address
Customer Phone
1/6
1/6
Refrigerator
KN-78-215-896
KN-1256
Robles
Sophie Goldberg
123 Main St, Hopkinton, MA
508-555-1256
1/6
1/7
Dishwasher
WP-55-311-698
WP-1788
Wong
Mitch Chu
5525 Winter Rd, Medford, MA
617-555-9898
1/7
1/7
Refrigerator
WP-78-956-694
WP-8877
Henson
Jamie Fernandez
2 Hope St, Hull, MA
617-555-4125
1/8
1/10
Microwave
AB-99-357-753
AB-3321
Wong
Mike Singh
15 Arch St, Tewksbury, MA
508-555-3596
1/9
1/9
Washing machine
GE-10-122-542
GE-2119
Robles
George Kostanza
369 Pike Circle, Danvers, MA
508-555-6235
1/9
1/10
Dishwasher
KN-55-396-477
KN-5511
Robles
Felicia Parkinson
50 Central Ave, Hopedale, MA
508-555-2144
CompanyWebsite/CompanyWebsite1
CompanyWebsite/CompanyWebsite2
CompanyWebsite/CompanyWebsite3
CompanyWebsite/CompanyWebsite4
Case study: appliance
warehouse application design
This presentation uses a free template provided by FPPT.com
www.free-power-point-templates.com
Service department software design
As a business analyst, I have gone through different service based business applications and evaluate the future adoption impacts of implementing SaaS or in-house customized software in appliance warehouse.
As far as adoption of SaaS OR in-house customized software implementation in appliance warehouse information system is concerned, we have to figure out some facts about both approaches.
This presentation uses a free template provided by FPPT.com
www.free-power-point-templates.com
brief Introduction
2
Pros of SaaS in appliance warehouse information system
Saved maintenance cost for different interfaces screens and design
Comfortability in deployment
Accessibility
Scalability
This presentation uses a free template provided by FPPT.com
www.free-power-point-templates.com
Saved maintenance cost: as a third party, saas would save the maintenance cost, bugs and error removal cost during the usage of system.
Comfortability in deployment : the employees only have to get the system and initial access. They don’t have to waste time in its deployment. Until end of subscription, any employee according to status can access and use the system.
Accessibility: all employees and users need a good internet connection and browser to access the system. This is generally available on a wide range of devices and from anywhere in the world
Scalability: the company can change or adopt new subscription offers according to their needs.
3
Cons of SaaS for Appliance warehouse
Security issues related to accessing system through interfaces.
Performance issues of screens and whole system.
Lack of control
Connectivity problems
This presentation uses a free template provided by FPPT.com
www.free-power-point-templates.com
Security : access management and the privacy of sensitive information is a major consideration around cloud and hosted services.
Connectivity problems : SaaS model is based on web delivery, if user’s internet service fails, they will lose access to software or data
Lack of control : the system is controlled by third party which is not good approach for the service department.
Performance : the performance can be reduced such as latency rate, speed and reliability by third party control.
4
Pros of in house-customized software
High level of customization in the whole design
Easy and comfortable interface
Full control by company and its management.
access to knowledgeable support
This presentation uses a free template provided by FPPT.com
www.free-power-point-templates.com
High level of customization in the whole design : as our proposed system is highly customized and need a customized solution so in house can give us more oprtions to get the system according to our needs.
Easy and comfortable interface : as the developers know about everyone going to use system so they will develop interface according to their user.
Full control by company and its management: as they have developed by their won developers so it is very easy for management to manage it.
access to knowledgeable support: in case of any technical error, team can help to remove it and provide full support.
5
Cons of using in-house customized software
Bugs and glitches
Lack of scalability
Maintenance issues
Cost issues
This presentation uses a free template provided by FPPT.com
www.free-power-point-templates.com
Bugs and glitches : in case of poor development by developers, chances of errors are high.
Lack of scalability : low level of subscription options.
Maintenance issues : it is hard to upgrade it
Cost issues : company have to invest more for developing whole system.
6
Recommended in-house and reasoning of choosing it
I would highly recommend to choose in-house customized software because
The warehouse needs a highly customized design and system so designer and developers can make each screen and design according to their users.
Comfortable interface can be developed so that all the users, employees and managers learn to use the system.
The system has to schedule services and have to generate reports, knowledgeable experts can provide support in case of any technical issue in system.
This presentation uses a free template provided by FPPT.com
www.free-power-point-templates.com
Reasoning
7
Software requirements
Data management
Budget management
Cost management
Service notifications
Service orders
Provide details about Resources used
Billing document
Shared database
Application management
Report generation
This presentation uses a free template provided by FPPT.com
www.free-power-point-templates.com
These are some requirements that software will do to support the service department.
8
Communication plan
This presentation uses a free template provided by FPPT.com
www.free-power-point-templates.com
Communication plan
Form of communication Frequency Method Audience Millstones
Stakeholder meeting Weekly Meeting All project stakeholders Current and future progress of project
Stakeholder update Monthly Email news tellers All project stakeholders Discussion of recent progress
Management team meeting 2 times in a week Meeting Management Report status, risks, and solution for each design interface
Status reports Weekly Report All stakeholders Issues and risk
Millstones review Weekly Meeting for demonstration of deliverables Stakeholders Take feedback, status review
This presentation uses a free template provided by FPPT.com
www.free-power-point-templates.com
A complete communication plan is provided in tabular form
10
Webmail Client Emails/Email1
Webmail Client Emails/Email2
Webmail Client Emails/Email3