CORPORATE EMPLOYEE WELFARE Software Requirements Specification Team ABC
Version 3 18th March, 2015
Team ABC
CORPORATE EMPLOYEE WELFARE Software Requirements Specification Specification
Version 3
Team Guide: Prof. Senthilnathan Members: Vartika Dwivedi (12bce0409), Krishna Nand Pandey (12bce0027), Ankit Aggarwal(12bce0433)
College Name: VIT University Department: Computer Science
1|Page
Team ABC/ VIT
PREFACE
This document represents the Software Requirements S pecification for the Web Application Project on Corporate Employee Welfare. The document begins with an Introduction section that describes the purpose of the document and what is considered to be in the scope of this document as well as what is outside the scope of this document. The next section is an Overall Description of the requirements and functions. This section includes the overall constraints that the project is working within as well as the assumptions made by the project as far as the defining the requirements is concerned. Lastly, the project dependencies are also listed in this section. The Specific Requirements section comes next and is the most important section of this document. The Specific Requirements section also describes the Functional and Non Functional Requirements that are to be met by the Corporate Employee Welfare.
2|Page
Table of Contents 1.0
Introduction
1.1
Purpose
1.2
Scope
1.3
Definition, Acronyms, and Abbreviations
1.4
References
1.5
Technologies to be used
2.0 Overall Description
2.1
Product Perspective
2.2
Work Breakdown Structure
2.3
Product Function
2.4
User Characteristics
2.5
Constraints
2.6
Use Case Diagram
2.7
Assumptions and Dependencies
2.8
Stake holders and Process Model Identification
2.9
Project Scheduling
3.0
Requirements
3.1 Functional requirements 3.2 Non-functional requirements 3.3 Software Interface 3.4 Hardware Interface
4.0 User Interface Screen 3|Page
LIST OF FIGURES AND TABLES WORK BREAKDOWN STRUCTURE (FIGURE) USE CASE DIAGRAM (FIGURE) USE CASE DESCRIPTION (TABLE) TIMELINE CHART (FIGURE) PERT CHART (FIGURE) GANTT CHART (FIGURE) USER INTERFACE SCREENS (FIGURE)
4|Page
PAGE NO. 6 8 8 9 10 10 12- 14
Software Requirements Specification 1.0
Introduction:
Corporate Employee Welfare is the Web based application. Corporate Employee Welfare means “the efforts to make life worth living for workmen. It also means anything done for the comfort and improvement, intellectual or social, of the employees over and above the wages paid which is not a necessity of the industry. . The system has the facility to give a unique id for every employee and stores the details of every employee and the staff automatically.
1.1
Purpose:
In this project, the user can easily perform some basic functionalities like upload, Report generation. It helps the employees to perform complex task very easily. The admin can also see what their employees are currently doing instead of going and asking them. It will provide a platform for sharing views, leave proposal, claim and project proposal. The main purpose of this application is to maintain data easily in tabular form as well as it provides the facility of editing data in an easy way. However this application can easily understand by everyone and less time consuming.
1.2 Scope: The Scope of the Corporate Employee Welfare includes: There are two basic user : Employee and Admin Registration and Login for employees Project proposal by employees including project details Leave application by employee followed by approval by Admin Posting information regarding meetings and seminars Application for promotion by employees Claim
1.3 Definitions, Acronyms, and Abbreviations: HTML (Hyper Text Mark-up Language): It is used to create static web pages. MYSQL Database: It is a database management system that provides a flexible and efficient
database platform to raise a strong "on demand" business applications. CSS (Cascading Style Sheets): It is used to give style to web pages. HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server protocol between
a web browser and a web server
5|Page
1.4 References: a. www.wikipedia.com b. www.w3schools.com
1.5 Technologies to be used:
MYSQL: Relational Database Management System. RATIONAL ROSE SOFTWARE Microsoft Visio Stylesheet Komodo Edit: HTML editor
2.0 Overall Description: 2.1Product Perspective: The Corporate Employee Welfare is for the benefit of the employees. It helps them to do tedious task in a simple way. It helps them in increasing their productivity and in turn increasing the productivity of the organisation. The system accesses the databases of the organization to make the request and approval easy. The employees is given front end dashboard to access all the functions provided.
2.2 Work Breakdown Structure
CORPORATE EMPLOYEE WELFARE
Registration and login
Meetings and Seminars
1.Future Meetings 2.Seminars
6|Page
Leave Management
1.Leave approval 2.Reimbursement
Project Management
1.Project proposal 2.Join Project 3.Project Approval
Search
Claim
2.3Product Functions:
The following are the functions of CEW:The employee of all ranks can register in CEW by providing their basic details. Employees can search for other employees by providing the employee id. Employees can apply for leave. They can post their ideas for new project or can join existing project. They can share details of meetings and seminars. They can also apply for promotions based on their qualification. They can also claim for reimbursement.
2.4User Characteristics: The CEW application will consist of two users- Employee and Admin. It provides high user interface. Only admin has access to the database. He can change or update the database. Employees require only basic knowledge of compu ters. User or employee can apply for leave, can post their project ideas, can claim for reimbursement and can share details of meetings and seminars.
2.5 Constraints: 1. Login and password is used for the identification of users. 2. Only registered employees will be authorized to use the services. 3. Limited to HTTP/HTTPS. 4. This system is working for single server. 5. Migration of all existing employee data on paper to the database.
7|Page
2.6 Use Case Diagram :
USE CASE Registration & Login Authentication Leave Application Leave Approval Experience & Qualification Promotion Project proposal Project Approval Meetings & Seminars Claim Bills and Proofs
8|Page
DESCRIPTION Employees will login by their registered id Admin will give them authentication Employees will apply for leave Admin will approve the leave Employees will post about their Experience and Qualification Employees will apply for promotion Employees will propose a new project or join existing one Admin will approve the project according to its feasibility Employees and admin will post about meetings and seminars Employees can claim for reimbursement Employees need to upload bills and proofs for claim
2.7Assumptions and Dependencies:
Employees will be consisting of unique id Admin provide the authentication Only limited information of employees will be shared All the decision is made by admin only Every employee has access to all the features of CEW
2.8 Stake Holders and Process Model Identification
Users- Employees are users who will interact with the system and use the services provided by the software. Developers- Developers require tools and software to implement the dema nds of users. Decision Makers / CSR Officials- Within the organisation there will be decision making structure that relate to the system under development. These include the managers of the developer team, user manages in both user and developer side. In this project we are using V model. V- Model means Verification and Validation
model. Just like the waterfall model, the V-Shaped life cycle is a sequential path of execution of processes. Each phase must be completed before the next phase begins. Testing of the product is planned in parallel with a corresponding phase of development.
Advantages of V-model:
Simple and easy to use. Testing activities like planning, test designing happens well before coding. This saves a lot of time. Hence higher chance of success over the waterfall model. Proactive defect tracking – that is defects are found at early stage. Avoids the downward flow of the defects. Works well for small projects where requirements are easily understood.
2.9Project Scheduling TIMELINE CHART
9|Page
PERT CHART
GANTT CHART
10 | P a g e
3. Requirements 3.1 Functional Requirements 3.1.1 User Registration and login - employee can register and get unique id and password for the login Project Management – employee can suggest, propose, and can join with other projects Leave Management – employee can apply for leave Meetings and Seminars – employee can get and share information regarding meetings and seminars Promotion – employees can apply for promotion which will be approved by admin based on their qualification 3.1.2 Admin Authentication of employee information Leave approval Project approval and suggestions Update information regarding meetings and seminars
3.2Non Functional Requirements Usability- helps the employees to share the ideas, innovate, connect and work in effective
and healthy manner Security- System is authenticated so once the employee is registered he gets a unique id and password Availability- application will be available for 24*7 for both user and admin Privacy- only limited information of the user is shared. Portability – the system will run on windows xp, vista, 7, and 8 Capacity- it has the capacity to register all the employees of the organization Performance – there will be no delay in functioning of CEW
3.3 Software Interface: Client on Internet Web Browser- Chrome, Mozilla, Internet Explorer, Operating System- Windows 7, 8 Client on Intranet Web Browser- Chrome, Mozilla, Internet Explorer, Operating System- Windows 7, 8
Data Base Server MYSQL, Operating System -Windows 7, 8
Development End PHP, HTML, AJAX, JAVASCRIPT, CSS, MYSQL, OS (Windows)
11 | P a g e
3.4 Hardware Interface: Client Side: Browser- Internet Explorer - 6 Processor- Intel Pentium III or AMD -800 MHz RAM- 128 MB Disk Space- 100 MB Server Side: Browser- Internet Explorer - 6 Processor- Intel Pentium III or AMD -800 MHz RAM- 1 GB Disk Space- 3.5 GB
4 User Interface Screens:
12 | P a g e
13 | P a g e
14 | P a g e
15 | P a g e
16 | P a g e
17 | P a g e
