2022 Final Year Projects

Software Requirements Specification

Name of the System goes here
Version 00

Group Number: 00
Lastname, Initials, Student number
Lastname, Initials, Student number
Lastname, Initials, Student number
Lastname, Initials, Student number

To be completed by Coordinator

Date Received: _____/_____/_______

Signature: ______________________

Coordinator Notes:

________________________________________

________________________________________

________________________________________

Acknowledgement: Sections of this document are based upon the IEEE Guide to Software
Requirements Specification (IEEE 830)
Software Requirements Specification Document Page ii

Table of Contents
Table of Contents....................................................................................................................... ii

Revision History........................................................................................................................ iii

1. Introduction.......................................................................................................................... 1
1.1 Purpose..................................................................................................................................1
1.2 Document Conventions..........................................................................................................1
1.3 Intended Audience and Reading Suggestions..........................................................................1
1.4 Product Scope........................................................................................................................1
1.5 References..............................................................................................................................1

2. Overall Description.............................................................................................................. 2
2.1 Product Perspective................................................................................................................2
2.2 Product Functions...................................................................................................................2
2.3 User Classes and Characteristics.............................................................................................2
2.4 Operating Environment..........................................................................................................2
2.5 Design and Implementation Constraints..................................................................................2
2.6 User Documentation...............................................................................................................3
2.7 Assumptions and Dependencies..............................................................................................3

3. External Interface Requirements........................................................................................ 3

3.1 User Interfaces........................................................................................................................3
3.2 Hardware Interfaces................................................................................................................3
3.3 Software Interfaces.................................................................................................................3
3.4 Communications Interfaces.....................................................................................................4

4. Specific Requirements (System Features and Functional Requirements)........................4

4.1 System Features.....................................................................................................................4
4.2 Use Cases...............................................................................................................................5
4.3 Use Case Diagram..................................................................................................................5
4.4 Classes / Objects....................................................................................................................6
4.5 Business Rules.......................................................................................................................6

5. Other Nonfunctional Requirements.................................................................................... 7

5.1 Performance Requirements.....................................................................................................7
5.2 Safety Requirements...............................................................................................................7
Software Requirements Specification Document Page iii

5.3 Security Requirements............................................................................................................7

5.4 Software Quality Attributes....................................................................................................7

6. Other Requirements............................................................................................................. 7

Appendix A: Glossary................................................................................................................ 8

Appendix B: Analysis Models.................................................................................................... 8

Appendix C: List of References................................................................................................. 8

Revision History
Name Date Reason For Changes Version
Software Requirements Specification Document Page 1

1. Introduction
1.1 Purpose
<Identify the product whose software requirements are specified in this document, including the
revision or release number. Describe the scope of the product that is covered by this SRS,
particularly if this SRS describes only part of the system or a single subsystem.>

1.2 Document Conventions

<Describe any standards or typographical conventions that were followed when writing this SRS,
such as fonts or highlighting that have special significance. For example, state whether priorities
for higher-level requirements are assumed to be inherited by detailed requirements, or whether
every requirement statement is to have its own priority.>

1.3 Intended Audience and Reading Suggestions

<Describe the different types of reader that the document is intended for, such as developers,
project managers, marketing staff, users, testers, and documentation writers. Describe what the
rest of this SRS contains and how it is organized. Suggest a sequence for reading the document,
beginning with the overview sections and proceeding through the sections that are most pertinent
to each reader type.>

1.4 Product Scope

<Provide a short description of the software being specified and its purpose, including relevant
benefits, objectives, and goals. Relate the software to corporate goals or business strategies. If a
separate vision and scope document is available, refer to it rather than duplicating its contents
here.>

1.5 References
<List any other documents or Web addresses to which this SRS refers. These may include user
interface style guides, contracts, standards, system requirements specifications, use case
documents, or a vision and scope document. Provide enough information so that the reader could
access a copy of each reference, including title, author, version number, date, and source or
location.>
Software Requirements Specification Document Page 2

