2. P a g e | 1
Abstract
The residential quarter allotment portal has been designed to allocate residential quarters
to the employees of the organization; Diesel Locomotive Works (D.L.W.). The manual
allotment process used earlier lead to creep some errors unintentionally which can be
avoided by the use of this system.
The system is developed to make the quarter allotment process easier thus great
emphasis is laid on making an intuitive, user-friendly interface. The system is designed to
reduce the time taken in the allotment process. It automatically prepares the priority list of
the eligible employees according to the specified constraints. The Admin of the system can
then allot the residential quarters according to the availability, which would otherwise have
to be performed manually, which is rather more time consuming.
3. P a g e | 2
Acknowledgement
I would like to thank my supervisor Mr. Mohammad Azam for his guidance. It would not
have been possible to complete this project in 4 weeks without his help and ideas. I would
also like to thank the academic council of Bhagwant University for keeping industrial grades
as a mandatory requirement for all its undergraduate students. This gave me an opportunity
to explore the industrial area and work at Diesel Locomotive Works, Varanasi on a software
project as an intern. This has helped me in learning a lot about the industrial requirements.
I want to thank my parents for their great love and support. All the credit goes to
them. Also I want to thank my friends for their precious suggestions and help. It helped me
delivering not a huge but a useful system with attracting features, considering the limited
time.
4. P a g e | 3
Table of Contents
1. Introduction .................................................................................................4
2. Detailed System Description.........................................................................5
2.1 Product Perspective..............................................................................................................6
2.2 Product Features...................................................................................................................6
2.3 User Documentation ............................................................................................................7
2.4 Funtionalities........................................................................................................................7
3. Requirements...............................................................................................9
3.1 Operating Environment........................................................................................................9
3.2 Design and Implementation Constraints..............................................................................9
3.3 Assumptions and Dependencies ........................................................................................10
5. Data Requirements.....................................................................................11
5.1 Accessibility.......................................................................................................................11
5.2 Correctness.........................................................................................................................12
5.3 Availability.........................................................................................................................12
5.4 Usability.............................................................................................................................12
5.5 Performance .......................................................................................................................12
5.6 Supportability.....................................................................................................................13
5.7 Portability...........................................................................................................................13
5.8 Reliability...........................................................................................................................13
5.9 Safety .................................................................................................................................14
6. Appendix....................................................................................................15
6.1 Data Flow Diagram............................................................................................................16
6.2 Use Case Diagram..............................................................................................................16
6.3 Screenshots.........................................................................................................................17
5. P a g e | 4
1. Introduction
This software is aimed at developing an electronic system which has the ability to assign
residential allotments/quarters to the employees of DLW (Diesel Locomotive Works,
Varanasi); it is a production unit owned by the Indian railways that manufactures diesel-
electric locomotives and its spare parts. This portal will be useful to add new allotment
records and maintain the record of already allotted quarters. The basic purpose of this
system is to make the allotment process easier and efficient with the use of optimal
software. It would otherwise have to be performed manually, which is rather more time
consuming.
Since the system is developed to make the quarter allotment process easier thus
great emphasis is laid on making an intuitive, user-friendly interface. Using this portal,
the allotment authority can maintain the record of all the employees that have been
allotted a quarter. These allotments are done on the basis of rank of the employee
keeping his basic salary and date of promotion as the primary constraint, thus portal will
be efficient in assigning the residential allotments in accordance with the availability of
quarters. Also new vacancies and queries for class upgrade can be handled through this
portal. This software systemwill notify about the availability of new quarters and eligible
employees can apply for it online. The allotment of quarters will be done on the basis of
a seniority list that is prepared according to the ranks of the officers and the promotion
date after they have applied for accommodation, The only operating system that the
system will be tested under is Microsoft Windows, however it is expected that any
system with a standard web browser will be compatible with the system. Manually, the
evolution pattern can lead to creep some errors unintentionally which can be avoided by
the use of this system.
6. P a g e | 5
2. Detailed System Description
2.1. Product Perspective
Using this online portal system, the allotment authority can maintain the record of
all the employees that have been allotted a quarter. These allotments are done on
the basis of rank of the employee, keeping his basic salary and date of promotion as
the primary constraints, thus portal will be efficient in assigning the residential
allotments in accordance with the availability of quarters. The system is also used as
an informative portal. The portal will contain a notice section that will display the
information about the availability and new vacancies. The employees can register to
upgrade their quarter class and this will be carried out on the basis of a seniority list
that will be prepared for the list of employees that apply for an upgrade before the
deadline. All the allotment rights will be reserved for the admin login, the employees
will have a user login through which they can check their current allotment and
apply for an upgrade.
2.2. Product Features
Major features:
- Admin can add a new record in the database.
- Admin can delete an existing record in the database.
- Admin can update an existing record in the database.
- Employees can view the records.
- Employees can apply (before deadline, if any) for available quarters.
Other features:
- Admin can add the notice for the availability of a quarter.
- Admin can remove the notice for the availability of a quarter.
- Employees can view their respective profiles.
7. P a g e | 6
2.3. User Documentation
- Admin User: Has full permission on portal, can manage employee user account,
validate announcements. The admin can add, update and delete employee records,
and allot quarters to employees.
- Employee User: Can register for class upgrade in case a higher class quarter is
available, can view the profile details.
- Unregistered user: can only view items on portal.
2.4. Functionalities
- The portal has two types of access modes i.e. Admin login and Employee login.
Admin login has full access permission whereas Employee login has limited
permission.
- The Admin can add a new data record in case of a new joining; delete existing record
in case of a retirement.
- The Admin can view the existing records and the corresponding details of each and
every employee.
- The Admin has the authority to assign residential quarters to employees as per the
availability and according to the basic salary as per the following convention:
Basic pay (Rs) Eligible for Residential Quarter type
Up to 25,000 Type D
25,001 – 35,000 Type C
35,001 – 50,000 Type B
Above 50,000 Type A
On the basis of basic pay, corresponding type of quarter is allotted to employee. In
case two employees are eligible for same type of quarter, the priority is decided on
the basis of the date of promotion. The employee with prior date of promotion is
given a higher priority.
- The Employees can only view the details but cannot make any changes to it and also
cannot add any details and records or delete them.
8. P a g e | 7
- The Employees can apply for an up-gradation in a higher type of residential quarter
in case there is availability. The availability is issued once a record is deleted by the
Admin and is displayed as a notification on the portal as a notice. Interested
employees can apply for it.
- The Admin has the authority to assign this available quarter type to eligible
employee. This allotment is done on the basis of a seniority list which is prepared
according to the date of promotion of the employees that have applied for an up-
gradation i.e. the employee with a prior promotion date is preferred and is assigned
a higher priority.
- The Admin has the permission to update the existing records in the database such as
employee name details, contact information, etc.
2.5. Technology Used:
JAVA
PHP
MYSQL
JAVA
Java is a programming language created by James Gosling from Sun Microsystems
(Sun) in 1991. The first publicly available version of Java (Java 1.0) was released in 1995.
Sun Microsystems was acquired by the Oracle Corporation in 2010. Oracle has now
the statesmanship for Java.
Over time new enhanced versions of Java have been released. The current version of
Java is Java 1.7 which is also known as Java 7.
From the Java programming language the Java platform evolved. The Java platform
allows software developers to write program code in other languages than the Java
programming language which still runs on the Java virtual machine. The Java platform is
usually associated with the Java virtual machine and the Java core libraries.
9. P a g e | 8
PHP( Hypertext Preprocessor)
PHP is best summarized as an embedded server-side Web-scripting language that
provides developers with the capability to quickly and efficiently build dynamic Web
applications. PHP bears a close resemblance; both syntactically and grammatically, to the C
programming language, although developers haven’t been shy to integrate features from a
multitude of languages, including Perl, Java, and C++. Several of these valuable borrowed
features include regular expression parsing, powerful array-handling capabilities, an object-
oriented methodology, and vast database support. For writing applications that extend beyond
the traditional, static methodology of Web page development (that is, HTML), PHP can also
serve as a valuable tool for creating and managing dynamic content, embedded directly
beside the likes of JavaScript, Stylesheets, WML (Wireless Markup Language) and many
other useful languages.
MySQL
In today's connected world, data and the systems that manage that data must always
be secure yet available to our users. With MySQL, users and information technology (IT)
professionals across your organization will benefit from reduced application downtime,
increased scalability and performance, and tight yet flexible security controls. MySQL also
includes many new and improved capabilities to help make your IT staff more productive.
10. P a g e | 9
3. Requirements
3.1. Operating Environment
- Operating System: Windows XP(SP2)/Vista/7/8, Linux, MacOS
- RAM: 1GB or more
- Processor: Intel Core 2 Duo and above, AMD Athlon
3.2. Design and Implementation Constraints
Hardware limitations:
- Response time is less than 7.0 seconds.
- Can support for 100 users in the same time.
Specific technologies used:
- Front End: JAVA,PHP,HTML
- Back End: MySQL
Language requirements:
- Support English
Time constraints:
The time of 4 weeks was specified to finish all documentation, bug fixing and
development. I had a lot of ideas but could not implement them due to time constraint.
Actually, working on this project has made me realize that the context of this residential
allotment process is really huge. There are so many features that are possible to be
included in the system, but I aimed delivering not huge but useful system with some
attracting features considering the limited time.
11. P a g e | 10
Design Constraints
Software Language Used: The languages that have been used for coding the
Residential Allotment System are Java, HTML and PHP. The system is made with the use
of the available Java Development Tool kits for working with Java. Also, online
references available for developing programs in HTML and JavaScript have been used.
3.3. Assumptions and Dependencies
The users must have sufficient knowledge of computers. The local computer should
have Internet connection and Internet server capabilities. The users must know the
English language, as the user interface will be provided in English. The product can
access the database of the system and it can be modified if necessary.
12. P a g e | 11
4. Data Requirements
4.1. Accessibility
This subsection specifies the following requirements associated with the degree to
which the system must be accessible to people with authorization rights:
- The graphical user interface menus for adding a new record, updating the existing
record and deleting the stored records windows shall be usable only by the Admin.
- The portal menu for the up-gradation notice and allotment can be accessed only by
the Admin.
- Employees can view the details.
- Employees can apply for an available upgrade before the deadline.
4.2. Correctness
This subsection specifies the following requirements associated with the degree to
which the system can contain defects and still be acceptable to the customer:
Accuracy
The accuracy of the system is limited by the accuracy of the speed at which the
employees of the system work.
Precision
The values of date field, name field, etc to be input from the user are precise and
cannot be entered absurdly.
Timeliness
When Admin updates some data, the system shall ensure that the Admin will see the
update on next login.
13. P a g e | 12
4.3. Availability
The system is fully available for the user and is used 24 hrs a day and 365 days a
year. The system shall be operational 24 hours a day and 7 days a week.
4.4. Usability
This subsection specifies the following requirements associated with the degree to
which the system can be used for purposes other than originally intended:
- The system allows the users to access the system from the Internet using HTML or its
derivative technologies. The system uses a web browser as an interface.
- Since all users are familiar with the general usage of browsers, no specific training is
required.
- The system is user friendly and self-explanatory.
4.5. Performance
This subsection specifies the following requirements associated with the speed with
which the system shall function:
Latency
- The sign in time for the system shall be less than 5 seconds.
- The Admin can update a record in less than 10 seconds.
Response Time
The Splash Page or Information page should be able to be downloaded within a
minute using a 56K modem. The information is refreshed every two minutes. The
access time for a mobile device should be less than a minute. The system shall
respond to the member in not less than two seconds from the time of the request
submittal. The system shall be allowed to take more time when doing large
processing jobs.
14. P a g e | 13
Administrator Response: The system shall take as less time as possible to provide
service to the administrator or the employee.
Throughput
This is directly dependent on the number of users. The users may be the
Administration, students or employees of the system.
Capacity
The system is capable of handling 100 users at a time.
4.6. Supportability
The system designers shall take in to considerations the following supportability and
technical limitations:
- Internet Protocols: The system can comply with the TCP/IP protocol standards and is
designed accordingly.
- Information Security Requirement: The system can support the UHCL information
security requirements and use the same standard as the UHCL information security
requirements.
4.7. Portability
This subsection specifies the following requirements associated with the ease with
which the system can be moved from one environment to other:
- The system can be run on a machine with processor; Intel Pentium 4 or higher.
- They size of RAM of the machine should be 1GB or more.
- The operating system supported; Windows XP service pack 2 or higher.
4.8. Reliability
On this project an important aspect is the reliability of the delivered software.
Possible defects may cause great amount of time and money loss. To ensure the
reliability the system has recovery system where we can recover the data.
15. P a g e | 14
4.9. Safety
This subsection specifies the following requirements associated with the degree to
which the system does not directly or indirectly cause accidental harm to life or
property:
- The system shall not accidentally lose user account information.
- The system shall accurately prepare the seniority list for allotment.
16. P a g e | 15
5. Appendix
5.1. Data flow diagram
