Timely Final

TIMELY

Time Management System

Software Requirements Specification

1.01

24th March, 2015

AKSHAY KUMAR, SOUNAK SAHA, PRATIK SHAW, ANKITA BHATTACHARYYA, HARSHIT TIWARI, ARNAB

CHAKRAVARTY, ISHIT PATEL, RASHMIMAN RAY, SATYA PRAKASH, PRIYANKA SINGH

Lead Software Engineers

Prepared for

CS891- Design Lab

Instructor : Sujoy Saha, Poulami Das

4th Year, 8th Semester

TIMELY

ii

Revision History

Date Description Author Comments

Document Approval

The following Software Requirements Specification has been accepted and approved by the following:

Signature Printed Name Title Date

TIMELY

iii

Table of Contents

REVISION HISTORY ...................................................................................................................................................

DOCUMENT APPROVAL ...........................................................................................................................................

1. INTRODUCTION .................................................................................................................................................. 1

1.1 PURPOSE ................................................................................................................................................................ V

1.3 SCOPE .................................................................................................................................................................... V

1.4 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS ............................................................................................................ V

2. GENERAL DESCRIPTION ..................................................................................................................................... VI

THE BACKBONE OF TIMELY IS A HIGH CAPACITY DIGITAL WORKSTATION LOCATED IN THE SRS CENTRAL

COMPUTER FACILITY CAPABLE OF HANDLING THE TIMETABLE FOR ALL USERS. THIS WORKSTATION GATHERS DATA

FROM A NETWORK OF ALL THE USERS WORKSTATIONS. IN ADDITION, ALL HARDWARE IN THE NETWORK IS

CONFIGURED FOR UNINTERRUPTED POWER SUPPLY USING ADDITIONAL BACKUPS. ................................................... VI

2.1 PRODUCT FUNCTIONS .............................................................................................................................................. VI

2.2 USER CHARACTERISTICS ........................................................................................................................................... VII

THE INTENDED USERS OF THE SYSTEM WILL COMPRISE CO-WORKERS OF VARIOUS DESIGNATIONS OF AN

ORGANIZATION. THE USERS WILL BE FROM DIFFERENT BACKGROUNDS HAVING BASIC COMPUTER KNOWLEDGE. THE

USER INTERFACE WOULD BE MINIMALISTIC IN NATURE AND USER FRIENDLY IN DESIGN CONTAINING A DETAILED

WALKTHROUGH OF THE ENTIRE PROCESS. ................................................................................................................ VII

2.3 ASSUMPTIONS AND DEPENDENCIES ........................................................................................................................... VII

THE USER WORKSTATIONS, EXPECTED TO HAVE PREDEFINED USER TIME TABLES READY, WILL BE INTEGRATED WITH

THE SERVER TO VIEW THE COLLECTED TIMETABLE DATA SHOULD BE CAPABLE OF HANDLING MINIMAL GUI,

SUPPORT 32-BIT ARCHITECTURE AND THE OPERATING SYSTEM SUPPORT HOME GROUPING AND HOSTING

FACILITIES TO ATTACH HARDWARE LIKE PRINTERS ETC. .......................................................................................... VII

3. SPECIFIC REQUIREMENTS .....................................................................................................................................

3.1 EXTERNAL INTERFACE REQUIREMENTS ............................................................................ ERROR! BOOKMARK NOT DEFINED.

3.1.1 User Interfaces ............................................................................................. Error! Bookmark not defined.

3.1.2 Hardware Interfaces ..................................................................................... Error! Bookmark not defined.

3.1.3 Software Interfaces ...................................................................................... Error! Bookmark not defined.

3.1.4 Communications Interfaces .......................................................................... Error! Bookmark not defined.

3.2 FUNCTIONAL REQUIREMENTS ................................................................................................................................... VII

3.2.1 Data Creation and Storage ........................................................................... Error! Bookmark not defined.

3.2.2 Scheduling of meetings ................................................................................ Error! Bookmark not defined.

3.2.3 Notification Module ..................................................................................... Error! Bookmark not defined.

3.3 NON-FUNCTIONAL REQUIREMENTS .......................................................................................................................... VIII

3.3.1 Performance ............................................................................................................................................. viii

TIMELY

iv

3.3.2 Reliability .................................................................................................................................................. viii

3.3.3 Availability ................................................................................................................................................ viii

3.3.4 Security ....................................................................................................................................................... ix

3.3.5 Maintainability ........................................................................................................................................... ix

3.3.6 Portability ................................................................................................................................................... ix

3.4 DESIGN CONSTRAINTS .............................................................................................................................................. IX

4. ANALYSIS MODELS ............................................................................................................................................ IX

4.1 SEQUENCE DIAGRAMS.............................................................................................................................................. IX

4.2 DATA FLOW DIAGRAMS (DFD) .................................................................................................................................. IX

4.3 STATE-TRANSITION DIAGRAMS (STD) ......................................................................................................................... IX

TIMELY

v

1. Introduction

1.1 Purpose

The Software Requirements Specification (SRS) will provide a detailed description of the