2. Overall Description
2.1 Product Perspective
<Describe the context and origin of the product being specified in this SRS. For example, state
whether this product is a follow-on member of a product family, a replacement for certain existing
systems, or a new, self-contained product. If the SRS defines a component of a larger system,
relate the requirements of the larger system to the functionality of this software and identify
interfaces between the two. A simple diagram that shows the major components of the overall
system, subsystem interconnections, and external interfaces can be helpful.>

2.2 Product Functions

<Summarize the major functions the product must perform or must let the user perform. Details
will be provided in Section 3, so only a high level summary (such as a bullet list) is needed here.
Organize the functions to make them understandable to any reader of the SRS. A picture of the
major groups of related requirements and how they relate, such as a top level data flow diagram
or object class diagram, is often effective.>
<The functions should be organized in a way that makes the list of functions understandable to
the customer or to anyone else reading the document for the first time.>

2.3 User Classes and Characteristics

<Identify the various user classes that you anticipate will use this product. User classes may be
differentiated based on frequency of use, subset of product functions used, technical expertise,
security or privilege levels, educational level, or experience. Describe the pertinent characteristics
of each user class. Certain requirements may pertain only to certain user classes. Distinguish the
most important user classes for this product from those who are less important to satisfy.>

2.4 Operating Environment

<Describe the environment 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.>

2.5 Design and Implementation Constraints

<Describe any items or issues that will limit the options available to the developers. These might
include: corporate or regulatory policies; hardware limitations (timing requirements, memory
requirements); interfaces to other applications; specific technologies, tools, and databases to be
Software Requirements Specification Document Page 3

used; parallel operations; language requirements; communications protocols; security

considerations; design conventions or programming standards (for example, if the customer’s
organization will be responsible for maintaining the delivered software).>

2.6 User Documentation

<List the user documentation components (such as user manuals, on-line help, and tutorials) that
will be delivered along with the software. Identify any known user documentation delivery formats
or standards.>

2.7 Assumptions and Dependencies

<List any assumed factors (as opposed to known facts) that could affect the requirements stated
in the SRS. These could include third-party or commercial components that you plan to use,
issues around the development or operating environment, or constraints. The project could be
affected if these assumptions are incorrect, are not shared, or change. Also identify any
dependencies the project has on external factors, such as software components that you intend
to reuse from another project, unless they are already documented elsewhere (for example, in the
vision and scope document or the project plan).>

3. External Interface Requirements

3.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., help) that
will appear on every screen, keyboard shortcuts, error message display standards, and so on.
Define the software components for which a user interface is needed. Details of the user interface
design should be documented in a separate user interface specification.>

3.2 Hardware Interfaces

<Describe the logical and physical characteristics of each interface between the software product
and the hardware components of the system. This may include the supported device types, the
nature of the data and control interactions between the software and the hardware, and
communication protocols to be used.>
Software Requirements Specification Document Page 4

3.3 Software Interfaces

<Describe the connections between this product and other specific software components (name
and version), including databases, operating systems, tools, libraries, and integrated commercial
components. Identify the data items or messages coming into the system and going out and
describe the purpose of each. Describe the services needed and the nature of communications.
Refer to documents that describe detailed application programming interface protocols. Identify
data that will be shared across software components. If the data sharing mechanism must be
implemented in a specific way (for example, use of a global data area in a multitasking operating
system), specify this as an implementation constraint.>

3.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. Define any pertinent message formatting. Identify any communication
standards that will be used, such as FTP or HTTP. Specify any communication security or
encryption issues, data transfer rates, and synchronization mechanisms.>

4. Specific Requirements (System Features and Functional

Requirements)
< This will be the largest and most important section of the SRS. The customer requirements will
be embodied within Section 2, but this section will give the D-requirements that are used to guide
the project’s software design, implementation, and testing.> <This section illustrates organizing
the functional requirements for the product by system features (or functional requirements), the
major services provided by the product. You may prefer to organize this section by use case,
mode of operation, user class, object class, functional hierarchy, or combinations of these,
whatever makes the most logical sense for your product.>

