A Software Requirement

Specification
On

EMPCORE System
Swami Keshvanand Institute of
Technology, Management &
Gramothan, Jaipur

In the partial fulfillment of Bachelor of technology

in computer science and Engineering under
Rajasthan Technical University.
Submitted to:
Submitted by:
Prof. Dr. CM Choudhary
11ESKCS717

Empcore System

Deepak Sharma

Page 1

(HOD CS)
11ESKCS718

Deepali Arora

Mrs. Rubal Gill

11ESKCS758

Vijay Kumar

(Senior Lecturer CS)

11ESKCS728

Mahipal Singh

Empcore System

Page 2

Table of contents
1. Introduction
1.1
Methodology
.3
1.2
Purpose
.4
1.3 Scope..
. 4
1.4 Definitions, Acronyms and
Abbreviations. 5
1.5 Tools Used

. 5
1.6 References

. 6
1.7 Technologies to be used
. 6
1.8 Overview

... 6
2. Overall Description
2.1 Product Perspective
..
7
2.2 Software Interface
..
7
Empcore System

Page 3

2.3

Hardware

Interface

8
2.4 Communication Interface
.. 9
2.5 Constraints

9
2.6 Data flow
Diagram
. 10
2.7 E-R Diagram

.. 12
2.8 Database
Design
. 13
2.9Class Diagram

. 15
2.10Use-Case Model

.. 16
3. Specific Requirement
3.1 Activity
Diagrams
.. 17
3.2Sequence
Diagrams
.. 19

Empcore System

Page 4

1.Introduction
1.1 Methodology
Rational Unified Process
The Rational Unified Process brings together elements from all of the generic
process models, supports iteration and illustrates good practice in specification
and design. The RUP is normally described from three perspectives:
A dynamic perspective that shows the phases of the model over time.
A static perspective that shows the process activities that are enacted.
A practice perspective that suggests good practices to be used during the
process.

Empcore System

Page 5

Fig 1.1:Phases of RUP

The different phases in RUP are :Inception

The goal of the inception phase is to establish a separation case for the system.
Identifying all external entities that will interact with the system and defining
these interactions. This information is used to assess the contribution of system
to separate.
Elaboration
The goals of the elaboration phase are to develop an understanding of the
problem domain, establish an architectural framework, develop project plan and
identify key project risks.
Construction
This phase is concerned with system design, programming and testing. Parts of
the system are developed in parallel and integrated during this phase.
Transition
This is the final phase of RUP and is concerned with moving the system from the
development community to the user community and making it work in real
environment.

1.2 Purpose

The EMPCORE System is a cloud-based SAAS (software as a server) solution to

facilitated client companies to manage its employees HR performance and day
to day activities through a simple portal. It is very essential for a company to
manage the activities and performance of employees. This system is helpful for
the interaction among the employees and HR and gets regularly updated about
the company which will help in developing an employees performance. This
system has two end users, the admin and the users.
With this system, the employees will be able to log in to this system and on the
basis of this. His regular attendance and more things can be managed such as
suggestions, leaves, upcoming events, and notices by the admin with some
restrictions for the user. With each entry of an employee the regarding database
will be updated and as well as it will be displayed on the dashboard. The admin
have all the rights to update or view each and every information of the
employee.

1.3 Scope
Empcore System

Page 6

EMPCORE is a heaven for the company administrator and employees. It contains

all the basic requirements for them. Some of the real examples are HTML, CSS,
and PHP etc. Since these software in bulk quantities, hence they require some
sort of software with proper database for handling the records and a simple user
interface to make its handling easy. We hereby present software that allows the
administrator to maintain records, update all the system and create a user
friendly interface for convenience.
Since, success of EMPCORE depends on its proper management, a balance has
to be maintained between income generated and cost incurred. This software
helps in those areas by providing a proper balance and thus ensuring a proper
administration for the software.

1.4 Definitions, Acronyms and Abbreviations

CSS
Cascading Style Sheets (CSS) is a style sheet language used for
describing the look
and formatting of a document written in a markup language.
PHP
Server side scripting language designed for web development but also
used as a
general purpose programming language
ADMIN
Administrator: He has the authority to add/delete users, grant
permission to students and departments.
UML
Unified Modeling Language is a standard language for writing
software blueprints. The UML may be used to visualize, specify,
construct and document.
XML
Extensible Markup Language is a text based format that let
developers describe, deliver and exchange structured data between a
range of applications to client for display and manipulation.
HTTP
Hypertext Transfer Protocol: Its a service protocol.
RAD
Rational Application Developer 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.

