Leave Management System

ONLINE HOTEL MANAGEMENT SYSTEM


A PROJECT SYNOPSIS

Submitted by

in partial fulfillment for the award of the degree

of

BACHELOR OF BUSINESS ADMINISTRATIONIN

INFORMATION TECHNOLOGY

VASANT KUNJ, NEW DELHI

SEPTEMBER 2011

CERTIFICATE FOR PROJECT


This is to certify that this is a bonafide record of the project work done

satisfactorily at ------------- by the following students in the partial fulfillment of

BBA V Semester Examination-

This report or similar report on the topic has not been submitted for any other

examination and doesn’t form a part of any other course undergone by the

candidates.

Date: Place: Project Guide

University, Delhi)Vasant Kunj, New Delhi


ACKNOWLEDGMENT

I would like to thank for introducing us to the field of

and for her professional guidance and direction during the entire length of our

project at the ----------I would also like to thank my Project advisor

for his guidance, support and patience. Their experience and

expert knowledge inspired us to reach beyond our previous limits and capabilities.

We are also grateful to , our teacher for his support and excellent

corrections.

Last but not the least; we would like to thank all those people who directly or

indirectly contributed for helping us in the successful completion of the project.

Thank you


ABSTRACT

This project entitled “Online Hotel Management System” is the software that deals

with the problem of storing employee’s leave details in a manual way. The project

planning is to automate an organization’s day-to-day and monthly dealings with

employee leaves like new leave, cancel leave, etc.

The information provided by this software will be of great use in managing all the

records of various employees and their respective leaves. It also checks the entered

data before storing any specific record to the database. This software is very user-

friendly and can be mastered with very few efforts.

As the existing system required a lot of stress in maintaining records and producing

reports, hence this computerized system of the existing manual system is

undertaken for increasing the efficiency in terms of speed and accuracy of

information in reports. Standardization of all the activities at various levels for

uniformity, ease of maintenance and an ultimate aim to achieve the effortless

generation of reports makes this software an intelligent investment.

This software is developed on the platform Microsoft Visual Basic 6.0 as the

front-end and Microsoft Access 2007 as the back-end. The software is running

efficiently.


TABLE OF CONTENTS

Chapter 1 Introduction

1.1Objective

1.2 Need for the system

1.3 Characteristics of proposed system

1.4 Scope of the project

1.5 Advantages of proposed system

Chapter 2 System Requirements

2.1 Hardware Requirements

2.2 Software Requirements

Chapter 3 System Specification

3.1 Security

3.2 Maintainability

3.3 Portability

3.4 Feasibility

Chapter 4 System Design

4.1 System Design

4.2 Design Principle

4.3 Design Concepts

4.4 Project Execution Model

4.5 Database


Chapter 5 Implementation and Coding

Chapter 6 Software Testing

6.1 Objectives of testing

6.2 Testing Principles

6.3 Verification and Validation

6.4 Types of Testing

6.5 Testing procedure

Chapter 7 Utilities in the system

Chapter 8 Conclusion


Chapter 1

INTRODUCTIONLEAVE MENEGEMENT SYSTEM

AN OVERVIEW

This system “LEAVE MANAGEMENT SYSTEM” has been designed for

maintaining the records of employees and their respective leave applications to the

college. Till now our college has been recording the leave applications of

employees manually in the form of a file called dak file.

As from the security and discipline perspective it is very important to have all

records of all leaves of an employee, and in this system the margin of error is very

less.

Keeping in mind all the above aspect, a computerized version of leave

management has been designed which we think will be very beneficial and is

strongly needed by our college


1.1 Objectives

The main objective of any computerized system is to minimize the manual work

performed. As our project reduces the register work or manual work of the gate

keeper as all the entry system has been computerized. Objective of our system is to

minimize and overcome the limitations of manual work.

This computerized system possesses a good GUI which provides an ease of

support to the administrators and to perform their task in a very efficient manner

and this work is also effective in nature. This system is also capable of generating

error free reports that describes all records and custom reports can also be

generated. The handling of this project is also very simple so that anyone can

understand it easily. And this system is also very beneficial from the security point

of view.

1.2 Need of the system

In today’s fast changing world of technology every organization is in want of fully

