CONTENTS

1. Abstract .........................................................................................................3

2. Introduction....................................................................................................5-6

2.1. General Introduction

2.2. Project Description

3. System Analysis..............................................................................................7-10

3.1. Objectives of System

3.2. User Requirements

3.3. Hardware And Software Requirements

4. Feasibility Study.............................................................................................

4.1. Economic Feasibility

4.2. Operational Feasibility

4.3. Technical Feasibility

5. Software Design.............................................................................................

5.1. Software Implementation

5.2. Data Flow Diagrams

5.3. About UML

5.4. UML Diagrams

5.4.1. Use Case Diagrams

5.4.2. Activity Diagrams

5.4.3. Class Diagrams

5.4.4. Sequence Diagrams

-1-
6. Database Design.............................................................................................

7. Input and Output Screens...............................................................................

8. Testing .........................................................................................................

8.1. Unit Testing

8.2. Integration Testing

8.3. System Testing

8.4. Validation Testing

8.5. Output Testing

8.6. Acceptance Testing

9. Conclusion......................................................................................................

10. Bibliography...................................................................................................

-2-
 ABSTRACT

Description:

WORK FLOW PLUS is a Work Flow management system for maintaining and managing

the schedules and related details of the employees working on different projects in

different Work Flows. Moreover, the calculation and maintenance of comprehensive

Work Flow-related allowances for the employees is done using the system. This tool is a

Web enabled system with increased efficiency and accuracy.

The main objective of the system is to minimise problems that are faced while

scheduling the employees for the Work Flows and offer a better solution then what exists

currently in the market. The system has been designed to manage the schedule and

maintain the details related to employees working in different Work Flows.

Features:-

 Managing Work Flows (Setting/Editing) for different employees.

 Maintaining information if the employees like the project on which they work,

under the leadership of whom and in which Work Flow.

 Calculation of Work Flow-related allowances for the employees.

 User authentication.

 Different interfaces corresponding to different user-levels.

-3-
-4-
Introduction:

WORK FLOW PLUS is a Work Flow management system for maintaining and managing

the schedules and related details about the employees working on different projects and in

different Work Flows. The calculation and maintenance of comprehensive Work Flow-

related allowances of the employees can be done systematically. The Project involves a

transformation of current platform dependant system to a Web enabled system with

increased efficiency and accuracy.

Basically, employee scheduling is the process of producing daily schedules for

individual employees. And it takes organization’s goals into consideration at different

time schedules that can be monthly, weekly or quarterly. Moreover, it is an important

component of project workforce management.

The main objective of the system is to minimise the problems that might come in

scheduling the employees offer a better solution than what is currently existent in the

market. The system has been designed to take care of schedule management and the

related details about the employees working in different projects and in different Work

Flows.

Organizations in IT pitch for employee scheduling software, basically for some important

reasons:

-5-
 1) 24 x 7 project support requires staff presence at any time of the day.

2) Multiplicity of projects with different levels of criticality are to be maintained

3) To effectively change the employee working hours to ensure that:

a) Project development is not paused due to employee unavailability

b) Employees should not have overwork

c) The 24 hours of the clock are utilized, rather than a “standard working

day”

Features:-

 Managing Work Flows (setting/editing) for different employees.

 Maintaining information about entities like – the project the employee is working

on, his/her leader worked in different Work Flows.

 Calculation of Work Flow-related allowances for the employees.

 Audit trails (containing the history of transactions)

 User authentication.

 Different interfaces corresponding to different user-levels.

 Report generation, printing, publishing and mailing as per requirement that can be

exported to excel sheet

 Provision of employee backup in case an employee not turning up. – To be

implemented with user intervention

 Sending mails to team members whenever there is new schedule or change in

schedule.

-6-
-7-
SYSTEM:

 Designing and implementing the new links.

 Designing and implementing the System for the users.

 Arranging new links in a subject wise.

SYSTEM ANALYSIS:

System analysis will be performed to determine if it is feasible to design information

based on policies and plans of the organization and on user requirements and to eliminate

the weaknesses of the present system.

 The new system should be cost effective.

 To augment management, improve productivity and services.

 To enhance user / system interface.

 To improve information qualify and usability.

 To upgrade systems reliability, availability, flexibility and growth potential.

Objectives of system

The proposed system is an attempt to provide a rich solution to lessen the inconvenience

in handling the cumbersome job of managing and scheduling a large pool of employees

who are to be assigned to different Work Flows. Systematic handling of the schedules in

such a way is a key to increasing its manageability,

-8-
Objective:-

1. The job can be decomposed to convenient modules of setting / editing Work Flow

details as per the project requirements so that they can be implemented easily and

more productively.

2. A comprehensive report generation technique is in place to put on screen the

various categories of reports as per the requirements

3. One manager/team leader is only responsible for his team and can’t have the

details of other teams. This brings in security to the system.

4. The allowances of the employees who work in different Work Flows is calculated

by the system for the benefit of the GAP / Finance department

5. Work Flow swapping is also possible with the new system.

6. The employees can be given the facility to view their Work Flow details as well as

the allowances that they are expected to get.

7. Employee backup facilities can be incorporated in case an employee is not able to

turn up for the designated Work Flow

-9-
User Requirements

1. Setting/Editing Work Flows for Employees Working in Different Projects

and Work Flow Time.

