construction management system final year report

Construction Management System
pg. 1
CHAPTER 1: INTRODUCTION
Construction management system is Web Application to manage all day
to day operations related to events for an organization. There are mainly 4
modules in this website CCD, Account, admin, super admin. In this website admin
can register the members and assign a roles to member.
1. 1 PROJECT SUMMERY
Construction management provide information in a quick time according to the
requirements that are to be fulfilled. This website provides inconsistency of data
and reduce the paper work.
Functionality:
Admin:
Create users
Assign roles to member
Member:
Create Branch
Create Project
Create Vendor
Create Items
Create Purchase Order
Create Instruction
Create Vendor payment request

2
1.2 PROJECT PROFILE
Project Title Construction Management System
Operating System Windows 7,8
Front end tool PHP
Back end tool MySQL
Editor Notepad++
1.3 PURPOSE
The purpose of this project is to develop the user friendly and interactive website
which will reduce the paper work, faster and easy work and save the time.
1.4 SCOPE
The aim of the project is to build a simple, effective computerized Construction
Management System. It starts from the process of collecting relevant details and
requirements from the Companies. The Scope of this application deals with the
administrator of the software. The administrator here is the advocate who deals
with the handling of addition, deletion and updating the detail This Daily Board
software is limited to advocates only who is the administrator of the software,
who manages all the working and allows the client to enroll and handle the data
of clients in their respective registered cases and its details

3
1.5 TECHNOLOGY & LITERATURE REVIEW
Technology used:
1) PHP :
PHP is stand for hypertext preprocessor. PHP is a powerful server-side
scripting language for creating dynamic and interactive websites. PHP is the
widely-used, free, and efficient alternative to competitors such as Microsoft's ASP.
PHP is perfectly suited for Web development and can be embedded directly into
the HTML code. The PHP syntax is very similar to C language. PHP is often used
together with Apache (web server) on various operating systems. It also supports
ISAPI (Internet Server Application Programming Interface.) and can be used with
Microsoft's IIS on Windows.
In that all the concepts are from OOPS (Object Oriented Programming System),
so if anyone knows about that concept then he/she can learn php easily. PHP
scripts are executed on the server side. PHP supports many databases like
(MySQL, Oracle,
ODBC etc…). PHP files have a file extension of ".php" or ".tpl" ".phtml"
2) MySQL :
 MySQL is the most popular Open source Database System.
 MySQL Database Management System. The main goal of MySQL are speed and
robustness.
 MySQL, the most popular open source SQL (Structured Query Language)
Database Management system, is developers, distributed, and supported by
MySQL AB.

4
 MySQL AB is a commercial company, founded by the MySQL developers. It is
a second generation open Source company that unites open source values and
Methodology with a successful business model.
 The MySQL website (http:www.mysql.com/) provides the latest information
about MySQL software and MySQL AB.

5
CHAPTER 2: PROJECT MANAGEMENT
2.1 PROJECT PLANNING AND SCHEDULING
For getting project on time and getting functionality completely working we have
to follow some plan. That means if you have not plan to work then you will not get
project on time. So for getting project on time we have to do some plan and we
have to follow it also. And if you have made perfect plan and you follow it also then
you will be surly got project on time.
2.1.1 PROJECT DEVELOPMENT MODEL
 Water fall Model:-
[Fig 2.1.1 Stages of the Incremental model]

6
WATER FALL MODEL was being chosen because all requirements were
known beforehand and the objective of our software development is the
computerization/automation of an already existing manual working system.
Reasons to choose waterfall model are:
 Waterfall model is simple to implement and also the amount of resources
required for it are minimal.
 When to use the waterfall model:
o This model is used only when the requirements are very well
known, clear and fixed.
o Product definition is stable.
o Technology is understood.
o There are no ambiguous requirements
o Ample resources with required expertise are available freely
o The project is short.
 Advantages of waterfall model:
o Simple and easy to understand and use.
o Easy to manage due to the rigidity of the model – each phase has
specific deliverables and a review process.
o Phases are processed and completed one at a time. Phases do not
overlap.
o Works well for smaller projects where requirements are very well
understood.
 Disadvantages of waterfall model:
o Once an application is in the testing stage, it is very difficult to go
back and change something that was not well-thought out in the
concept stage.

