new

SAINTGITS COLLEGE OF APPLIED SCIENCES,
PATHAMUTTOM
Department of Computer Application
2014 – 2017
CERTIFICATE
Certified that this is the bonafide record of the project work entitled
APARTMENT MANAGEMENT SYSTEM
Submitted by
TIJO P ELIAS (140021046513), JOEL ALEX (140021046488), MIDHUN JAYAN (140021046495),
PRAVEEN XAVIER (140021046501), ASWATHY SABU (140021046480), GRAISU SARA SIMON
(140021046484)
In partial fulfillment of the requirements for the award of the degree of Bachelor of
Computer Application under the Mahatma Gandhi University during the year 2014-17.
Johnsymol Joy
Project Guide,
Department of Computer Application
Ambily Merlin Kuruvilla
Lecturer and Head,
Department of Computer Application

External Examiner
ACKNOWLEDGEMENT
It is with great pleasure that we find ourselves penning down these lines
to express our sincere thanks to various people who helped us a long way in
completing this project.
First and foremost , we thank GOD Almighty for giving us the opportunity to
complete this project successfully. We are grateful for all his blessings and his great care.
We are highly obliged to our principal, Prof.M.C. Joseph, for being the source of
inspiration and for his complete co-operation. we express our deep gratitude to our Head of BCA
Department Lr. Ambily Merlin Kuruvila and our faculty Lr.Johnsymol joy for their
encouragement and support throughout this project .
We are thankful to and fortunate enough to get constant encouragement , timely
support and guidance from all Teaching staffs of department of computer science which
helped us in successfully completing our project work. Also ,we would like to extend our
sincere regards to all the non-teaching staffs of department of computer science for their
timely support.

TABLE OF CONTENTS.
Chapter Title Page No
1 INTRODUCTION
1.1 Project Abstract
1.2 Objective and Scope
1.3 Problem Statement & Project Relevance
1.3.1 Problem Definition
1.3.2 Existing System
1.3.3 Proposed System
2 SYSTEM ANALYSIS & REQUIREMENT
SPECIFICATION
3 SYSTEM DESIGN & DEVELOPMENT
3.1 Modules
3.2 Data Flow Diagram
3.3 Data Base Design
3.4 Coding
4 TESTING
4.1 Testing Methodologies & Strategies
4.2 Testing Methods
4.2.1 Unit Test
4.2.2 Integration Test
4.2.3 System Test
5 IMPLEMENTATION & MAINTENANCE
5.1 Implementation Details
5.2 Screen Shots

6 CONCLUSION & FUTURE SCOPE
6.1 Conclusion
6.2 Future Scope
7 REFERENCES

INTRODUCTION

CHA
PT
ER
1.
INTRODUCTION
1.1 PROJECT ABSTRACT
In this modern world of technology, computers are affecting our lives in more ways than
we probably are aware of computerized management, maintaining information of institution. The
project “Apartment Management System” is a standalone application for private construction
firm. The main aim of the project is to provide utility to maintain day to day operations of the
apartments. This software helps them to store all transactions electronically in a system, which
in turn saves lot time, money and energy. This project is developed for a reputed construction
company in a city. This company built many apartments in the city and they have planned to
construct many other apartments in the city.
This software helps to main the track records of flat, ownership, booking, maintenance,
rent, employee details. It helps in replacing the manual system of record keeping with the
modern computerized system. Thus the project makes easy the hardships of manual apartment
management. It is an automated version of manual apartment management system.
1.2 OBJECTIVE AND SCOPE
Clearly the scope of project is to provide the employees and residents of the selected
apartment, an easy way of managing various apartment data. The project has mainly 2 types of
users:
Administrator
Staff

Each type of users has their own rights. And the project can be divided into five modules.
Next page constitutes of the module & user table:
1.3 PROBLEM STATEMENT AND PROJECT RELEVANCE
1.3.1 Problem Definition
The apartment management system has to handle records of a large number of flats,
booking, ownership, rent, maintenance details and the maintenance of these records was difficult.
Though it has used an information system, it was totally manual. Hence there is a need to
upgrade the system with a computer based information system.
1.3.2 Existing System
Every year the company is designing new apartments and it’s a difficult task to manage
the records of each and every apartment in the manual system. It will not only take a lot of time
but it also increases the chance of errors. Sometimes even after repeated cross-checks errors are
found which leads to wrong entry of details. It creates a problem when you need details of any
particular project. All these problems lead to the rise of an alternative option. It has the following
disadvantages:
1. Wastage of time :- As the computations are done manually, takes lot of time to
complete the works
2. Inaccuracy:- As the computations are done manually, the chances for occurrence of
errors is very high
3. Data checking is very difficult:- If we want to check the data, we have to search from
the beginning until we find it. So the data checking also take lot of time.
4. Paper file updating and keeping is a tedious process:- Data are stored to some extend
on paper file. Updating of file requires manual correction, which requires the physical
transfer of file from one place to another. This will consume more time.
5. Loss of corruption of records:- There are chances for loss of records due to fire or some
other reasons such as changes made by other persons
6. Human labor:- When processing is done manually, more manpower is needed