2. Employee can View his/her Work Flows and Allowances.

3. Provision of employee backup in case an employee not turning up.

4. A “Help file” pertaining to different possible queries.

5. The system runs on any platform.

6. Employee can view his/her schedule in calendar form.

7. Automatic Allowances generation.

- 10 -
HARDWARE & SOFTWARE SPECIFICATIONS

3.1 HARDWARE REQUIREMENTS:

Processor : Intel P-IV system

Processor Speed : 250MHz to 833MHz

RAM : 512MB RAM

Hard Disk : 40GB

3.2 SOFTWARE REQUIREMENTS:

Operating System : Windows XP

Database : Sql Server

Server side Technology : ASP.Net

Server side Scripting : ASP

Client side scripting : HTML

Web-Server : IIS

- 11 -
- 12 -
- 13 -
5.1 Software Implementation

Microsoft.NET Framework

The .NET Framework is a new computing platform that simplifies application

development in the highly distributed environment of the Internet. The .NET Framework

is designed to fulfill the following objectives:

 To provide a consistent object-oriented programming environment whether object

code is stored and executed locally, executed locally but Internet-distributed, or

executed remotely.

 To provide a code-execution environment that minimizes software deployment

and versioning conflicts.

 To provide a code-execution environment that guarantees safe execution of code,

including code created by an unknown or semi-trusted third party.

 To provide a code-execution environment that eliminates the performance

problems of scripted or interpreted environments.

 To make the developer experience consistent across widely varying types of

applications, such as Windows-based applications and Web-based applications.

 To build all communication on industry standards to ensure that code based on the

.NET Framework can integrate with any other code.

- 14 -
SQL SERVER

DATABASE

A database management, or DBMS, gives the user access to their data and helps

them transform the data into information. Such database management systems include

dBase, paradox, IMS, Sql Server and SQL Server. These systems allow users to create,

update and extract information from their database.

A database is a structured collection of data. Data refers to the characteristics of

people, things and events. SQL Server stores each data item in its own fields. In SQL

Server, the fields relating to a particular person, thing or event are bundled together to

form a single complete unit of data, called a record (it can also be referred to as raw or an

occurrence). Each record is made up of a number of fields. No two fields in a record can

have the same field name.

During an SQL Server Database design project, the analysis of your business

needs identifies all the fields or attributes of interest. If your business needs change over

time, you define any additional fields or change the definition of existing fields.

- 15 -
- 16 -
5.4 UML DIAGRAMS
Use Case Documentation:

Use Case Diagram

 A use case diagram is a diagram that shows a set of use cases and actors and
relationships.
Contents
 Use case commonly contain
 Use cases
 Actors
 Dependency, generalization and association relationships

- 17 -
Administrator Use Case:

<<includes>>

Login Validation

<<includes>>

Projects Add/Edit/Delete

<<includes>>

Employees Add/Edit/Delete

Administrator

Reports

Change Password

Logout

- 18 -
Project Manager UseCase:

<<includes>>

Login Validation
<<includes>>

Projects Assign/Add/Edit/Delete

Schedules

Project Manager
Reports

Change Password

Logout

- 19 -
Team Leader Use Case:

<<includes>>

Login Validation

<<includes>>

Schedules Add/Edit/Delete

<<includes>>

Allowances Add/Edit/Delete

TeamLeader

Reports

Change Password

Logout

- 20 -
- 21 -
Table Name:

Employee Registration:

- 22 -
Projects:

- 23 -
Work Flow in Work Flow Plus:

- 24 -
Allowances in Work Flow Plus:

- 25 -
Assign Project in Work Flow Plus:

- 26 -
- 27 -
Login Page:

- 28 -
System Administrator Home Page

- 29 -
Project home Page

- 30 -
Assign Project

- 31 -
Add Project:

- 32 -
- 33 -
Edit Project

- 34 -
- 35 -
Delete Project

- 36 -
- 37 -
Employee Page

- 38 -
Add Employee

- 39 -
Edit Employee

- 40 -
Delete Employee:

- 41 -
Report page:

- 42 -
Project Report

- 43 -
Employee Report

- 44 -
- 45 -
Logout

- 46 -
Project Manager

- 47 -
Team Leader Home

- 48 -
Schedule Menu

- 49 -
Add Schedule

- 50 -
Edit schedule

- 51 -
Add Allowances

- 52 -
Report Menu

- 53 -
Employee Report

- 54 -
Schedule Report

- 55 -
Employee report

- 56 -
View Allowances Report

- 57 -
Work Flow Report

- 58 -
10. Conclusion:

 The project has been appreciated by all the users in the organization.

 It is easy to use, since it uses the GUI provided in the user dialog.

 User friendly screens are provided.

 The usage of software increases the efficiency, decreases the effort.

 It has been efficiently employed as a project management mechanism.

 It has been thoroughly tested and implemented.

- 59 -
- 60 -
11. BIBLIOGRAPHY

The following books were referred during the analysis and execution phase of the

project

SOFTWARE ENGINEERING

By Roger’s. Pressman

COMPLETE HTML

Steven Holzner

UNIFIED MODELING LANGUAGE

By Grady Booch, Ranbaugh, Jacobson

SQL FOR PROFESSIONALS

By Jain

C#.NET Black Book

By Evangeleous Petersons

MSDN 2005

By Microsoft

- 61 -
- 62 -