1.

INTRODUCTION

1.1 OVERVIEW OF THE PROJECT

This project named “ Building Constriction Management System ” is used

The system provides Land and Construction information; with a user-friendly Graphics User
Interface (GUI).The scope of this project is limited to handling Customer and their Booking
module. This can be extended to include other modules of Builders and Developers
Organization. The project aims to develop software, which will store data about Customers
Details and Land Available, Booking Lands, Raw Material, Report and so on.
The current system is base on manual procedures. Means, all the records of about
customers, Land Owner, etc. are store manually in to the file registers. They have to maintain
that record for long duration, but the maintaining all this records as manually is very difficult
task.
The project has a facility to save, edit, delete or insert any records. The front end, which has been
used in this project is Visual Basic and the backend is MS Access.

1.2 SYSTEM SPECIFICATION

1
 1.2.1 Hardware Configuration

Computer : Personal

Processor : Pentium 111

RAM : 64MB.

Hard Disk Drive : 40 GB.

Cd ROM Drive : 52 x cd-ROM.

Monitor : 15 inch color Samsung.

Mouse : Logitech

Keyboard : Board with 104 Keys.

1.2.2 Software Specification

Front End : Visual Basic

Back End : Ms-Access

Operating System : Windows XP

1.2.3 SOFT WARE DESCRIPTION

2
VISUAL BASIC 6.0

The visual part refers to the method used to create the graphical user interface (GUI).
The ‘Basic’ part refers to the BASIC (Beginners All – Purpose Symbolic Instruction Code)
Language. Visual Basic has evolved from the original basic language and now contains several
hundred statements Functions and keyword, many of which relate directly to the Windows GUI.

The first tool to make Windows based programming easy the Microsoft Visual Basic
version 6.0 programming. System is now the leading tool for helping, developers create and use
Active X components, build Active Documents for intranet browsers, build client/server or multi
– tier solutions with high speed data access and built fast applications based on Windows version
6.0 adds a native code compiler, implicit multi – threading and integration with Microsoft
Transaction Server to bring a new level of scalability to server based components built with
Visual Basic.
Visual Basic 6.0 also provides developers with a new interface for faster programming.
The IDE now features Multiple Document Interface (MDI) with docking and linking. Windows
to eliminate unnecessary, mouse and keyboard actions and the code editors offers Intelli Sense
Technology such as Quick Tips, Data Tips, List Members and List Constants which eliminate the
need to memorize syntax and learn object models.

Visual Basic 6.0 is an application development tool used in developing Client/Server

applications. Before beginning with visual Basic 6, let’s have a look at the client/Server
architecture.

3
MS-ACCESS

MS-Access is a database management system (DBMS). Like other items in the category,
Access stores and retrieves data, presents information and automates repetitive tasks (such as
maintaining accounts payable, inventory control and scheduling).
Access is also a powerful windows application, for the first time, the itemivity database
meets the usability of Microsoft windows and Access are also from Microsoft the two items
works very well together. Access runs on windows platform, so all the advantages of windows
are available in access. Using OLE (object Linking and Embedding) objects in windows 98 items
we can extend access into a being true database operating environment through integration with
these items.
Access is a set of tools for end user database management. Access has a creator, a form
designer, a query manager, and a report writer. Access provides a new relational database
management. Access includes definition for primary and foreign keys, and has a full referential
integrity built in a level of database engine itself. The relational processing in access fills many
needs with its flexible architecture. It can be used as a standalone database management system,
in a file server configuration or it can be used as a backend for VB or VC++ etc.

1. SYSTEM STUDY

4
2.1 Existing System :

The system, which is followed at present, is a manual system. Important drawback of

existing system is time factor. It will not help the management to solve the problem in time.

The existing system has been carried manually. It is a tedious and time consuming
process. At each level of processing data are updated in ledger manually by the Chief. So data
are not retrieved easily. There is no facility for monitoring and reporting the work progress and
the day-to-day transactions.

The existing system needs to be computerized by new software technology for maintaining day-
to-day operations effectively. Building is looking forward the graphical user interface with all the
functions for their transaction with security aspects.

2.1.1 DRAWBACKS

It is very difficult and time consuming to maintain all the details in to the registers when the
organization is very big.
• Modifying the records is not very easy, since for a minute change the whole record would be
required to re-entered. For instance, if , the address of any customer changes then locating that
customer and doing modification in registers is very tedious.
• It also take much time for doing entry and checking of records.
• There is also possibility of mismatching of entries during entry of records.
• To make and maintain the different reports is also very tough and tedious job.
• Information is stored into registers, which requires large storage space.
• Searching particular record is very tedious job, since as a time passes the condition of the
registers becomes bad.
• Every year, they have to maintain new registers.

2.2 PROPOSED SYSTEM

