Software Requirements

Specification
for

<Project>
Version 1.0 approved

Prepared by <author>

<organization>

<date created>

Copyright © 2024
Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose..............................................................................................................................................1
1.2 Document Conventions.....................................................................................................................1
1.3 Intended Audience and Reading Suggestions...................................................................................1
1.4 Definitions, acronyms, abbreviations...............................................................................................1
1.5 Scope…………………………………………………………………………………… 1
1.6 References.........................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective...........................................................................................................................2
2.2 Product Features................................................................................................................................2
2.3 User Classes and Characteristics......................................................................................................2
2.4 Operating Environment.....................................................................................................................2
2.5 Design and Implementation Constraints...........................................................................................2
2.6 User Documentation.........................................................................................................................2
2.7 Assumptions and Dependencies.......................................................................................................3
3. System Features.......................................................................................................................3
3.1 System Feature 1...............................................................................................................................3
3.2 System Feature 2 (and so on)............................................................................................................4
4. External Interface Requirements...........................................................................................4
4.1 User Interfaces..................................................................................................................................4
4.2 Hardware Interfaces..........................................................................................................................4
4.3 Software Interfaces...........................................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................5
5.1 Performance Requirements...............................................................................................................5
5.2 Safety Requirements.........................................................................................................................5
5.3 Security Requirements......................................................................................................................5
5.4 Software Quality Attributes..............................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary....................................................................................................................5
Appendix B: Analysis Models.......................................................................................................6
Appendix C: Issues List.................................................................................................................6

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> Page 1

1. Introduction
1.1 Purpose
This document describes the software requirements and
specification of Arcobat reader DC.

1.2 Document Conventions

In this document we are using font ‘Times’, Font size ‘12’.
Margins Top ‘1in’, Bottom ‘1in’, Left ‘0.9in’, Right ‘0.9in’.

1.3 Intended Audience and Reading Suggestions

The
document is intended for Writers, designers, and other content creators who produce documents
that will be distributed electronically in PDF format.

Guides and resources available from organizations such as the W3C and Adobe provide tips and
best practices for creating accessible PDF documents.

1.4 Definitions, abbreviations

1.4.1 Definitions
PDF (Portable Document Format): A file format developed by Adobe that preserves the layout
and formatting of documents across different platforms and devices. PDF files can contain text,
images, hyperlinks, and other elements.

Font Embedding: The process of including font data within a PDF file to ensure that the document
displays correctly even if the recipient does not have the same fonts installed on their device.

Hyperlink: A clickable element within a document that, when activated, directs the reader to
another location within the same document, a different document, or a webpage.

Bookmarks: Navigation aids in a PDF document that allow readers to quickly jump to specific
sections or pages. Bookmarks are typically organized hierarchically to reflect the document's
structure.

Table of Contents (TOC): A list of the main sections or chapters in a document, along with their
corresponding page numbers. In PDF documents, the table of contents often includes hyperlinks to
facilitate navigation.

Alternative Text (Alt Text): Descriptive text added to images, charts, or other non-text elements
in a document to make them accessible to individuals with visual impairments. Alt text describes
the content and function of the element.
Software Requirements Specification for <Project> Page 2

PDF Accessibility: The practice of ensuring that PDF documents are usable by individuals with
disabilities, including those who use screen readers or other assistive technologies. Accessibility
features include proper document structure, alt text for images, and logical reading order.

Security Settings: Controls in Adobe Acrobat Reader DC that allow document creators to restrict
certain actions, such as printing, editing, or copying content, to protect sensitive information in PDF
files.

Document Metadata: Information embedded in a PDF file that provides details about the
document, such as the title, author, creation date, and keywords. Metadata can be viewed and
edited using Adobe Acrobat Reader DC.

Revision History: A record of changes made to a document over time, including the date of each
revision and a description of the changes. Adobe Acrobat Reader DC allows users to view the
revision history of a PDF document if it has been enabled by the document creator.

1.4.2 Abbreviations
Throughout this document the following abbreviations are used:

TOC: Abbreviation for "Table of Contents," a list of the main sections or chapters in a document, often with
corresponding page numbers and hyperlinks for navigation.

Alt Text: Abbreviation for "Alternative Text," descriptive text added to images, charts, or other non-text elements
in a document to make them accessible to individuals with visual impairments.

URL: Abbreviation for "Uniform Resource Locator," the address used to identify resources on the internet. In PDF
documents, URLs are often hyperlinked for easy access to web content.

OCR: Abbreviation for "Optical Character Recognition," the technology used to convert scanned images of text into
editable and searchable text in PDF documents.

ISO: Abbreviation for the "International Organization for Standardization," an international standard-setting body
responsible for developing and publishing standards for various industries, including document formats.

UI: Abbreviation for "User Interface," the graphical layout of an application through which users interact with the
software. In Adobe Acrobat Reader DC, the UI includes menus, toolbars, and dialog boxes.

1.5 Project Scope

Clear and specific statements describing the intended outcomes of the project. Objectives should be
measurable and achievable within the defined scope, time frame, and budget.A list of tangible outputs or
results that will be produced as part of the project. Deliverables should be well-defined and directly linked to
the project objectives.A description of what is included in the project and what is not. This helps to manage
Software Requirements Specification for <Project> Page 3

stakeholders' expectations and prevent scope creep.Important checkpoints or stages in the project timeline.
Milestones mark significant progress points and help track the project's overall progress.

1.6 References
User Interface Style Guide
 Title: "Company X User Interface Style Guide"
 Author: Company X Design Team
 Version Number: 2.0
 Date: January 15, 2024
 Source: Internal Document Repository or Company Intranet
