Software Requirement Specification: 1.1purpose

GROUP-05 CST-304
Software Requirement
Specification
Introduction
The entire System of Employee Management (EMS) is designed to remove problems in
existing system and the organisation will meet its specific aims. The role of EMS is to
centralise the repository of staff data including recruitment, attendance and salary. An
effective EMS helps to generate accurate and timely employee information to fulfil the
objectives. EMS keeps the record of employee joining date, leaving date, assets provider. It
manages salary of employee according to the attendance, also focuses on the capabilities and
facilities provided by the company.
1.1Purpose:
The system will be designed to satisfy employees by delivering services like salary
accurately and on time. Employee attendance and salary system will be automated. All the
transactions and staff data will be stored in the system. It’ll also facilitate keeping records of
employees, such that all the information about the employee will be available quickly. It’ll
also make it very easy to generate statistical data or custom data, like finding a certain set of
employees.
1.2 Scope:
TimeTracker 2.0 is a web-based application that will allow users to manage their timesheets
and leave through an intuitive, easy-to-use interface. It will have a corresponding Android
application. The system will also allow reports on that data to be easily generated, printed or
exported. A detailed description of the project scope can be found in TimeTracker 2.0 Vision
and Scope.
1.3 Advantages of the system (EMS):
1. Providing a comprehensive information picture.

2. Increasing the speed of information transactions.
3. Improving employee satisfactions by delivering services timely, more quickly
and accurate to them.
1.4 Problem Statement:
The problem definition for designing the system is to maintain data of employee,
to make easy controlling of employees, to divide jobs and
1|Page
GROUP-05 CST-304
access control between employees, to use technology for accurate and timely
processing by fully privacy and fully authority access. The objective of the
project is to set up employee information system about status of employee and
attendance of employee and monthly salary process and delivery. To eliminate or
reduce as much as possible the hardships of existing system and avoid errors
while entering data. No formal knowledge is needed for user to use the system.
Whole system is completely protected.
1.5 Basic Features:
1. Online advertising
2. Accepting applications
3. Registering new employees
4. Creating accounts and attendance for employees.
5. Employees can check their details/status and mark attendance.
6. Employee, Manager or administrator see their performances.
7. Calculating net salary and delivering according to attendance.
2|Page
GROUP-05 CST-304
GROUP-05 CST-304
2. Project Description
2. Product Perspective
2.1. Login Module
It is one of the most important modules of the Employee Management System. Each
Employee of the system has to be assigned its own username and password. And the
assigning job is to be performed by the administrator. The login module chiefly
contains:
! Administrator Login
! Employee Login
2.2. Administrator Module
The administrator of the application has to be provided the highest access priority
which enables him/her to perform all the functionalities that exist in the application.
In addition to that, the administrator is able to register Employee. The administrator
is allowed to:
! Register Employee as users of the system.

! Add, search and edit personal information of Employee.
! Delete record of any Employee.
! Calculate salary package of Employees.
2.3. Employee Module

The Employee in this application has the lowest access priority that only enables
him/her to only view the personal information and the annual salary.
3|Page
GROUP-05 CST-304
2.4. Identification Card (IC) Number Generation Module

Each employee in the application has to be assigned with its unique Identification
Card (IC) Number by which the employee can be identified uniquely for the
operations and this is automatically generated by the system.  
2.5. Record Searching Module
The searching of any record in the system must be done by using the following categories:
! IC Number
! Designation
! Department
4|Page
GROUP-05 CST-304
3.Product Features
FE-1: Data and application hosting on Google Apps