utilization of time and space in order to be counted in the lists of worlds highest-

ranking organizations.

In order to this each organization is making itself fully computerized.

Computerization also helps organization to minimize paper work as well as

manpower. In this revolution software engineers play a vital role. Software

packages provided by them help organization to maintain records of faculties,

students and visitors, automatic calculation of time consuming problems and in lot

of other work that involves a lot of time and manpower.


The project “Leave Management System” does the same.

The system helps in (need of system):

Registering a new employee.

Removing the record of an employee who has left the institute.

Modifying information about an employee.

Searching for information about an employee

Updating the records.

Adding leave applications of an employee.

Cancelling leave.

1.3 Characteristics of proposed system The manual dealing of preparing reports is a very tedious job, as administrator first

needs to search for applications from the dak file and then presenting those in the

form of reports. Thus we need to automate this process to systemize and fasten up

the overall system, as through computerization enormous data will become easily

accessible. The system should be distributive in nature; it should be designed to

provide functionalities as explained below:

Database can be accessed by the Administrator.

Maintains the employee information and leave applications.

Administrator can take the backups and generate reports of any or all the

databases.


1.4 Scope of the work

As in today’s world there is nothing perfect, so there is always a chance of scope in

every aspect of project. At this point of time our project is a standalone application

whereas it can be converted into a fully automated system, reducing the paperwork

to close to zero. Also in this the administrator has to enter the unique ID of an

employee into the forms of Visual Basic which consumes time.

We can improve this project further by using web services and fully automating it

where-in applications can be submitted online and receive the corresponding

response by e-mail. The data can be stored centrally at the server terminal.

1.5 Advantages of proposed system

With the feature of Login ID and password , data becomes more secure ,

as only the person who has the password and login id can view or modify

records , rest no one can enter the system without password.

It provides a better and faster way of managing and maintaining various

leave applications and related employee details.

Time wastage is minimal, as all records and reports are just a click away.

This system is an efficient, secure, tidy and fast way to manage so many

records.


Chapter 2

SYSTEM REQUIREMENTS

2.1 Hardware requirements

2 GB Hard Disk(minimum requirement)

128 MB RAM

Supports for printer (Dot Matrix / Inkjet / Laser printer)–that is,

appropriate drivers are installed and printer connected. Printer will be

required for printing of reports.

Standalone system or network based system- not a concern, as it will

be possible to run the application on any of these.

Processor- Pentium 166MHz or above

Monitor with appropriate resolution and color quality for proper and

complete viewing of screens.

2.2 Software requirements

Any windows-based operating system (Windows-98/2000/XP/NT)


Visual Basic 6.0 – for coding/developing the software

MS Access- for database

PLATFORMS

VISUAL BASIC AS VISUAL PROGRAMMING LANGUAGE

VISUAL BASIC follows an event driven programming approach. The user

interface is designed first with all the required controls placed on the user interface

form. Customizing their properties modifies these controls. After the user interface

is designed the events that occur in the application are decided and are relating to

their respective controls. Every control is associated with its respective events to be

trapped.

VISUAL BASIC APPLICATION DEVELOPMENT

The figure shows the steps that all visual basic developers follow as they prepare

projects: -

Design and build

user interface

Write event

driven code

Create and call

other procedures

Test and debug

Prepared

distribution file


The prototypical visual basic development cycle

The steps mentioned above aren’t symmetrical. Some steps take longer than other

do and there is repetition of several steps as the initial application is design is

refined and enhanced. Most of the development time is spent in the first four steps.

Even the most complex visual basic projects follow the steps described above.

Most of time is spent in building the user interface and writing the code required

by the application.

UNDERSTANDING THE ADVANTAGES OF VISUAL BASIC

Let’s take a minute to review some of the features that make visual basic such a

robust and exciting development platform. The following key points make visual

basic an excellent development tool: -

1 Visual Basic Application Are Event Driven - Event driven means the user is in

control of the application. The user generates a stream of events each time he

clicks with mouse or presses a key on the keyboard. Your visual basic application

respond to those event a through the codes written and attached to those events.

2 Visual Basic Supports The Principals Of Object Oriented Design - This

means that you can comport mentalist different aspects of your application as

object and develop and test those objects independently of the rest of the

application.


