South University
file:///C|/Users/CWATKIM/Desktop/Understanding%20the%20Performance%20Management%20Process.html[7/22/2020 11:24:56 AM]
Understanding the Performance Management Process You are a new HR Manager for a company with 250 employees. During your third week of employment, you have discovered that none of the employees have job descriptions. Some employees have worked for the company over five years. Employees have been classified as exempt when, in fact, they are nonexempt employees according to the Fair Labor Standards Act (FLSA). In addition, the company has never established a performance management process. Employee morale is low, employees are not performing at an optimal level, and employee reviews have not been conducted for two years. What are the necessary steps to take in order to get the organization on track?
First, you must have a clear understanding of the organization’s mission and strategic goals and then create a list of jobs. Without a list of jobs, it will be virtually impossible to begin the process. There are multiple steps in understanding the performance management process:
1. Know the mission and strategic goals of the company.
2. Conduct a job analysis.
3. Write job descriptions.
4. Implement a well-designed performance management process.
5. Determine when performance appraisals will be conducted and how coaching feedback will be given.
6. Define the type of employee behavior required to attain the desired outcome.
7. Establish a set of new goals to attain and set benchmarks.
The scenario suggested above actually happened. After three weeks of employment in her first role as an HR Manager, this manager found the organization to be in total disarray. Prior to her onboarding, an employee had filed a grievance since he was classified as exempt when he was actually a nonexempt employee. Employees were disgruntled because they had not received a raise in over two years. The company did not have a clear idea of the mission or strategic goals. When the performance management process was clearly defined and linked to the strategic goals of the organization, employee morale lifted.
Benefits of the FLSA Employers are required to follow the guidelines established by the FLSA to ensure employees are properly compensated for the work performed.
Review the tabs to study the benefits of the FLSA through the given case studies.
Case Study 1
Case Study 2
South University
file:///C|/Users/CWATKIM/Desktop/Understanding%20the%20Performance%20Management%20Process.html[7/22/2020 11:24:56 AM]
The manager of your fast-food restaurant has advised all employees to clock out after their eight-hour shift; however, the manager insists that the employees cannot leave until the restaurant is cleaned and ready for the morning crew. The manager has been trying to remain within the monthly budget. A disgruntled employee filed a claim since she has not received overtime pay. The franchise is now facing a class action lawsuit.
Locate a court case to understand the repercussions for an employer failing to adhere to the FLSA.
What are some other options the manager could have used to remain within the monthly budget?
What are five critical areas that you have discovered from reading the court case you selected?
How can you apply this knowledge to your current or future organization?
Additional Materials
From your course textbook, Performance Management, read the following chapter:
Performance Management Process
From the South University Online Library, read the following article:
10 Performance Management Process Gaps
- Local Disk
- South University
Service Department Software Design
Joseph Kamishlian
22 July 2020
User Interface
Link with parts department
Recording of appliances brought for servicing
Status of appliances
Link with finance department for billing
Link with Sales department
Communication with Customers
Report generation
Service Department Software Design
Service Based Applications that can be used for the Service Department
There are two main service based applications that can be used for the department
SaaS (software as a service)
SaaS is an on-demand third party software where the organization pays to access the services it desires.
2. In-house customized software
A software specifically designed by the organization to meet its needs. The organization has to maintain the software
There are two main service based applications that can be used for the department.
The first is SaaS which is an on-demand third party software where the organization pays to access the services it desires. The organization will not have ownership of the software. They will rent out the software designed and maintained by a third party. The organization will have to pay monthly or annual payments to have access to the software.
The second type of service based application is an in-house customized software. The software is specifically designed by the organization to meet its needs. The organization has to maintain the software to ensure that it serves them
3
Advantages of SaaS
SaaS has five main advantages
Has easy accessibility
Has easy upgrades
Low up-front costs
Can be easily set up and deployed (Souri, Asghari & Rezaei, 2017).
Supports scalability
SaaS has five main advantages.
The first advantage is that it can be easily accessed. All that is needed is a computer connected to the internet and that has a browser.
The second advantage is that SaaS providers deal with hardware and software updates, deploying upgrades centrally to the hosted applications and removing this workload and responsibility from you.
SaaS is generally subscription-based and has no up-front licence fees resulting in lower initial costs. The SaaS provider manages the IT infrastructure that is running the software, which brings down fees for hardware and software maintenance.
SaaS application is already installed and configured in the cloud. This minimizes common delays resulting from often lengthy traditional software deployment.
Lastly, SaaS providers generally offer many subscription options and flexibility to change subscriptions as and when needed, egg when your business grows, or more users need to access the service.
4
Disadvantages of SaaS
There are four main disadvantages of SaaS
There is a limit on the range of applications and their services
There are many security and data concerns in the use of SaaS
There is lack of control (Nowrin & Khanam, 2019)
It is dependent on the internet
There are four main disadvantages of SaaS
The first disadvantage is that there is a limit on the range of applications and their services.
The second disadvantage is that there are many security and data concerns in the use of SaaS. The organization has to consider whether it is willing to share its data and security protocols to a third party
The third disadvantage is that there is lack of control. in-house software application gives businesses a higher degree of control than hosted solutions where control resides with a third party. Typically everyone has to use the latest version of the software application and cannot defer upgrades or changes in the features.
Lastly, SaaS is dependent on the internet. Since the SaaS model is based on web delivery, if the internet service fails, the organization will lose access to its software or data
5
Advantages of In-house customized software
There are four main advantages of the in-house customized software
Tailor-made solution
Return on investment
Offers high security (Wiesbaden, 2016).
There is improved software support
There are four main advantages of the in-house customized software.
The first advantage is that the software can be tailor made to meet the exact needs of the organization.
The second advantage is that it has a high return on investment in the long run as there are no monthly or annual subscription payments
The third advantage is that it supports high security. The organization can better secure its data and processes as it does not deal with third parties
Lastly, since the software is in-house customized, in case of an issue or a challenge, the issue can be sorted fast.
6
Disadvantage of in-house customized software
There are four main disadvantages of in-house customized software
It is a high cost investment.
It is time involving.
Needs additional technical expertise.
Possible challenges in support and documentation.
There are four main disadvantages of in-house customized software.
The first disadvantage is that it is a high cost investment. The organization will spend money on getting an analyst, a developer and a project team
Secondly, developing a software is time involving as the developers have to go through the software development lifecycle.
Thirdly, developing and maintaining customized software needs additional technical expertise.
Lastly, there are possible challenges in support and documentation.
7
Recommendation
I would recommend the use of the in-house customized software based on three reasons
The solution can be tailor-made to meet the needs of the organization
The solution offers advanced security features
The solution is high return investment (Brambilla, Cabot & Wimmer, 2017).
I would recommend the use of the in-house customized software based on three reasons.
The solution can be tailor-made to meet the needs of the organization. Secondly the solution offers advanced security features.
Lastly the solution is a high return investment
8
Requirements the software must do to support the Services Department.
The software must be compatible with the other software used by the parts department.
The software must allow recording of appliances to be repaired.
Employees in the department must be able to indicate the status of appliances brought for services.
Employees must be able to communicate with customers on the status of their products.
The software must be linked to the finance unit of the organization for billing.
The software must be linked with the sales department to confirm if an appliance brought for service has a warrant or not.
The software must support report generation to enable the department identify the repairs that they do the most
There are seven requirements the software must do to support the service department
The software must be compatible with the other software used by the parts department.
The software must allow recording of appliances to be repaired.
Employees in the department must be able to indicate the status of appliances brought for services.
Employees must be able to communicate with customers on the status of their products.
The software must be linked to the finance unit of the organization for billing.
The software must be linked with the sales department to confirm if an appliance brought for service has a warrant or not.
The software must support report generation to enable the department identify the repairs that they do the most
9
Communication Plan on the project process
The project manager will communicate after every two days, weekly, fortnightly and monthly
The service department manager/IT manager- every two days via status reports
Operations manager-Weekly
Executive Management of the organization-Fortnightly via email
The board of directors- Monthly via the organization’s monthly meeting
The project manager will communicate after every two days, weekly, fortnightly and monthly
The service department manager/IT manager- every two days via status reports
Operations manager-Weekly
Executive Management of the organization-Fortnightly via email
The board of directors- Monthly via the organization’s monthly meeting
10
References
Souri, A., Asghari, P., & Rezaei, R. (2017). Software as a service based CRM providers in the cloud computing: challenges and technical issues. Journal of Service Science Research, 9(2), 219-237.
Wiesbaden, S. F. (2016). Developing our own software and IT expertise gives us an advantage. ATZ worldwide, 118(4), 22-25.
Brambilla, M., Cabot, J., & Wimmer, M. (2017). Model-driven software engineering in practice. Synthesis lectures on software engineering, 3(1), 1-207.
Nowrin, I. N., & Khanam, F. K. (2019, May). Importance of Cloud Deployment Model and Security Issues of Software as a Service (SaaS) for Cloud Computing. In 2019 International Conference on Applied Machine Learning (ICAML) (pp. 183-186). IEEE.
Orange- customer facing areas.
Strengths – wider customer base, all in one shop, customer has ability to purchase new if cost is comparable, customer can shop while waiting resulting in more revenue,
Weaknesses – increase in warehouse space, specialty competitors, other department funding cut until new department becomes profitable,
Opportunities – increase revenue, larger footprint, ability to handle small jobs quicker and more effective than small chains, customer return increase
Threats – potential for increased damages, specialty competitors, negative customer reviews results in decrease revenue in other departments
New Company quote: Your one stop home shop
Verify login details Enter login details View the appliance number Compare in accounts database Check the number of services done to the appliance If less than 3; service for free If it’s a new customer; pay the full service If more than 3 times pay 20% of service fee Service the appliance Details okay Login details Login details Load user account Number of services Send message; less than 3 More than 3 times Service message display Service message display Service message display New customer to pay full amount Structure chart for application warehouse
SYSTEM DESIGN SPECIFICATION
Management Summary
Need to interview and see initial mock up of 3 major sofware designers. One of which is scheduled for Jun 25 2020 with SAP.
System Components Details
Program Design
We will need atlease a 3 level GUI interface. 1 for tech and schedulers, 1 for management. and one with back end access for IT analyist.
User Interface Design
Maintain a check box system with automated calendar access as well as comment box for technician and schedulers. Management will need to be able to see calls made, duration of ticket times, as well as any notes made and deleted. IT will need full access to give permissions to all 3 levels.
Output and Input Design
output will need to have access for dialoge box to send information from individual tech to groups and to HQ/management.
File and Database Design
will need to have at a min. of 3gb per file to allow for notes and photos as well as initial ticket and tech information
Support Processing Design
photos will be needed and accessable
Environmental Requirements
color, 3gb per, ability to be cross platform, user signin and out ability, tracking software, direct and group function as well.
Implementation Requirements
Token key will ensure company information is secure, mobile devices will need to be tracked, computers and mobile devices will need to be constantly monitored
Time and Cost Estimates
151 days and database 60/hr
web dev. if needed 75/hr
app dev 75/hr for 3 days
ux des 60/hr
business analyst 50/hr
trainers 50/hr
cybersecirty spec 90/hr
system admin 70/hr
Appendices (as needed)
avg 75/hr
SYSTEM SECURITY CHECKLIST
· Overview of System S ecurity I ssues and C oncerns
phone system breakdown, company device for tech, theft from work trucks, damages caused by tech, black time(downtime of techs),
· Analysis of Physical Security
work vehicles will have trackers,
· Analysis of Network Security
all onsite techs and schedulers will have wired connections instead of a wifi setup, Managers will have token key access to wifi only when using company laptop or mobile device
· Analysis of Application Security
token keys installed on mobile dev to protect company
· Analysis of File Security
files will be encrypted once completed and put in the archived files
· Analysis of User Security
users will have individual user names and passwords to all devices
· Analysis of Cloud vulnerability, if any
Cloud will need to be monitored to asses any intursions
· Additional Comments and Recommendations
A disaster recovery plan will need to be started. This will ensure min downtime should we need to have techs at home or out of the office or any issues arrising at the office or in town.
Processing Model
Business customer
Start
New customer
Mobile payments
Make Transaction
Create an account
Login
Thank you for choosing our appliance services.
Error. Invalid password or account details. Log in again?
Display balance
Thank you for choosing our services .please come again later
Transaction Completed
End
Accepted
Decline
Yes
Yes
No
Business customer
Start
New customer
Phone call
transfer
Schedulers
Are you looking to schedule a repair?
Login
Are you within the warranty period?
Error. Invalid password or account details. Log in again?
transfer
Warranty department
Thank you for choosing our services .please come again later
Transaction Completed
End
Accepted
Decline
Yes
Yes
No
Gantt
Create a Gantt Chart in this worksheet. Enter title of this project in cell B1. Legend title is in cell I1. Information about how to use this worksheet, including instructions for screen readers and the author of this workbook is in the About worksheet. Continue navigating down column A to hear further instructions. | PROJECT TITLE | Legend: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Enter Company Name in cell B2. A legend is in cells I2 through AC2. | AW Appliance | On Track | Low Risk | Med Risk | High Risk | Unassigned | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Enter the name of the Project Lead in cell B3. Enter the Project Start date in cell F3 or allow the sample formula to find the smallest date value from the Gantt Data table. Project Start Date: label is in cell D3. | Joseph Kamishlian | Project Start Date: | 6/22/20 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A Scrolling Increment is in cell F4. Months for the dates in row 5 are displayed starting in cells I4 through cell BL4. Do not modify these cells. They are auto updated based on the project start date in cell F3. | Scrolling Increment: | 0 | June | July | August | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Cells I5 through BL5 contain the day number of the month for the Month represented in the cell block above each date cell and are auto calculated. Do not modify these cells. Today's date is outlined in Red (hex #AD3815) from today's date in row 5 through the entire date column to the end of the project schedule. | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | |||||||
A scrollbar is in cells I6 through BL6. The increment for paging through the data is defined as 2 pages at a time and can be configured in the settings for the control bar. To jump forward or backward in the timeline, enter a value of 0 or higher in cell F4. A value of 0 takes you to the beginning of the chart. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This row contains headers for the project schedule that follows below them. Navigate from B7 through BL7 to hear the content. The first letter of each day of the week for the date above that heading, starts in cell I7 and continues through cell BL7. All project timeline charting is auto generated based on the category, start date and number of days entered in the Milestones table. | Milestone Description | Category | Assigned To | Progress | Start | No. Days | M | T | W | T | F | S | S | M | T | W | T | F | S | S | M | T | W | T | F | S | S | M | T | W | T | F | S | S | M | T | W | T | F | S | S | M | T | W | T | F | S | S | M | T | W | T | F | S | S | M | T | W | T | F | S | S | |
Do not delete this row. This row is hidden to preserve a formula that is used to highlight the current day within the project schedule. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Hire Service Manager | On Track | Name | 25% | 6/25/20 | 7 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Warehouse Extension | Med Risk | 6/30/20 | 17 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Questionnaire for deparment heads | Milestone | 50% | 6/22/20 | 10 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||||||||||||||
Train new users | On Track | 1000% | 7/15/20 | 7 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Select software | High Risk | 10% | 7/1/20 | 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Set up user GUI | High Risk | 60% | 7/1/20 | 19 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Risk Analysist | On Track | 50% | 7/3/20 | 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Software Dev/ IT test | Low Risk | 33% | 7/8/20 | 28 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Inventory for new equiptment | Milestone | 7/10/20 | 13 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||||||||||||
Disaster response plan | On Track | 7/11/20 | 10 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Management reporting report | On Track | 7/10/20 | 3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Testing | Med Risk | 7/13/20 | 8 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Implementation Plan | On Track | 7/28/20 | 5 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Interview for new employees | Goal | 8/1/20 | 6 | 2 | 2 | 2 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Office setup | Low Risk | 7/1/20 | 10 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This is an empty row | 151 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This row marks the end of the Gantt milestone data. DO NOT enter anything in this row. To add more items, insert new rows above this one. | To add more data, Insert new rows ABOVE this one | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Running Head: QUESTIONER 1
Joseph Kamishlian
June 2020
Questionnaire 1 (Service Repair)
As Emily, the new service manager starts work, a new system for scheduling appliance repair has been proposed. In order for the company to get best results and optimal performance from employees, the organization has resorted to interview some employees to get their opinion on the proposed new system. A list of the employees to be interviewed include; service manager, workshop manager, parts manager, and repair technicians. Below are some of the important questions that these employees will be asked concerning the new proposed system.
Please click here to indicate your informed consent to participate in this study |_|
[Questionnaire: Service repair department]
In charge |
|
Department |
|
Results |
|
Organization |
|
Date | [Date] |
Period |
|
Please read and answer all questions
Are you happy with the current system?
[Type an answer here.]
[Type an answer here.]
[Type an answer here.]
What are some of the challenges that you face?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
What is your opinion on the proposed new system?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
In what ways do you think the new system will improve operations?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
How is the new system likely to impact on your work?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
What are some of the changes you would like to see under the new system?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
Do you understand how the proposed system works?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
Do you have any reservations about the new system?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
Please indicate appropriately with either yes or no
Do you agree with the proposed new system?
Do you think the new system will help to increase sales?
Do you think that the proposed new system will improve efficiency?
Are willing to support the new system?
Do you have any additions you would add to the new system?
Questionnaire 2 (Appliance Warehouse)
The list of employees to be interviewed is as follows; warehouse manager, operations manager, project manager, and warehouse attendant. The type of technique chosen for this project is Rapid Application Development technique (RAD). This is because of the urgency of the matter. RAD was also chosen because we do not have to come up with individualized questions for each employee interviewed.
Please click here to indicate your informed consent to participate in this study |_|
[Appliance Warehouse Questionnaire]
In charge |
|
Department |
|
Results |
|
Organization |
|
Date | [Date] |
Period |
|
Please read and answer all questions
1. What areas of your work would you like to see some changes?
[Type an answer here.]
[Type an answer here.]
[Type an answer here.]
2. What do you think AW (Appliance Warehouse) is doing right?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
3. What do you think AW is doing wrong?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
4. What are your suggestions on how AW can increase capacity?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
5. What is your opinion about procurement system at AW?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
6. What changes do you believe can help to improve procurement system at AW?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
7. Do you believe you are well equipped to handle your duties efficiently?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
8. What kind of support would like to get from AW to facilitate your work?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
Please indicate appropriately with either yes or no
9. Are you getting enough support from AW to do your work?
10. Are you happy with current system at AW?
11. Are you happy with your work?
13. Do you think AW can do better to increase sales?
14. Do you like working for AW?
Summary
· (1)gathering requirements,
· (2)representing requirements, and
· (3)validating and verifying requirements.
During requirements engineering, the business-related requirements for the new information system are identified. Scalability is considered to ensure that the system can support future growth and expansion. Security is an essential requirement of all modern connected systems. The TCO is also estimated to identify all costs, including indirect costs.
Popular team-based approaches include JAD, RAD, and agile methods. JAD is a popular, team-based approach to fact-finding and requirements engineering. JAD involves an interactive group of users, managers, and IT professionals who participate in requirements engineering and develop a greater commitment to the project and to their common goals.
RAD is a team-based technique that speeds up information systems development and produces a functioning information system. RAD is a complete methodology, with a four-phase life cycle that parallels the traditional SDLC phases.
Agile methods attempt to develop a system incrementally by building a series of prototypes and constantly adjusting them to user requirements. Tools are often avoided and replaced with simpler aids, such as whiteboards and sticky notes to facilitate communication.
The requirements gathering process includes interviewing, document review, observation, questionnaires, sampling, and research. Successful interviewing requires good planning and strong interpersonal and communication skills. The systems analyst must decide on the people to interview; set interview objectives; and prepare for, conduct, and analyze interviews. The analyst also might find it helpful to use one or more software tools during fact-finding.
Systems analysts use various tools and techniques to represent system requirements. Natural language, structured or unstructured, is still the default. Requirements can be stored as simple text in a plain file or in an Excel spreadsheet. They can also be stored online for automated search and analysis.
Diagrams are another way of representing requirements. They are suitable for analysts who are more visually oriented. They can also capture complementary aspects of the system requirements. Sample diagram types include FDDs, business process diagrams, and DFDs.
Models provide a more formal representation of system requirements. The UML is a widely used method of visualizing and documenting software design through the eyes of the business user. UML tools include use case diagrams and sequence diagrams to represent actors, their roles, and the sequence of transactions that occurs.
Systems analysts should carefully record and document factual information as it is collected, and various software tools can help an analyst visualize and describe an information system.
Requirements V&V is concerned with demonstrating that the requirements define the system that the customer really wants. Validation asks if the correct requirements are stated, while verification asks if the requirements are stated correctly.
All requirements engineering activities can be helped through the judicious use of tools. They provide automated support for requirements attributes such as traceability. For very large systems with thousands of requirements to manage, CASE tool assistance is necessary.
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
Service Records Sample
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. |
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 |
DATA DICTIONARY
RECORD DESCRIPTION
SYSTEM
RECORD ID
RECORD NAME
ALTERNATE NAMES
DEFINITION
RECORD DATA ELEMENTS
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
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 |
Sheet2
Sheet3
SYSTEM REQUIREMENTS DOCUMENT
· Introduction
· Summary
· Findings
· Recommendations
· Time and Cost Estimates
· Expected Benefits
· Appendix
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
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% |
Sheet2
Sheet3
DATA DICTIONARY
DATA FLOW DESCRIPTION
ID NAME
ALIAS
DESCRIPTION
ORIGIN DESTINATION
RECORD
VOLUME AND FREQUENCY
COMMENTS
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.]
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 |
Sheet2
Sheet3
DATA DICTIONARY
PROCESS DESCRIPTION
SYSTEM
PROCESS NAME
PROCESS ID
INPUT DATA FLOWS
OUTPUT DATA FLOWS
PROCESS DESCRIPTION
SYSTEM DOCUMENTATION
NAME OF SYSTEM
DATE
PAGE of
ANALYST
PURPOSE OF DOCUMENTATION
PROGRAM IDENTIFICATION
PURPOSE
FILES – DATABASES – CLOUD REQUIREMENTS
WEB PROCESSING REQUIREMENTS AND RESOURCES
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 _____________________
DATA DICTIONARY
EXTERNAL ENTITY DESCRIPTION
LABEL
ENTRY TYPE
DESCRIPTION
ALIAS
VALUES & MEANINGS
NOTES
LONG NAME
SYSTEM DOCUMENTATION
NAME OF SYSTEM
DATE
PAGE of
ANALYST
PURPOSE OF DOCUMENTATION
FIELD FIELD TYPE FIELD LENGTH
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:
SYSTEM DESIGN SPECIFICATION
Management Summary
System Components Details
Program Design
User Interface Design
Output and Input Design
File and Database Design
Support Processing Design
Environmental Requirements
Implementation Requirements
Time and Cost Estimates
Appendices (as needed)
DATA DICTIONARY
DATA STORE DESCRIPTION
LABEL
ENTRY TYPE
DESCRIPTION
ALIAS
COMPOSITION (ATTRIBUTES)
NOTES
LONG NAME
INTERVIEW DOCUMENTATION
Name of System: Page
Date:
Prepared by:
Title:
Purpose:
Location:
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

Get help from top-rated tutors in any subject.
Efficiently complete your homework and academic assignments by getting help from the experts at homeworkarchive.com