Initial Requirements

Redesign of current GUI to be more user friendly (making use of current logos and themes)
User Logon feature which either makes use of the current network logon credentials or has a password reset functionality in order allows users to access the website
Ability to add permissions to certain users to limit sections of the website that they can access
Functionality to allow users with the correct permissions to be able to set up groups showing a department's structure with the ability to assign roles i.e. engineer/team manager/reporter/administrator
Functionality to generate overtime reports based on the information selected by users using simple filters, and the ability to send these monthly to users on request if they have the correct permissions
Functionality to generate the special claims form (again with the ability to send these monthly to users with appropriate permissions) in the necessary format
Functionality to be able to integrate with the current ESS system used to determine employee pay

MoSCoW Requirements

Requirement	Type	Category	Priority
Time machine shall have users logon to connect to the system using their current credentials (i.e. email).	Functional	Login	Must
Time machine shall have a database which stores these user’s accounts with their passwords hashed in order to access stored data related to them.	Functional	Login	Must
Time machine shall be able to assign different level of permission to users limiting which features they can access depending on what role they have in the company.	Functional	Login	Must
Time machine shall have a page for creating a new account upon a user’s first time using the site.	Functional	Login	Must
Time machine shall have a page to reset the password if the user has forgotten by utilising their ATOS email.	Functional	Login	Should

Requirement	Type	Category	Priority
Time machine shall be able to give the user of form to fill in when they want to submit an overtime request making use of textboxes and combo lists, and store these in a database.	Functional	Standard User	Must
Time machine shall have the feature of adding favourite WBS codes which can be used when submitting an overtime request, which can be chosen from a list.	Functional	Standard User	Should
Time machine shall have the feature of being able to edit a user profile where they can change submit a request to change their name, address and email which can overseen by a user with a high level of permissions	Functional	Standard User	Must
Time machine shall email users once the pre-approved overtime has been completed informing them of the need to go on Time Machine and confirm the anticipated overtime specifics matches up to what happened.	Functional	Standard User	Should
Time machine shall have a tab which shows a summary of their overtime request and then for each request a link to page which enables them to enter the details of what actually and a textbox to supply a comment explaining any difference in time.	Functional	Standard User	Must
Time machine shall have a tab which shows all of the overtime requests that have been approved and confirmed by the user.	Functional	Standard User	Should

Requirement	Type	Category	Priority
Time machine will be able to allocate certain users with the correct permissions as an approved for a selection of other users.	Functional	Team Leaders	Must
Time machine shall have a tab for approvers to see the overtime requests of the users they’re overseeing with a button to begin processing these requests.	Functional	Team Leaders	Must
Time machine shall have a page for the approvers which show a summary of other users overtime request and then radio buttons to decide whether or not to approve the request with space to add comment before they submit.	Functional	Team Leaders	Must
Time machine shall allow approvers to generate overtime reports based on the information selected by users using simple filters specifically the date, and the ability to send these monthly to users on request.	Functional	Team Leaders	Should

Requirement	Type	Category	Priority
Time machine will be able to allocate certain users with the correct permissions as an administrator.	Functional	Administrators	Must
Time machine will have a page for administrators to view and edit all users, as well as the ability to create new users specify emails which can be used when creating accounts and what roles these users will have as well as their personal information.	Functional	Administrators	Must
Time machine will allow administrators to transfer users from one group i.e the supervision of one approver (team leader) to another.	Functional	Administrators	Must
Time machine will allow administrators to control the payment options for roles and if need be individual users.	Functional	Administrators	Must
Time machine will allow administrators to see an overview of all the team/groups will the ability to edit it.	Functional	Administrators	Should
Time machine will be able to link approved overtime requests to ESS with the payment changes by administrators noted as well.	Functional	Administrators	Could

Requirement	Type	Category	Priority
Time machine will allow users to complete each task within 5 clicks.	Non-Functional	Ease of Use	Should
Time machine will have an uptime of at least 99%.	Non-Functional	Availability	Must
Time machine will make sure users do not need to spend more than 5 minutes on completing tasks.	Non-Functional	Ease of Use	Should
Time machine shall support the latest versions of Chrome, Safari, Firefox, and Internet Explorer.	Non-Functional	Performance	Must
Time machine will be able to scale and resize for mobile and other devices.	Non-Functional	Ease of Use	Could
Time machine shall have a method of getting text based help which can help navigate and utilise site, which can be accessed on every page.	Non-Functional	Ease of Use	Must

Use Case	Logging in
Description	A user attempts to log in to the system
Primary actor	Standard users
Secondary actor	None
Precondition	None
Main Flow	The user loads up the webpage The user enters their email in the appropriate field The user must enter their password in the appropriate field The user must either use the 'log on' button or press enter
Post-Condition	The user should land on the homepage

Use Case	Overtime Request
Description	A user attempts to submit an overtime request
Primary actor	Standard users
Secondary actor	None
Precondition	The user must have logged into the system
Main Flow	The user must head to the overtime request tab They must select the option to create a new request They must then fill in all of the field They must then submit the overtime request
Post-Condtion	The overtime request will then go to their team leader for approval, and then request the user confirm that they did follow what their request claims

Use Case	Overtime Report
Description	A team leader attempts to generate an overtime report
Primary actor	Team leaders
Secondary actor	Standard users
Precondition	The user must have logged into the system, have team leader permissions, and users under their supervision must have submitted one overtime request which has since been approved.
Main Flow	The user must head to the the overtime report tab They must then select the option to set up a new report They must then fill in all of the fields They then must select how after they want the reports to be sent to their email
Post-Condtion	The team leader will then be emailed a report with summaries of the overtime reports within the timeframe specified when setting up the report

Use Case	Special Claims Form
Description	A user attempts to generate a special claims form
Primary actor	Standard users
Secondary actor	None
Precondition	None
Main Flow	The user must head to the the special claims tab They must then select the option to set up a new special claims form They must then fill in all of the fields They then must submit their request
Post-Condtion	The user will then be able to download or get an email sent to them with the special claims form they just generated