ERP FOR CONSTRUCTION COMPANY

SYNOPSIS

The objective of this project is to maintain the customer details and raw materials of
the building in the construction company
In the big construction company the customer estimation may be mismatched with
company made estimation and also there is possible for one customer information such that
house design, estimation of raw materials may be entered in customer information. To avoid
this problem separate database maintained in this project. So there is no possible for
entering the wrong information.
The main objective of developing this project is to ease the maintenance of
Construction Company, customer and also the employee details of the customer. The
various modules are
In this customer database we enter the customer name, customer ID Number and
personal address of the customer along with site (area) name in which he wants to build,
type of the building whether it is single floor or double floor such a information’s are
verified in the customer report.
After the customer details entered in the database then raw materials information’s
are entered in the raw materials database depends upon the customer requirement. Raw
material database consists of raw material name like sand, stone price of the raw material
per square feet and estimation of the raw materials as per customer requirement.
The estimation of the electrical raw material like switches and number of lights,
fans etc are entered in the electrical raw material database. Similarly the estimation of stair
case septic tank and dispersion trench and unforeseen items are entered in the database.
Above those information’s are verified in the report.
We also maintain the estimation of foundation details, earth work, labor charge of
earth work, flooring concrete and RCC roof slab. Finally in this project we compare overall
estimation of the customer estimation and construction company estimation of the building.
This project is very useful for Construction Company as well as customer. All the
calculate done in the system based. So there is no possible to cause the error and also there
is no possible entry of bargain between Construction Company and customers.
This Project is developed in VB.NET with the database in SQL Server2000. With an
improved integrated development environment (IDE) and a significantly reduced startup
time, Visual Basic .NET offers fast, automatic formatting of code as you type, improved
IntelliSense, an enhanced object browser and XML designer, and much more. Database
MSSQL Server 2000 is very essential RDBMS to develop application and it is very simple
to create and maintain.
1.2 OVERVIEW OF THE PROJECT

In this Project is used to maintain customer,l abour and estimations details. In an

existing system includes paper works made by human so the times taken to maintain all

these details are very long and also tedious to implement. Our Proposed system

overcomes these drawbacks of existing system, which is implemented in automated

manner.

Our Proposed system has modules, which are

 Admin Login

 Master Module
 Raw Material Collection
 Customer Details
 Transaction module
 Painting
 White Washing
 Earth Work
 Wood Work
 Electrician Work
 Estimation module
 Unforeseen Estimation
 Labour Charge Estimation
 Overall Estimation
Reports:

 Customer Report

 Labour Report

 Overall Report
MODULE DESCRIPTION:

ADMIN LOGIN:
In this administrator login module the authorized user can only login to the
construction company. The authorized user can only maintain the construction details
for the customer.

MASTER MODULE:
In master module contains the following three important module like raw
material, Customer and labour module. Now we will discuss the module one by one.

1. Raw Material Collection:

Raw material collection module contains three types of raw materials like
paint & whitewash, wood and cement & sand. These are the three important
raw materials for the construction company. In this raw material contains the
customer code, material code, material name, quantity cost of the material for
those three raw materials.
2. Customer Details:
A customer detail contains the customer code, customer name, address and
phone number for the customer details. Which customer comes and order the
details their details can maintain this construction projects.

3. Earth Work
Earth work details contains the three important different module like
excavation, sand filling, and cement concrete these three module contains area,
customer code, worker name, worker code and estimation.

4. Wood Work
Wood work details contains the three important different module like
excavation, sand filling, and cement concrete these three module contains area,
customer code, worker name, worker code and estimation
 5. Electrician Work:
Electrician work details contains the three important different module like
excavation, sand filling, and cement concrete these three module contains area,
customer code, worker name, worker code and estimation

ESTIMATION MODULE
1. Unforeseen module:
Unforeseen module contains the fields of area, customer code and estimation
of the unforeseen of the module cost.
2. Overall estimation:
Overall estimation can be calculated by the administrator for a construction
process. These details are maintained by the administrator.

REPORTS:
These above module details are maintained as a report manner by the
administrator.

TRANSACTION MODULE:
Transaction module contains the following five different types of modules
like earth work, electrical work, painting work, wood work and unforeseen. This
module contains the following fields like worker code, worker name, address, phone no
and work of the labor. These details maintained the labor information.

1. Painting:
Painting information module contains area of the customer, customer
code, work code, worker name and estimation of the painting details has
maintained by the administrator.

2. White Washing:
Whitewash details also contain the above fields details like code, name,
area name, worker name, worker code and cost of the product.
 System analysis is a process of gathering the facts concerning the system breaking
them into elements and relationship between elements. It provides a framework for
visualizing the organizational and environmental factors that operate on a system. The
quality of work performed by a machine is usually uniform, neat and more reliable when
compared to doing the same operations manually.

