Software Requirements

Specification

for

EFFORT TRACKING SYSTEM

Prepared by

SONALI SINHA 14ESKCS754 sinhasonali1996@gmail.com

SANGEETA GURJAR 14ESKCS748 sangeetagurjar34@gmail.com
KUSUM SANKHALA 14ESKCS732 kusumsankhala714@gmail.com

Instructor: Mrs. RUBAL GILL

Date: 31-07-2017
 Contents
1 INTRODUCTION ............................................................................................................................................... 3
1.1 DOCUMENT PURPOSE ................................................................................................................................ 3
1.2 PRODUCT SCOPE ....................................................................................................................................... 3
1.3 TECHNOLOGY TO BE USED ................................................................. ERROR! BOOKMARK NOT DEFINED.
1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS ....................................................................................... 6
1.5 DOCUMENT CONVENTIONS ........................................................................................................................ 6
1.6 OVERVIEW .................................................................................................................................................. 7
2 OVERALL DESCRIPTION .............................................................................................................................. 7
2.1 PRODUCT PERSPECTIVE ............................................................................................................................ 7
2.2 PRODUCT FUNCTIONALITY ......................................................................................................................... 8
2.3 USERS CHARACTERISTICS...............................................................................................................8
2.4 OPERATING ENVIRONMENT ....................................................................................................................... 9
2.5 DESIGN AND IMPLEMENTATION CONSTRAINTS.......................................................................................... 9
2.6 ASSUMPTIONS AND DEPENDENCIES .......................................................................................................... 9
3 EXTERNAL INTERFACE REQUIREMENTS .............................. ERROR! BOOKMARK NOT DEFINED.
3.1 USER INTERFACES ............................................................................. ERROR! BOOKMARK NOT DEFINED.
3.2 HARDWARE INTERFACE ..................................................................... ERROR! BOOKMARK NOT DEFINED.
3.3 SOFTWARE INTERFACE……………………………………………………………………………………………………………………….. 7
3.4 COMMUNICATION INTERFACE………………………………………………………………………………………………………………. 7
4 SYSTEM FEATURES……………………………………………………………………………………………………….. 7
5 UML DIAGRAMS ............................................................................. ERROR! BOOKMARK NOT DEFINED.
4.1 E R DIAGRAM ..................................................................................... ERROR! BOOKMARK NOT DEFINED.
4.2 DATABASE DESIGN ............................................................................ ERROR! BOOKMARK NOT DEFINED.
4.3 USE CASE DIAGRAM ....................................................................................................................................
4.4 ACTIVITY DIAGRAM.....................................................................................................................................
4.5 SEQUENCE DIAGRAM....................................................................................................................................5

6 OTHER NON-FUNCTIONAL REQUIREMENTS.............................................................................8

6.1 Performance Requirement..................................................................................................8.1

6.2 Safety Requirement.............................................................................................................6
6.3 Security Requirement...........................................................................................................7
6.4 Requirement Attributes..........................................................................................................5
6.5 Business Rule..........................................................................................................................6
6.6 User Requirement.......................................................................................................................7

7 .REFERENCES.....................................................................................................................................................
 1 Introduction
Biggest organization will use the website for the purpose of Timesheets entry system.
Every employee will have a separate login to enter into the system and enter the
timesheets. In this project there will be 3 users like Administrator, Reporting Manager and
Employee. It is an intuitive web based time tracking system for gathering and tracking
project employee time. It is design to reduce project cost and to help you complete your
projects on time and on budget. This web application will track the effort of each employee
which will help the organization to certify them yearly or quarterly.

1.1 Document Purpose

Effort tracking system is a web application is used to track the employee activities and
summarize all related activities with the total hours spent and percentage efficiency utilized
and generate the report for the same. This web application is more effective, quick in
providing the efficiency of employees. The system provides various metrics to analyze the
performance of the employee to the department. It helps the management to dynamically
add questions to the database.
It provides the mechanism through which the administrator can save the existing database
to the file. The employee can immediately know his capacity and the working hours weekly
once or when the task allotted to him is finished.

1.2 Product Scope

 There are two basic users- EMPLOYEE and ADMIN.

 All users have their own profiles in Effort Tracking System.
 Admin enter his user is and password for login, Employees enter his user id and
password for login , Admin enter new project details, New employee gives his
completed personnel, address and phone details for registration, Employee submit
daily, weekly working hours, Manager Set the status of weekly submissions of
employees, Admin gives different kind of user information for search the user data,
Employees can change password after login into the system, Project Manager
search for a team of employees for assign jobs and work.
 Admin can have his own home pages, Employees can have their own home page,
Employees get the assigned project details, Employees get the task details of the
current project, Employee receives mails the user defined data can store in the
centralized database, Admin will get the all employee information, ht new user’s
 data will be stored in the centralized database, Admin get the search details of
different criteria.
 Authentication is provided for this application only registered users can access.