3 Microsoft Has Designed Visual Basic To Be A Complete Window Development

System - This means that your visual basic application will look and behave like

other windows program user might work with.

4 Visual Basic Is Infinitely Extensible Through The Use Of Active X, Controls,

Dynamic Link libraries (DLL’S) And Add

MS-ACCESS 07

Microsoft (MS) Access is relational database management system (RDBMS) used

to stored and manipulate large collection of information of any kind. Here RDBMS

refers to the organization of data in a series of rows and columns in such a manner

that any specific piece of information is available with the click of a mouse and a

few keystrokes. MS-Access has tools, which are easy to used and provide powerful

development environment, making it an appropriate choice for novices as well as

professional.

There are different ways in which an application with multiple components that

includes, Access can be integrated. A component (in Microsoft terminology) is an

application or development tool that makes it objects available to other

applications. Using automation in Visual Basic it is possible to work with objects

from other components to construct a seamless integrated application. Using the

Object Linking and Embedding (OLE) technology, a user can include documents

created in another component on a report or form within Access. Automation and

OLE are distinct technologies, which are a part of the Component Object Model

(COM), a standard proposed by Microsoft.


Microsoft Access is used as backend because: -

1. It is easy to use.

2. It can be integrated / connected easily with a Visual Basic.

3. No programming skills required to work with.

4. The database access time is better than other database Software.

5. Access uses ‘structured query language (SQL)’, which is English like

language, and makes interaction between user and the database very simple. It

helps in easy creation, manipulation and modification of the database.

Chapter 3

SYSTEM SPECIFICATIONS

3.1 Security


The application will be password protected. The user (administrator) will have to

enter the correct username and password in order to access the application.

3.2 Maintainability

The application will be designed in maintainable manner. It will be easy to

incorporate new requirements in the individual modules.

3.3 PortabilityThe application is easily portable on any Windows-based system.

3.4 FeasibilityThe economical and technical factors are considered to be feasibility study of the

system.

ECONOMICAL FEASIBILITY

1. No manpower cost is incurred in this proposed system as the system has

been developed as project work.

2. The system has been developed in an environment where no hardware &

software facilities have to be installed for the purpose of development.

3. The cost entailed in this respect was nil.

TECHNICAL FEASIBILITY

1. The existing hardware & software facilities are sufficient for development

of this proposed system. However at the beginning of the project, the P-II

400MHz machine was enough for the work. Soon we realized that machine


is little bit slower for some complicated data retrieval & it will keep the user

unnecessary waiting for the result to pop-up on the screen.

2. So the project was relocated to P-IV machine. Thus no additional costs are

incurred during the development of the project.

OPERATIONAL FEASIBILITY

Here we consider the extent to which the proposed system will fulfill any

administrator’s requirement. That is whether the proposed system covers all

aspects of the working system or it has considerable improvements.

BEHAVIORAL FEASIBILITY

A disputation of any kind of change in existing system may be appeared by users.

But in the “Leave Management System” there may be less chance of having any

opposing views because this software is easy to operate and increases the

efficiency in user operation. Because of its simplicity, any user can easily be

trained to use the software.

Chapter 4

SYSTEM DESIGN

Requirement elicitation


Interview- an interview was conducted with (Accounts Head,). Mr. Joshi is

responsible for managing pay roll for all employees in and also for maintaining

leave records. thereby, we concluded that he would be the right to person to gather

requirements from. Questions asked were as follows:

1.1How are you maintaining records?

1.2Problems with existing system?

1.3 Any calculation errors?

1.4 Any requirement of data from other system?

1.5 Any specific problem?

1.6 Any additional functionality desired?

1.7 What are the organization’s policies regarding leave of an employee

Time (in person-months) estimation

We now know that the proposed system is of organic type, having 1484LOC

(Lines Of Code).

By organic type we mean, that the proposed system is simple and is being

developed by experienced professionals in a very familiar environment. The source

code of organic type ranges from 1 to 50 KLOC.

E(Effort) = ab(KLOC)b

D(Development time) = cb(E)d

Where, ab=2.4 bb=1.05 cb=2.5 db=0.38


E= 2.4(1.5)1.05

=3.96 person- months

=3 (approx.)

D =2.5(1.5)0.38