2.1 EXISTING SYSTEM

In the existing system the billing alone is maintained in FoxPro. The staff details, the
attendance details, the students details, the timetable details, marks details are maintained
manually. The study of the existing system revealed that the system has several drawbacks.

DRAWBACKS
 The existing system has no security measure against logging in and no
checks are made for authorized users.
 The end user has to remember a lot of command to make efficient use of the
system.
 The system does not have any descriptive reports and thus did not help
management in decision-making.
 The sales information per day is unable to find.
 Enormous amount of time is consumed
2.2 PROPOSED SYSTEM
The proposed system is been developed to maintain the construction company
maintenance by the administrators to maintain . The staff details, the attendance details, the
students details, the timetable details, marks details etc.,
BENEFITS

 The user can enter only if the username and the password are correct.
 The process of planning will be easy since every process is computerized.
 Time Saving.
 The Sales information per day and per month can be known.
 The details of the all saved information can be viewed.
 The data can be accessed easily whenever needed and so the manual work can
be reduced.
1.3 SYSTEM ENVIRONMENT:

HARDWARE CONFIGURATION:

System : HCL

Processor : Pentium IV

Processor Speed : 2.80GHz

Main Storage : 512MB RAM

Hard Disk Capacity : 80GB

Floppy Disk Drive : 1.44MB

CD-ROM Drive : LG 52X Reader

Keyboard : 104 Keys

Mouse : Logitech

Monitor : Samsung 17” Color

SOFTWARE CONFIGURATION

Operating System : Windows XP

Front end : Visual Basic.Net

Back End : SQL Server

1.4SOFTWARE FEATURES

VISUAL BASIC.NET

Visual Baic.Net has revolutionized windows programming windows programming

and with an object based, event driven approach to software designs. Visual basic.Net
applications act as a front end to the database. Visual basic.Net application provides the
interface between the user and the database. Sophisticated features that make the language
truly object oriented and interfaces it with the latest in the database technology.

.NET provides a new, object-oriented API as a set of classes that will be accessible
from any programming language. This book describes this framework of classes and
provides a reference to what is available and how you can use this framework to write
Windows applications in the brave new world of .NET.

Microsoft .NET Framework is a computing platform for developing distributed applications

for the Internet. Following are the design goals of Microsoft .NET Framework:

1. To provide a very high degree of language interoperability

2. To provide a runtime environment that completely manages code execution

3. To provide a very simple software deployment and versioning model

4. To provide high-level code security through code access security and strong type
checking

5. To provide a consistent object-oriented programming model

6. To facilitate application communication by using industry standards such as SOAP

and XML.

7. To simplify Web application development

 Visual basic.net lets the user to add menus, text boxes, command buttons, option
buttons, check boxes, list boxes, scroll bars, and file directory boxes to blank windows.
Visual basic.net has many different tools.

The Common Language Runtime

The CLR is the mechanism through which .NET code is executed. It is built upon a
single, common language—IL—into which source languages are compiled and includes
mechanisms for executing the compiled code. This includes code verification and just-in-
time (JIT) compilation, garbage collection and enforcement of security policies, and the
provision of profiling and debugging services.
The CLR provides a lot of added value to the programs it supports. Because it
controls how a .NET program executes and sits between the program and the operating
system, it can implement security, versioning support, automatic memory management
through garbage collection, and provide transparent access to system services

IMPORTANT FEATURES:

 The application is a graphical user interface.

 Client-Server architecture benefits picture and image box can be
easily handled using bit mapped files and icons.
 Bit mapped files and icons are used as simple debugging tools.
 With the advent of .NET, Microsoft has introduced many new
technologies that make writing component-based distributed systems
easier, more flexible, and more powerful than ever before.
 It is now easier than it has ever been to write components in any
programming language that can interoperate with components on
other machines, which may not be Windows-based at all.
SQL SERVER 2000

The purpose of this document is to help you migrate your applications when you are

migrating the underlying database from Microsoft SQL Server to Some other Database.

Most of the issues encountered when migrating applications to use an Sql Server

Database are related to database incompatibility. This paper presents these

incompatibilities and provides solutions for many issues.

You should familiarize yourself with this document prior to migrating your

databases. The choices made about how to migrate your application affect how you migrate

the underlying database from Microsoft SQL Server to some other Database.

If the application uses the Microsoft OLE DB Provider for SQL Server or a third-

party OLE DB Provider to connect the Microsoft SQL Server database, use the Sql Server

Provider for OLE DB (SQLOLEDB) to connect to the migrated Database.

SQL Server Security

 Login Authentication.

 Windows NT Authentication

 SQL Server Authentication

 Permissions validation on user database.

 T-SQL statements sent to SQL Server.

  SQL server checks user permissions on receipt of T-SQL statements

