Software Requirements Specification
Version 1.0
17 March 2021
Heavy Industry Taxila Management
System
Maham Tabish
45(SE-3rd)
2020-24
University Of Poonch Rawalakot
Department of CS and IT
i
SRS By Maham Tabish
Table of Contents
HEAVY INDUSTRIES TAXILA MANAGEMENT SYSTEM ............................................................................ 4
1. Introduction ............................................................................................................................................. 4
1.1. Purpose ........................................................................................................................................... 4
1.2. Scope of Project .............................................................................................................................. 4
1.3. Glossary .......................................................................................................................................... 5
1.4. References ..................................................................................................................................... 5
1.5. Overview of Document .................................................................................................................. 5
2. Overall Description ................................................................................................................................. 6
2.1 System Environment....................................................................................................................... 6
2.2 Product Functions Specification ..................................................................................................... 6
2.2.1 Login: ......................................................................................................................................... 6
2.2.2 Logout: ....................................................................................................................................... 6
2.2.3 Submit Report:............................................................................................................................ 6
2.2.4 Place Order: ................................................................................................................................ 6
2.2.5 Manage Record:.......................................................................................................................... 7
2.2.6 Security:...................................................................................................................................... 7
2.2.7 Admin: ........................................................................................................................................ 7
2.2.8 Crew Detail:................................................................................................................................ 7
2.2.9 Budget: ....................................................................................................................................... 7
2.3 User Characteristics ........................................................................................................................ 7
3. Requirements Specification ................................................................................................................... 8
3.1 Functional Requirements ................................................................................................................ 8
3.2 Detailed Non-Functional Requirements ......................................................................................... 8
4. Sequence Diagram: ..................................................................................................................................15
5. Class Diagram .......................................................................................................................................16
1|Page
SRS By Maham Tabish
Fig 1.1 System Environment ........................................................................................................................... 6
Fig 1.2 Use Case Diagram .......................................................................................................................... 9
Fig 1.3 Activity Diagram Post a Complaint ...............................................................................................12
Fig 1.4 Activity Diagram Upload Report ...................................................................................................13
2|Page
SRS By Maham Tabish
Chapter 1
System Analysis
3|Page
SRS By Maham Tabish
HEAVY INDUSTRIES TAXILA MANAGEMENT SYSTEM
1. Introduction
1.1. Purpose
The objective of the project is to develop a system that automates the processes and
activities of the Heavy Industry Taxila. The purpose is to design a system using which
one can perform all operations related to the industry. It will explain the purpose and
features of the system, the interfaces of the system, what the system will do, the
constraints under which it must operate. This document is intended for both the
stakeholders and the developers of the system.
1.2. Scope of Project
This system will help the employees of the industry to efficiently do their work. It will
also help in managing the record of everything including different types of machinery
and crew. The head of department will be able to keep record of every thing in a very
convenient and effective way. The customers including foreign customers will be able to
view the product details and place order. The software will also facilitate communication
between customers and HODs or Chairman via E-Mail.
4|Page
SRS By Maham Tabish
1.3. Glossary
Terms Definitions
HOD Head of department.
Crew Employees of the industry.
Machinery Tools and devices used in making army weapons.
HITMS Heavy Industry Taxila Management System.
1.4. References
Recommended Practice for Software Requirements Specifications. IEEE Computer
Society, 1998
1.5. Overview of Document
This document is a guide for how to make an efficient system for the industry. As the
industry is under the command of the Army so this system will help in recognizing the
functional and non-functional requirements of the Army from the HIT.
5|Page
SRS By Maham Tabish
2. Overall Description
2.1 System Environment
This section represents what are the boundary and scope of HIT Management System. It
describes the main objective of the system and its entities involved.
Machinery
Products
CREW
Department
Heavy Industry Taxila Management
System
HOD
Fig 1.1 System Environment
2.2 Product Functions Specification
The functions which are used in this project and their functioning:
2.2.1 Login:
To enter the details of the head of each department and the chairman. Also, to let them
use the HIT management system.
2.2.2 Logout:
To logout of the system when the persons get changed.
2.2.3 Submit Report:
To submit test report of the product.
2.2.4 Place Order:
6|Page
SRS By Maham Tabish
To submit or place the request for more machinery or crew.
2.2.5 Manage Record:
To manage the record of crew, machinery and products.
2.2.6 Security:
System and administration will ensure the security of the crew and products on their end.
2.2.7 Admin:
Head of the departments who will be able to access the system.
2.2.8 Crew Detail:
The detail of the crew of each department should be handled separately.
2.2.9 Budget:
The system will help in managing or keep record of the budget of each project.
2.3 User Characteristics
The user is expected to be Internet literate and be able to use a search engine.
The HOD and other staff who are authorized to access the system are expected to be
Internet literate and to be able to use email with attachments.
7|Page
SRS By Maham Tabish
3. Requirements Specification
3.1 Functional Requirements
ID Requirement Justification
REQ-1 Login/Logout To use HITMS enter username and password to
login.
REQ-2 Submit product report It allows the admin\user to upload the report of the
experiment of the different products.
REQ-3 Post a complaint It allows the admin\user to post the complaint.
REQ-4 Manage Payment The system will manage the detail of payment.
REQ-5 Manage machinery record It helps the HOD to manage the machinery record
of every department respectively.
REQ-6 Manage crew record It helps the HOD to manage the crew record of
every department respectively.
REQ-7 Manage Department record It helps the HOD to manage the record of the whole
department which includes machinery as well as
crew.
REQ-8 Place an order\request for It allows the HOD to request for new machinery.
machinery
REQ-9 Place an order\request for It allows the HOD to request for new staff/crew.
crew
REQ-10 Manage first-aid It allows the HOD to manage and order for new
medicine.
3.2 Detailed Non-Functional Requirements
The non-functional requirement of the HIT Management System offered online are listed
below:
Speedy performance
Maintainability
Good user interface
3.3 Use case Diagram
This section will provide use case diagrams of the proposed application. Use case
diagrams are considered as analysis tool which help in gathering/soliciting requirements
of the application. A use case diagram at is a representation of a user's interaction with
the application that shows the relationship between the user and the different use.
8|Page
SRS By Maham Tabish
Fig 2.2 Use Case Diagram
3.4 Use Case Description:
Use case description tells the whole process of all functionalities in detail step by step.
It has actor actions and system response is given in sequence. That is why this system is
particularly important. Further more the activity diagrams are also derived or made
according to the use case description.
9|Page
SRS By Maham Tabish
3.4.1 Use case description of functionality post a complaint
Use case name: Post a complaint
Scope: Heavy Industry Texla Management System
Level: User goal
Primary actor: User (customer)
Precondition: Actor should only be a user to post a complaint
Postcondition: Actor successfully posted a complaint
Main success scenario: Actor Action System Response
(1) User requests (2) System asks for the following
the system to post a information:
complaint. -> Name
-> Subject of complaint
-> Body of complaint
(3) User provides the required (4) System validates the submitted
Information. Information.
(5) System successfully posted a
complaint.
Extension: 4(a) Invalid Information.
5(a) System is unable to post a complaint.
Frequency of As required.
occurrence:
10 | P a g e
SRS By Maham Tabish
3.4.2 Use case description of functionality Upload Report
Use case name: Upload report
Scope: Heavy Industry Texla Management System
Level: User goal
Primary actor: HOD
Precondition: Actor should be HOD
Postcondition: Actor successfully uploaded a report.
Main success scenario: Actor Action System Response
(1) User requests (2) System asks for the following
the system to upload information:
a report. -> Name
-> Subject of report
-> Body of report
(3) User provides the required (4) System validates the submitted
Information. Information.
(5) System successfully posted a
complaint.
Extension: 4(a) Invalid Information.
5(a) System is unable to post a complaint.
Frequency of As required.
occurrence:
11 | P a g e
SRS By Maham Tabish
3.5 Activity Diagram:
Activity diagram is another important diagram in UML to describe dynamic aspects of
the system. Activity diagram is basically a flow chart to represent the flow form one
activity to another activity.
3.5.1 post a complaint.
Fig 3.3 Activity Diagram Post a Complaint
12 | P a g e
SRS By Maham Tabish
3.5.2 Upload Report
Fig 4.4 Activity Diagram Upload Report
13 | P a g e
SRS By Maham Tabish
Chapter 2
System Designs
14 | P a g e
SRS By Maham Tabish
4. Sequence Diagram:
UML sequence diagrams are used to show how objects interact in a given situation. An
important characteristic of a sequence diagram is that time passes from top to bottom, the
interaction starts near the top of the diagram and ends at the bottom (i.e. Lower equals
later). Sequence Diagram (SD) is one of the key notations of UML and serves as a well-
accepted media among software developers, stakeholders, and tool builders. The appeal
can be attributed to the intuitive nature of its graphical representation and its capability to
capture scenarios of how the system might be used or how entities interact by
transmitting sequences of Messages.
4.1 Post a Complaint
Fig 2.1 Sequence Diagram Post a Complaint
15 | P a g e
SRS By Maham Tabish
4.2 Upload Report
Fig 2.2 Sequence Diagram Upload Report
5. Class Diagram
The class diagram is a static diagram. It represents the static view of an application. Class
diagram is not only used for visualizing, describing and documenting different aspects of
a system but also for constructing executable code of the software application. The class
diagram describes the attributes and operations of a class and also the constraints
imposed on the system.
The class diagrams are widely used in the modelling of object-oriented systems because
they are the only UML diagrams which can be mapped directly with object-oriented
languages. The class diagram shows a collection of classes, interfaces, associations,
collaborations and constraints. It is also known as a structural diagram.
16 | P a g e
SRS By Maham Tabish
Fig 2.3 Class Diagram
17 | P a g e
SRS By Maham Tabish
6. References
➢ Applying UML and Patterns: An Introduction to Object-Oriented Analysis and
Design and Iterative Development (3rd Edition)
➢ IEEE
➢ UML Designs and Patterns
18 | P a g e