7
o No working software is produced until late during the life cycle.
o High amounts of risk and uncertainty.
o Not a good model for complex and object-oriented projects.
o Poor model for long and ongoing projects.
o Not suitable for the projects where requirements are at a moderate
to high risk of changing.
2.1.2 PROJECT PLAN
In the development of this project, we will first check to see if our project is
feasible functionally, technically and economically. Then we collect the
requirements from the end users and analyze it. We also analyze similar systems
to get an exact idea of how to create this system. Hence, we gather all the
requirements which we need to develop our system. Then, after thoroughly
understanding the need of end user, we will develop the Graphical User Interface
(GUI).
The GUI is viewed by the user and the user communicates with the system and
hence, it should be appealing an attractive. After this comes the coding part, which
involves handling databases and manages queries and forms etc. There are certain
coding standards to be followed so that the flow of program is easily understood.

8
2.1.3 PROJECT SCHEDULING
Software life cycle phase Completion
date/duration
System Analysis: Problem definition and description. 3 weeks
Hardware Software analysis 1 weeks
Constraints/Goals of implementation 1 week
Requirement gathering 1 week
Requirement analysis 1 week
Requirement specification 1 week
System Design 2 weeks
GUI form design 2 weeks
Coding Standard Conversion 1 week
Coding 2 week
Testing and deployment 1 week
2.2 RISK MANAGEMENT
Risk management consists of a series of steps that help a software development
team to understood and manage uncertain problems that may arise during the
course of software development and can plague a software project.

9
Risks are the dangerous conditions or potential problems for the system which
may damage the system functionalities to very high level which would not be
acceptable at any cost. so in order to make our system stable and give its 100%
performance we must have identify those risks, analyze their occurrences and
effects on our system and must prevent them to occur .
2.2.1 RISK IDENTIFICATION
Each and every software project is developed under the shadow of risk. All
software development groups have three prime concerns with risk.
1. Future – what risk might cause the software project to go awry?
2. Change concern – how will change in requirement and
development in technologies will occur.
3. Choice – what methods and tools should be used, how to
distribute the work, what level of emphasis is to be given on
quality.
2.2.2 RISK ANALYSIS
Regardless of the prevention techniques employed, possible threats that could
arise inside or outside the organization need to be assessed. Although the exact
nature of potential disasters or their resulting consequences are difficult
to determine, it is beneficial to perform a comprehensive risk assessment of all
threats that can realistically occur to the organization.
 Types of Risks:-
• Performance Risk - The degree of uncertainty that the product will
meet its requirements and be fit for its intended use. -As we are trainees,
the performance risk is there in our project.

10
• Cost Risk - The degree of uncertainty that the project budget will be
maintained. The cost of our project is already decided by management.
• Support Risk - The degree of uncertainty that the resultant software will
be easy to correct, adapt, and enhance. Client of this project is in different
premises.
• Project Risks - Threaten the project plan. If project risk become real, it is
likely that project schedule will slip and that costs will increase. The
budget of this project was decided before starting the project and it is
enough to complete it. -All the works are divided between team members.
Required all the resources are available.
• Technical Risks - Threaten the quality and timeliness of the s/w to be
produced. If technical risk becomes real, implementation may
become difficult or impossible. -Technology is already decided for this
project.
• Business Risks - Threaten the viability of the s/w to be built. This is live
project so no business risk is there.
• Known Risks - are those that can be uncovered after careful
evaluation of the project plan.
• Experience Risks - Are extrapolated from past project experience. As we
are trainees, make this project no such experience is there.

11
2.2.3 RISK PLANNING
Risk Type Remedies/Plans
Hardware Failure Back up must be taken at each specific interval.
Schedule Slippage
Reorganize team so that there is proper
understanding of project and people therefore
understand each other’s job.
Rapidly Change in requirements
For this risk we must have to analyze new
requirements that proper changes made.
2.3 ESTIMATION
2.3.1 EFFORT ESTIMATION
While doing effort estimation we must keep in mind that the software must be
user friendly. That is this software can be used by any person who has a bit
knowledge about the software
2.3.2 COST ESTIMATION
The target software aims at the person who will not find jobs and resources Hence
the cost effectiveness of the software was the important factor which had to be
taken care of throughout the development process
It is done mainly in two categories.
Hardware used
 Processor : dual core or above
 Hard disk : 60GB
 Memory : 512MB

12
CHAPTER 3: SYSTEM REQUIREMENT STUDY
3.1 HARDWARE REQUIRMENTS
 Processor : dual core or above
 Hard disk : 60GB
 Memory : 512MB RAM(minimum)