FE-2: Log and submit time spent on projects and clients
FE-3: Manage leave time
FE-4: Generate, print and export reports
FE-5: Employee management
FE-6: Time approval and rejection with notification
FE-7: Integration of Google Calendar, Mail and Talk
FE-8: Brand customisation
FE-9: Time management through Android application
FE-10: Impersonate other users
FE-11: Project/Client Management
See Figure 2 for the relationship between these features. Please note that this document
covers all features.
Figure 2. Major features and how they relate.
5|Page
GROUP-05 CST-304
4. User Classes and Characteristics
Employee (favored) The Employee is the person or people who work for the
business using TimeTracker 2.0 and need to log time spent
on clients/projects and manage leave. They will also use the
new system to manage company email, schedule business
meetings in the calendar, and communicate with other
employees through instant messenger. Some might have to
be trained to use the new system. Employees will have the
ability to generate reports associated with their own work
only.
Project Manager A Project Manager is a special employee or group of
(favored) employees which are in charge of managing a particular
project. Project Managers will use the new system in the
same way as a regular user, but will also need the ability to
view project status and approve/reject timesheets. Project
Managers will also need the ability to manage employees
associated with their projects as well. Project Managers
will have the ability to generate reports associated with their
own work as well as the projects which they manage.
Project Lead A Project Lead is a special employee or group of employees
who are the lead on a particular project or projects. They
will have the ability to approve/reject time in the event that
the Project Manager is unable to do so. Project Leads, like
Project Managers, will have the ability to generate reports
associated with their own work as well as the projects which
they are leading.
System Administrator The Administrator is the person or people who will have
any and all the privileges of all other user types. They will
be able to impersonate other employees within the system.
They will also have the authority to edit the branding and
manage/generate reports regarding all projects/employees.
Accounting The Accounting Department Member is the person or group
Department Member of people that will be in charge of all payroll activities.
They will need to have the ability to generate timesheet
reports.
Client The client is the person or people who are employing the
talents of the business using TimeTracker 2.0. They will
use the new system to view the remaining time and status
reports associated with all their current project(s).
6|Page
GROUP-05 CST-304
4.Operating Environment
OE-1: System is not dependent on geographical areas.

OE-2: System shall operate in newest versions of all web browsers.
OE-3: There should be no constraint on users being able to access the

system at a given time.
OE-4: Data is generated by online forms and stored in the Google App
Engine database.
OE-5: Continuous service is preferred, but as long as there is no data loss,
minor service interruptions can be tolerated.
OE-6: Personal data will be stored in the database, so the Google App
Engine database must be secure.
OE-7: jQuery javascript library will be needed to create the user interface
for the system.
5.Design and Implementation Constraints
CO-1: All data shall be stored on Google App Engine.

CO-2: User interface shall be composed using jQuery javascript library.
6.User Documentation
No user documentation information at this time.
7.Assumptions and Dependencies
AS-1: No more than 500 MB of data stored on Google App Engine.

AS-2: No more than 5 million page views monthly.
AS-3: Users have a Google Account with which they can login.
AS-4: Users have javascript enabled.

DE-1: Free Google App Engine account.
DE-2: jQuery javascript library (for user interface).
7|Page
GROUP-05 CST-304
4.System Features
4.1. Data and application hosting on Google Apps
4.1.1. Description and Priority

Application will need to be hosted on Google App Engine.
Priority: high.
4.1.2.Stimulus/Response Sequences
Not applicable.
4.1.3.Functional Requirements
Not applicable.
4.2.Log and submit time spent on projects and clients
4.2.1.Description and Priority
Users will need to be able to log time spent on particular projects or clients along with
descriptions of the activities which comprised the time spent. At the end of pay
periods, users will need to submit their time for approval.   
Priority: high.
Stimulus: User requests to review time.

Response: System retrieves and displays all time logged for current time period.
Stimulus: User requests to log time.
Response: System adds time to Google App Engine database and redirects user to
dashboard displaying all time logged for current pay period.
Stimulus: User requests to edit logged time
Response: System recalls from the database the information that has been saved,
and fills in the data on a new form for the user to fill out.
Stimulus: User requests to duplicate logged time to a different day.
Response: System copies data from currently selected submission to selected
‘duplicate’ day.
Stimulus: User requests to submit time.
Response: System flags all time associated with the current pay period that has
not already been submitted as ‘needs approval’.
Time Review The system shall allow a user who is logged