1.5 Tools Used

Application architecture PHP, Javascripts, CSS
Apache Tomcat
The E-Separation System has been deployed on APACHE TOMCAT7.0 SERVER which help us to run
the portal online.
Empcore System

Page 7

Heidei SQL It is a free and open source client, or frontend for MYSQL and
its forks like MariaDB and Percena Serer.
PHP Storm - It is a commercial, cross-platform IDE for PHP built
on JetBrains IntelliJ IDEA platform. It provides an editor
for PHP, HTML and JavaScript with on-the-fly code analysis, error prevention
and automated refactorings for PHP and JavaScript code.

Database platform MySQL

MySQL Database is the database management system that delivers a flexible
and cost effective database platform to build robust on demand business
applications and supports the J2EE and web services standards.
Design tool Rational Software Modeler
IBM Rational Software Modeler, (RSM) made by IBM's Rational Software
division, is a Unified Modeling Language UML 2.0-based visual modeling and
design tool. Rational Software Modeler is built on the Eclipse open-source
software framework and includes capabilities focused on visual modeling and
model-driven development (MDD) with the UML for creating resilient,
thought-out applications and web services.

1.6 References

Object Oriented Modeling and Design with UML-Michael Blaha, James

Rambaugh.
Software Engineering, Fifth Edition, Pressmen.
PHP - www.W3schools.com
Wikipedia - www.wikipedia.com
Database Management Systems Korth
Complete Reference - PHP - Keogh.

1.7 Technologies to be used

MySQL: Relational Database Management System.

PHP Storm: HTML.
Tomcat Server 7.0
Rational Software Modeler.

1.8 Overview

Proposed System:
Login for students, admin and departments.
Our Plan:
Empcore System

Page 8

Login for students.

Online maintenance of student record.
Online payment facility.
Updating student records.

2. Overall Description
2.1 Product Perspective

Fig 2.1 Product Perspective

2.2 Software Interface

Client on Internet
Web Browser, Operating System (any)
Client on Intranet
Web Browser, Operating System (any)
Web Server
Empcore System

Page 9

Apache Tomcat, Operating System (any)

Data Base Server
MySQL, Operating System (any)
Development End
PhpStorm (PHP, JavaScript, HTML, CSS), MySQL, OS (Windows),Tomcat(Web
Server)

2.3 Hardware Interface

Minimum Requirements:de
Processor RAM Disk Space

Client Side

Internet Explorer - 6

Processor

RAM

Disk Space

Intel Pentium III or AMD

-800 MHz

128 MB

100 MB

Server Side
PHP STORM

Processor

RAM

Disk Space

Intel Pentium III or AMD

-800 MHz

1 GB

3.5 GB

256 MB

500 MB (Excluding
Data
Size)

MySQL

Recommended Requirements:
C
Client Side
Empcore System

Page 10

Processor

RAM

Disk Space

Internet Explorer - 6
All

Intel or AMD - 1 GHZ

256 MB

100 MB

PHP STORM

All Intel or AMD - 2 GHZ

Server Side
MySQL

2 GB

3.5 GB

512 MB

500 MB
(Excluding Data
Size)

2.4 Communication Interface

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

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

2.5 Constraints

Login and password is used for the identification of users.

GUI is only in English.
Limited to HTTP/HTTPS.
This system is working for single server.

Empcore System

Page 11

2.6 Data flow diagram

0-Level

Validate
user

Control

Login

Student

E-Separation
Admin

Check
status
Online
payment

Updation

1-level

User

Empcore System

Check
status

Login
Departments
Page 12
process

Access

Confirmation
Login
Rejectio

Admin

2-Level
Valid for separation

Student

College database

Library

Hostel
Canteen

Accounts

Login
Rejection

Empcore System
Confirmatio

Login
process
Page 13
Login database

Admin

2.7 E - R diagram

Empcore System

Page 14

2.8 Database Design

Tables
Attendance Table
Serial No
1
2
Empcore System

Field name
User_Id
Eminence

Data type
Int
Enum
Page 15

Constraint
Foreign Key

3
4
5
6
7
8