1.3.3 Proposed System
For managing all the details, we are proposing a software application that takes care of all
the important details in an apartment. Implementation of this software will help the users in
several ways. The present software application has various modules which can ease the work.
This system is 100% reliable as it provides accurate results. It also provides easy mechanism for
searching and editing different desired details. Thus the proposed system helps the company for
managing various apartment details by providing mass storage facility.
In short, by developing the system we attain the following features:
• Easy to handle and feasible
• Cost Reduction
• Fast and Convenient
• Maintainability
• User friendly
• Security
• Performance
• Ability to add employees
• Eliminate paper works. Go green
• Fully customizable
• Fully scalable
• Reduces HR daily works, increases productivity, user satisfaction, and a significant cost
savings

SYSTEM ANALYSIS & REQUIREMENT
SPECIFICATION

cha
pt
er
2.
SYSTEM ANALYSIS & REQUIREMENT SPECIFICATION
2.1 REQUIREMENT STUDY
2.1.1 Feasibility Report
Feasibility study is to determine whether the proposed system is technically,
economically and behaviorally feasible in all respects. The main aim of feasibility study is to
evaluate alternative system and propose the most feasible and desirable system for
development. If there is no loss for the organization then the proposed system is considered
financially feasible.
2.1.2 Technical Feasibility.
The project gives the instant responses to all sort of queries that are being raised.
The resources included are capable and can hold all types of data
the project will work on any platform if it is packaged and deployed
the project can be further expanded to satisfy the needs of the company
Hardware requirements.
CPU
HARD DISK SPACE
DISPLAY
MEMORY
OTHER DEVICES
: PIII and above processor
: 40 GB and above
: 15'' MONITOR
: 256 GB and above
: DVD Drive

Software requirements.
OPERATING SYSTEM : Windows 8 or compatible
FRONT-END
: Visual Basic
BACK-END :Microsoft sql server 2008
2.1.3 Economic Feasibility
This involves questions such as whether the company can afford to build the system, whether its
benefits should substantially exceed its costs, and whether the project has higher priority and
profits than the existing system. Here there is no problem. The company had a well-equipped
hardware and software, so no need to spend money on these issues. And as the client and
developer are one, there is no further problem in economic issues.
2.2 REQUIREMENT ANALYSIS AND CLASSIFICATION
Requirement analysis involves studying the current system to find out how it works and
where improvements could be made. A clear idea about the existing system is a must for making
improvements where it is required. Proper planning and collection of data services the purpose.
The system manages all the information about an apartment.
2.2.1 System Requirements
System Requirements specification is a collection of information that incorporates the
requirements of a system. This gives an idea about the system specification required to develop
and install the project “Apartment Management System”.
the
The software Requirement Specification is a technical specification of requirements for
software product. The goal of software requirements definition is to completely and

consistently specify the technical requirements for the software product in a concise and
unambiguous manner.The software Requirement Specification is based on the System
Definition. The requirement specifications are primarily concerned with functional and
performance aspects of a software product and emphasis are placed on specifying product
characteristics implying how the product will provide those characteristics.
One of the difficult tasks is selecting software, once the system requirement is found out
then we have to determine whether a particular software package fits for those system
requirements. This section summarizes the application requirements.
2.2.2 Hardware Requirements
CPU - PIII and above processor
HARD DISK SPACE
RAM
DISPLAY
- 40 GB and above
- 256 and above
- 15'' MONITOR
2.2.3 Software Requirements
OPERATING SYSTEM :- Microsoft Windows 8
FRONT-END :-Visual Basic 6.0
BACK-END :-Microsoft SQL Server 2008

SYSTEM DESIGN AND DEVELOPMENT

CHA
PT
ER
3.
SYSTEM DESIGN & DEVELOPMENT
3.1 Modules
1) Flat Management
This module includes managing the flat details such as flat, booking, ownership,
rent, maintenance details. Staff enters the details and updates the changes.
Administrator will view the entire details given by the staff to manage the flat.
2) Employee Management
This module includes managing the employee details .Staff will provide the
details about each employee. Administrator is the overall controller of this
module.
3) Report Generation
In this module, report is generated by the administrator about salary and flat
details. Staff can have no access to this module
3.2 DATA FLOW DIAGRAM
A data flow diagram (DFD) is a network that describes the flow of data throughout a
system, data stores and the processes that changes, or transform, data flows. The DFD network is
a formal, logical abstract of a system that may have many possible physical configurations. For
this reason, a set of symbols that do not imply a physical form is used to request data sources,
data flows, data transformation and data storage. they represent one of the most ingenious tools

