Construction Administration System

Software Requirement Specification (SRS)

SEMESTER MAC – JULAI 2020

GROUP: CS1104D

Ezzad Bin Ab Malek, 2018693374

Aina Nazahah Binti Mohd Nor, 2018215484
Nor Farzanah Binti Sharom, 201841646
Marha Firzanah Binti Mohd Mazlan, 2018204328
Farisha Afrina Binti Mohd Hisham, 2018652338

i
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

Table of Contents
1. Overall Description...........................................................................................................2
1.1 Product Perspective..............................................................................................................2-3
1.2 Product Functions................................................................................................................4-5
1.3 User Characteristics................................................................................................................6
1.4 Operating Environment..........................................................................................................7
1.5 General Constraints.................................................................................................................7
1.6 References.................................................................................................................................8

2. External Interface Requirements...............................................................................9

2.1 User Interfaces.........................................................................................................................3
2.2 Hardware Interfaces................................................................................................................3
2.3 Software Interfaces..................................................................................................................3
2.4 Communications Interfaces...................................................................................................3

3. Functional Requirements...............................................................................................4

4. Other Nonfunctional Requirements..........................................................................5

4.1 Performance Requirements....................................................................................................5
4.2 Safety and Security Requirements.........................................................................................5

Appendix........................................................................................................................................6

Revision History
Name Date Reason For Changes Version
Nor Farzanah Binti 3/5/2020 Develop Overall Description 1.0
Sharom
Aina Nazahah Binti 5/5/2020 Develop Overall Description 2.0
Mohd Nor

1
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

1. Overall Description

1.1 Product Perspective

Make sure to include a simple diagram that shows the major components of the overall system, subsystem
interconnections, and external interface.

Construction Administration System is a computerized system which helps user (staff and
admin) to manage the administrator daily activity in electronic format. It reduces the risk of
paperwork and human error such as file lost, file damaged and time consuming. It can help user
to manage the transaction or record more effectively and time saving.

 Staff Procurement description

Include item details form and design form to send to the Construction. Procurement will make a deal
with other organization outside the company during purchasing the raw material. After that,
Procurement will create the item details form for certain products which is to be produce.

 Staff Construction description

Include construct form to send to the Testing after the product has been done created. Testing will
return the product to the Construction if the product is failed during testing. After that, Construction
will fix or recreate the product and send the fix form to the Testing.

 Staff Testing description

Include testing form which staff need to test every product has been produced by Construction.
Testing will determine whether the product is functional or malfunction (pass of failed). If the
product is functional, Testing will generate the receipt for the customers. If the product is
malfunction, Testing will return the product to the Construction.

 Admin description
Include update new staff and delete the staff. Admin will have a access to view the form of item
details (Procurement, Construction, Testing) and view the receipt that has been saved by Testing in
the system.

2
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

Figure 1.0 Overall System for Staff

3
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

Figure 2.0 Overall System for Admin

1.2 Product Functions

Summarize the major functions the product must perform or must let the user perform. Provide a bulleted
list of all the major functions of the system. Provide a Data Flow Diagram (DFD) of the system to show
how these functions relate to each other.

The major features of Construction Administration System are to let the user perform well than the
manual system. This system is working in user friendly area and more secure for the user. It will keep the
users and customers records in a permanent files system and recording the result of the firm activities.

The Data Flow Diagram (DFD) below shows the layout of our Construction Administration System:

4
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

Figure 3.0 Context Diagram

5
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

Figure 4.0 Data Flow Diagram (DFD)

6
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

1.3 User Characteristics

Describe the different types of users/reader/stakeholders that the document is intended for. Users may be
differentiated security or privilege levels and job level.

A user may be actively involved in a project’s outcome or in a position to affect the project’s success. For
Construction Administration system, the user which are the staff and admin as a stakeholder. The user
characteristics include experience and technical expertise.

For the details user characteristics as listed below:

STAFF (Procurement/Construction/Testing)
 Update profile
 Received the design and create the item details
 Create new item
 Testing new item
 Fix failed item
 Verify the item
 Generate the receipt

ADMIN
 View item and item details
 Update new staff and delete staff
 View receipt

7
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

1.4 Operating Environment

Describe the environment/platform in which the software will operate, including the hardware platform,
operating system and versions, and any other software components or applications with which it must
peacefully coexist.