In_Time
Out_Time
Dates
Status
Created_Date
Modified_Date

Time
Time
Date
Enum
Datetime
Datetime

Serial No
1

Field name
Role_Id

Data type
Int

2
3

Role_title
Role_Descripti
on

Varchar
Varchar

Field name
Sug_Id
User_Id
Dislikes

Data type
Int
Int
Int

Constraint
Foreign Key

Field name
Sug_Id
User_Id
Likes

Data type
Int
Int
Int

Constraint
Foreign Key

Role Table
Constraint
Primary key,
Auto
Increment

Dislike Table
Serial No
1
2
3

Likes Table
Serial No
1
2
3
Events Table
Serial no
1
2
3
4
5
Empcore System

Field name
Events_Id
Event
Start_Date
End_Date
Status

Data type
Int
Varchar
Date
Date
Enum
Page 16

Constraint
Primary key

6
7
8
9

Start_Time
End_Time
Created Date
Modified
Date

Time
Time
Datetime
Datetime

Serial no
1

Field name
Leave_Id

Data type
Int

2
3
4
5
6
7
8
9

User_Id
From_Date
To_Date
Leave_Status
Leave_Type
Days
Reason
Leave_Appro
ver
Comment
Created Date
Modified
Date
Status

Int
Date
Date
Enum
Varchar
Int
Varchar
Int

Leaves Table

10
11
12
13

Constraint
Primary
Increment
Foreign Key

key,Auto

Varchar
Datetime
Datetime
Enum

Monthly Table
Serial No
1
Empcore System

Field name
Month_Id

Data type
Int
Page 17

Constraint
Primary Key

2
3
4
5

User_Id
Year
Month
Days

Int
Int
Int
Int

Foreign Key

Field name
Notice_Id
Notices
Status
Created_Date
Modified_Date

Data type
Int
Varchar
Enum
Datetime
Datetime

Constraint
Primary Key

Notice Table
Serial No
1
2
3
4
5

NoticeDislikes Table
Serial No
1
2

Field name
Notice_Id
User_Id

Data type
Int
Int

Constraint
Foreign Key

Noticelike Table
Serial No
1
2

Field name
Notice_Id
User_Id

Data type
Int
Int

Constraint
Foreign Key

Occasion Table
Serial no
1

Empcore System

Field name
Occasion_Id

Data type
Int

Page 18

Constraint
Primary
key,
Increment

Auto

2
3
4
5
6
7

Occasion_Na
me
From_Date
To_Date
Days
Created Date
Modified
Date

Varchar
Date
Date
Int
Datetime
Datetime

Resource Table
Serial no
1

Field name
Resource_Id

Data type
Int

2
3
4

User_Id
Technology
Interview_Dat
e
Interview_Tak
er
Expected
Salary
Current_Comp
any
Current_City
Current_Salar
y
Experience
Resume
Created Date
Modified Date
Status

Int
Varchar
Datetime

5
6
7
8
9
10
11
12
13
14

Constraint
Primary
Increment
Foreign Key

key,Auto

Char
Int
Varchar
Char
Int
Varchar
Varchar
Datetime
Datetime
Enum

Suggestion Table
Serial no
1
2
3
Empcore System

Field name
Suggestion_I
d
User_Id
Sugggestion

Data type
Int
Int
Date
Page 19

Constraint
Primary
key,
Increment
Foreign Key

Auto

4
5
6

Status
Created Date
Modified
Date

Date
Datetime
Datetime

Serial no
1

Field name
Emp_Id

Data type
Int

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

User_Id
First_Name
Last_Name
Date_of_Birth
Addressline1
Addressline2
Addressline3
City
State
Country
Password
Gender
Mobile_no.
Email
Pincode
Language
Roll_Id
Created Date
Modified
Date
Status

Int
Varchar
Varchar
Date
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar
Enum
Big_Int
Varchar
Int
Char
Int
Datetime
Datetime

Users Table

21

Enum

2.9 Class diagram

Empcore System

Page 20

Constraint
Primary
Increment
Unique Key

Foreign Key

key,Auto

2.10 Use Case diagram

Empcore System

Page 21

3. Supportive Diagrams
2.8 Activity diagram
Login activity
Empcore System

Page 22

Separation Activity

Empcore System

Page 23

2.9 Sequence diagram

Empcore System

Page 24

Empcore System

Page 25

Empcore System

Page 26