used for structured analysis. It has the purpose of clarifying system design. It is the major starting
point in the design phase that functionality decomposes the requirement specification down to
the lowest level of detail. Structured analysis follows a top-down approach to describe the
system. An initial model of the system only shows major activities of the system and this model
is then explored into more detailed lower level diagrams. Each process in the system can be
described with data flow diagram and can be broken into several another process to fully
understand the system. In the normal convention, the DFD has four major symbols.
Figure:1, Symbols Used
The following are the symbols used in the Data Flow Diagram:
:Rectangle, which defines source or destination
of data.
:Arrow, which shows data flow.
:Circle, which represents a process that transforms
incoming data into outgoing data.

:Open Rectangle, which shows data store.
Figure:2, Level 0(Context Diagram).
request
response
USER
Apartment
management
System
USER
Staff Level

Figure:3, Level 1
Figure:4, Level 1.1

Figure:5,Level 1.2
Figure:6,Level 1.3

Figure:6, Level 1.4
Figure:7, Level 1.5

Admin Level

Figure:8, Level 1
Figure:9, Level 1.1

Figure:10,level 1.2

Figure:11, level 1.3

3.3 DATABASE DESIGN
Table1: tbl_Login.
FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION
Id Int Primary Key Resident id
Username n varchar(50) Not null Username
Password n varchar(50) Not null password
Role n varchar(50) Not null Person who log in
Table2: tbl_empreg
FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION
Emp_id Int Primary key Employee id
Emp_name nvarchar(50) Not null Employee name
Address nvarchar(50) Not null Employee address
Gender nvarchar(50) Not null Gender
Age Int Not null Age
Email nvarchar(50) Not null Email Address
Phone nvarchar(50) Not null Phone number
Qualification nvarchar(50) Not null Qualification
Experience Nchar(10) Not null Experience
Designation nvarchar(50) Not null Designation
Date_join Date Not null Date of Join
Salary Int Not null Salary

Table3: tbl_book
FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION
Id Int Primary Key Booking id
Name nvarchar(50) Not null Resident Name
Address nvarchar(50) Not null Resident Address
Phone nvarchar(50) Not null Phone Number
Email nvarchar(50) Not null Email Address
Flatno Int Foreign Key Flat number
Tenants nvarchar(50) Not null Tenants
Total_amount nvarchar(50) Not null Total Amount
Advance nvarchar(50) Not null Advance Amount
Balance_amt nvarchar(50) Not null Balance Amount
Transaction_mode nvarchar(50) Not null Transaction Mode
Book_date nvarchar(50) Not null Booking date
Status nvarchar(50) Not null Status
Total_residents Int Not null Total Residents
Table4: Tbl_flat1
FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION
Flat_no Int Primary Key Flat number
Floor_no Int Not null Floor number
Furnished nvarchar(50) Not null Furnished
Rooms nvarchar(50) Not null Number of rooms
Amount nvarchar(50) Not null Total amount
Status nvarchar(50) Not null Flat status

Table 5: tbl_owner
FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION
Id Int Primary Key Owner id
Name nvarchar(50) Not null Owner name
Mobile nvarchar(50) Not null Owner mobile number
Email nvarchar(50) Not null Owner email
Flatno Int Foreign Key Flat no
Tenants nvarchar(50) Not null Type of resident
Parking nvarchar(50) Not null Mode of parking
Transaction_mode nvarchar(50) Not null Mode of transaction
Date_entry nvarchar(50) Not null Date
Table6: tbl_rent
FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION
Id Int Primary Key Rent id
Name nvarchar(50) Not null Resident name
Mobile nvarchar(50) Not null Resident mobile
number
Email nvarchar(50) Not null Resident email
Flatno Int Foreign Key Resident flatno
Tenants nvarchar(50) Not null Type of Resident
Parking nvarchar(50) Not null Mode of parking
Transaction_mode nvarchar(50) Not null Mode of transaction
Rent_date nvarchar(50) Not null Rent date
Amount nvarchar(50) Not null Rent amount

Table 7: tbl_main
FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION
Id Int Primary key Id
Flatno Int Foreign Key Flat number
Type nvarchar(50) Not null Type of maintenance
Person_allotted nvarchar(50) Not null No. of person allotted
for maintenance
Status nvarchar(50) Not null Status of the request
3.4 CODING
The process of creating and maintaining information system is called system development
system analysis and design. In addition to technical knowledge, it requires business knowledge
and management skill. System development is also known as “Procedures design” is a series of
operations carried out according to the specification in order to manipulate the data stored
through the input to produce required output from the computer system. The principle activities
performed during the development phase can be divided into major sequences:
‣ External System Development
Implementation planning
Preparation of manuals
Personal training
‣ Internal System Development
Computer program development
Overall system performance testing

3.4 CODE
1. CONNECTION MODULE
Public cn, rs, s
Public Function CONNECT()
Set cn = New ADODB.Connection
cn.Open = "Provider=sqloledb;server=DELL-
PC\SQLEXPRESS;database=apartment;trusted_connection=yes"
Set rs = New ADODB.Recordset
End Function
2.MAIN MDI FORM
Private Sub emp_Click()
DataReport1.Show
End Sub
Private Sub MDIForm_Load()
Call CONNECT
'rs.Open "select * from tbl_log1 ", cn, adOpenDynamic, adLockPessimistic
If s = "admin" Then
mnuemp.Visible = True
mnuviewdetails.Visible = True
mnureports.Visible = True
mnulogoff.Visible = True
mnuflat.Visible = False
mnuowner.Visible = False

