A CONSTRUCTION PROCUREMENT

SYSTEM

SOFTWARE

Requirements Specification

Version 1.0

VU-ID: MC220201701

SUBMITTED BY: MISBAH KHAN

SUPERVISOR NAME: ANAM NAVEED

SEMESTER Spring: 2023

1
 REVISION HISTORY

Date (DD/MM/YYYY): 06-10-2023

Version: 1.0

Description:
SRS document includes Scope of the project, Functional requirements, Use Case
diagram, Usage Scenarios, Adopted Methodology, and Work Plan/Gantt Chart.

Author: MC220201701

Table of Contents

2
Scope (of the project) ------------------------------------------------------------- 04

Functional Requirements --------------------------------------------------------- 05

Non-Functional requirements ---------------------------------------------------- 06

Use Case Diagram ----------------------------------------------------------------- 07

Usage Scenarios -------------------------------------------------------------------- 08

Adopted Methodology ------------------------------------------------------------- 11

Work Plan (Work Plan) ----------------------------------------------------------- 13

SRS DOCUMENT

3
SCOPE OF PROJECT:

Procurement is the process of securing products and services needed to complete a

construction project on time and within budget. It is handled by a project manager and

typically includes the following five areas of responsibility:

 Define project requirements.

 Solicit bids for and select services.

 Buy or lease supplies and equipment.

Monitor construction contracts, potential cost fluctuations, and completion schedules.

Resolve conflicts with budgets, timelines, or quality, among other issues.

The key to procurement process success is using the right strategy and procurement

technology to make sure materials and services are high quality and available on the job

site when required.

Having a dedicated, well-trained construction procurement system is an immeasurable

benefit to any building operation. It is the one area of the company that has as its sole

function the evolution of a construction job from idea to completion, ideally under budget

and ahead of schedule. In fact, many companies receive bonuses based on reaching preset

goals.

It is important that a construction operation has a comprehensive, easy-to-use system to

help the project team manage procurement. A disconnected system that doesn’t have

seamless integration among functions can cause havoc on construction projects and cause

mistakes, the need to re-forecast, costly change orders, and budget overages.

Main purpose of the system is keeping an eye on supply chain risk monitoring. It helps to

improve the procurement process and boost the efficiency and accuracy. It automates the

4
entire source to pay cycle. System shows the availability of supplier, services and

products in market. It uncovers the purchasing trend and offers list of products and

services respectively.

Functional Requirements:

User
 Employees of the organization can able to login the system.
 System shall allow user/employee to search for available Supplier offering
relevant products.
 System shall able to display required products and service available in market
with location of supplier, product details and other necessary information.
 When user place new bid, system firstly display products from registered supplier.
 If user wants to know more offer, system will able to display results extracted
from other source (like google or any other media).
 System will be able to score the best vendor (you can compare the vendor offers
by comparing product’s cost, supply cost and product quality etc.).
 System shows recommended vendor with all details (location, offer of product
and service).
 Contract management feature. System shall able to create contract quickly using
pre-written templets. User can able to select relevant templet and system allows
users to perform required changes in the contract.
 System has feature of e-invoicing as system able to accept supplier’s invoice
online.

Administration
 Admin shall be able to add user information
 Admin shall be able to maintain user information.
 Admin can add contract templets.
 Admin can add information of newly registered suppliers in the system, with
approval of higher authority.
 Admin maintain supplier and their offers (products and services) information..

5
Non-Functional Requirements:

o Performance requirements:
 The system need to be reliable.
 Web pages are loaded within few seconds.
 If unable to process the request appropriate error message.
o Safety Requirement:

 Users must be authenticated.

 Details need to be maintained properly.

o Security Requirements:

 Sharing of details.

 The details of user must be safe and secure.

 After entering the password and user id the user can assess his profile.

o Evolution

 Testability.

 Maintainability.

 Extensibility

 USE CASE DIAGRAM:

6
 USAGE SCENARIOS:

Title: Admin – Users Registration

7
Use case ID: OGPM _01
Actor: Admin
Description: All Users(users/Patients) Create his/her
Account
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Click on register.
Fill in particulars.
Clicks submit.
Admin Approved Accounts
Post condition: Task has been completed successfully.
Author: MC220201701

Title: Admin / Supplier Information

Use case ID: OGPM _02
Actor: Admin
Description: Admin Add new supplier information
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Login Account
Click on add new information
Fill in particulars.
Clicks submit.
Post condition: Task has been completed successfully.
Author: MC220201701

Title: Admin/ update Supplier Information

Use case ID: OGPM _03
Actor: Admin
Description: Admin can update information
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Login Account
Click on Supplier you want to update
Update required fields
Clicks update.
Post condition: Task has been completed successfully.
Author: MC220201701

Title: Admin Add Contract Templets

Use case ID: OGPM _04

8
Actor: Admin
Description: Admin add Contract info
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Click on contracts.
Reload page
Post condition: Task has been completed successfully.
Author: MC220201701

Title: Admin Manage Users

Use case ID: OGPM _05
Actor: Admin
Description: Admin manage users
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Click user list.
Fill in particulars.
Clicks submit.
Post condition: Task has been completed successfully.
Author: MC220201701

Title: Admin View Bids

Use case ID: OGPM _06
Actor: Admin
Description: Admin view user Bids
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Login admin
Click on Bids
Click on view
Post condition: Task has been completed successfully.
Author: MC220201701

Title: Admin/ Generate Reports

Use case ID: OGPM _07
Actor: Admin

9
Description: Admin create reports.
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Login with your account
Click on Reports
Create
Post condition: Task has been completed successfully.
Author: MC220201701

Adopted Methodology

10
Definition:
“Methodology is a framework that is used to structure, plan and control the process
developing an information system”.
VU process model is a combination of the waterfall and spiral model.

Waterfall model:
Waterfall model is the first process model to be introduced. This model is also known as
linear sequential model or classic life cycle model. It consists of five stages.

1. Requirement definition:
In this stage, the systems services, constraints and goals are established by consultation
with system users.
2. System and software design:
In this stage, we conceptualize overall system architecture.

3. Implementation and unit testing:

In this stage the software design is realized as a set of programs or program units.
4. Integration and system testing:
In this stage, the individual program unit or programs are integrated and tested as a
complete system to ensure that the system requirements have been met.
5. Operation and maintenance:
Maintenance means correcting errors which were not discovered in earlier stages.
Spiral model:
It is a form of incremental model. In this model, main emphasis is given on risk analysis.
It is used for large and complicated projects. Generally, the spiral model has four phases:
planning, risk analysis, development, and evaluation. Planning phase covers scope,
requirement and functionality of the system. Second phase risk analysis is most important
phase. Development phase covers the designing, coding and testing and finally the
application is delivered to client for further evaluation
Adopted model: VU process model

11
 In our project we choose VU process model it is the combination of waterfall and spiral
model.VU process model is a hybrid approach. It is depicted in following diagram

Requirements Analysis In each vu model

Each phase
Planning: risk analysis: report back
Software requirement cost effectiveness
Work plan with less work

Client evaluation: development: Design

deliver project designing, coding,
with specific testing
requirement otherwise
recycle for further
evaluation.

Acceptance Testing Coding

Above is the diagram of combination of waterfall and spiral model.

Reason for choosing this methodology:

1. VU process model has the benefits of predictability.
2. Maintenance is easy in this model.
3. Requirements are well understood.
4. It is more concise and advanced model than waterfall model.
5. VU process model is heavily dependent on risk analysis.
6. VU process model allows us to do correction at any stage.

WORK PLAN:

12
13