=3.16 months

=3(approx.)

It implies that if 3 persons had worked on this project then it would be completed

in 3 months time. However, we had a time limit of 2 months thereby reducing the

number of development months. To overcome this problem 2 more developers

were introduced in the team to compensate and speed up the process.

4.1 System designDesign is a meaningful engineering representation of something to be built.

Software design is the first of three technical activities- designs, code generation

and tests- that are required to build and verify the software. Design focuses on the

four major areas of concern- data, architecture, interfaces and components.

The Data design transforms the information domain model created during

analysis into the data structures that will be required to implement the

software. The data objects and relationships defined in the ERD provide the

basis for the data design activity.

The Architectural design defines the relationship between major structural

elements of the software, the "design patterns" that can be used to achieve

the requirements that have been defined for the system. The architectural

design representation i.e. the framework of a computer based system can be

derived from the system specification, the analysis model and the interaction


of subsystems defined within the analysis model.

The Interface design describes how the software communicates with itself,

with systems that interoperate with it. An interface implies a flow of

information and a specific type of behavior. Therefore, data and DFDs

provide much of the information required for interface design.

The Component-level design transforms structural elements of the software

architecture into a procedural description of software components. The

importance of software design can be stated with a single word- Quality.

Design is the only way that we can accurately translate a customer's

requirements into a finished software product or system.

4.2 Design principlesSoftware design is both a process and a model. The design process is a sequence of

steps that enable the designer to describe all aspects of software to be built.

The design model is the equivalent of an architect's plans for a house.

The design process should not suffer from "tunnel vision"- a good designer

should consider alternative approaches, judging each based in the

requirements of the problem.

The design should be traceable to the analysis model- it is necessary to have

a means for tracking how requirements have been satisfied by the design

model.

The design should exhibit uniformity and integration- rules of styles and

format should be defined for a design team before design work begins. A

design is integrated if care is taken in interfaces between design components.

The design should be structured to accommodate change

The design should be structured to degrade gently, even when aberrant data,

events or operating conditions are encountered- it should be designed to

accommodate unusual circumstances.


Design is not coding, coding is not design- when detailed procedural

designs are created for program components, the level of abstraction of the

design model is higher than source code. The only design code level address

the small implementation details that enable the procedural design to be

coded.

The design should be reviewed to minimize conceptual (semantic) errors- a

design team should ensure that major conceptual elements of the design have

been addressed before worrying about the syntax of the design model.

4.3 Design conceptsThe beginning of wisdom is to recognize the difference between getting a program

to work, and getting it right. Fundamental software design concepts provide the

necessary framework for “getting it right”.

ABSTRACTION

When we consider a modular solution to any problem, many level of

abstraction can be posed. At the highest level of abstraction, a solution is

stated in broad terms using the language of the problem environment. At

lower level of abstraction, a more procedural orientation is taken. Finally, at

lowest level of abstraction, the solution is stated in a manner that can be

directly implemented.

REFINEMENT

Refinement is a process of elaboration. Refinement causes the designer to

elaborate on the original statement, providing more and more detail as each

successive refinement occurs. It helps the designer to reveal low-level

details as design progresses. It aids the designer in creating a complete

design model as the design evolves.

MODULARITY


Software is divided into separately named and addressable components,

often called modules that are integrated to satisfy problem requirements.

4.4 Project execution modelIn this, we are developing an application phase developing process to manage the

complexity, better project tracking, and quality to achieve consistency, software

process is divided into set of phase, quality and progress checks are made without

waiting till the development is completed.

We have selected the waterfall model in the present application because this model

is suitable to automate the existing manual system for which all requirements are

known before the design starts.

USE CASE APPROACH-

Use case diagram for Leave Management System

Requirement analysis & specification

Design

Implementation & unit testing

Integration & system testing

Operation & maintenance


Administrator

1. Maintain employee records- add/modify/update employee details like

name, employee number, department number, etc.

2. Maintain leave records- add/modify/update employee leave details like leave

id, reason, duration, etc.

3. Log-in – use to provide a way to enter through user id and password.

4. Generate leave reports- use to print various reports like monthly leave,

annual leave etc.

Log-in

Maintain employee records

Maintain leave records

Generate leave reports