mnubooking.Visible = False
mnurent.Visible = False
Else
mnuflat.Visible = True
mnuowner.Visible = True
mnubooking.Visible = True
mnulogoff.Visible = True
mnumain.Visible = True
End If
End Sub
Private Sub mnuadd_Click()
flatdetails.Show
End Sub
Private Sub mnuaddbooking_Click()
Form7.Show
End Sub
Private Sub mnuaddemp_Click()
Form10.Show
End Sub
Private Sub mnuaddmain_Click()
Form14.Show
End Sub
Private Sub mnuadowner_Click()
Form2.Show
End Sub

Private Sub mnuadrent_Click()
rentdetails.Show
End Sub
Private Sub mnubookingdetails_Click()
Form9.Show
End Sub
Private Sub mnuflatdetails_Click()
Form13.Show
End Sub
Private Sub mnulogoff_Click()
Form4.Show
Unload Me
End Sub
Private Sub mnumaindetails_Click()
Form16.Show
End Sub
Private Sub mnuownerdetails_Click()
Form6.Show
End Sub
Private Sub mnusearch_Click()
Form3.Show
End Sub
Private Sub mnusearchemp_Click()
Form12.Show

End Sub
Private Sub mnuupdate_Click()
Form5.Show
End Sub
Private Sub mnuupdatebooking_Click()
Form8.Show
End Sub
Private Sub mnuupdateemp_Click()
Form11.Show
End Sub
Private Sub mnuupdatemain_Click()
Form15.Show
End Sub
Private Sub mnuupdaterent_Click()
Form17.Show
End Sub
Private Sub mnuview_Click()
Form6.Show
End Sub
Private Sub mnuviewbooking_Click()
Form9.Show
End Sub
Private Sub mnuviewmain_Click()

Form16.Show
End Sub
Private Sub mnuviewrent_Click()
Form18.Show
End Sub
Private Sub r_Click()
Form18.Show
End Sub
Private Sub upd_Click()
Form1.Show
End Sub
3.LOGIN FORM
Private Sub Command1_Click()
Call CONNECT
If Text1.Text = "" Or Text2.Text = "" Then
MsgBox ("Please enter data")
Else
rs.Open "select * from tbl_log1 where Username='" + Text1.Text + "' and
Password = '" + Text2.Text + "'", cn, adOpenDynamic, adLockPessimistic
If rs.EOF = False Then
s = rs.Fields("Role")
If s = "admin" Then
MDIForm1.Show
ElseIf s = "employee" Then
MDIForm1.Show
End If

Else
MsgBox ("invalid username or password")
End If
End If
Text1.Text = ""
Text2.Text = ""
Unload Me
End Sub
4 .EMPLOYEE DETAILS
Dim g, e
Private Sub Command1_Click()
Call CONNECT
rs.Open "select * from tbl_empreg", cn, adOpenDynamic,
adLockPessimistic
rs.AddNew
rs.Fields("Emp_name") = Text1.Text
rs.Fields("Address") = Text2.Text
If Check1.Value = 1 Then
g = "Male"
ElseIf Check2.Value = 2 Then
g = "Female"
End If
rs.Fields("Gender") = g
rs.Fields("Age") = Text3.Text
rs.Fields("Email") = Text4.Text
rs.Fields("Phone") = Text5.Text
rs.Fields("Qualification") = Combo1.Text
If Check3.Value = 1 Then
e = "Yes"

ElseIf Check4.Value = 1 Then
e = "No"
End If
rs.Fields("Experience") = e
rs.Fields("Designation") = Text6.Text
rs.Fields("Date_join") = Date
rs.Fields("Salary") = Text7.Text
rs.Update
MsgBox ("Successfully registered")
rs.Close
End Sub
Private Sub Command2_Click()
MDIForm1.Show
End Sub
5.BOOKING DETAILS
Dim s, b, t
Private Sub Check1_Click()
Check2.Enabled = False
End Sub
Private Sub Check2_Click()
Check1.Enabled = False
End Sub
Private Sub Check3_Click()
Check4.Enabled = False
Check5.Enabled = False

End Sub
Private Sub Check4_Click()
Check3.Enabled = False
Check5.Enabled = False
End Sub
Private Sub Check5_Click()
Check3.Enabled = False
Check4.Enabled = False
End Sub
Private Sub Command1_Click()
Call CONNECT
rs.Open "select * from tbl_book", cn, adOpenDynamic, adLockPessimistic
rs.AddNew
rs.Fields("Name") = Text1.Text
rs.Fields("Address") = Text2.Text
rs.Fields("Phone") = Text3.Text
rs.Fields("Email") = Text4.Text
rs.Fields("flatno") = Text12.Text
If Check3.Value = 1 Then
t = "Family"
ElseIf Check4.Value = 1 Then
t = "Friends"
ElseIf Check5.Value = 1 Then
t = "Single"
End If
rs.Fields("Tenents") = t

