Apartment Management System
Apartment Management System
Apartment Management System
1. INTRODUCTION
1.1 PROBLEM DEFINITION
In the existing system all references are done manually. Data to be stored in hand written
format. All the calculation to be performed takes lot of time. There is a probability for
occurring mistakes during the calculation for providing the expenditure which is to be paid by
resident. It causes difficulty in finding manually each residents detail and recording whether
the expenses are paid or unpaid monthly any balance due is there.
PROJECT OVERVIEW
MODULES
APARTMENT DETAIL
o The apartment detail module deals with details of apartment. It consist the
name of the apartment, location, area, facility available in apartment and the
details of the owner. It gives an overall view of the apartment. It shows the
amount of expenses to be paid by residents every month.
GENERAL EXPENSES
o In the general expense details, the one month expense details is allowed to
store in th centralized database which includes the security charge, vehicles
parking, club membership, health club, cleaning and sweage disposal, water
charge, lift charge and every two months expense details such as walking
track,swimming pool, play ground, lightining, celebration. These details are
allowed to store in the centralized database.
BLOCK LEVEL
o The block details records the number of blocks available in the apartment. It
shows the floor levels in each block, area of the block as well as, flats
available in each floor. It indicates the details of the flat such as unit type, cost
estimation and market value, orientation etc.
FLOOR LEVEL
o In the floor level details, it includes the floor id, floor name, block and the
units. These details are allowed to store in the centralized database.
RESIDENT
o The resident module deals with the details of resident. There are two kind of
resident they are owner and tenant. The resident is a tenant then rent, advance
paid and agreement detail is recorded. The allocation details of the resident are
recorded so that the history of residents would be tracked.
PAYMENTS
o The payment module contains rent and expenses, maintenance expense and
installments detail. The rent and expenses is to be paid by all the residents
monthly and rent would be paid by only those who are tenant. Maintenance
expense is not to be paid monthly is to be done when necessary. The payment
details of owner of flat will be indicated in installment, which shows the
various stages of their payment from the initial booking of flat.
REPORT
o Other Expense
o Apartmant Details
o Rent Expense Report
o Apartment Maintenance
When an application project is considered the three basic software requirements are
the platform in which the project is developed, the front-end tool that provides the interaction
with the users and the back-end tool that stores the data.
Visual Basic was derived from BASIC and enables the rapid application development
(RAD) of graphical user interface (GUI) applications, access to databases using Data
Access Objects, Remote Data Objects, or ActiveX Data Objects, and creation of ActiveX
controls and objects. Scripting languages such as VBA and VBScript are syntactically
similar to Visual Basic, but perform differently.[3]
A programmer can put together an application using the components provided with
isual Basic itself. Programs written in Visual Basic can also use the Windows API, but
doing so requires external function declarations.
The final release was version 6 in 1998. Microsoft's extended support ended in March
2008 and the designated successor was Visual Basic .NET (now known simply as Visual
Basic).
2. SYSTEM STUDY
It is the most creative and challenging phase of the system life cycle. The analysis phase
is used to design the logical model of the system whereas the design phase is used to design
the physical model.
Many things are to be done in this phase .we began the designing process by
identifying forms, reports and the other outputs the system will produce. Then the specify
data on each were pinpointed. we sketched the forms or say, the displays, as expected to
appear, on paper, so it serves as model for the project to began finally we design the form on
computer display, using one of the automated system design tool, that is VB 6.0 and SQL
Server as back end tool.
After the forms were designed, the next step was to specify the data to be inputted,
calculated and stored individual data items and calculation procedure were written in detail.
File structure such as paper files were selected the procedures were written so as how to
process the data and procedures the output during the programming phase. The documents
were design ion the form of charts.
Output design means what should be the format for presenting the results. It should be
in most convenient and attractive format for the user. The input design deals with what
should be the input to the system and thus prepare the input format. File design deals with
how the data has to be stored on physical devices. Process design includes the description of
the procedure for carrying out operations on the given data.
2.1 EXISTING SYSTEM
In the existing system all references are done manually. Data to be stored in hand
written format. All the calculation to be performed takes lot of time. There is a probability for
occurring mistakes during the calculation for providing the expenditure which is to be paid by
resident. It causes difficulty in finding manually each residents detail and recording whether
the expenses are paid or unpaid monthly any balance due is there etc. The major drawbacks
of the existing system are as follows
In the existing system, the details of the customers are collected manually and are
later filled in Microsoft Excel Worksheets. In manual system there is lots of customer for
these efforts and also keep a large set of files to solve this problem we thus proposed a
computerization of the system. As and when the organization get new clients, their details are
added to the sheet. There is a chance of missing the contract renewal and payment dates. It
may lead to confuse when applied with more customers. Collecting information manually is
so slower compare to computerization.
The proposed system can be performed automatically. Individual resident detail has
been entering as the input and the project calculates the expenses. With the help of this
project user can analyze the expenses. By using this project a lot of manual work can be
reduced and resident details can be maintained accurately .This project will produce error free
information with less man work, hundred times faster than, manual work etc.
This project was concluded that the problem which had to be tackled on a high
priority basis was a better information system for billing, accounting issues in the residents of
an apartment. Anybody can manage this software with little knowledge about computer.
Calculate expenses of each month to resident. By using this project can get an easy reference
to check the availability of flats, resident details and their payment at various months.
Time saving.
Save paper.
Most feasibility studies are distinguished for both users and analysts. First, the study
often presupposes that when the feasibility document is being prepared, the analyst is in a
position to evaluate solutions. Second, most studies tend to overlook the confusion inherent
in system development – the constraints and the assumed attitudes.
People are inherently resistant to change, and computers have been known to facilitate
change. An estimate should be made of how strong a reaction the user staff is likely to have
toward the development of a computerized system. It is common knowledge that computer
installations have something to do with turnover, transfers, retraining, and changes in
employee job status. Therefore, it is understood that the introduction of a candidate system
requires special effort to educate, sell and train the staff on new ways of conducting business.
Technical feasibility centers around the existing computer system (hardware, software,
etc.) and to what extend it can support the proposed addition. For example, if the current
computer is operating at 80 percent capacity – an arbitrary ceiling – then running another
application could overload the system or require additional hardware. This involves
financial considerations to accommodate technical enhancements. If the budget is a
serious constraint, then the project is judged not feasible.
2.4.3 Cost/ Benefit analysis
Economic analysis is the most frequently used method for evaluating the effectiveness of a
candidate system. More commonly known as cost benefit analysis, the procedure is to
determine the benefits and savings that are expected from a candidate system and compare
them with costs. If benefits overweigh costs, then the decision is made to design and
implement the system. Otherwise, further justification or alterations in the proposed
system will have to be made if it is to have a chance of being approved. This is an ongoing
effort that improves in accuracy at each phase in the system life cycle.
Costs:
Cost of new computer approximately Rs. 22,000/-
Cost of operating system approximately Rs. 5000/-
Benefits:
Avoids tedious typing task
Faster document retrieval
Saving storage sMaintenance
Keeps data secure
Easy to use, update and maintain
CHAPTER - 3
ADVANTAGE
The advantage of waterfall development is that it allows for departmentalization and
control. A schedule can be set with deadlines for each stage of development and a
product can proceed through the development process model phases one by one.
Development moves from concept, through design, implementation, testing,
installation, troubleshooting, and ends up at operation and maintenance. Each phase of
development proceeds in strict order.
DISADVANTAGE
The disadvantage of waterfall development is that it does not allow for much
reflection or revision. Once an application is in the testing stage, it is very difficult to
go back and change something that was not well-documented or thought upon in the
concept stage.
A relationship is how the data is shared between entities. There are three types of
relationships between entities:
1. One-to-One
One instance of an entity (A) is associated with one other instance of another entity
(B). For example, in a database of employees, each employee name (A) is associated
with only one social security number (B).
2. One-to-Many
One instance of an entity (A) is associated with zero, one or many instances of
another entity (B), but for one instance of entity B there is only one instance of entity
A. For example, for a company with all employees working in one building, the
building name (A) is associated with many different employees (B), but those
employees all share the same singular association with entity A.
3. Many-to-Many
One instance of an entity (A) is associated with one, zero or many instances of
another entity (B), and one instance of entity B is associated with one, zero or many
instances of entity A. For example, for a company in which all of its employees work
on multiple projects, each instance of an employee (A) is associated with many
instances of a project (B), and at the same time, each instance of a project (B) has
multiple employees (A) associated with it.
ER DIAGRAM:
3.2 DATA FLOW DIAGRAM
A data flow diagram (DFD) is a graphical representation of the "flow" of data
through an information system, modeling its process aspects. Often they are a preliminary
step used to create an overview of the system which can later be elaborated. DFDs can also
be used for the visualization of data processing (structured design).
A DFD shows what kinds of data will be input to and output from the system, where
the data will come from and go to, and where the data will be stored. It does not show
information about the timing of processes, or information about whether processes will
operate in sequence or in parallel (which is shown on a flowchart).
It is common practice to draw the context-level data flow diagram first, which shows
the interaction between the system and external agents which act as data sources and data
sinks. On the context diagram the system’s interactions with the outside world are modeled
purely in terms of data flows across the system boundary. The context diagram shows the
entire system as a single process, and gives no clues as to its internal organization.
This context-level DFD is next “exploded”, to produce a Level 0 DFD that shows
some of the detail of the system being modeled. The Level 0 DFD shows how the system is
divided into sub-systems (processes), each of which deals with one or more of the data flows
to or from an external agent, and which together provide all of the functionality of the system
as a whole. It also identifies internal data stores that must be present in order for the system to
do its job, and shows the flow of data between the various parts of the system.
Data flow diagrams were proposed by Larry Constantine, the original developer of
structured design, based on Martin and Estrin’s “data flow graph” model of computation.
Data flow diagrams are one of the three essential perspectives of the structured-systems
analysis and design method (SSADM). The sponsor of a project and the end users will need
to be briefed and consulted throughout all stages of a system’s evolution. With a data flow
diagram, users are able to visualize how the system will operate, what the system will
accomplish, and how the system will be implemented. The old system’s dataflow diagrams
can be drawn up and compared with the new system’s data flow diagrams to draw
comparisons to implement a more efficient system. Data flow diagrams can be used to
provide the end user with a physical idea of where the data they input ultimately has an effect
upon the structure of the whole system from order to dispatch to report. How any system is
developed can be determined through a data flow diagram model.
In the course of developing a set of leveled data flow diagrams the analyst/designers
is forced to address how the system may be decomposed into component sub-systems, and to
identify the transaction data in the data model.
Data flow diagrams can be used in both Analysis and Design phase of system
development life cycle (SDLC).There are different notations to draw data flow diagrams
(Yourdon & Coad and Gane&Sarson), defining different visual representations for processes,
data stores, data flow, and external entities.
DFD
Level - 0
Figure 1 – Shows Level1 data flow diagram for “Apartment Maintenance System”
Level-1
Figure 2 – Shows Level1 data flow diagram for “Apartment Maintenance System”
3.3 INPUT DESIGN
Input design is the method by which valid data are accepted from the user. If the data
going into the system is incorrect, then the processing and output will magnify these errors.
The system has been designed to communicate effectively with the user. The goal of
designing input design is to make input data entry as easy and error free. Input screen take
care to filter the invalid data from becoming an operational data at each entry phase. This is
achieved by providing proper checks and validation procedures and certain features to the
users wherever possible. The input format in this system has been designed with the
following objectives.
To produce a cost effective method of inputs.
To achieve highest possible level of accuracy.
To ensure that the input is acceptable and understood by the user.
The Apartment Maintenance system contains Ten input fields. User login: The
manager can enter user name, password for login in to the system. OtherExpenses: The
expenses and maintenance amount details of apartment. BlockDetails: This gives
information about the block details.
FloorDetails: This gives information of floor existing in each block. Resident: This
gives details of the resident. If the resident is tenant it shows the advance amount detail.
Allocation: This gives the history of resident allocation detail of each flat.
Rent and Expense: The rent and expense amount to be paid by resident monthly.
Maintenance: The maintenance amount to be paid by resident. Installment: The installment
details of the resident while purchasing the flat.
3.4 DATABASE DESIGN
The first table named Apt_ApartmentDetail has twelve fields such as apartment name,
apartment location, area, contact number, email, apartment facilities etc. Each field has its
own data types. These fields are using to show the details of apartment
The second table named Apt_OtherExpenses has thirteen fields such as security, car
parking, health club, lift charges etc. These fields are used to show the expense and
maintenance amount to be paid by the residents.
The third table named Apt_Block has three fields such as block id, block name, and
block area. The field block id set as primary key. These fields are used to indicate the number
of blocks in an apartment.
The fourth table named Apt_Floor has five fields such as floor id, floor name, units etc.
The field floor id is set as primary key. These fields are used to show the number of floors in
each block.
The fifth table named Apt_ Resident has twenty fields such as resident id, resident name,
occupation, allocation date etc. The field resident id is set as primary key. The table shows
the details of resident in apartment.
The sixth table named Apt_RentExpenses have eighteen fields such as flat no, rent, lift
charges, electricity, water bill, security, car parking etc. The primary field is flat no. The table
shows rent and expenses that are to be paid by a resident in monthly basis.
The seventh table named Apt_Maintenance has twelve fields such as flat no, celebration,
walking track, total etc. The primary field is flat no. The table shows payment detail of
maintenance expense.
TABLE NAME : Apartment details
Primary key :Apt_name
Column name Size Data Type Description
Apt_name 20 Nvarchar Apartment name
Apt_location 50 Nvarchar Apartment location
Apt_area Int Apartment area
Apt_contactperson 20 nvarchar Apatment contact person
Apt_contactno (12,0) Numeric Apartment contact no
Apt_emil 20 Nvarchar Apartment email
Output design generally refers to the results and information that are generated by the
system. For many end-users, output is the main reason for developing the system and the
basis on which they evaluate the usefulness of the application. Care must be taken to present
the right information. So that right decisions are made. The objective of a system finds its
shape in terms of output. The analysis of the objective of a system leads to determination of
outputs. Outputs of a system can take various forms. The most common are reports, screens
displays printed form.
The output from a system is the justification for its existence. If the outputs are
inadequate in anyway, the system itself is inadequate. The basic requirements of output are
that it should be accurate, timely and appropriate, in terms of content, medium and layout for
its intended purpose. Hence it is necessary to design output so that the objectives of the
system are met in the best possible manner. The outputs are in the form of reports.
The Apartment Maintenance System has five output fields. Resident report: The
report shows the resident information.
Rent and expense report: The report gives the complete payment details of resident
.Maintenance report: The report gives complete maintenance expense detail. Installment
report: The report shows the information about resident’s installment detail
CHAPTER - IV
4. SYSTEM TESTING
Validation Testing
In validation testing we ensure that all the data entered was displayed properly on the
view screen and that we got the expected results.
Integration Testing
The last step was to integrate the various modules in the software. The proposed system is
implemented top-down integration. The integration was performed in five steps:
The main control module was used as test driver and stubs were substituted for all
components directly subordinate to the main control module.
Depending on depth first search subordinate stubs was replaced with actual
components.
Tests were conducted as each component with real component.
On completion of each set of tests, another stub is replace with real component.
Integration testing was conducted to ensure execution of some subset of tests have
already been conducted had not propagated unintended side effects.
Test Cases
Case Scenario Sr. Action Expected Actual Result
no. no Output Outpu
t
1 Login A User forgets to Message Messa PASS
enter the window saying ge
username/ “Please enter windo
password the username/ w
password” saying
“Pleas
e enter
the
userna
me/
passwo
rd”
B User enters Message Messa PASS
wrong username/ window saying ge
password “Wrong windo
username/ w
password” saying
“Wron
g
userna
me/
passwo
rd”
C User enters Takes user to Takes PASS
correct Apartment user to
username/ Maintenance Apart
password System ment
Mainte
nance
System
CHAPTER – 5
System Implementation is the stage of the project when the theoretical design is
tuned into working system. If the implementation system stage is not carefully
controlled and planned, it can cause chaos. Thus it can be considered to be the most
critical stage in achieving a successful new system and in giving the users a
confidence that the system will work and be effective.
End Users
No specific knowledge or skills are required from the end user.
End user should have basic idea about computer operations and database.
Administrator
Administrator must be having good knowledge of database management system.
Administrator must be capable to manage user rights.
If the network connection does not work properly than our system should not work
as intended.
Also that is assumed that the product is installed properly at windows server
This system will not take care of any virus problem, which might occur either on
the
client or the server system. Avoiding the use of pirated software and ensuring that
floppies and other removable media are scanned for viruses before use could
minimize the possibility of viral infection.
Recovery of data after a system crash will be possible only if backups are taken
at regular intervals.
Manual interfaces cannot be fully avoided. Documented proofs like data entry
of employees etc. will have to be verified by the concerned management staff
before entering it into the computerized system.
Assumptions and Dependencies
Assumptions:
The code should be free with compilation errors/syntax errors.
The product must have an interface which is simple enough to understand.
Dependencies:
All necessary hardware and software are available for implementing and
use of the tool.
The proposed system would be designed, developed and implemented
based on the software requirements specifications document.
End users should have basic knowledge of computer and they also assure
that the users will be given software training documentation and reference
material.
The system is not required to save generated reports.
The application’s validations are made, taken into account of the entry levels
available in various modules. Possible restrictions like number formatting, date formatting
and confirmations for both save and update options ensures the correct data to be fed into the
database. Thus all the aspects are charted out and the complete project study is practically
implemented successfully for the end users.
CONCLUSION
The project “APARTMENT MANAGEMENT SYSTEM” provides maximum
flexibility. The testing of the whole system is completed with the data and outputs are
generated. The efficiency of the new system is found to be better than the existing system in
all respects. The system is able to maintain the details in an effective manner.
As the company needs information quickly so that they can provide their customers
better service support. Most of all anybody can control this with little knowledge about
computer. The computer solution is more users interactive so that change of error in data
inputting is very low. I can store plenty of records in computer “safely”.
The programming techniques used in the design of the system provide a scope for
further enhancements in the future. The various reports generated by the system are also very
useful. Since the requirement of any organization and their standards are changing day by day
the system is designed in such a way that its scope and boundaries could be expanded in
future with a little modification. If the management wants to implement more enhancements
in the future then that can also be accommodated easily.
At this time of the century when software is getting highly acclaimed the
computerized system eliminates the burden of manual record keeping. The new system
provides more quick and accurate retrieval of information. It also gives provision for proper
security. The system is very user friendly and the report is screen oriented. Available data
valuation, updating and integrity observed in the system are found to be satisfactory. This
software skillfully and successfully replaces large volume of manpower.
BOOKS REFERRED
2. Steven Holzner, “Visual Basic 6.0 Black Book”, 2003 Edition, Dreamtech
Publications
4. Pooja Bembey and Kuljit Kaur with NIIT,”Microsoft Visual Basic Professional
Projects”,2002 Edition, Prentice Hall of India Private Limited.
Websites:
1. www.msdn.microsoft.com
2. www.vbcity.com
3. www.codeguru.com