FEATURES

 Created by Microsoft and Sybase in the 80s.

 Is SQL Compliant - Uses ANSI SQL

 Supports SQL – 92 standards - Uses T-SQL

 Stores data in a central location and delivers it to clients on request

 New Server Architecture

 Graphic Administration Tools

 Maintains ANSI standards and 6.x Compatibility

 Data integrity means reliability and accuracy of data.

 Integrity rules keep data consistent.

 Supports Client/Server model.

 Request response dialog.

 workload is split between the client and the server.

 Operating System compatibility.

 Runs on Win 95/98 NT, Netware, UNIX, OS/2, Appletalk, Banyan VINES.

 SQL Server must have Service Pack 4 (SP4) to run on Windows NT 4.0.

 Multiple protocol compatibility.

 SQL Server supports these protocols - Appletalk, TCP/IP.

 SMP Compatibility and Scalability

 Supports multiple processors. SMP leads to scalability.

 3. SYSTEM ANALYSIS

In this chapter, concepts associated with term structured system and how
they are implemented in the project has been dealt with the tools used for structure
system analysis are,

 Data Flow Diagram

 Entity Relationship Diagram

3.1 ENVIRONMENTAL MODEL

The Environmental model defines the interfaces between the system and the
environment. Building an environmental model is the first and the most important part of
building complete model of user requirements. The critical aspect of environmental model
is to identify the events occurring in the environment to which the system must respond. It
also defines the boundary between the system and the environment.

3.2 BEHAVIOURAL MODEL:

A system flow diagram is a pictorial representation of the working of the system. It

is a tool that depicts the flow of data through a system and the work processing performed
by that system. This takes an important role in the system analysis part to know the present
level of existing system and what modification is to be done to overcome the problem
occurring in the system. It is the starting point of the design phase that functionally
decomposed the requirement. A system flow diagram consists of a series of rectangles
joined by lines. The rectangles represents data transformation and lines represent data flow
in those systems. A data flow diagram describes data flow rather than how they are
proposed. System Flow Diagram of “CONSTRUCTION COMPANY MAINTENANCE”
is shown in Fig 3.2.1
 DATA FLOW DIAGRAM

3.3 DATA MODEL

Entity Relationship Diagram is a model that describes the stored data layout of a

system at high level of abstraction. Entity Relationship Diagram enables us to examine and

highlight data structures and relationship independent of the processes or control flow. The

participation of the entities in the relationship and cardinality ratio are indicated in the entity

relationship diagram to provide further information .

Entities are the principal data object about which information is to be collected.

Entities are usually recognizable concepts, either concrete or abstract, such as person,

places, things, or events which have relevance to the concept.

Relationship represents an association between two or more entities. Relationships

are classified in terms of degree, connectivity, cardinality, and existence.

Attributes describe the entity of which they are associated. A particular instance of

an attribute is a value. Attributes can be classified as identifiers or descriptors. Identifiers,

more commonly called keys, uniquely identify an instance of an entity. A descriptor

describes a non-unique characteristic of an entity instance.

 The Entity Relationship Diagram shows the relationship and types of relationship

between the entities. The entity for the system “STUDENT DATABASE SYSTEM” is

shown in Fig 3.3.1.The major components are

 Rectangle - represent the entity sets

 Ellipses - which represents attributes

 Diamond - which represent relationship set

 Line - which links the attributes to entity sets and entity sets to relationship

Set.

EEEEEDIAGRAM
in Visual Basic 6.0 as front end and MS-Access as back end. The

HARDWARE CONFIGURATION:
 4. SYSTEM DESIGN

System design is the process of planning a new system to complement or altogether

replace the old system. The purpose of the design phase is the first step in moving from the

problem domain to the solution domain. The design of the system is the critical aspect that

affects the quality of the software. System design is also called top-level design. The design

phase translates the logical aspects of the system into physical aspects of the system.

3.2 INPUT DESIGN

Input design is one of the most important phase of the system design. Input design is

the process where the input received in the system are planned and designed, so as to get

necessary information from the user, eliminating the information that is not required. The

aim of the input design is to ensure the maximum possible levels of accuracy and also

ensures that the input is accessible that understood by the user.

The input design is the part of overall system design, which requires very careful

attention. if the data going into the system is incorrect then the processing and output will

magnify the errors.

The objectives considered during input design are:

 Nature of input processing.

 Flexibility and thoroughness of validation rules.

 Handling of properties within the input documents.

 Screen design to ensure accuracy and efficiency of the input

relationship with files.

  Careful design of the input also involves attention to error handling,

controls, batching and validation procedures.

Input design features can ensure the reliability of the system and produce result from

accurate data or they can result in the production of erroneous information. The input design

of the system includes the followin

Form Design:

3.3 OUTPUT DESIGN

Output design is very important concept in the computerized system, without