s.Fields("Total_amount") = Text9.Text
rs.Fields("Advance") = Text10.Text
rs.Fields("Balance_amt") = Text11.Text
If Check1.Value = 1 Then
s = "By cash"
ElseIf Check2.Value = 1 Then
s = "By cheque"
End If
rs.Fields("Transaction_mode") = s
rs.Fields("Book_date") = Date
rs.Fields("Status") = "Booked"
rs.Update
MsgBox ("Successfully booked")
rs.Close
End Sub
Private Sub Text10_Change()
Text11.Text = Val(Text9.Text) - Val(Text10.Text)
End Sub
6.BOOKING UPDATE DETAILS
Private Sub Combo1_Click()
Call CONNECT
rs.Open "select * from tbl_book where Name = '" + Combo1.Text + "'", cn,
adOpenDynamic, adLockPessimistic
Text1.Text = rs.Fields("Book_date")

Text2.Text = rs.Fields("flatno")
Text5.Text = rs.Fields("Total_residents")
Text6.Text = rs.Fields("Total_amount")
Text7.Text = rs.Fields("Advance")
Text8.Text = rs.Fields("Balance_amt")
rs.Update
End Sub
Private Sub Command1_Click()
Call CONNECT
rs.Open "select * from tbl_book where Name = '" + Combo1.Text + "'", cn,
adOpenDynamic, adLockPessimistic
rs.Fields("Book_date") = Text1.Text
rs.Fields("flatno") = Text2.Text
rs.Fields("Total_residents") = Text5.Text
rs.Fields("Total_amount") = Text6.Text
rs.Fields("Advance") = Text7.Text
rs.Fields("Balance_amt") = Text8.Text
rs.Update
MsgBox ("Successfully updated")
End Sub
Public Function bindcombo()
Call CONNECT
rs.Open "select * from tbl_book", cn, adOpenDynamic, adLockPessimistic
While rs.EOF = False
Combo1.AddItem (rs.Fields("Name"))
rs.MoveNext
Wend
End Function

Private Sub Command2_Click()
Call CONNECT
rs.Open "select * from tbl_book where Name = '" + Combo1.Text + "'", cn,
adOpenDynamic, adLockPessimistic
rs.Fields("Book_date") = Text1.Text
rs.Fields("flatno") = Text2.Text
rs.Fields("Total_residents") = Text5.Text
rs.Fields("Total_amount") = Text6.Text
rs.Fields("Advance") = Text7.Text
rs.Fields("Balance_amt") = Text8.Text
rs.Fields("Status") = "Cancelled"
rs.Update
MsgBox ("Successfully cancelled")
rs.Open "select * from tbl_flat1 where Flat_no = '" + Text2.Text + "'", cn,
adOpenDynamic, adLockPessimistic
rs.Fields("Status") = "Not booked"
End Sub
Private Sub Command3_Click()
MDIForm1.Show
End Sub
Private Sub Form_Load()
bindcombo
End Sub
Private Sub Text7_Change()

Text8.Text = Val(Text6.Text) - Val(Text7.Text)
End Sub
7.FLAT DETAILS
Dim s, r
Private Sub Check1_Click()
Check2.Value = 0
End Sub
Private Sub Check2_Click()
Check1.Value = 0
End Sub
Private Sub Check3_Click()
Check4.Value = 0
End Sub
Private Sub Check4_Click()
Check3.Value = 0
End Sub
Private Sub Command1_Click()
Call CONNECT
rs.Open "select * from tbl_flat1", cn, adOpenDynamic, adLockPessimistic
rs.AddNew
rs.Fields("Flat_no") = Text1.Text
rs.Fields("Floor_no") = Text2.Text
If Check1.Value = 1 Then
s = "Yes"

ElseIf Check2.Value = 1 Then
s = "No"
End If
rs.Fields("Furnished") = s
If Check3.Value = 1 Then
r = "3BHK"
ElseIf Check4.Value = 1 Then
r = "2BHK"
End If
rs.Fields("Rooms") = r
rs.Fields("Amount") = Text3.Text
rs.Fields("Status") = "Not booked"
rs.Update
MsgBox ("saved")
clear
End Sub
Public Function clear()
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
End Function
8.FLAT UPDATE DETAILS
Private Sub Combo1_Click()
Call CONNECT