Generate employee reports

View employee and leave records


5. Generate employee reports- use to print various reports like custom

employee reports, etc.

6. View results- according to employee number, department number, etc.

1. Login

1.1 Introduction: This use case describes how a user logs into the Leave

Management System.

1.2 Actors: System Administrator

1.3 Pre Conditions: None

1.4 Post Conditions: If the use case is successful, the actor is logged into the

system. If not, the system state is unchanged.

1.5 Basic Flow: This use case starts when the actor wishes to login to the

Leave Management system.

(i) System requests that the actor enter his/her name and password.

(ii) The actor enters his/her name & password.

(iii) System validates name & password, and if finds correct allow the

actor to logs into the system.

1.6 Alternate Flows

1.6.1 Invalid name & password

If in the basic flow, the actor enters an invalid name and/or password, the

system displays an error message. The actor can choose to either return to

the beginning of the basic flow or cancel the login, at that point, the use case

ends.


2. Maintain employee records

2.1 Introduction: Allow administrator to maintain employee details. This

includes adding, changing and deleting employee information.

2.2 Actors: Administrator

2.3 Pre-Conditions: Administrator must be logged onto the system before

this use case begins.

2.4 Post-conditions: If use case is successful, employee information is

added/updated/deleted from the system. Otherwise, the system state is

unchanged.

2.5 Basic Flow: Starts when administrator wishes to

add/modify/update/delete employee information.

(i) The system requests the administrator to specify the function,

he/she would like to perform (Add/update/delete).

(ii) One of the sub flows will get executed after getting the

information.

If administrator selects "Add employee", "Add employee" sub flow

will be executed.

If administrator selects "update", "update" sub flow will be executed.

If administrator selects "delete employee", "delete employee" sub

flow will be executed.

2.5.1 Add an employee

(i) The system requests the administrator to enter:

Emp no

Emp name

Emp title


Dept no

Joining date

Contact no

Salary

Address

(ii) Emp no is the unique id.

2.5.2 Update employee records

(i) The system retrieves and displays the employee information.

(ii) Administrator makes the desired changes to the employee

information.

(iii) The system prompts the administrator to confirm the

updation of the employee.

(iv) After changes, the system updates the employee record

with changed information.

2.5.3 Delete an employee

(i)The system retrieves and displays the student information.

(ii) The system prompts the administrator to confirm the

deletion of the employee.

(iii) The administrator confirms the deletion.

(iv) The system marks the employee record for deletion.

2.6 Alternative flows

2.6.1 Update Cancelled


If in the update a employee sub-flow, the data entry operator

decides not to update the employee information, the update is

cancelled and the basic flow is restarted at the begin.

3. Maintain leave applications

3.1 Introduction: The administrator maintains leave applications. This

includes adding, changing, deleting leave application from the system

3.2 Actors: administrator

3.3 Preconditions: administrator must be logged onto the system before the

use case begins.

3.4 Post conditions: If the use case is successful, the leave applications can

be added or deleted from the system, otherwise the system state is

unchanged.

3.5 Basic flows: The use case starts when administrator wishes to add or

delete leave application from the system.

(i) The system requests administrator to specify the function he/she would

like to perform i.e.

• Add an application

• Delete an application

(ii) Once the administrator provides the required information, one of the sub

flows is executed.

If administrator selected “Add Leave Application”, the “Add leave” sub

flow is executed.

If administrator selected “Delete Leave Application”, the “Delete leave” sub

flow is executed.

3.5.1 Add a Subject


(i) The System requests the administrator to enter the leave

details. This includes:

Emp no

Dept no

Leave id

Start date

End date

Reason

(ii) The application is added to the system.

3.5.2 Delete an application

(i)System retrieves & displays leave applications.

(ii)System prompts the administrator to confirm the deletion.

(iii) Administrator verifies the deletion.

(iv)The system marks the leave record for deletion.

4. View employee and leave records

4.1 Introduction: This use case allows the administrator to view the

employee and leave records.

4.2 Actors: Administrator

4.3 Pre Conditions: administrator must be logged onto the system before the

use case begins.

4.4 Post Conditions: If use case is successful, the employee and leave

information is displayed by the system. Otherwise, state is unchanged.