3.2 SOFTWARE REQUIRMENTS
 Web server : Wamp/Xamp server.
 OS : Windows/Linux
 Platform : PHP
 Editor : Notepad++ Editor
 Browser : All

13
CHAPTER 4: SYSTEM ANALYSIS
4.1 REQUIREMENT OF SYSTEM
This Website is a very important feature used for construction management. The
primary goal of this website is to store or keep all records of construction project.
In this project only admin will have to create new user, than they create the
records, create purchase order, create vendors, etc. and super admin will provide
the role like ccd, account and admin to users.
 ADMINISTATOR
 Editing/Deleting/Creating the database.
 Super admin can give roles to users.
 MEMBER
 Logging into the system.
 He/she can change or create the records when access is granted by super
admin.
 Can update /edit its records.
4.2 FEASIBILITY STUDY
4.2.1 Operational Feasibility
In this we check the entire task by operation. That means when we get task at the
time first we search for what operation will going on during this task. What will
be input, output and what condition we have to put. And from this kind of
operation we get more clear idea, and thus we can understand more about client
requirement and functionality which client want. So, operational feasibility is
helpful to get more idea about task and client requirement.

14
4.2.2 Technical feasibility
 Technically my project was feasible enough.
 But the sources for guidance was not enough for my development.
4.2.3 Economic feasibility
 For any system if the expected benefits equal or exceed the expected costs,
the system can be economically feasible.
 In economic feasibility, cost benefit analysis is done in which expected
costs and benefits are evaluated.
 I consider economic analysis for checking how much my project would
cost.

15
CHAPTER 5: SYSTEM DESIGN
5.1 USE CASE DIAGRAM
 Member
Login
Create Branch
Create Project
Create Vendor
Create Purchase
Order
Create Instructions
Member
Add New Item
Logout

16
 Admin
Login
Create Member
Assign Roles
Manage Database
Logout
Admin

17
5.2 DATA FLOW DIAGRAM (0 & 1 LEVEL)
Level – 0

18
LoginLogin
Branch
Create
Branch
Employee
Create
Vendor
Create
Special
Instruction
Item Create
Purchase
Order
Employee
Special Instruction
Purchase
Order Item
Purchase Order
Vendor
Project
Create Projects
Request
Response
Login_id
Successful Login
Branch_id Branch_id
Branch info Branch info
Employee_id Employee_id
Employee info Employee info
Vendor_id Vendor_id
Vendor info Vendor info
Instruction_id Instruction_id
Special Instructions Special Instructions
Item_id
Item_id
Item Info Item Info
Order_id Order_id
Order Info Order Info
Project_id Project_id
Project Info Project Info
Admin
Level - 1

19
5.3 E-R DIAGRAM
BranchTIN No
CST No
CIN No
Branch Name
Branch Code
Address
Contact Person
Contact No
Projects
Project Name Company
Branch
Site Address
Contact
Person
Contact No
Start Date
End Date
Amount
Login
Vendor
Order
Type
Order No
Project Name
Vendor Name
Date
Amount
Address
Name
Vendor Code
Payment Day
Email Contact Person Contact No
Items
Unit
Item Name
Port No
User Name
Password
Estimate Date

20
5.4 Sequence Diagram
Member BranchLogin Logout
Login Succesfull
Login
Logout
Logout Succesfull
Create Branch
View Branches
Branch

21
CHAPTER 6: TESTING
Software Testing is an empirical investigation conducted to provide
stakeholders with information about the quality of the product or service under
test, with respect to the context in which it is intended to operate.
Software Testing also provides an objective, independent view of the
software to allow the business to appreciate and understand the risks at
implementation of the software. Test techniques include, but are not limited to,
the process of executing a program or application with the intent of finding
software bugs.
It can also be stated as the process of validating and verifying that a
software program/application/product meets the business and technical
requirements that guided its design and development, so that it works as expected
and can be implemented with the same characteristics.
Software Testing, depending on the testing method employed, can be
implemented at any time in the development process, however the most test
effort is employed after the requirements have been defined and coding process
has been completed.
6.1 Unit Testing
The primary goal of unit testing is to take the smallest piece of testable
Software in the application, isolate it from the remainder of the code, and
determine whether it behaves exactly as you expect. Each unit is tested separately
before integrating them into modules to test the interfaces between modules. Unit
testing has proven its value in that a large percentage of defects are identified
during its use.