s.Open "select * from tbl_flat1 where Flat_No = '" + Combo1.Text + "'",
cn, adOpenDynamic, adLockPessimistic
Text2.Text = rs.Fields("Floor_No")
Text3.Text = rs.Fields("Furnished")
Text4.Text = rs.Fields("Rooms")
Text5.Text = rs.Fields("Amount")
rs.Update
End Sub
Private Sub Command1_Click()
Call CONNECT
rs.Open "select * from tbl_flat1 where Flat_No = '" + Combo1.Text + "'",
cn, adOpenDynamic, adLockPessimistic
rs.Fields("Floor_No") = Text2.Text
rs.Fields("Furnished") = Text3.Text
rs.Fields("Rooms") = Text4.Text
rs.Fields("Amount") = Text5.Text
rs.Update
MsgBox ("Successfully updated")
End Sub
Private Sub Command2_Click()
Call CONNECT

s.Open "select * from tbl_flat1 where Flat_No = '" + Combo1.Text + "'",
cn, adOpenDynamic, adLockPessimistic
rs.Fields("Floor_No") = Text2.Text
rs.Fields("Furnished") = Text3.Text
rs.Fields("Rooms") = Text4.Text
rs.Fields("Amount") = Text5.Text
rs.Update
MsgBox ("Successfully cancelled")
End Sub
Private Sub Form_Load()
bindcombo
End Sub
Public Function bindcombo()
Call CONNECT
rs.Open "select * from tbl_flat1", cn, adOpenDynamic, adLockPessimistic
While rs.EOF = False
Combo1.AddItem (rs.Fields("Flat_no"))
rs.MoveNext
Wend
End Function
9.OWNER DETILS
Dim s, r
Dim t1, t2

Dim tm1
Private Sub Check1_Click()
Check2.Visible = False
End Sub
Private Sub Check2_Click()
Check1.Visible = False
End Sub
Private Sub Check3_Click()
Check4.Visible = False
End Sub
Private Sub Check4_Click()
Check3.Visible = False
End Sub
Private Sub Check5_Click()
Check6.Visible = False
End Sub
Private Sub Check6_Click()
Check5.Visible = False
End Sub
Private Sub Combo1_Click()
Call CONNECT
rs.Open "select * from tbl_flat1 where Flat_no ='" + Combo1.Text + "'", cn,
adOpenDynamic, adLockPessimistic

If rs.EOF = False Then
Text5.Text = rs.Fields("Floor_no")
Text6.Text = rs.Fields("Amount")
rs.Update
End If
End Sub
Private Sub Command1_Click()
Call CONNECT
Text4.Text = Date
rs.Open "select * from tbl_owner", cn, adOpenDynamic, adLockPessimistic
rs.AddNew
rs.Fields("Name") = Text1.Text
rs.Fields("Mobile") = Text2.Text
rs.Fields("Email") = Text3.Text
rs.Fields("Date_entry") = Text4.Text
rs.Fields("flatno") = Combo1.Text
If Check1.Value = 1 Then
t1 = "Family"
ElseIf Check2.Value = 1 Then
t1 = "Friends"
End If
rs.Fields("Tenents") = t1
If Check3.Value = 1 Then
t2 = "2 weeler"
ElseIf Check4.Value = 1 Then
t2 = "4 weeler"
End If

s.Fields("Parking") = t2
If Check5.Value = 1 Then
tm1 = "By cash"
ElseIf Check6.Value = 1 Then
tm1 = "By cheque"
End If
rs.Fields("Transaction_mode") = tm1
rs.Fields("Date_entry") = Date
rs.Update
rs.Close
rs.Open "select * from tbl_flat1 where Flat_no = '" + Combo1.Text + "'",
cn, adOpenDynamic, adLockPessimistic
rs.Fields("Status") = "booked"
rs.Update
End Sub
Public Function bindcombo()
Call CONNECT
rs.Open "select * from tbl_flat1", cn, adOpenDynamic, adLockPessimistic
While rs.EOF = False
Combo1.AddItem (rs.Fields("Flat_no"))
rs.MoveNext
Wend
End Function
Private Sub Form_Load()
Call bindcombo
End Sub

10.OWNER UPDTAE DETAILS
Private Sub Combo1_Click()
Call CONNECT
rs.Open "select * from tbl_owner where flatno = '" + Combo1.Text + "'",
cn, adOpenDynamic, adLockPessimistic
Text1.Text = rs.Fields("Name")
Text2.Text = rs.Fields("Mobile")
Text3.Text = rs.Fields("Email")
Text4.Text = rs.Fields("Tenents")
Text5.Text = rs.Fields("Parking")
End Sub
Private Sub Command1_Click()
Call CONNECT
rs.Open "select * from tbl_owner where flatno = '" + Combo1.Text + "'",
cn, adOpenDynamic, adLockPessimistic
rs.Fields("Name") = Text1.Text
rs.Fields("Mobile") = Text2.Text
rs.Fields("Email") = Text3.Text
rs.Fields("Tenents") = Text4.Text
rs.Fields("Parking") = Text5.Text
rs.Update
MsgBox ("Successfully updated")
MDIForm1.Show
End Sub
Private Sub Command2_Click()
Call CONNECT