Contract
 Title: "Software Development Agreement between Company Y and Vendor Z"
 Author: Legal Department of Company Y
 Version Number: 1.1
 Date: March 1, 2023
 Source: Legal Department of Company Y or Contract Management System
Standards
 Title: "IEEE Standard for Software Requirements Specifications (IEEE Std 830-1998)"
 Author: Institute of Electrical and Electronics Engineers (IEEE)
 Version Number: 1998 Edition
 Date: December 7, 1998
 Source: IEEE Xplore Digital Library (https://ieeexplore.ieee.org/document/720574)
System Requirements Specification (SRS)
 Title: "Project Alpha System Requirements Specification"
 Author: Project Alpha Development Team
 Version Number: 3.0
 Date: February 28, 2024
 Source: Internal Document Repository or Project Management System
Use Case Documents
 Title: "Project Alpha Use Case Scenarios"
 Author: Project Alpha Business Analyst Team
 Version Number: 1.2
 Date: January 10, 2024
 Source: Internal Document Repository or Project Management System
Vision and Scope Document

 Title: "Project Alpha Vision and Scope Document"

 Author: Project Alpha Product Owner
 Version Number: 1.0
 Date: December 15, 2023
 Source: Internal Document Repository or Project Management System
Software Requirements Specification for <Project> Page 4

2. Overall Description
2.1 Product Perspective
This section provides an overview of how the software product fits into the broader context of existing systems or
processes. It may include descriptions of interfaces with other systems, dependencies, or interactions with external
components.

2.2 Product Features

Here, the specific features and functionalities of the software product are outlined. Each feature should be
described in detail, including its purpose, requirements, and any associated dependencies.

2.3 User Classes and Characteristics

This section identifies the different types of users who will interact with the software product and describes their
characteristics, needs, and expectations. It may include personas or user profiles to illustrate typical users and their
goals.

2.4 Operating Environment

This part outlines the technical environment in which the software product will operate. It includes information
about hardware, software, network configurations, and any other infrastructure requirements necessary for the
product to function properly.

2.5 Design and Implementation Constraints

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

• Hardware never fails
• ATM casing is impenetrable
• Limited number of transactions per day (sufficient paper for receipts)
Software Requirements Specification for <Project> Page 5

• Limited amount of money withdrawn per day (sufficient money)

3. Specific Requirements
3.1 Functional Requirements
The functional requirements are organized in two sections First requirements of the ATM
and second requirements of the bank.

3.1.1 Requirements of the automated teller machine

The requirements for the automated teller machine are organized in the following way Gen_
eral requirements, requirements for authorization, requirements for a transaction.
General

Functional requirement 1

• Description
Initialize parameters t, k, m, n
• Input
ATM is initialized with t dollars, k, m, n are entered
• Processing
Storing the parameters.
• Output
Parameters are set.

Functional requirement 2

• Description
If no cash card is in the ATM, the system should display initial display.

Functional requirement 3
• Description
If the ATM is running out of money, no card should be accepted. An error message is
Displayed.
• Input
A card is entered.
• Processing
The amount of cash is less than t.

• Output
Display an error message. Return cash card.
Software Requirements Specification for <Project> Page 6

Authorization

The authorization starts after a customer has entered his card in the ATM

Functional requirement 4

• Description
The ATM has to check if the entered card is a valid cash-card.
• Input
Customer enters the cash card.
• Processing
Check if it is a valid cash card.It will be valid if
1. the information on the card can be read.
2. it is not expired.
• Output
Display error message and return cash card if it is invalid.

__

4. External Interface Requirements

4.1 User Interfaces
The customer user interface should be intuitive, such that 99.9% of all new ATM users are able to
complete their banking transactions without any assistance

4.2 Hardware Interfaces

The hardware should have following specifications:

• Ability to read the ATM card

• Ability to count the currency notes
• Touch screen for convenience
• Keypad (in case touchpad fails)
• Continuous power supply
• Ability to connect to bank’s network
• Ability to take input from user
• Ability to validate user

4.3 Software Interfaces

The software interfaces are specific to the target banking software systems.
Software Requirements Specification for <Project> Page 7

5. Other Nonfunctional Requirements

5.1 Performance Requirements
• It must be able to perform in adverse conditions like high/low temperature etc.
• Uninterrupted interrupted connections
• High data transfer rate

5.2 Safety Requirements

• Must be safe kept in physical aspects, say in a cabin
• Must be bolted to floor to prevent any kind of theft
• Must have an emergency phone outside the cabin
• There must be an emergency phone just outside the cabin
• The cabin door must have an ATM card swipe slot
• The cabin door will always be locked, which will open only when user swipes
his/her ATM card in the slot & is validated as genuine

5.3 Security Requirements

• Users accessibility is censured in all the ways
• Users are advised to change their PIN on first use
• Users are advised not to tell their PIN to anyone
• The maximum number of attempts to enter PIN will be three

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.>

5.4.1 Availability
The ATM network has to be available 24 hours a day.

5.4.2 Security
The ATM network should provide maximal security .In order to make that much more
Transparent there are the following requirements
1. It must be impossible to plug into the network.

5.4.3 Maintainability
Only maintainers are allowed to connect new ATMs to the network.
Software Requirements Specification for <Project> Page 8

6. Other Requirements
Data Base
The ATM must be able to use several data formats according to the data formats that are
provided by the data bases of different banks. A transaction should have all the properties of
a data base transaction (Atomicity, Consistency, Isolation, Durability).

Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire
organization, and just include terms specific to a single project in each SRS.>

Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>

Appendix C: Issues List

< This is a dynamic list of the open requirements issues that remain to be resolved, including
TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>