requirements for the Time Management System (TMS). This SRS will allow for a complete

understanding of what is to be expected from the newly introduced system which is to be

constructed. The clear understanding of the system and its functionality will allow for the correct software to be developed for the end user and will be used for the development of the

future stages of the project. This SRS will provide the foundation for the project. From this SRS,

the Time Management System can be designed, constructed, and finally tested.

The main objective of this document is to describe the time management system to support the

timetabling of meetings and appointments across a group of co-workers. The purpose of this project is to

find a common slot in each of their diaries and arrange the appointment for that time. This document

contains the functional and non-functional requirements of the project. This project describes the

hardware and the software interface requirements using ER Diagrams and UML diagrams.

1.2 Scope

Time Management System is basically finding a common slot in each of the co-workers diary

and arranging the appointment. If no common slots are available, it interacts with the user to

rearrange their personal diary to make room for the appointment.

The project is specifically designed for the use of employees of an organization. The product will

work as a complete user interface for the time tabling management process for the employees.

The project can be easily implemented under various situations. We can add new features as and

when we require, making reusability possible.

1.3 Definitions, Acronyms, and Abbreviations

J2EE Java 2 Enterprise Edition

SQL Structured Query Language

TIMELY

vi

2. Overall Description

The backbone of Timely is a High Capacity digital workstation located in the SRS central

computer facility capable of handling the timetable for all users. This workstation gathers data

from a network of all the users workstations. In addition, all hardware in the network is configured for uninterrupted power supply using additional backups.

2.1 Product Functions

Project In-

charge

View

Insert

Update

Delete

Add

Update

Delete

Add

Update

Meeting Schedules

Daily Schedules

Routine Diary

Details

Database

Meeting

Details

Meeting Details

Delete Meeting Details

Make Schedules Meetings

Employees

Administrator

TIMELY

vii

The System is designed to integrate data from various sources and:

(A) Find a free common slot for meetings/appointments for the participating members.

(B) If a common slot is found, then the concerned users are notified of the appointment for that

time and date.

(C) If no common slot is found, then the users are notified to reschedule their timetable.

2.2 User Characteristics

The intended users of the system will comprise co-workers of various designations of an

organization. The users will be from different backgrounds having basic computer knowledge.

The user interface would be minimalistic in nature and user friendly in design containing a

detailed walkthrough of the entire process.

2.3 Assumptions and Dependencies

The user workstations, expected to have predefined user time tables ready, will be integrated

with the server to view the collected timetable data should be capable of handling minimal GUI,

support 32-bit Architecture and the Operating System support Home Grouping and hosting

facilities to attach hardware like printers etc.

3. Specific Requirements

3.1 Data Creation and Storage

1. The employees(Executives) create and manage their own diaries for their daily

timetables.

2. Any update in employees diary by the employees is immediately stored in the database

for processing when required.

3. An administrator creates and manages a group diary which keeps track of the date, time

and the executives involved in meetings that are scheduled.

3.2 Scheduling of meetings

1. A project in-charge initiates a request for a meeting via the application.

2. He enters the names of the employees who are to be involved in the meeting.

TIMELY

viii

3. The application then accesses the database and retrieves the timetables for all the

concerned employees.

4. The application then processes the retrieved timetables of the concerned users and

finds the first available common free slot for the meeting.

5. In case a free slot is not found then the output is sent to the notification module which

then notifies the concerned employees to re-aarrange their schedules in their diaries.

6. In case a free slot is found the administrator is informed of it and also outcome is then

forwarded to the notification module.

7. The administrator confirms and books that slot for the meeting with specified

employees in the group diary.

3.3 Notifying the concerned users

1. If the meeting has been successfully scheduled, then the venue, date and time of the

meeting is sent to the concerned employees.

2. If the meeting cannot be scheduled because of unavailability of free common time

slot, then the employees notified to alter their schedules in order to create a unanimous

free time slot for the meeting.

3.3 Non-Functional Requirements

3.3.1 Performance

Timely is capable of collecting data from its sources as and when a user updates his/her time table on

his/her respective workstation or when a meeting is to be scheduled.

3.3.2 Reliability

Timely will be highly reliable as the system has built-in error handling capabilities.

3.3.3 Availability

Timely operates and store its data in the server so that it is available to the users at all times who wish to

fix an appointment.

TIMELY

ix

3.3.4 Security

Timely is a highly secure system as required by the company policy to prevent sniffing and the raw and

archived data are not available to users without proper security clearances.

3.3.5 Maintainability

Timely will be designed keeping in mind that its immediate users have low computing

knowledge so the design and structure of the system would be kept minimal and can be maintained by anyone

by giving them some hours of formal trainings to handle it.

3.3.6 Portability

Timely will be designed with interface compatible with both UNIX and WINDOWS System.

3.4 Design Constraints

The Design frameworks and protocols to be used complies with the design standards of the

organisation.

4. Analysis Models

4.1 Sequence Diagrams

4.2 Data Flow Diagrams (DFD)

4.3 State-Transition Diagrams (STD)

Documents

Timely Final