5
To overcome the drawbacks of present system and ease the working of such consultancies our
project comes into the picture. Our software is multifunctional which includes land introduction,
customer introduction, and agreement system.
• The master file that is file which contains all the details of the data’s which are kept for long
time are land master, flat master and customer master.
• The land master contains all the details of different lands with their owner location,
purchasing date, total area, owner name, etc.
The flat master contains land no., flat no, area, rate, etc.
Raw master contains details of the raw material like its name, price, its limit value, etc.
The customer master contains personal details of the customer like customer id, customer name,
profession, office address, etc.
• Transaction file contains Payment details, Construction, Booking, Agreement, Cancellation,
etc.
• In construction transaction it will keep the information of the total available raw material,
total used raw material. Also you can get the message if the total available quantity is less than
the limit value.
2.2.1 FEATURE
provide information in a quick time according to the requirements that are to be
Fulfilled.
• Easier retrieval will be possible as multiple search facilities will be available.
• Security of data.
• The important process is integrated together for a proper functioning.
• Redundancy of data is removed.
• Inconsistency of data is removed.
• The Paper Work would be reduced to a greater extent.

2. SYSTEM DESIGN AND DEVELOPENT

6
 3.1 DATAFLOW DIAGRAM

Data flow diagram is a structured analysis tool for showing the movement of data through
the different transformation or processes in the system. Named bubbles show the processes and
data named arrows, entering or leaving the bubbles, represent flows. A rectangle represents a
source or sinks and is a net originator or consumer of data. A source or sink is typically outside
the main system study. DFD can be hierarchically organized which helps in partitioning and
analyzing the large system, such system are called leveled DFD’s. For the hierarchy to be
consistence it is important that net input or output of a DFD for a process are the same input and
output of the process in the higher level DFD. The refinement stops until each bubble is atomic.

The data flow diagram may be used to represent a system or software at any level of
abstraction. In fact, DFD may be partitioned into levels that represent increasing information
flow and functional detail. A level 0 DFD is called a Context Level DFD. This model represents
entire software element as a single bubble with input and output data indicated by incoming and
outgoing arrows respectively.
DFD is a Graphical representation of the flow data through an information system, modeling in
DFD primary steps is creates an overview of the system.

Types of DFD
1) Physical DFD
An information dependent view of the current system showing what the data’s are carried
out and how they are performed.

2) Logical DFD
An implementation independent view of the system focusing on the flow of data between
process without specified devices storage locations or people in the system.

7
DFD Components
Entity
An Entity is the source of destination of data the source in a DFD represents, these
entities that are outside the content of the system. Entities are represents rectangle.

Process
The process is the manipulation or work that transforms data, performing computation,
making decisions.

Data Store
A data store is a process stores data between processors for lateral retrieval by the same
process.

Data Flow
It’s a moment of data between the entity process and datastore.Data Flow is an interface
between the components of the DFD.It’s represents by an arrows.

3.2 INPUT DESIGN

8
The input design is the process of converting a user-oriented description of the input to a
computer-based format. The source of errors is due to in correct input data. Effective input
design minimizes the errors made in the entry level. It is necessary to make the entries easy,
logical and free from errors. Visual basic is used for designing the input screens; a part from
general design requirements such as collecting any required data etc.., certain consideration
should be followed. The field length must be documented in order to avoid the entries exceeding
the allocated space. The sequence of fields must match. The processing flow, on-line help
message and errors handling information should be made.

Module
1. Raw material purchase details
2. Contractor details
3. Job details
4. Labour details
5. Bill details
6. Payment details

3.3 OUTPUT DESIGN

9
Computer output is the most important and direct source of information to the user. Efficient,
intelligible output design should improve the system’s relationships with the user and help in
decision making. A major form of output is the hardcopy from the printer.

Output requirements are designed during system analysis. A good starting point for the output
design is the data flow diagram (DFD). Human factors educe issues for design involves
addressing internal controls to ensure readability.

1. Raw material purchase details

2. Contractor details
3. Job details
4. Labour details
5. Bill details
6. Payment details

3.3 DATABASE DESIGN

10
 A database design is a collection of interrelated data stored with minimum redundancy to
serve many users quickly and efficiently. The general objective is to make information access
easy, quick, and inexpensive and flexible or the user.

The fundamental task structures are:

 Hierarchical structure

 Network structure

 Relational structure

The database is designed for the project using the above steps. This is followed in order
to attain the database objectives like elimination of redundancy, integration of existing data files,
sharing data, improved accuracy, consistency and data security, economic storage and retrieval of
data and control over standards.

The system also aimed in achieving the major objectives like:

 Data integration

 Data integrity

 Data independence

3.5 SYSTEM DEVELOPMENT

11
3.5.1 DESCRIPTION OF MODULES

1. Raw material purchase details