s.Open "select * from tbl_owner where flatno = '" + Combo1.Text + "'",
cn, adOpenDynamic, adLockPessimistic
rs.Delete
MsgBox ("Succesfully deleted")
End Sub
Private Sub Form_Load()
bindcombo
End Sub
Public Function bindcombo()
Call CONNECT
rs.Open "select * from tbl_flat1 where Status = 'booked' ", cn,
adOpenDynamic, adLockPessimistic
While rs.EOF = False
Combo1.AddItem (rs.Fields("Flat_no"))
rs.MoveNext
Wend
End Function

TESTING

CHA
PT
ER
4.
TESTING
4.1 TESTING METHODOLOGIES AND STRATEGIES
Software testing is an integral part of development to ensure software quality. Some
software organizations are reluctant to include in their software cycle, because they are afraid of
the high cost associated with the software testing. There are several factors that attribute that cost
of software testing. creating and manipulating large number of tester cases is a time consuming
process. Furthermore, it requires skilled and experienced tester to develop greater quality test
cases. Even with the wide availability of automation tools for testing, the degree of automation
mostly remains at the automated test script level, and generally, significant amount of human
intervention is required in testing. Testing provides a good indication of software as a while .The
debugging process is the most unpredictable part of testing process.
Testing begins at the module level and work towards the integration of the entire
computer based system. No testing is the complete without verification and validation part. The
goal of verification and validation activities are to access and improve the quality of work
product generated during the development and modification of the software. Testing plays a vital
role in determining the reliability and efficiency of the software and hence is very important
stage in software development. Test is to be conducted on the software to evaluate its
performance under a number of conditions .Ideally, it should do so at the level of each module
and also when all of them are integrated to form the complete system.

In the project "APARTMENT MANAGEMENT SYSTEM" the testing has been
successfully handled with the modules. The test data was given to each and every module in all
respect and got the desired output. Each module that has been tested is found working properly.
4.2 TESTING METHODS
The entire process can be divided into 3 phases
.Unit Testing
.Integrated Testing
. Final/System Testing
4.2.1 Unit Test
Here, we test each module individually and integrate the overall system. Unit test focuses
verification efforts even in the smallest unit of software design in each module. This is known as
‘Module testing'. The modules of this project are tested separately .This testing is carried out in
the programming style itself. In this testing each module is focused to work satisfactory as regard
to expected output from the module. There are some validation checks for the fields unit testing
gives stress on the modules of 'Apartment management system independently of one another, to
find errors. Here different modules are tested against the specification produced during the
design of the modules. Unit testing is done to test the working of individual modules with test
SQL servers .Program unit is usually small enough that the programmer who developed it can
test it in a great detail. Until testing focuses first on the modules to locate errors. These errors
are verified and corrected and so that the unit perfectly fits to the "apartment management
system".
4.2.2 Integration Test
Data can be lost across an interface ,once module can have an adverse effect on the other
sub functions, when combined they may not perform the desired functions. Integrated testing is
the systematic testing to uncover the errors within the interface .This testing is done with simple

data and the developed system has run successfully with this data. The need of integrated system
is to find the overall system performance .In this whole modules college Apartment management
system are connected and tested.
4.2.3 System Test
System testing focuses on testing the system as a whole. System testing is a crucial step
in quality management process. In the software development life cycle ,system testing is the first
level where the system is tested as a whole .The system is tested to verify whether it meets the
functional and technical requirements .The application /system is tested in an environment
closely resembles production environment where the application will be finally developed.

IMPLEMENTATION & MAINTENANCE

CHA
PT
ER
5.
IMPLEMENTATION & MAINTENANCE
INTRODUCTION
The implementation is one phase of software development. Implementation is the stage in
the project where theoretical design is turned into working system. Implementation involves
placing the complete and tested software system into actual work environment. Implementation
is concerned with translating design specification with source code.
The primary goal of implementation is to write the source code to its specification that
can be achieved by making the source code clear and straight forward as possible.
Implementation means the process of converting a new or revised system design into operational
one.
The three types of implementation are
Implementation of a computerized system to replace a manual system
Implementation of a new system to replace existing one
Implementation of a modified system to replace an existing one
5.1 IMPLEMENTATION DETAILS

The implementation process is as follows:
Requirement analysis and project planning
The project started on 09-06-2015 and the first phase was analyze the requirements like
Who will be the end user and what total expected duration for completion of project .There were
several meeting conducted with project-in-charge.
For project planning there were two modules
Admin module
User module
Design
The second phase of the implementation was design phase. In this phase before the
coding the DFD, Database Design were done.
Coding
The coding phase is the next phase in the model. The coding was done with the visual
basics 6.0 which handled the front end and MS SQL SERVER 2008 handles the backend.
Testing
Once the coding phase gets completed the next major phase was the testing phase.
System testing was conducted against the requirements and almost all of the requirements got
satisfied.
Implementation
The final phase of the project is the implementation . The project was implemented and
worked correctly in the local system.
Front End Description