4.5 Basic Flow: Use case begins when administrator wishes to view the

records.


5. Generate reports

5.1 Introduction: This use case allows the administrator to generate reports.

Options are

a. leave reports

b. employee reports

5.2 Actors: administrator

5.3 Pre-Conditions: administrator must be logged on to the system.

5.4 Post conditions: If use case is successful, desired report is generated.

Otherwise, the system state is unchanged.

5.5 Basic Flow: The use case starts, when administrator wishes to generate

reports.

(i) Administrator selects option.

(ii) System retrieves the information displays.

(iii) Administrator takes printed reports.

0 - LEVEL DATA FLOW DIAGRAM (DFD)


Administrator

Employee information entry Leave information entry

MS-Access

Employee reports Leave reports Custom reports

1 – LEVEL DATA FLOW DIAGRAM (DFD)

Leave Management System


Admin

Employee reports Leave reports

Custom employee reports

Database

The very first step towards database designing is Entity Relation (ER) diagram.

Log in

Enter employee detailsEnter leave details

Database

deptno deptnameempno

empnamed.o.j

jobtitle

econtact

deptno


As a byproduct of ER diagram we get our database design, entities become tables

and their corresponding attributes form the columns or fields of the table. But we

first need to normalize them before actually implementing them.

Normalization

While designing database, one should always try to make relation tables or

relations as simple as possible i.e. it can very well be defined in terms of two

dimensional tables. This process is known as normalization.

Normalization theory is built around the concept of Normal Forms. A relation is

said to be in a particular normal forms (NF), if it satisfies a certain specified set of

constraints or conditions.

Department

Employs

Employee

Applies

Leave

Abides by

Leavetypeleavetype_idlend_dt

lstart_dt

reason

deptno

empno

leavetype_idType


Finally, what we achieve after this exercise is our final database, which is as

follows:-

Chapter 5Implementation and Coding

The proposed system is an application developed in Visual Basic 6.0, making it an

event driven or menu driven system. Visual basic is an object based programming

language. The programming does not execute itself in any predetermined sequence

but different lines of code in response to events.

Visual Basic specifically follows procedural approach of coding wherein the

problem is decomposed into independent procedures or modules (coded and

tested), which are later combined and finally a system is ready to be executed.

Department

Department nameDepartment id

Employee

Empname EmpnoDept idEmp titled.o.jContact

Leave

Emp noDept idLeave idLstart_dateLend_dateReason

Leave_type

Leave idLeave type

Log – in

UsernamePasswordCategory


It allows us to adopt a parallel approach, with independent sections of code for

each option that the user might select.

Coding for the proposed system was not a very tedious task since forms were

distributed amongst the team of developers, who individually coded their parts,

tested them and then combined them to form ‘Leave Management system’.

Full coding of the proposed system is provided in the copy of CD being provided

with this project report.

Screen Shots

Login screen


Home Screen

Add New Employee


Add new leave

View employee records


View leave records

Chapter 6


TESTING

Software testing is the process used to measure the quality of developed software

product. Effective software testing will contribute to the delivery of higher quality

software products, more satisfied users, lower maintenance costs, more accurate,

and reliable results. Usually, quality is constrained to such topics as correctness,

completeness, security, but can also include more technical requirements as

described under the ISO standard ISO 9126, such as capability, reliability,

efficiency, portability, maintainability, compatibility, and usability. Testing is a

process of technical investigation, performed on behalf of stakeholders, that is

intended to reveal quality-related information about the product with respect to the

context in which it is intended to operate. This includes, but is not limited to, the

process of executing a program or application with the intent of finding errors.

Hence software testing is necessary and important activity of software

development process. It is a very expensive process and consumes one-third to

one-half of the cost of a typical development project. It is partly intuitive but

largely systematic. Good testing involves much more than just running the

program a few times to see whether it works. Thorough analysis of a program

helps us to test more systematically and more effectively.

6.1 Objectives of testing Testing is a process of executing a program with the intent of finding an

error.

A good test case is one that has a high probability of finding as yet

undiscovered error.

A successful test is one that uncovers an as-yet-undiscovered error

6.2 Testing Principles


All tests should be traceable to customer requirements.

Tests should be planned long before testing begins.

Testing should begin “in the small” and progress toward testing “testing in