2. Contractor details
3. Job details
4. Labour details
5. Bill details
6. Payment details

Raw material purchase details:

In this module the purchase of the raw materials are maintained, and the raw materials are
given separate item code. This module also maintains the number of units of purchase of the
raw materials.

Contractor details:
This module maintains the details of the contractor who are having dealing with the
company. The contractors will get the raw materials and do the job by giving out side and
complete the job. Until the finished product is received the contractor does the whole follow-
up of the job work.

Job details:
This module maintains the details of the various jobs given out side through the
contractors. The details of the company that doing the job is also maintained.

Labour details:
This module maintains the details of the Labour and through which contractor the job is
done. The number of Rooms of the finished in Building is also maintained.

Bill details:

12
 The finished products are got from the job and the respective bill details are maintained.
Then the settlement of the bill is done according to the bill number.
Payment details:
The received bills are maintained according to the date of the bill. Then the mode of the
settlement of the bills us done according to the bill number in the first out basis. Then the
mode of the settlement is also mentioned.

3. TESTING AND IMPLEMENTATION

It is the stage of implementation, which ensures that system works accurately and effectively
before the live operation Commences. It is a confirmation that all are correct and opportunity to

13
show the users that the system must be tested with data and show that the system will operate
successfully and produce expected results under expected conditions.

Before implementation, the proposed system must be tested with raw data to ensure that the
modules of the system works correctly and satisfactorily. The system must be tested with valid
data to achieve its objective.

The purpose of system testing is to identify and correct errors in the candidate system. Testing is
done to achieve the system goal. Testing is vital to the parts of the system are correct; the goal
will be successfully achieved. Inadequate testing or non-testing leads to errors that may not
appear until months later. The various types of testing done on the system are:

 Unit Testing
 Integration Testing
 Validation Testing
 Quality Assurance

UNIT TESTING

A program represents the logical elements of a system. For a program to run satisfactorily, it
must compile and test data correctly and tie in properly with other programs.
Achieving an error free program is the responsibility of the programmer. Program
statement that violates one or more rules of the language in which it is written. An
improperly defined field dimension or generated by the computer

14
INTEGRATION TESTING

Programs are invariable related to one another and interact in the total system. Each program is
tested to see whether it conforms to related programs in the system. Each portion of
the system is tested against the entire module with both the test data and the live data
before the entire system is tested as a whole.

VALIDATION TESTING

The validation testing is performed for all the data in the system. The data are completely
validated according to the companies request and requirement. The function or
performance characteristic’s is confirm specification is uncovered and efficiency list is
created

QUALITY ASSURANCE

 The Project is tested completely and various errors found are rectified.

 Security is maintained by providing a separate login for the users.

 Duplication of records are not allowed.

 Various validations are performed to ensure that important data are not missed.

 Testing is performed with some sample inputs from the company and the output is
verified and found right.

15
4. CONCLUSION

The goal of the project “Building Constraction Management System ” defined has

been successfully achieved. The implementation and testing has been done in a step-by-step

process. Each module has been developed and tested individually to obtain the necessary

required output in the desired form. The project has been done as user-friendly software for easy

handling of transactions.

The software developed has been designed and run to satisfy the requirements and needs of the

organization as well as the end users. The system reduces the manual work of maintenance of the

records. It has also resulted in quick retrieval and reference of required information, which is

vital to the degrees of the organization.

The entire system is documented and can be easily understood by the end users. The forms are

very user friendly and also easy to handle even by the beginners with very little effort and

guidance.

5. SCOPE FOR FUTURE ENHANCEMENT

16
The system has been designed flexible according to the current requirement of the users. As the
information requirements may still increase further in the near future, further developments can
be made.

System has been designed and developed according to the current requirements of the users. By
the same time system is much flexible and extensible. Hence further enhancement if needed can
be made without much difficulty. So new applications can be developed and it can be integrated
with the existing system very easily. It can be further expanded to add more modules as the
necessity arises.

Since MS ACCESS AND VB are flexible tools. Any modular program can be easily
incorporated into the application.

7. BIBLIOGRAPHY

17
  “Database System concepts”, McGraw-Hill 1996, Abrasilberschaz
Henry F. Eorth.s. Sunder Shan.

 “Getting Results with Microsoft Office 97”, Stephen L. Nelson.

 “Mastering MS-Access for window 95”, Alan Simpson, BPB

publications.

 “System Analysis and Design”, Golgotha Publications Pvt Itd.2001,

Elias.M.Award.

 “System Design in A Database Environment”, McGraw-Hill 1980

Kenneth S.Brathwait.

 “Visual Basic 6”, Corndex Computer Publishing 1998, Steven Holzer.

8.APPENDIX

A.DATAFLOW DIAGRAM (DFD)

18
 Rawmetirial Details