reliable output the user may feel the entire system is unnecessary and avoids using it. The
proper output design is important in any system and facilitates effective decision-making.
The output design of the system includes the following
 5. TESTING AND IMPLEMENTATION
5.1 TESTING

Testing is a series of different tests that whose primary purpose is to fully

exercise the computer based system. Although each test has a different purpose, all work

should verify that all system element have been properly integrated and performed allocated

function. Testing is the process of checking whether the developed system works according

to the actual requirement and objectives of the system.

The philosophy behind testing is to find the errors. A good test is one that has a

high probability of finding an undiscovered error. A successful test is one that uncovers the

undiscovered error. Test cases are devised with this purpose in mind. A test case is a set of

data that the system will process as an input. However the data are created with the intent of

determining whether the system will process them correctly without any errors to produce

the required output.

Types of Testing:

 Unit testing
 Integration testing
 Validation testing
 Output testing
 User acceptance testing
5.1unit Testing
All modules were tested and individually as soon as they were completed and were
checked for their correct functionality.
5.2 Integration Testing

The entire project was split into small program; each of this single programs gives a
frame as an output. These programs were tested individually; at last all these programs
where combined together by creating another program where all these constructors were
used. It give a lot of problem by not functioning is an integrated manner.
The user interface testing is important since the user has to declare that the
arrangements made in frames are convenient and it is satisfied. when the frames where
given for the test, the end user gave suggestion. Based on their suggestions the frames
where modified and put into practice.

Validation Testing:
At the culmination of the black box testing software is completely assembled as a

package. Interfacing errors have been uncovered and corrected and a final series of test i.e.,

Validation succeeds when the software function in a manner that can be reasonably

accepted by the customer.

5.3 Output Testing

After performing the validation testing the next step is output testing of the proposed
system. Since the system cannot be useful if it does not produce the required output. Asking
the user about the format in which the system is required tests the output displayed or
generated by the system under consideration. Here the output format is considered in two
ways. one is on screen and another one is printed format. The output format on the screen is
found to be corrected as the format was designed in the system phase according to the user
needs. And for the hardcopy the output comes according to the specifications requested by
the user.

User Acceptance System

 An acceptance test as the objective of selling the user on validity and
reliability of the system. It verifies that the procedures operate to system specification and
mat the integrity of vital is maintained.

Performance Testing

This project is a application based project, and the modules are interdependent with
the other modules, so the testing cannot be done module by module. So the unit testing is
not possible in the case of this driver. So this system is checked only with their performance
to check their quality.

5.2 IMPLEMENTATION

System implementation is stage in the project where the theoretical design is

turned into the working system. The most crucial stage is giving the users confidence that

the new system will work effectively and efficiently.

The performance of reliability of the system is tested and it gained acceptance.

The system was implemented successfully. Implementation is a process that means

converting a new system in to operation.

Proper implementation is essential to provide a reliable system to meet

organization requirements. During the implementation stage a live demon was undertaken

and made in front of end-users. The various features provided in the system were discussed

during implementation
 6. CONCLUSION

The “CONSTRUCTION COMPANY MAINTENANCE” has been developed to

satisfy all proposed requirements. The system is highly scalable and user friendly. Almost

all the system objectives have been met. The system has been tested under all criteria. The

system minimizes the problem arising in the existing manual system and it eliminates the

human errors to zero level.

The software executes successfully by fulfilling the objectives of the project. Further

extensions to this system can be made required with minor modifications. The invention can

be implemented in digital electronic circuitry, or in computer hardware, firmware, software,

or in combinations of them. Apparatus of the invention can be implemented in a computer

program product tangibly embodied in a machine-readable storage device for execution by a

programmable processor; and method steps of the invention can be performed by a

programmable processor executing a program of instructions to perform functions of the

invention by operating on input data and generating output

 BIBLIOGRAPHY

 .Elias Awath, “SYSTEM ANALYSIS AND DESIGN”,Tata Mc Graw Hill

Publication, Sixth Edition,2003

 .S.Ramachandran,”COMPUTER AIDED DESIGN”, Air Walk Publication,

Third Edition,2003

 .Richard Fairley,”SOFTWARE ENGINEERING CONCEPTS”,Tata Mc

Graw Hill Publication, Second Edition,1997

 .Distributed .NET Programming in VB .NET by Tom Barnaby

 Professional VB.NET, 2nd Edition by Fred Barwell, et al

 The .NET Languages: A Quick Translation Guide by Brian Bischof

 Programming VB.NET: A Guide for Experienced Programmers

by Gary Cornell, Jonathan Morrison

 Learning Visual Basic.NET Through Applications by Clayton Crooks

II

 Visual Basic .NET How to Program (2nd Edition) by Harvey M.

Deitel, Paul J. Deitel, Tem R. Nieto