There is no risk of data management at any level while the project development is
under process Categorization of computers in the datebase make easy to identify
the various computer peripherals. Client also having facility to log into the system,
and verify his project status.
 Admin has the authority to add/delete users,grant promotion to employees. He also
views the performance of employees and takes necessary actions.

1.3 Technology to be used

1.3.1 TECHNOLOGY USED FOR DESIGNING

 HTML

HTML is a standard markup language for creating web pages and web
applications. HTML describes the structure of web pages using markup. HTML
elements are the building block of HTML pages. HTML elements are represented
by tags. HTML tags label pieces of content such as “heading”,”paragraph”,”table”,
and so on.

 CSS

Cascading style sheet is a style sheet language used for describing the
presentation of a document written in a markup language. Although most often
used to set the visual style of web pages and user interfaces written in HTML and
CSS. CSS is a cornerstone technology used by most website to create visually
engaging web pages, user interfaces for many mobile applications.

 JAVASCRIPT

Javascript , often abbreviated as JS, is a high-level ,dynamic ,weakly typed, object-

based, multi-programming language. Along with HTML and CSS, Javascript is one
of the three core technologies of World Wide Web content production. Javascript is
a full-fledged dynamic programming language that , when applied to an HTML
document, can provide interactivity on websites.
  BOOTSTRAP

BOOTSTRAP makes the front-end web development faster and easier. It’s made
for folks of all skill levels, devices of all shaped, and projects of all sizes. Bootstrap
easily and efficiently scales your websites and applications with a single code
base, from phones to tablets to desktops with CSS media queries.

1.3.2 TECHNOLOGY USED FOR DEVELOPMENT

 PHP

PHP is a server-side scripting language designed primarily for web development

but also used as a general-purpose programming language. Originally created by
Rasmus lerdorf in 1994, PHP code may be embedded into HTML or HTML5
markup, or it can be used in combination with various web template systems, web
management systems and web frameworks.

1.3.3 DATABASE PLATFORM

 MySQL

MySQL is the most popular open-source relational SQL database management

system. MySQL is one of the best RDBMS being used for developing various web
based software application. MySQL is developed marketed and supported by
MySQL AB, which is a Swedish company.

1.3.4 DESIGN TOOL – RATIONAL SOFTWARE MODELER

 IBM Rational Software Modeller , (RSM) made by IBM’s Rational Software

division, is a Unified Modeling language UML 2.0- based visual modelling and
design tool. Rational Software Modeler is built on the Eclipse open-source software
framework and includes capabilities focused on visual modelling and model driven
development (MDD) with thw UML for creating resilient, throughout applications
and web services.
1.4 Definitions, Acronyms and Abbreviations
Abbreviation used:

 ETS(EFFORT TRACKING SYSTEM)

It’s a web application that provides online medical services for people.

 Admin(Administrator)
He has the authority to add/delete employees, grant promotion to them.

 UML(UNIFIED MODELING LANGUAGE)

It is a standard language for writing software blueprints. The UML may be used to
visualize, specify, construct and document.

 HTTP(HYPERTEXT TRANSFER PROTOCOL)

It’s a service protocol.

 RAD(RATIONAL APPLICATION DEVELOPER)

It is a development tool that helps to design web pages and also helps to design
the diagrams like ER, Database schema diagrams and to generate DDL.

 HTML(HYPERTEXT MARKUP LANGUAGE)

HTML is a standard markup language for creating web pages and web applications.

 CSS(CASCADING STYLE SHEET)

CSS is a language that describes the style of an HTML document and how HTML
elements should be displayed.

1.5 Document Conventions

<In general this document follows the IEEE formatting requirements. Use Arial font size 11, or 12
throughout the document for text. Use italics for comments. Document text should be single
spaced and maintain the 1” margins found in this template. For Section and Subsection titles
please follow the template.

TO DO: Describe any standards or typographical conventions that were followed when writing this
SRS, such as fonts or highlighting that have special significance. Sometimes, it is useful to divide
this section to several sections, e.g., Formatting Conventions, Naming Conventions, etc.>
1.6 References and Acknowledgments

References:
1. www.w3schools.com
2. http://www.sql-server-performance.com/articles performance.asp
3. www.codeproject.com
4. www.microsoft.com

2 Overall Description

2.1 Product Perspective

The application will be a Windows/Linux based, self contained and independent product.

2.1.1 System Interfaces

List each system interface and identify the functionality of the system(hardware and
software both) to accomplish the system requirement and interface description to match
the system.

2.1.2 User Interfaces

There are registered people in the system employee ,Admin and Manager.
A person should be able to-
 Login to the system through the first page of the application.
 Submit a weekly report to his superior .
 View the submitted and the non-submitted reports.
 Modify the non-submitted report.
 Modify the approvers name and the project code.
 Get help about the Effort Tracker System on how to use the different featuers of the
system.

2.1.3 Hardware Interfaces

 Screen resolution of at least 800 x 600 pixels is required for proper and complete