in to review their time.
Time Review Log The system shall allow a user who is logged
in to log time.
Time Review Submit The system shall allow a user who is logged
in to submit time.
8|Page
GROUP-05 CST-304
Time Submit Incomplete The system shall check to see if all required
information is present, and prompt the user
to fill out missing data and resubmit.
Time Submit Duplicate The system shall copy selected time
submission to new day(s).
4.3.Manage leave time
Users will need to be able to manage leave time, including sick and vacation days.
Priority: high.
Stimulus: User requests to review leave time.
Response: System retrieves and displays all leave time logged for current time
period.
Stimulus: User requests to edit logged leave time
Stimulus: User requests to duplicate logged leave time to a different day.
Stimulus: User requests to submit leave time.
Leave Time Review The system shall allow a user who is logged
in to review their leave time.
Leave Time Review Submit The system shall allow a user who is logged
in to submit leave time.
Leave Time Submit Incomplete The system shall check to see if all required
Leave Time Submit Duplicate The system shall copy selected leave time
9|Page
GROUP-05 CST-304
4.4.Generate, print, and export reports
Application will need to be able to generate reports for project managers and clients as
well as administrators. Clients and project managers could generate and export or
print reports for their records.
Priority: medium.
Stimulus: User requests to generate a report.

Response: System displays form containing parameters and submit button.
Stimulus: User requests to submit a report generation form.
Response: System retrieves information from database and displays report in web
browser along with ‘Export’ and ‘Print’ buttons.
Stimulus: User requests to export report.
Response: System exports report to selected export option and prompts user to
open/save/cancel in web dialog box.
Stimulus: User requests to print report.
Response: System redirects user to pdf version of report in web browser.
Report Submit The system shall allow the user to fill out a
form to be submitted through the website.
Report Submit Incomplete The system shall check to see if all required
Report Submit Recall The system shall recall any previously
saved data and fill in the application
automatically
Report Export The system shall recall data from database
and format in file according to export
preference.
Report Print The system shall recall data from database,
generate a PDF of formatted data and
display PDF.
4.5.Employee management
Administrators will be able to log into the system and manage employee
information. Project managers will be able to add/drop employees from being
associated with projects they are managing.
Priority: high.
10 | P a g e
GROUP-05 CST-304
Stimulus: User requests to review employees
Response: System displays information related to requested employee.

Stimulus: User requests to add employee.
Response: System checks user permissions and if employee does not already exist
in database adds it and displays list of current employees with
notification of newest employee added at top.
Stimulus: User requests to remove employee.
Response: System checks permissions and if employee exists in database removes
it and displays list of current employees with notification of employee
removed at top.
Stimulus: User requests to edit employee.
Response: System checks user permissions and recalls from the database the
information that has been saved, and fills in the data on a new form for
the user to fill out.
Stimulus: User requests to submit changes to employee.
Response: System checks user permissions and updates employee in database and
returns to list of employees with notification at top of recently added
entity.
Stimulus: User requests to view all employees.
Response: System checks user permissions and displays list of all current
employees.
Employee Add The system shall let a User that is an administrator or

Project Manager with correct permissions who is logged
into the system to add employees.
Employee Remove The system shall let a User that is an administrator or
into the system to remove employees.
Employee Edit The system shall let a User that is an administrator or
into the system to edit employees.
Employee Review The system shall let a User that is an administrator or
into the system to review employees.
Employee Change The system shall let a User that is an administrator or
Cancel Project Manager with correct permissions who is logged
into the system to abandon the process of changing an
employee (add/delete/edit) without submitting changes.
11 | P a g e
GROUP-05 CST-304
4.6.Time approval and rejection with notification
Application will need to allow users who are Administrators or who are Project
Managers/Leads with the correct permissions to approve/reject submitted timesheets
and leave time. The system should then generate a notification to be displayed to the
user who submitted the time when they next log in.
12 | P a g e
GROUP-05 CST-304
13 | P a g e
GROUP-05 CST-304
CST-
GROUP-05 304
 
Priority: high.
Note: For the sake of simplicity, both timesheets and leave time will be referred to as
time and Administrators and Project Managers will be referred to as users for the
remainder of this section.
Response: System displays requested submitted time.
Stimulus: User requests to approve time.
Response: System checks user permissions and flags time as ‘approved’ in
database. System then generates notification to be displayed to the
user who submitted the time upon next login.
Stimulus: User requests to reject time.
Response: System checks permissions and prompts user for reason, then flags
time as ‘rejected’ in database and generates notification with reason
to be displayed to user who submitted the time upon next login.
Time Review The system shall let a user who is an administrator or a

