Construction Management System (chapter 2 Requirement Analysis)

Introduction
The purpose of our systems is to manage Time, employees, projects, manage project
material, task schedule, Update the task schedule if it is necessary, record project and
managing project progress. The proposed system is intended to replace manual
systems with automated systems.

Current System
In the current structure, work is done from the client down to the lowest employee.
The contractor oversee all of the work and direct the other employees. According to
the business rules of construction, the contractor hires employees based on their
experience, and the consultant provides some criteria to contractors that win the bid.
The contractor employs engineers, workers, and supplies building supplies.

Current System Description

The current system actors are;
1. Client(Owner)
Meet the consultant.

2.Consultant
A. Design the project
B. Prepare contract document
C. Hire contractor
D. Monitor schedule

3. Engineers
A,Plan the project

4. Contractor
A. Provide material
B. Manage material
C. Control construction process
D. Plan construction process
E. Employee monitoring
5. Employee
A. Perform the work
B. Give comment orally

Problem of the Existing System

Users of the current system are unable to obtain any information electronically. There
are numerous tasks at the office that are completed by direct interaction with the
owner, consultants, and contractors.

Information regarding employees, scheduling projects, and project status is manually

kept and written down on paper. This could lead to data loss and resource waste .The
existing system actually faces to a lot of problems, and these problems results due to
the manual system.
 Proposed System
Overview
We're going to set up a new system to address the issues with the current one. The
new system functions by requesting information from the user and storing that input
in a database for later use.

Proposed system includes the following working principles or rules:

Business Rule1: Only Contractor can modify employee information

Business Rule2: Only consultant can modify schedule
Business Rule3: Consultants can represent the owner
Business Rule4: Contractor can modify any information that are related to project except
schedule
Business Rule5: Consultants view all things about project.

Functional Requirements
The functional requirements of the system are:
1. register a employees and their job site.
2. Register a project
3. Register a equipment.
4. Generate the job site and who work under the site (labour) , which equipment is
used,
5. Reports and comments from user and employee 
6. Current project status
7.Create schedule
8,Update the schedule, if it is necessary

Non Functional Requirements

A. Security issue
Security requirements are important factors in this system as classified data will be
stored in the database. User validation will be done during login to insure that the user
is valid and that the user only has access to his or her permission data. General users
will only have access through the user interface.

B. Documentation
With the full version of the system we will submit to the system administrators well
commented document both internally and externally about the database schema.

1, internally :comments of line and paragraph inside the code of the system. This will
give a brief explanation of the code.
2, externally: the graphical user interface .

The document includes all the necessary user guideline. Documentation will be part
of the system.
 The system have a good documentation that facilitates the burden on the coding and
the database parts in such a way ;that we use “//” to comment a single line comment ,
“/**…………..**/” for multiple line comment.

C. Safety Requirements

System use shall not cause any harm to human users.

D. Performance

The performance is generally measured by two things this are the response time and
the throughput

1, the response time, we have to minimize the response time, so as for one operation
not to take more than the allocated time for it.

2, throughput, describes how much operation are performed per unit time.

In general, the performance can be optimized by having direct access to the

operation queried by the object as far as that will not sabotage the system, any
unnecessary associations or classes will be removed at the designing stage.In
addition to this the period that an operation to take has to be limited.

The response time of the CMS is fast because it runs with highest speed. The
system will allow one user to update and multiple user to view.

.
E. Physical environment
The system will be deployed in the construction company and there is no
external factors that disturb the performance of the system.

F. User Interface and Human Factors

Our system uses GUI(Graphical User Interface).Any users with the skill of reading
can use our system.

G. Hardware Consideration
Processor:
Hard disk:
Memory:

H. Error handling
When an error occurs, the system prohibit any kind of change. It will only allow the
user to view the content.

I.Quality issue
The system will have multiple users/clients So in order to get the best performance
out of the system we will consider the best interest of our users along the development
and improvement process.
 System Model

Use case diagram

Use case description

Table for use case description for login

Use case name Login Login

Identifier CMS001
Description To authenticate the user
Actor Contractor, consultant , owner and employee
Precondition The user must have an account
Post condition The authenticated person gets the appropriate page
Basic course of action 1.User wants to login
2.The system displays the login form
3.Fill user name and password
4. Validate user name and password
5. The system displays the appropriate page.
6. Use case ends.
Alternative course of 5.1 If the username and password is incorrect the system displays incorrect
action user name and password message.
5.2. The system redirects to go step 4i.e.to enter the username and
 password
5.2. Use case ends.

Table for use case description for managing employee info

Use case name Login manage employee info