Operating system for Construction Administration System is as listed below:

PROCESSOR Intel Core Processor or better performance

OPERATING Windows2000, Windows7, Windows10
SYSTEM
MEMORY 1GB RAM or more
HARD DISK SPACE Minimum 3GB for database usage for future
DATABASE MySQL

1.5 General Constraints

Describe any items or issues that will limit the options available to the users/stakeholders. These might
include hardware limitations, interfaces to other applications, communications protocols, security
considerations or programming standards.

Software limitations:

 The system shall need Windows2000 or greater with at least the Microsoft .NET Framework 1.1
installed.

 Xampp with C++ shall be used in the development of the ADS.

Hardware limitations:

 Each operator shall need a PC capable of running Microsoft Windows2000 or greater, with at least
the Microsoft .NET Framework 1.1 installed.

 The database shall be stored on a Windows or Linux server using Apache and MySQL.

 All computers shall need to be networked together so that all can have access to the database.

8
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

1.6 References
List any other documents (including previous student projects) or Web addresses to which this SRS refers.
These may include user interface style guides. Use the standard IEEE citation guide for this section.

1. Software Requirement Specification document with example. [Online]. Available:

https://krazytech.com/projects/sample-software-requirements-specificationsrs-report-airline-
database/amp. [Accessed: April. 26, 2020].

2. Library Management System Mini Project Report on LIBRARY MANAGEMENT SYSTEM. [Online].
Available:
https://www.academia.edu/37726542/Library_Management_System_Mini_Project_Report_O
n_LIBRARY_MANAGEMENT_SYSTEM. [Accessed: May. 3, 2020].

3. 11_chapter3.pdf – Shodhganga. [Online]. Available:

http://shodhganga.inflibnet.ac.in/bitstream/10603/10053/11/11_chapter%203.pdf. [Accessed:
May. 5, 2020].

4. Example requirements specification. [Online]. Available:

https://www.slideshare.net/mobile/indrisrozas/example-requirements-specification. [Accessed:
May. 6, 2020].

9
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

2. External Interface Requirements

2.1 User Interfaces

Describe the logical characteristics of each interface between the software product and the users. This may
include sample screen images, any GUI standards or product family style guides that are to be followed,
screen layout constraints, standard buttons and functions (e.g., Cancel) that will appear on every screen,
error message display standards, and so on. Those who will be able to provide optional Graphical User
Interface (GUI) screenshots will be rewarded by extra marks.

2.2 Hardware Interfaces

Describe the logical and physical characteristics of each interface between the software product and the
hardware components of the system.

2.3 Software Interfaces

Describe the connections between this product and other specific software components (name and
version), including databases or operating system.

2.4 Communications Interfaces

Describe the requirements associated with any communications functions required by this product,
including e-mail, web browser, network server communications protocols, electronic forms, and so on.

10
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

3. Functional Requirements

Functional requirements capture the intended behavior of the system. List the detail of different
user/stakeholder functions with specific explanations regarding every function.

Users/Stakeholders Function Description

User able to sign up and create user
Student Free sign up for user account without intermediate person to
validate the registration process
After completing the registration
Student. Lecturer Login process process, user able to log into the
information system

11
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

4. Other Nonfunctional Requirements

4.1 Performance Requirements

If there are performance requirements for the product/information system (IS) under various
circumstances, state them here and explain their rationale, to help the users/stakeholders understand the
intent and make suitable design choices.

For example: 1. Any transaction will not take more than 10 seconds.

The steps involved to perform the implementation of Construction Administation System database as listed
below:

1. Admin login to the system to update new staff or delete staff

2. Staff will view the details form before start the project
3. Any details form will be verified by staff before proceed the project
4. Receipt will be saved in the Testing file

4.2 Safety and Security Requirements

Specify those requirements that are concerned with possible loss, damage, or harm that could result from
the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be
prevented.

 Availability

Testing should be available on the specified date and specified time as many product need to be test
whether it functional or malfunction before it can be proceed to the customers.

 Maintainability

Admin need to ensure staff know what to do in the even of a security breach or incident including a
near-miss and staff must report any suspicious behavior that notice on company premise or
construction sites.

 Usability

Testing have to ensure that every products are able to use by the customers and if the products are
malfunction, the company might loss the project.

12
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

Appendix

13