22
Unit testing is a software verification and validation method where the
programmer gains confidence that individual units of source code are fit for use.
A unit is the smallest testable part of an application. In procedural programming
a unit may be an individual program, function, procedure, etc., while in object-
oriented programming, the smallest unit is a class, which may belong to a
base/super class, abstract class or derived/child class.
6.2 Integration testing
Integration testing, also known as integration and testing (I&T), is a
software development process which program units are combined and tested as
groups in multiple ways. In this context, a unit is defined as the smallest testable
part of an application. Integration testing can expose problems with the interfaces
among program components before trouble occurs in real-world program
execution. Integration testing is a component of Extreme Programming (XP), a
pragmatic method of software development that takes a meticulous approach to
building a product by means of continual testing and revision.
There are two major ways of carrying out an integration test, called the
bottom-up method and the top-down method. Bottom-up integration testing
begins with unit testing, followed by tests of progressively higher-level
combinations of units called modules or builds. In top-down integration testing,
the highest-level modules are tested first and progressively lower-level modules
are tested after that. In a comprehensive software development environment,
bottom-up testing is usually done first, followed by top-down testing.
6.3 Validation Testing
At the validation level, testing focuses on user visible actions and user
recognizable output from the system. Validations testing is said to be successful
when software functions in a manner that can be reasonably expected by the
customer. Two types of validation testing,

23
 Alpha testing: alpha testing is simulated or actual operational testing by
potential users/customers or an independent test team at the developers'
site. Alpha testing is often employed for off-the-shelf software as a form of
internal acceptance testing, before the software goes to beta testing.
 Beta testing: beta testing comes after alpha testing. Versions of the
software, known as beta version, are released to a limited audience outside
of the programming team. The software is released to groups of people so
that further testing can ensure the product has few faults or bugs.
Sometimes, beta versions are made available to the open public to increase
the feedback field to a maximal number of future users.
 Gray box testing: Grey box testing is the combination of black box and
white box testing. Intention of this testing is to find out defects related to
bad design or bad implementation of the system. it is used for web
application.
Case 1: Login
Condition Action
Correct user id and correct password Accepted
Correct user id Incorrect Password Rejected
Incorrect user id Correct Password Rejected
Incorrect user id Incorrect Password Rejected

24
CHAPTER 7: USER INTERFACE
7.1 LOGIN
This is login screen. If member is already registered, then they can login and move
to dashboard.

25
7.2 DASHBOARD
This is home screen. It shows order chart and vendor payment request.

26
7.3 BRANCHES
This screen shows branches that we had created and they can also changes in the
records.

27
7.4 CREATE NEW BRANCH
By this screen we can create a new branch. In this screen there are validation on
fields. Branch name, code, address, contact person, contact no, telephone no are
compulsory.

28
7.5 PROJECTS

29
7.6 CREATE NEW PROJECT
By this screen we can create new project. For create new project first select the
branch names then we can create a new project.

30
7.7 VENDORS

31
7.8 CREATE NEW VENDOR
This screen shows create new vendor.

32
7.9 VENDOR PAYMENT REQUEST

33
7.10 CREATE VENDOR PAYMENT REQUEST
This screen shows create new vendor payment request. For create new vendor
payment request first select vendor name and order no.

34
7.11 PURCHASE ORDER

35
7.12 CREATE PURCHASE ORDER
Using this screen we can create a new purchase order. For create a new purchase
order we want to select a branch, project and vendor. In this screen we can also
add new items.

36
7.13 ITEM
7.14 CREATE NEW ITEM

37
CHAPTER 8: LIMITATION AND FURTHER ENHANCEMENT
8.1 Limitation
 Only admin can create a new Member.
 User cannot print whole data only admin can.
 Members can change or create the records when access is granted by
admin.
8.2 Further Enhancement
This system is developed based upon the basics requirement so may there is some
limitation in development. But as per global requirement it may be enhanced to
following points in next release.
 Member can give orders online.
 Member can do online bidding.
 Data security can be enhanced.
 Reminder System can be enhanced.
 User Tracking.

38
CHAPTER 9: CONCLUSION
This website is basically used for keep data on related construction. This website
provides features that member can create Projects, Branches, Vendors, items, etc.
of construction. And also they can change the created records. This website is fast
and easy retrieval and to reduce the work and time. Use of this project would make
the website interactive.

39
CHAPTER 10: REFERENCES
Reference for PHP
http://www.w3schools.com/php/
http://www.w3schools.com/css/
http://www.php.net

construction management system final year report

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a construction management system final year report

Similar a construction management system final year report (20)

Último

Último (20)

construction management system final year report