project manager with the correct permissions and
logged into the system to review time.
Time Review The system shall let a user who is an administrator or a
Approve project manager with the correct permissions and
logged into the system to approve submitted time.
Time Review Reject The system shall let a user who is an administrator or a
logged into the system to reject submitted time, giving
an optional reason.
Time Review Cancel The system shall let a user who is an administrator or a
logged into the system to exit the review of time
without either approving or rejecting it.
4.7.Integration of Google Calendar, Mail and Talk
Application will allow users who are logged in to access Google Calendar, Mail and
Talk through the application. 
 
Priority: medium.

Stimulus: User requests to add time.
14 | P a g e
GROUP-05 CST-304
EMPLOYEE MANAGEMENT SYSTEM

!1
4
15 | P a g e
GROUP-05 CST-304
CST-
GROUP-05 304
Stimulus: User requests to start stopwatch.
Response: System displays timer along with ‘Pause’ and ‘Submit’ buttons.
Stimulus: User requests to pause stopwatch.
Response: System stops timer and displays ‘Resume’ and ‘Submit’ buttons.
Stimulus: User requests to submit stopwatch time.
Response: System pulls stopwatch time and adds it to Google App Engine
database, then redirects user to dashboard displaying all time logged
for current pay period.
Time Review The system shall allow a user who is logged

Time Review Log The system shall allow a user who is logged
in to log time.
Time Review Submit The system shall allow a user who is logged
in to submit time.
Time Submit Incomplete The system shall check to see if all required
Time Submit Duplicate The system shall copy selected time
4.8.Brand customization
Administrators who are logged in will be able to customize the overarching brand of
the entire application through a simple web form.   
Priority: low.
Stimulus: Administrator requests to review brand.
16 | P a g e
GROUP-05 CST-304

!1
5
17 | P a g e
GROUP-05 CST-304
CST-
GROUP-05 304
Response: System checks permissions and displays current brand preferences.

Stimulus: Administrator requests to change brand.
Response: System takes new brand preferences and updates brand information in
database.
Stimulus: Administrator/User requests to cancel changes.
Response: System reverts theme to previous version without submitting any
changes.
Brand Review The system shall let a user who is an administrator and
logged into the system to review the brand preferences.
Brand Review The system shall let a user who is an administrator and
Change logged into the system to change the brand preferences.
Brand Review Cancel The system shall let a user who is an administrator and
logged into the system to cancel the brand preference
changes without submitting them to the database.
4.9.Time management through Android application
Application will have an Android application component which will have

stopwatch capability and allow users to manage time from their mobile devices. 
 
Priority: low.

Stimulus: User requests to log time.
Stimulus: User requests to start stopwatch.
Response: System displays timer which begins counting along with ‘Pause’ and
‘Submit’ buttons.
Stimulus: User requests to pause stopwatch.
Response: System displays timer which begins counting along with ‘Resume’ and
‘Submit’ buttons.
18 | P a g e
GROUP-05 CST-304

!1
6
19 | P a g e
GROUP-05 CST-304
CST-
GROUP-05 304

Android Time Review The system shall allow a user who is logged
Android Time Review Log The system shall allow a user who is logged
in to log time.
Android Time Review Submit The system shall allow a user who is logged
in to submit time.
Android Time Submit Incomplete The system shall check to see if all required
Android Time Submit Duplicate The system shall copy selected time
4.10.Impersonate other users
Administrators will have the ability to impersonate other users, allowing them
to troubleshoot more easily and correct information if necessary.   
Priority: medium.
Stimulus: User requests to view all users.

Response: System retrieves and displays a list of all users within the system.
Stimulus: User requests to impersonate user.
Response: System changes currently logged in user to the selected user.
Impersonate User View The system shall allow a user who is logged
in and is an administrator or project
manager with the correct permissions to
view a list of all users within the system.
Impersonate User Submit The system shall allow a user who is logged
manager with the correct permissions to
impersonate other users.
20 | P a g e
GROUP-05 CST-304

