Development of a feature-rich, Employee Transfer Application.


Title of the project


Development of a feature-rich, Employee Transfer Application.


Abstract of the project


Develop an Intranet Application for ABC Technologies Ltd. for maintaining information related to its employees transfer and generating the transfer related documents. This application would be facilitating the system administrator (Higher Management) to search the employees transfer record, make new transfers and also amend the allowances offered to the employee which usually depends on the post of the employee and the type of transfer he is getting.


Develop an Intranet Employee Transfer Application, which will cover the following functionalities:

1) Login

            a) Employees

            b) System Administrator


2) Interface for filling up the following information

            a) Searching the transfer records.

            b) Updating the transfer records.

c) Making new transfers.(this can be combined with the update page by enabling and disabling the update and make transfer buttons.)


3) Interface to generate the transfer related documents in Doc format.


4) Automatic mail notifications to the employees who got transferred and to the managers who would be receiving the transferred employees.


5) Logout




Generic Technology keywords


Databases, Programming


Specific Technology keywords


MS-SQL server, HTML, Active Server Pages, Visual Basic


Project type keywords


Analysis, Design, Implementation, Testing, User Interface


Functional components of the project:


Following is a list of functionalities of the system. More functionalities that you find appropriate can be added to this list. And, in places where the description of a functionality is not adequate, you can make appropriate assumptions and proceed.


1)Search Transfer Record


The search can be based on the following fields :

Employee Number, Employee Name, Band, From Location, To Location, From Project, To Project, From Department, To Department etc


The Employee Master Record may contain the following fields (and some more which you wish to add):

Employee Number, Employee Name, Role, Band, Work Experience, Current Project, Current Location, Transfer Project, Transfer Location, Current Department, Transfer Department., Transfer Relieving Date, Transfer Joining Date, Reporting Manager.





3)Benefit Form


The Project Can be developed using either two tiers or three tiers Architecture.











Three-Tier Architecture:

The Front-End is Asp.

The Back End is SQl Server 2000.

The Middle layer consists of the following objects:

1)      Data Value Objects.

2)      Business Logic objects.

3)   Data Access Objects.



Two-Tier Architecture:


1) Front-End: ASP

2) Back-End: SQLServer


Steps to start-off the project


The following steps will be helpful to start the project.


  1. Study and be comfortable with technologies such as


  1. Active Server Pages/HTML and SQL server and Visual Basic. Some links to these technologies are given in the ‘Guidelines and References’  Section of this document


  1. Decide The format of the various transfer Related documents Like Transfer                                   Letter, Relieve Letter     etc.



Hardware requirements:




Alternatives (If available)


PC with 2 GB hard-disk and 256 MB RAM







Software requirements:




Alternatives (If available)


Visual Basic 6.0



SQl Server 2000

Oracle 8




Windows 2000


Alternatively, Windows 98 with IIS Server Installed.



Manpower requirements:

                        Project Duration:  3months

            Project team-size: 5-6


Milestones and Timelines



Milestone Name

Milestone Description





Week no. 

from the start

of the project





Requirements Specification

Complete specification of the system (with appropriate assumptions) including the information to be present in the Transfer Related Documents. A document detailing the same should be written and a presentation on that be made.


Attempt should be made to add some more relevant functionality other than those that are listed in this document.


Technology familiarization

Understanding of the technology needed to implement the project.


The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.


Database creation

A database of at least 100 entries of employees of all grades should be created. The number of mail-ids to be created need not be 100. It can be around 10 to 20.A Database design document should be made.


It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself.


High-level and Detailed  Design

Listing down all possible scenarios (like Entering Transfer information, Searching Transfer Record based on several criteria) and then coming up with flow-charts or pseudo code to handle the scenario.


The scenarios should map to the requirement specification (i.e., for each requirement that is specified, a corresponding scenario should be there).


Implementation of the front-end of the system

Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options (transfer request, transfer approval etc).


During this milestone period, it would be a good idea for the team (or one person from the team) to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.


Integrating the front-end with the database

The front-end developed in the earlier milestone will now be able to update the employee transfer records database. Other features like mail notification etc should be functional at this stage. In short, the system should be ready for integration testing.




Integration Testing

The system should be thoroughly tested by running all the test cases written for the system (from milestone 5).


Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.


Final Review

Issues found during the previous milestone are fixed and the system is ready for the final review.


During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled (or appropriate reasons given for not fulfilling the same)


Guidelines and References


1) tutorial)


2) tutorial)


3) (Shell script introduction)


4) (Many Tutorials Available)





Tags :
Your rating: None Average: 4 (1 vote)