Visual basic is the favorite programming environment of many users. When visual basics
was originated, it created a revolution in windows programming, and that revolution appears to
this day. Windows programming was never easy as it is in using visual basics it is so easy that
Programs are made right before the eyes and are executed.
Visual basic was derived from BASIC, and is an event –driven programming language.
Programming in visual basics is done visually, which means that as you can see how our
application will look on execution. We can therefore change and experiment with design to meet
our requirement .visual basic 6.0 has many powerful features that are required in today’s
programming environment. Visual basic is used in a task-oriented way, which is the best way to
write programs. VISUAL BASIC is high level programming language which evolved from the
earlier DOS . Version called BASIC.BASIC means Beginners All purpose Symbolic instruction
Code .it is a relatively easy programming language to learn.
Features of Visual Basic
‣ Visual basic applications are event driven: Event driven means the user
is in control of the application. The user generates a stream of events each time be or she clicks
with the mouse or presses a key on the keyboard. Your visual basic application responds to those
events through the code you’ve written and attached to those events.
‣ Visual basic support the principle of object-oriented design: This means
that you can compartmentalize different aspect of your application as object and develop and
test those object independently of the rest of application .By modifying certain properties and
invoking the methods of these objects ,you exert a great deal of control over the user’s
interaction with the visual basic program you’ve written.
‣ Microsoft has designed Visual Basic to be complete windows application
developed system: This means that your Visual Basic application will look and behave like
other windows programs your user might work with .In other words ,your visual basic
application will conform to the windows 95 look and feel without any extra work on your part.
‣ Visual basic is infinitely extensible through the use of active controls,
Dynamically Linked Libraries (DDLs), and add –ins: you can create ActiveX

controls ,DDLs, and add-ins with Visual Basic 6 or buy them off shelf from a large number of
third –party software vendors.
Backend Description
SQL is a standard language for communicating with the RDBMS from any tool SQL
can be used by a range of users. It is non-procedural language which looks like English language.
When you enter an SQL statement , it is stored in SQL buffer and remains there until you enter a
new statement.
DDL:-DDL is the part of ESQL. it stands for Data Definition language. It provides
statement for creation and deletion of the database. The DDL statements insulate you from the
low level details of how data is physically stored in the database statement are: CREATE
TABLE,ALTER TABLE ,DROP TABLE etc.
DML:- DML is also the part of SQL .it stands for Data Manipulation Language . it
provides statements For manipulating the database. The DML statements can modify the data
stored in the database, but may cannot change its structure. It includes commands to insert
,delete and modify tuples in the database
Features of SQL
‣ Recovery and concurrency: Concurrency is concerned with the manner in which
multiple users operate the database. Each user can either reflect the updates of a
transaction or can cancel all the updates of a transaction.
‣ Security: The security can be maintained by view mechanism .A view is used to hide
sensitive information and defines only part of a table which should be visible.
‣ Integrity constraints: They are enforced by the system .For example, one can specify
that an attribute of a relation will not take on null values.
What SQL can do?
SQL can retrieve data from a database
SQL can insert records in a database
SQL can update records in a database

SQL can delete records from a database
SQL can create new databases
SQL can create new tables in a database
SQL can create stored procedures in a database
SQL can create views in a database
.SQL can set permission on tables ,procedures, and views
.SQL can execute queries against a database
Query Analyzer
Query analyzer is another tool with SQL server, which extends the capabilities of ANSI
standard SQL . it is an application that recognizes and executes SQL commands and specialized
T_SQL Commands that can be used to create database objects using SQL commands.
o We can use query analyzer commands to
o Enter ,edit, Sore and Retrieve and Run SQL commands.
o Format, perform calculations on ,store and print query results.
o List columns definitions for any table
o Access any copy of data between SQL database
o We can create tables and insert data or alter it or we can delete data using SQL
commands

5.2 SCREENSHOTS
Figure 13: add flat

Figure 14: add owner
Figure 15: booking view

figure 15:emp report
Figure 16:empreg

Figure 17:flat booking

Figure 18: flat report
Figure 19: Flat view

Figure
20:login
Figure 21: Maintenance

Figure 22:Maintenance view
Figure 23: owner view

Figure 24: rent view

CONCLUSION & FUTURE SCOPE

CHA
PT
ER
6.
CONCLUSION & FUTURE SCOPE
6.1 CONCLUSION
Developing a computer based system for construction company was a matter of essence.
It will be the medium for the apartment management system for the proper management of
residents information in an organized way. the conclusion can be summed up as follows:
Apartment management system has made easy flow of information.
Since the data are organized in the database, and are secure in computer system,
loss of information in minimized.
The system which we had developed is tested with real data and was found to be error
free. Also, it is found that the system will work successfully. We tried to make the system
maximum user friendly.
6.2 FUTURE SCOPE
The project can be later expanded to be used in a network system with a perfect working
condition than in a standalone system. An online system for registration can be developed.

CHA
PT
ER
REFERENCES
7.
Elements of System Analysis and Design
Visual Basic 6.0
Database Management System
-Marvin Gore
-Peter Norton
- Shamkant B. Navathe