!1
7
21 | P a g e
GROUP-05 CST-304
CST-
GROUP-05 304
Impersonate User Cancel The system shall allow a user who is logged
manager with the correct permissions who
is currently impersonating another user to
cancel their impersonation, reverting them
back to their original user identity.
Impersonate User Invalid The system shall check to see if the desired
user is valid, and prompt the user to choose
a different user and resubmit if it is not.
4.11.Project/Client management
Administrators and Project Managers/Leads will be able to log into the system and
manage project/client information. Project managers/leads will be able to review and
manage projects they are currently part of, but not be able to create new projects like
Administrators.
Priority: high.
Stimulus: User requests to review project/client.

Response: System displays information related to requested project/client.
Stimulus: User requests to add project/client.
Response: System checks user permissions and if project/client does not already
exist in database adds it and displays list of current projects/clients
with notification of newest employee added at top.
Stimulus: User requests to remove project/client.
Response: System checks permissions and if project/client exists in database
removes it and displays list of current projects/clients with
notification of project/client removed at top.
Stimulus: User requests to edit project/client.
Response: System checks user permissions and recalls from the database the
information that has been saved, and fills in the data on a new form
for the user to fill out.
Stimulus: User requests to submit changes to project/client.
Response: System checks user permissions and updates project/client in database
and returns to list of projects/clients with notification at top of
recently added entity.
Stimulus: User requests to view all project/client.
Response: System checks user permissions and displays list of all current
projects/clients.
22 | P a g e
GROUP-05 CST-304

!1
8
23 | P a g e
GROUP-05 CST-304
CST-
GROUP-05 304
Project/Client Add The system shall let a User that is an administrator or

Project Manager/Leader with correct permissions who
is logged into the system to add projects/clients.
Project/Client The system shall let a User that is an administrator or
Remove Project Manager/Leader with correct permissions who
is logged into the system to remove projects/clients.
Project/Client Edit The system shall let a User that is an administrator or
is logged into the system to edit projects/clients.
Project/Client Review The system shall let a User that is an administrator or
is logged into the system to review projects/clients.
Project/Client Change The system shall let a User that is an administrator or
Cancel Project Manager/Leader with correct permissions who
is logged into the system to abandon the process of
changing a project/client (add/delete/edit) without
submitting changes.
5.External Interface Requirements
5.1.User Interfaces
UI-1: Web application shall permit complete navigation and food item selection
using the keyboard alone, in addition to using mouse and keyboard
combinations.
UI-2: Android application shall support hardware as well as virtual keyboard input.
5.2.Hardware Interfaces
No hardware interfaces have been identified.
5.3.Software Interfaces
SI-1: Time Management System

SI-1.1: The time management system shall transmit data to be stored on
Google App Engine.
SI-1.2: Upon completion, system will display notification to user of result of
data transmission.
SI-1.3: If applicable, system will then generate notification to be displayed.
SI-2: Database - The system shall communicate with a database through a
programmatic
interface for the following operations: SI-
2.1: To manage employee, client, and project data. SI-2.2:
To allow a user to submit timesheets/leave time.
SI-2.3: To allow an administrator/project manager to approve/reject time.
SI-2.4: To store brand and theme preferences.
24 | P a g e
GROUP-05 CST-304

!1
9
25 | P a g e
GROUP-05 CST-304
CST-
GROUP-05 304
5.4.Communications Interfaces
CI-1: The system shall send a notification to the user to inform them of time
approval or rejection.
CI-2: The system shall send an email message to confirm registration with the
system.
CI-3: The system shall send a notification to inform the user of new email messages,
instant messages, or calendar event invitations.
6.Other Nonfunctional Requirements
6.1.Performance Requirements
PE-1: All Web pages generated by the system shall be fully downloadable in no more than
10  seconds over a 40KBps modem connection.
PE-2: Responses to queries shall take no longer than 7 seconds to load onto the screen after
the user submits the query.
6.2.Safety Requirements
No safety requirements have been identified.
6.3.Security Requirements
SE-1: Users shall be required to log in to the system for all operations.
SE-2: The system shall permit only staff members who are on the list of authorized
administrators to create or edit brand.
SE-3: The system shall permit users who are not project managers or administrators
to view only their own information, not the information of other users.
SE-4: All network transactions that involve financial information or personally
identifiable information shall be encrypted.
6.4.Software Quality Attributes
No software quality attributes have been identified.
EMPLOYEE MANAGEMENT SYSTEM !20

