Development of an Employee Cubicle Management System


Title of the project


Development of an Employee Cubicle Management System


Abstract of the project


This project is aimed at tracking and having the view of the cubicle and the person sitting in it. Assuming there is already system that has the cubicle numbers and the telephone number data, at the same time this system will also need to take the floor plan as input and maintain the cubicle plan and the seat numbers. The floor plan input is needed to make system more robust and adaptable to the new buildings coming up.




Generic Technology keywords


Databases, Programming


Specific Technology keywords


Windows XP, JAVA, Sql Server, Java Applet, Java Swing


Project type keywords


Analysis, Design, Implementation, Testing, User Interface


Functional components of the project


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


The work flow should be like this:


  1. User will log into the System.
  2. The system will open up a screen to enter employee no. Alternatively it will provide a screen to search a particular employee depending on various criteria.
  3. Once the employee is found out, his location details will be displayed pictorially on the screen. The whole floor plan should be visible on the screen. And the particular location of the employee should be highlighted.
  4. There must different user groups of different privilege levels.
  5. The Administrator group will be responsible for adding new floor plans, new employees to the database. The application should provide some screens to add/modify/delete Floor Plan and related details and employee details.



Steps to start-off the project


The suggested OS and languages to implement such a system are


Microsoft platform: The system is developed using Java, Java Swing, Java Applet and SQL Server as the back end.



The following steps will be helpful to start off the project.


  1. Study and be comfortable with technologies such as
    1. Java, Java Applet, Java Swing and SQL server


            Some links to these technologies are given in the ‘Guidelines and References’ 

            section of this document


  1. Decide on details of the review and defect that you want to have.


  1. Create the screen which will display the floor plan and highlight the particular location of the employee cubicle.


  1. Create the help-pages of the system in the form of Q&A. This will help you also when implementing the system


Create other sub-systems like screens for searching employee based on different criteria.




Hardware requirements




Alternatives (If available)


PC with 2 GB hard-disk and 256 MB RAM






Software requirements




Alternatives (If available)


Windows 95/98/XP with MS-office

Not Applicable


MS-SQL server




Not Applicable


Java Applet

Not Applicable


Java Swing

Not Applicable



Manpower requirements


2 to 3 students can complete this in 2-3 months if they work fulltime on it.


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). 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.


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 workflow scenarios (like adding a new employee, movement of an employee from one cubicle to another etc) and then coming up with flow-charts or pseudocode to handle them.


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.


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 location database. 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 (SQL-server tutorial)

Tags :
Your rating: None