Identifier CMS002
Description use case to add/delete/update/ and to view employee information
Actor Contractor
Precondition the contractor must be login to perform those activities.
Post condition System has successfully add/delete/update/ and display employee
information to the contractor.
Basic course of action 1. Contractor clicks the “employee info” consequently.
2. The system displays employee registration form/enter employee Id to
delete/enter employee Id to edit/enter employee Id to view.
3. Contractor fills employee data/enter employee Id.
4. When Contractor click “submit/delete/update/view “button
added/deleted/updated/search stored in systems database/deleted from
the data base/save to data base/search and display from the database
consequently.
5. Use case ends.
Alternative course of 3.1. When there is not filled the employee data correctly “please fill
action employee data correctly” message will be displayed.
3.2. When the contractor fills the form incorrect manner, the message
“Invalid data Entered please fill in appropriate format” will be displayed
Table for use case description for managing project

Use case name Login manage project

Identifier CMS003
Description use case to update and to view project information .
Actor Contractor
Precondition the contractor must be login to perform those activities.
Post condition System has successfully add/delete/update/ and display project
information to the contractor.
Basic course of action 1. Contractor clicks the “edit project /search project” consequently.
2. The system displays enter project Id to edit/enter project Id to view
consequently.
3. Contractor fills project data/enter project Id.
4. When Contractor click “ update/view “button the updated / save to data
base/search and display from the database consequently.
5. Use case ends.
Alternative course of 3.1. When there is not filled the project data correctly “please fill project
action data correctly” message will be displayed.
 3.2. When the contractor fills the form incorrect manner, the message
“Invalid data Entered please fill in appropriate format” will be displayed

Table for use case description for managing project material

Use case name Login manage project material

Identifier CMS004
Description use case to add/delete/update/ and to view project material
Actor Contractor
Precondition The contractor must be login to perform those activities
Post condition System has successfully add/delete/update/ and display project material
information to the contractor
Basic course of action 1.Contractor clicks the “add new item/delete item/edit item/search item”
consequently.
2. The system displays project material registration form/enter item Id to
delete/enter item Id to edit/enter item Id to view consequently.
3. Contractor fills project material data/enters item Id.
4. When Contractor click “submit/delete/update/view “button the
added/deleted/updated/search stored in systems database/deleted from
the data base/save to data base/search and display from the database
consequently.
5. Use case ends
Alternative course of 3.1. When there is not filled the project material data correctly “please fill
action item data correctly” message will be displayed. 3.2. When the contractor
fills the form incorrect manner, the message“Invalid data Entered please fill
in appropriate format” will be displayed.

Table for use case description for creating schedule

Use case name Login create schedule

Identifier CMS005
Description Use case to create /update /view schedule
Actor consultant
Precondition The consultant must be login to perform those activities
Post condition System has successfully created/update/ and display task schedule to the
consultant
Basic course of action 1, consultant clicks the “create schedule / update schedule
2, the system displays the task schedule form to create enter task id and
starting and ending date enter schedule id to update and enter schedule id
to view schedule
3, When consultant click “create/update/view “button the created schedule
will be stored in systems database/updated from the database /search and
 display from the database consequently.
5. Use case ends.

Table for use case description for creating project

Use case name Login Create project

Identifier CMS006
Description Use case to create / view and update project
Actor consultant
Precondition The consultant must be login to perform those activities
Basic course of action 1. consultant clicks the “create new project /update project /view project”
consequently.
2. The system displays project registration form enter project Id to
update/enter project Id to view consequently.
3. consultant fills project data/enter project Id.
4. When consultant click “submit/update/view “button the created
/updated/search stored in systems database. update from the data
base/save to database/search and display from the database .
5. Use case ends.
Alternative course of 3.1. If the username and password is incorrect the system displays incorrect
action user name and password message.
3.2.The system redirects to go step 4i.e.to enter the username and
password

Post condition System has successfully created/update and display project information to
the consultant.

Table for use case description for viewing project status

Use case name Login View project status

Identifier CMS007
Description To view project status.
Actor Consultant, client(owner)
Precondition The consultant and the owner must login to perform this activities
Basic course of action .1, When site-supervisor and contractor click “show project status “button
the system displays project status.
2, the consultant and owner must enter the project id to view the project
status
2. Use case ends.
Post condition The system must have a project that have been created with the same id

Table for use case description for commenting

Use case name Login comment
Identifier CMS008
Description To comment on a project
Actor Consultant, client(owner) and employee
Precondition The consultant, owner and the employee must login to perform this
activities
Basic course of action .1.The user must log to his/her page
2.The user select project using the project id .
3.clicks on comment
4. Use case ends
Post condition The system must have a project that have been created with the same id

Class diagram

Dynamic models
Sequence modeling
 The following sequence diagram is used primarily to show the interactions between objects in the
sequential order that those interactions occur in our system. We have identified the following use
case object for sequence diagram for our system:
1. Login
2. View project status
3. Manage project
4. manage employee
5. create schedule
6. manage material
7. Comment

Login sequence diagram

sequence diagram for manage project

Sequence diagram for employee management

sequence diagram for creating schedule

sequence diagram for comment

sequence diagram for managing equipment

sequence diagram for viewing project status