26 | P a g e
GROUP-05 CST-304
CST-
GROUP-05 304
Analysis Models
Figure 3  
System roles and how they relate. (Note: All arrows indicate extensions of user types.) 
27 | P a g e
GROUP-05 CST-304

!2
1
28 | P a g e
GROUP-05 CST-304
CST-
GROUP-05 304
Feasibility Study
Project Overview
A) Product prospective
This product will be able to manage information about Employee in more user friendly way
moreover it manage Employees information at various field offices. User ID and password
has been given to all the field offices so that they can enter their employee’s information
into central database. Their access to the central database is restricted to their information
only. Various reports based on the data entered by employees at field offices are generated
at Head Quarter. These reports are helpful in Manpower management decisions.
B) User Interface
* The system will be having user privileges based menu.
* User will have to select the options form the given menu.
* The system will be entering the information into the database to generate reports.
* The forms will be designed to enter the data.
* Buttons will be used to insert, retrieve or modify the data.
* Links will be provided to shift from one form to another.
C) Hardware – Software Interface

An Internet Web Server, running IIS, in this case Windows 2000 advanced server is
used to host the application. The application software, Employee Management, is
developed in ASP, JavaScript, and HTML. The backend database is MS SQL Server
2000. The Client systems with internet facility equipped with web browser will be
able to access the system
* Product Function
It is advisable to have weekly data backups. The system administrator will do the data
recovery. Selection of panel is user-initiated operation, while indent handling is client
initiated.
D) Constraints
* General Constraints
1) This system will not take care of any virus problem, which might occur either on the
client or the server system. Avoiding the use of pirated software and ensuring that

!2
2
29 | P a g e
GROUP-05 CST-304
CST-
GROUP-05 304
floppies and other removable media are scanned for viruses before use could minimise the
possibility of viral infection.
2) Recovery of data after a system crash will be possible only if backups are taken at
regular intervals.
3) Manual interfaces cannot be fully avoided. Documented proofs like dates etc. will have
to be verified by the concerned staff before entering it into the computerised system
* Hardware Constraints
Constraints of the Internet & Intranet will be applicable to the system. The performance of
the system will be dependent on the network conditions like network congestion, bandwidth
etc. The primary memory (RAM) and the secondary memory (Hard Disk Space) requirement
of the system at the client end will be the same as that required by the web browser and the
operating system. At the server end memory requirements will be that of the server software
(Operating system, Database Software, etc) and the space required to store the data. The
space required to store the data would increase as more and more records are added to the
system.
* Security Constraints
User will be authenticated by the use of username and passwords. This does not Provide
complete security and the system could be hacked into. Use of secure Socket Layer (SSL)
is recommended. Use of SSL prevents any unauthorised access as all communications are
encrypted. Valid Digital Certificates are required for this at the server end and the client
web browser should have support for SSL.
E) Assumptions and Dependencies

1. It is assumed that the user is familiar with the basic computer fundamentals.
2. Timely backup of data should be taken to avoid data loss in case of system crash.
3. The use of pirated software should be avoided as it may lead to data loss and system
crashes due to viral infections.
4. Floppies and other removable media should be scanned for viruses before use.
5. Proper configuration of the client, database server and network is necessary for the
system to function as intended.
6. It is assumed that the maintenance of the database will be assigned to the
authorised person only.
7. Only authorised persons will be allowed inside the server room.
30 | P a g e
GROUP-05 CST-304