2. Raw
metirial det
Admin 1. Login
3.contractor
registration contractor
Registration

Labour
6. Labour
5. Job Details Registration

Bill Details

7. Billing
Report
Payment
Details

B. DATABASE DESIGN

Table name: Raw metirial details

19
Primary key: pid

Field Name Data type Description

pid Number Product id
Pdate Text Purchase date
pname Text Product name
quqn Number Quantity
rate Number Product rate for single
tota Number Total amount
advan Number advance
balan Number balance

Table Name: Contractor details

Primary key: cid

Field name Data type Description

cid Number Contracter id
CName Text Contracter name
Dept Text Department
cdate Number Contracter join date
endate Text Contracter clos date
Address Text Address
city Text City
state Text state
cno Text Contact number
email Text Email id

Table name: Job details

Primary key: jid
Foreign key: cid

Field name Data type Description

20
jid Number Job id
jname Number Job name
cid Text Contracter id
cname Number Contracter name
jdate Text Job Date
jdeta Text Job Details
dure Text Duration
state Text State

Table name: Labour details

Primary key:lid

Field name Data type description

lid Number labour id
lName Text Labour name
Gent Text Gender
Cid Text Contractor id
Cname Text Contractor name
Jdet Text Job details
Addr Number Address
city Number City
Ldate Number Labour date
cno Number Contact number
Email Text Email id

Table name: Bill details

Primary key: bid
Foreign key: pid

Field name Data type Description

bid Number bill id
Bdate Number Bill date
Pid Text Product id

21
Pdate Text Name for treatment
Pname Text Doctor prescription
Rate Number Product Rate
quan number Quantity
Amt Number amount

Table name: Payment Deatails

Primary key: pid
Foreign key: cid
Field Name Data type Description
Pid Number Roll number
Pid Number Patient id
Ws Text Ward status
Roomallo Number Room allocated

C. SAMPLE CODEING

Option Explicit
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset
Dim rs1 As New ADODB.Recordset
Private Sub Combo1_Click()
rs.Open "Select * from warddet where rno=" & Combo1.Text & " "
Combo2.Text = rs.Fields(1)
Text1.Text = rs.Fields(2)
Combo3.Text = rs.Fields(3)
rs.Close

22
End Sub
Private Sub Combo2_Click()
rs1.Open "select * from patbill where pid=" & Combo2.Text & ""
Text1.Text = rs1.Fields(2)
rs1.Close
End Sub
Private Sub Command1_Click()
rs.Open "select max(rno)from warddet"
Combo1.Text = rs.Fields(0) + 1
End Sub
Private Sub Command2_Click()
con.Execute "insert into warddet values (" & Combo1.Text & ", " & Combo2.Text & ", '" &
Text1.Text & "', '" & Combo3.Text & "')"
MsgBox ("DATA SAVED")
'rs.Open "select * from warddet", con, adOpenDynamic, adLockOptimistic
While Not rs.EOF
Combo1.AddItem (rs.Fields(0))
rs.MoveNext
Wend
rs.Close
End Sub
Private Sub Command3_Click()
con.Execute "update warddet set pid=" & Combo2.Text & ", name= '" & Text1.Text & "',
wasta='" & Combo3.Text & "' where rno=" & Combo1.Text & ""
MsgBox ("DATA EDITED")
End Sub
Private Sub Command4_Click()
con.Execute "delete * from warddet where rno=" & Combo1.Text & ""
MsgBox ("DATA DELETED")
End Sub
Private Sub Command5_Click()
Combo1.Text = ""
Combo2.Text = ""
Text1.Text = ""
Combo3.Text = ""
End Sub
Private Sub Command6_Click()
Me.Hide
End Sub

Private Sub Command7_Click()

Form4.Show
End Sub
Private Sub Form_Load()
Combo3.AddItem ("General")
Combo3.AddItem ("Emergency")

23
Combo3.AddItem ("Special")
con.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=d:\jesi form\jesi
table\db2.mdb;Persist Security Info=False"
MsgBox ("Connected")
rs.Open "select * from warddet", con, adOpenDynamic, adLockOptimistic
While Not rs.EOF
Combo1.AddItem (rs.Fields(0))
rs.MoveNext
Wend
rs.Close
rs1.Open "select * from patbill", con, adOpenDynamic, adLockOptimistic
While Not rs1.EOF
Combo2.AddItem (rs1.Fields(1))
rs1.MoveNext
Wend
rs1.Close
End Sub

C. FORM DESIGN

LOGIN FORM:

24
Login Success Form

25
MDI Form

Master Menu

26
Transaction Menu

27
Report Menu

28
Raw Metirial Form

29
Contractor Form

30
Job Form

31
Labour Form

32
Bill Form

33
Payment Form

34
E.SAMPLE OUTPUT

35
36
37
38
39
40
41