employee phone book
DESCRIPTION
Employee Phone Book. Design Document www.worktamer.com. Revision History. Overview. This document specifies the design of the new Employee Phone Book system. This system will replace the current paper-based report circulated each month by human resources. Goals. - PowerPoint PPT PresentationTRANSCRIPT
Employee Phone Book
Design Documentwww.worktamer.com
www.worktamer.com 2
Revision HistoryVersion Date Author Comments
1.0 2009/01/01 WorkTamer Initial Draft
www.worktamer.com 3
Overview
• This document specifies the design of the new Employee Phone Book system. This system will replace the current paper-based report circulated each month by human resources.
www.worktamer.com 4
Goals
• Eliminate paper waste from printed employee phone lists– “by moving to a software-based solution”
• Keep the employee phone list current at all times
www.worktamer.com 5
Benefits
• Reduced paper costs• “Greener” office• Improved communication between employees
www.worktamer.com 6
Scope Statement
• The solution will be to provide a web-based application
• This application will provide a searchable listing of all employees
• It will provide name, role and phone number• It will only be accessible from the internal
organizational network
www.worktamer.com 7
Functional Team
• Jane– Office administrator– Responsible for: interface design
• Jill– Human resources manager– Responsible for: user acceptance
www.worktamer.com 8
Development Team
• Jeff– Database Administrator– Responsible for: data structure, data layer
• John– Team lead, developer– Responsible for: interface, reports, security
www.worktamer.com 9
Effort Schedule (estimate)
• 1 day: database layer development• 2 days: stored procedure development• 1 day: business logic layer development• 2 days: interface layer development• 2 days: report development• 2 days: alpha testing• 2 days: beta testing• 1 day: production release
www.worktamer.com 10
Decision Log
• There will be no administrative interface– This is to reduce development time– The DBA will use direct table access to enter new
employees and remove terminated employees– Asked by Jane, answered by John
• Background will be blue– To match the corporate color palette– Asked by John, answered by Jane
www.worktamer.com 11
Usage Scenario: New Employee
• John successfully interviews at Big Company• His employment application is forwarded to
Jeff, the Database Administrator• His information is entered into the “Employee
Phone Book” database by Jeff• Jeff confirms the information by using the
Search function of the “Employee Phone Book” application to look for John
www.worktamer.com 12
Usage Scenario: Voicemail• John arrives at work and notices the voicemail light on his
phone is flashing• He accesses his voicemail and receives a message from
Jane requesting that he call her back• John doesn’t know Jane’s extension so he opens his web
browser and opens the “Employee Phone Book” application
• John types in Jane’s name and presses the “Search” button• Jane’s information appears on his screen• John dials her extension
www.worktamer.com 13
Workflow: New Employee
HR •Hiring Approved•Employee form forwarded to IT
IT •Employee data entered into EPB•EPB searched to confirm new entry
www.worktamer.com 14
Security
• The “Employee Phone Book” will be accessible from the internal corporate network only
• Employees will validate using Active Directory credentials to eliminate the need for a separate password
• Employees will be able to view any and all records in the “Employee Phone Book” application
www.worktamer.com 15
Interface
www.worktamer.com 16
Report: Employee ListEmployee Name Role Phone Country
Jane Administration 555 Canada
Jeff IT 444 Canada
Jill Human Resources 333 Canada
John IT 222 Canada
www.worktamer.com 17
Input samplesEmployment Application
First Name: John
Last Name: Smith
Country: Canada
OFFICE USE ONLY
Role: IT team lead
Phone: 222 (internal only, no external number)
www.worktamer.com 18
Data Samples
• Countries– Canada (CA)– United States (US)
• Roles– Administration– IT– Human Resources
www.worktamer.com 19
Business layer entities• employee_search– Input
• Fullname string (accepts * and ? as wildcards)– Output
• FullName string• Country string• Phone string
• employee_list– Output
• FullName string• Role string• Phone string• Country string
www.worktamer.com 20
Data layer entities• [dbo].[employee_search]– Input
• FullName varchar(200) (accepts * and ? as wildcards)– Output
• FullName varchar(41)• CountryName varchar(20)• Phone varchar(15)
• [dbo].[employee_list]– Output
• FullName varchar(41)• RoleName varchar(20)• Phone varchar(15)• CountryName varchar(20)
www.worktamer.com 21
Database layer entities
• [dbo].[Employee]– EmployeeID int– FirstName varchar(20)– LastName varchar(20)– FullName varchar(41)– RoleID int– Phone varchar(20)– CountryID int
www.worktamer.com 22
Database layer entities
• [dbo].[Country]– CountryID int– CountryCode char(2)– CountryName varchar(20)– PhoneMask varchar(20)
• [dbo].[Role]– RoleID int– RoleName varchar(20)
www.worktamer.com 23
Signoff
• This document has been accepted by:– Jane, Administration– Jill, Human Resources– John, IT
www.worktamer.com 24
Change Request Form (sample)Date: 2009/01/01
Requestor: John Smith
Priority: Low
Schedule Impact: Minimal
Status: Approved
Description: Please add the country code to the employee list.