large”.

Exhaustive testing is not possible.

To be most effective, testing should be conducted by an independent third

party.

6.3 Verification and validationSoftware testing is used in association with verification and validation (V&V).

Verification is the checking of or testing of items, including software, for

conformance and consistency with an associated specification. Software testing is

just one kind of verification, which also uses techniques such as reviews,

inspections, and walkthroughs. Validation is the process of checking what has been

specified is what the user actually wanted.

6.4 Types of testing Unit Testing- In unit testing, different modules are tested against the

specification produced during design for the modules. The main goal of

unit testing is to test the internal logic of the modules. A module is

considered for integration and used by others only after it has been unit

tested satisfactorily.

Integration Testing- The main emphasis is on testing interfaces between

modules.


System Testing- In system testing, the entire software is tested. The

reference document for this process is the requirements document

and the goal is to see if software meets its requirements. This is

essentially a validation exercise.

Acceptance Testing- Acceptance testing involves planning and

execution of the functional tests, performance tests and stress tests in

order to demonstrate that whether the implemented system satisfies its

requirements or not.

Stress Testing- Applying stress to a plan means that a large amount of

data is fed in for processing in a short period of time. In other words,

consumption of computer resources is drastically raised in that time

frame with the intention to ensure that the system will still perform

effectively if the same condition occurs in the future.

6.5 Testing ProcedureDifferent types of checks like duplicate checks; completeness check, validity

check, etc. are incorporated in this system.

The user is not familiar with the new system, the data entry screens are designed in

such a way that they are

Consistent

Compatible

Easy to use

Has quick response


Conventions for the System to be User Friendly All items that are logically related must be placed together.

Whenever possible, list of values must be provided to display all

valid options to the user.

Errors and validation messages must be provided whenever required.

Test Review

Test Review is the process, which ensures that testing is carried out as planned.

Checks

Example of validation check:-

Username and password should successfully match before user logs into the

system.


Example of type check

User cannot enter text in the fields of numeric concern like emp no. and vice

versa.

Null check that is user cannot leave any field empty.


Leave start date and leave end date should be in ascending order only

Various combo boxes are applied to prevent user from entering ambiguous

values.


Chapter 7Utilities in the system

General utilities in the system are as follows:-

Calculator

Calendar

Notepad

Web search page

<Have to attach a screen shot here>


Chapter 8CONCLUSION

The project ‘Leave Management System’ has been a rewarding experience in more

ways than one.

Firstly, we have gained an insight into the institution. This represents a typical real

world situation.

Secondly, in order to generate information from the institution, a number of

validations have been performed which has strengthened our understanding of

database design.

Initially there were some problems but with the guidance of our project coordinator

and project head we were able to solve the problems easily and implement

validations.

Finally we can appreciate the power of VB and its file handling ability to make the

module interactive and how the code can be reduced by applying procedures. We

are now confident of handling such real life situations concerning front end and

back end designs.


BIBLIOGRAPHY

Special Edition Using Visual Basic 6 by Brian Siler and Jeff Spotts

“Mastering Visual Basic 6.0” , E. Petroutsos, BPB Publications, 1998

Microsoft ActiveX Data Object 2.6 Library

Microsoft Data Environment Instance 1.0

Microsoft Data Report Designer 6.0

Visual Basic Run Time Objects And Procedures

Visual Basic Objects And Procedures

“Software Engineering”, K. K. Aggarwal & Yogesh Singh, 2nd Ed., New

Age International,2005

“Software Engineering-A Practitioner’s Approach” R.S. Pressman, 5 th Ed.,

McGraw Hill Int. Ed. 2001

“Software Engineering”, I. Sommerville, Addison Wesley,2002

Components used are

Microsoft Hierarchal Flex grid Control 6.0(OLEDB)

Microsoft Windows Common Control 6.0

Microsoft ADO data control 6.0

Microsoft Chart Control 6.0

Microsoft Comm Control 6.0

Microsoft Data grid Control 6.0(OLEDB)

Microsoft Internet Controls

Microsoft Windows Common control 6.0


Date post:	09-Jun-2017
Category:	Documents
Upload:	reshma-hedaoo
View:	333 times
Download:	7 times

Leave Management System

Documents