4.1 System Features

4.1.1 System Feature #1: <Short Description for system feature>

a) Description and Priority

The ULJOBHUB application system maintains user’s profile , notifications for job
seekers to enter their qualifications and preferences ,also to receive the nonfictions
when a job vacancy matching their qualifications and preference is posted. Also the
Software Requirements Specification Document Page 5

user will be able to search for available job vacancies based on their preferences such
as job type and salary range , the app will also provide a list of recommended jobs
based on the user’s profile. And the app will provide answers to frequently asked
questions

b) Stimulus/Response Sequences
 Search for a job vacancy
 Post job vacancy
 Receives notifications regarding the feedback of the job application and also the
availability of vacancies.
 Decline the application when the closing date have passed.

c) Functional Requirements

Other system features include:

DISTRUBUTED DATABASE
Distributed database implies that a single application should be able to operate
transparently on data that is spread across a variety of different database and connected by
a communication network as shown below in figure.

REQ-1:
REQ-2:
REQ-3: etc.

4.1.2 System Feature #2: <Follow steps provided in 4.1.1 for all your system features>
Software Requirements Specification Document Page 6

4.2 Use Cases

4.2.1 Use Case #1
<Describe a list of actions or event steps, typically defining the interactions between a role (known
in the Unified Modeling Language as an actor) and a system, to achieve a goal.>
4.2.2 Use Case #2

4.2.3 Use Case #3

…………
4.3 Use Case Diagram
<A business Use Case Diagram depicts a model of several business use cases (goals) which
represents the interactions between a restaurant (the business system) and its primary stakeholders
(business actors and business workers)>

<EXAMPLE OF USE CASE>

Software Requirements Specification Document Page 7

4.4 Classes / Objects

4.4.1 Class / Object #1: <Describe a class or object>
a) Attributes
The attributes shall include use
b) Functions <Reference to functional requirements and/or use cases>

4.4.2 Class / Object #2: <Describe a class or object>

……….

4.5 Business Rules

 Applicant that do not meet the requirements are automatically rejected.
 User who did not register will not receive notifications, cannot be able to get answers from
help center.
 User cannot have two accounts .
 User have to enter all their details , qualifications




5. Other Nonfunctional Requirements

5.1 Performance Requirements
<If there are performance requirements for the product under various circumstances, state them
here and explain their rationale, to help the developers understand the intent and make suitable
design choices. Specify the timing relationships for real time systems. Make such requirements as
specific as possible. You may need to state performance requirements for individual functional
requirements or features.>
Software Requirements Specification Document Page 8

5.2 Safety 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. Refer to any external policies or regulations that state safety
issues that affect the product’s design or use. Define any safety certifications that must be
satisfied.>

5.3 Security Requirements

<Specify any requirements regarding security or privacy issues surrounding use of the product or
protection of the data used or created by the product. Define any user identity authentication
requirements. Refer to any external policies or regulations containing security issues that affect
the product. Define any security or privacy certifications that must be satisfied.>

5.4 Software Quality Attributes

<Specify any additional quality characteristics for the product that will be important to either the
customers or the developers. Some to consider are: adaptability, availability, correctness,
flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability,
and usability. Write these to be specific, quantitative, and verifiable when possible. At the least,
clarify the relative preferences for various attributes, such as ease of use over ease of learning.>

6. Other Requirements
<Define any other requirements not covered elsewhere in the SRS. This might include database
requirements, internationalization requirements, legal requirements, reuse objectives for the
project, and so on. Add any new sections that are pertinent to the project.>

Appendix A: Glossary

<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations.>

Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams. This is important and set a stage for
detailed System Design Document (SDD)>
Software Requirements Specification Document Page 9

Appendix C: List of References

<Collect a numbered list of references or sources that helped you to put together your SRS>
1. IEEE Recommended Practice for Software Requirements Specifications," IEEE Std 830-
1998
2. <Ref 3>
3. <Ref 4>
4. ………..
5. <Ref n>