!2
3
31 | P a g e
GROUP-05 CST-304
CST-
GROUP-05 304
Phase 1: Feasibility Study
The main objective of the feasibility study is to treat the technical, Operational, logical
and economic feasibility of developing the computerised system. All systems are
feasible, given unlimited resources and infinite time. It is both necessary and prudent to
evaluate the feasibility of the project at System study phase itself. The feasibility study to
be conduced for this project Involves.
1. Technical Feasibility
2. Operational Feasibility
3. Economic Feasibility
4. Logical Feasibility
1.1 Technical Feasibility

Technical feasibility includes Risk Resources availability and technologies. The
management provides latest hardware and software facilities for the successful
completion of the projects. With these latest hardware and software support the
system will perform extremely well. The system is available through Internet.
1.1.1 The proposed system will be developed in web bases completely and it is
required to use web technology approach.
1.2 Operational Feasibility

In the existing manual system it is very difficult to maintain and update huge amount of
information. The development of the system was started because of the requirement put
forward by the management of the concerned department. This system, will handles the
request in a better way and make the process easier thus, it is sure that the system
developed is operationally feasible.
1.3 Economic Feasibility

In the economic feasibility the development cost of the system is evaluated weighing it
against the ultimate benefit derived from the new system. It is found that the benefit, from
the new system would be more than the cost and time involved in its development.
1.4 Legal Feasibility

In the legal feasibility it is necessary to check that the software we are going to develop is
legally correct which means that the ideas which we have taken for the proposed system
will be legally implemented or not. So, it is also an important step in feasibility study.

!2
4
32 | P a g e
GROUP-05 CST-304
CST-
GROUP-05 304
33 | P a g e
GROUP-05 CST-304

!2
5
34 | P a g e

Software Requirement Specification: 1.1purpose

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Software Requirement Specification: 1.1purpose

Transféré par

Droits d'auteur :

Formats disponibles

GROUP-05 CST-304

1.3 Advantages of the system (EMS):

1. Providing a comprehensive information picture.

1.4 Problem Statement:

1.5 Basic Features:

2.1. Login Module

2.2. Administrator Module

! Register Employee as users of the system.

2.3. Employee Module

2.4. Identification Card (IC) Number Generation Module

2.5. Record Searching Module

FE-1: Data and application hosting on Google Apps

Figure 2. Major features and how they relate.

4. User Classes and Characteristics

OE-1: System is not dependent on geographical areas.

OE-3: There should be no constraint on users being able to access the

5.Design and Implementation Constraints

CO-1: All data shall be stored on Google App Engine.

No user documentation information at this time.

7.Assumptions and Dependencies

AS-1: No more than 500 MB of data stored on Google App Engine.

AS-4: Users have javascript enabled.

4.1.1. Description and Priority

4.2.Log and submit time spent on projects and clients

4.2.1.Description and Priority

Stimulus: User requests to review time.

Time Review The system shall allow a user who is logged

4.3.Manage leave time

4.3.1.Description and Priority

4.4.Generate, print, and export reports

4.4.1.Description and Priority

Stimulus: User requests to generate a report.

4.5.1.Description and Priority

Stimulus: User requests to review employees

Response: System displays information related to requested employee.

Employee Add The system shall let a User that is an administrator or

4.6.Time approval and rejection with notification

4.6.1.Description and Priority

Time Review The system shall let a user who is an administrator or a

4.7.Integration of Google Calendar, Mail and Talk

4.7.1.Description and Priority

Stimulus: User requests to review time.

EMPLOYEE MANAGEMENT SYSTEM

Time Review The system shall allow a user who is logged

4.8.1.Description and Priority

Stimulus: Administrator requests to review brand.

EMPLOYEE MANAGEMENT SYSTEM

Response: System checks permissions and displays current brand preferences.

4.9.Time management through Android application

4.9.1.Description and Priority

Application will have an Android application component which will have

Stimulus: User requests to review time.

EMPLOYEE MANAGEMENT SYSTEM

Stimulus: User requests to submit time.

4.10.Impersonate other users

4.10.1.Description and Priority

Stimulus: User requests to view all users.

EMPLOYEE MANAGEMENT SYSTEM

4.11.1.Description and Priority

Stimulus: User requests to review project/client.

EMPLOYEE MANAGEMENT SYSTEM

Project/Client Add The system shall let a User that is an administrator or

5.External Interface Requirements