Analysis 1-3

CSC 450

Shannon Rinehart

Stephen Kidd

Craig Hewett

Requirements Specification

Supported Activity List

  • Grocery Store Scheduler

-Ability to enter an employees information and availability

-Password protection

-2 departments: cashier and bagger

-Ability to handle special restrictions for certain employees, such as weekends off or no working late nights

-Ability to make a schedule for a set amount of time, such as one week or one month

-Output the schedule into a moderately attractive form

-Ability to schedule adequate help for peak sale periods such as summer months and holidays

-Intuitive design and interface

Human-computer interface description

  • GUI, buttons to add new employees, generate a new schedule and view the current schedule, possibly a web based application
  • Schedule will displayed in a grid format similar to TV listings

Solved problems list

  • Prevents conflicts between employees over hours
  • Automating the scheduling process saves time
  • Allows management to focus more on other job responsibilities
  • Ensures complete coverage for the entire day

Information sources list

  • Grocery store information: store hours, number of employees needed a day, peak times and daysto schedule people, special cases for employees such as only weekdays, etc.
  • Database of employee availability

Information-requesting organizations list

  • Store managers and supervisors can use the program to maintain employee information and generate schedules
  • Employees won’t ever use the program, but they will see the end output when schedules are posted

Checks and balances list

  • Password protection so only members of management can modify schedules
  • Ability to verify employee availability
  • Paper copies of employee availabilities and software backups are kept in case of data corruption

Security and fault-tolerance requirements

  • Password Protection for the schedule and employee information
  • Stamp the schedule with the date it was modified

Estimates of present information capacity and projected growth

  • Grocery stores have high employee turnover, so adding and removing employees from the schedule should be easy

Prioritization of requirements

  • High

-GUI to display schedule

-Ability to add and remove employees

-Ability to generate schedule
-Secure access with password

  • Medium

-Ability to backup database

  • Low

-E-mail schedule to employees

Ethical concerns

  • The scheduler will be impartial to employees when scheduling them, but if a member of management is “out to get” someone they could modify their availability and give them less hours
  • Use of Social Security number shouldn’t be an issue due to limited access to the database

Scenarios

New Employee

Precondition: The department manager, Lois Hathaway, has successfully logged onto the scheduling system with the appropriate username and password. An employee database with information on current employees has been created and initialized.

Cashier: Jamie Johnson has been called in for an interview with the intent to hire. Lois Hathaway has conducted the interview and has asked Jamie to prepare a list of when he is available to work. Lois receives the list and proceeds to enter it into the computer. She selects add a new employee to the database. A blank database entry appears and prompts Lois for the information about the new employee. She proceeds to fill in the appropriate fields with Jamie’s full name, Social Security number, job title, job status and availability for each day of the week. After she is finished, Lois selects to save the new employee’s information.

Post condition: Jamie’s information is immediately saved to the employeedatabase. The scheduling system will take his availability into account during the next scheduling period.

Insufficient Data

Precondition: Department manager, Lois Hathaway, has completed entering the availability data of all current employees. After saving, she is ready to proceed with the scheduling process.

After saving the entered data, the scheduling system checks to make sure that all hours are covered by at least 2 different people. Unbeknownst to Lois, there is a gap in the availability between 7 and 10 A.M. A dialog box appears on the screen alerting Lois to the flaws in the employee availability, allowing her to take the necessary steps to remedy the dilemma.

Post condition: The database saves, but the alert message will appear each time Lois tries to exit the system.

Not enough hours

Precondition:Department manager Lois Hathaway has logged into the system. Lois begins the automated scheduling process.

After the schedule has been created, a popup box appears alerting Lois that due to poor availability, Clark Wayne has only been scheduled for 4 hours during the entire week. Lois must decide if it is worth keeping Clark on board for one day a week or if she should hire someone with better availability.

Post condition: The generated schedule is saved, but Lois can go back if she chooses and modify Clark’s hours.

Holiday Rush

Precondition: It’s the Holidays and the Assistant Manager Brian Peterson knows that there is going to be a need for extra some employees and for existing employees to work longer hours during the Holiday Season. In order to create a schedule to meet the busy holiday routine, Brian will need the employees input and will need to hire additional workers.

Brian Peterson asks Bob Sanderson, Ralph Hudson and Jeff Freeman, who were just hired, to give him their availability and the days that they can work. Mike Cencia and Ed Dye are existing employees that can work additional hours. Brian, having all their information in front of him, logs on to the system and enters each individual’s availability. The system then shows the available slots that need to be filled and who meets the requirements for each shift/position that needs to be filled.

Post condition: Brian then selects which employees meet the shifts/positions requirements and experience needed to fill them.Brian now has all the information needed to accurately schedule his workers and cover the shifts needed.

Primary Class List

  1. Users
  2. Employees

-cashiers

-baggers

  1. Schedule
  2. Availability