viewing of screens. Higher resolutions in wide-screen mode will be better for a
better view.
  Support for printer is require. This implies that appropriate drivers should be
installed and printer device should be connected for printing of reports and
marksheets.
 A network connection is required to make the web service accessible on other
systems connected over the network.

2.1.4 Software interfaces

 Any Microsoft Windows 7 and higher or equivalent linux based operating system
with minimum kernel support 3.X.
 PHP, HTML, CSS, JAVASCRIPT, BOOTSTRAP.

2.2 Product Functionality

Following is a list of functionalities of the system.

 User will log on to the application and the login will be based on the role of the user.
The user will directly take into ‘Employee Objective Plan’, where the user can view
the details of the activities and the feedback given by manager.
 The access to the system will be baded on the roles. The roles will be based on
the type of department the user belongs to.
 Login to the system through the first page of the application.
 Submit a weekly report to his superior.
 View the submitted and the non-submitted report.
 Screens should also be provided to the administrator of the system to create the
employee as well as their manager.
 The manager of the user should be able to view the details of the request but
cannot modify the details entered; he can create the objective plan of the employee
working under him.

2.3 Users Characteristics

 Educational level: User should be at least graduate and comfortable with English.
 Experience: User should be well versed/ informed about the structure of the
program. Data entry and modification can be done only by the user suthorized for
this job.
 Technical Expertise: User should be comfortable using general purpose
applications on a computer.
2.4 Operating Environment

Operating environment for the Effort Tracking System is as listed below:-

 Distributed database
 Client – Server system
 Operating system: windows
 Database: SQL database
 Platform: java

2.5 Design and Implementation Constraints

 Since the DBMS being used in this project is My SQL, and the web server is PHP
which are free open source tools the server technologies are out of any guarantees,
unless specifically purchased for enterprise environment.
 Due to limited featured of DBMS being used, performance tuning features will not
be applied to the queries and thus the system may become slow with the increase
of data records being store.
 Due to limited features of DBMS database auditing will not be provided.
 As the application runs over a network environment, well documented security
policy is required to prevent and safeguard data as well as services over the
network.

2.6 User Documentation

<List the user documentation components (such as user manuals, on-line help, and tutorials) that
will be delivered along with the software. Identify any known user documentation delivery formats
or standards.
TO DO: You will not actually develop any user-manuals, but you need to describe what kind of
manuals and what kind of help is needed for the software you will be developing. One paragraph
should be sufficient for this section.>

2.7 Assumptions and Dependencies

 The number of domains being selected by the user does not change.
 The subject types(i.e. elective, core , lab, term paper and dissertation) do not
change.
 The number of semester programs in the client organization remains unchanged.
 3 External Interface Requirements

3.1 User Interfaces Requirements:-

Following screens will be provided by the system.

LOGIN SCREEN

This will be the first screen to be displayed. It will allow the user to acess different sections of the
system according to the user’s role. Various fields available to screen will be as follows:-

USER ID:- String of alphanumeric characters upto length 10 characters.

PASSWORD:- String of alphanumeric characters upto length 10 characters.

ROLE:- This attribute will describe the privileges provided to users according to their roles :
Administrator , Manager , Employee and reviewer.

HOME SCREEN

This screen will be accessible to users with assigned role . it will allow the user to check the related
information according to roles like employee, manager etc. Home screen contain different
information for each type of user.

OBJECTIVE PLAN SCREEN

This screen will be accessible to all users, it contain the objective plan of the user and show the
marks in different categories according to their performance.

3.2 Hardware Interfaces

 Screen resolution of at least 800 x 600 pixels is required for proper and complete
viewing of screens. Higher resolutions in wide-screen mode will be better for a
better view.
 Support for printer is require. This implies that appropriate drivers should be
installed and printer device should be connected for printing of reports and
marksheets.
 A network connection is required to make the web service accessible on other
systems connected over the network.
3.3 Software Interfaces

 Screen resolution of at least 800 x 600 pixels is required for proper and complete
viewing of screens. Higher resolutions in wide-screen mode will be better for a
better view.
 Support for printer is require. This implies that appropriate drivers should be
installed and printer device should be connected for printing of reports and
marksheets.
 A network connection is required to make the web service accessible on other
systems connected over the network.

3.4 Communication Interfaces

 Client(customer) on Internet will be using HTTP/HTTPS protocol.

 Client(system user) on Internet will be using HTTP/HTTPS protocol.

4 System Product Features

4.1 Security

The application will be password protected. Users will have to enter correct username,
password and role in order to access the application modules allowed to their privilege.

4.2 Maintainability

The application will be password protected. Users will have to enter correct username,
password and role in order to access the application modules allowed to their privilege.

4.3 Portablity

The application will be easily portable among any windows or linux based systems that
have IIS web server and Mysql database installed.

UML Diagrams
4.4 E-R Diagram

4.5 Database Design

4.6 Use Case Diagram

4.7 Activity Diagram

4.8 Sequence Diagram