Scribd
Upload
434 views3 pages

Software Requirements Specification: Media Player System Requirements

The document outlines the system requirements for a media player software called Eleven Version 1.0. It includes sections on the product perspective, functions, user characteristics, and specific requirements. The specific requirements section details the external interfaces, functional requirements, and non-functional requirements including reliability, security, maintainability and portability. The document is intended for the software engineers developing the media player and will allow them to understand what is expected of the system.

Uploaded by

asj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
434 views3 pages

Software Requirements Specification: Media Player System Requirements

The document outlines the system requirements for a media player software called Eleven Version 1.0. It includes sections on the product perspective, functions, user characteristics, and specific requirements. The specific requirements section details the external interfaces, functional requirements, and non-functional requirements including reliability, security, maintainability and portability. The document is intended for the software engineers developing the media player and will allow them to understand what is expected of the system.

Uploaded by

asj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Media Player System Requirements

Software Requirements
Specification
for

<Eleven>
Version 1.0 approved

Prepared by <Anuj Srivastava>

<S.I.E.T>

<date created>
Media Player System Requirements

Table of Contents

1. Introduction ................................................................................ Error! Bookmark not defined.


1.1 Purpose ..............................................................................................Error! Bookmark not defined.
1.2 Document convention .......................................................................Error! Bookmark not defined.
1.3 Intended audience and reading suggestion ........................................Error! Bookmark not defined.
1.4 Product scope ....................................................................................Error! Bookmark not defined.
1.5 Product scope...................................................................................................................................... 1

2. Overall Description .................................................................... Error! Bookmark not defined.


2.1 Product Perspective ...........................................................................Error! Bookmark not defined.
2.1.2 Software Requirements ............................................................Error! Bookmark not defined.
2.3 Product Functions .............................................................................Error! Bookmark not defined.
2.4 User Characterstics ...........................................................................Error! Bookmark not defined.
2.5 Apportioning of requirments .............................................................Error! Bookmark not defined.
2.6 Assumptions and Dependencies........................................................Error! Bookmark not defined.

3. Specific Requirements ................................................................. Error! Bookmark not defined.


3.1 External Interfaces ............................................................................Error! Bookmark not defined.
3.1.1 User Interfaces ...........................................................................Error! Bookmark not defined.
3.1.2 Software Interfaces ....................................................................Error! Bookmark not defined.
3.1.3 Hardware Interfaces ...................................................................Error! Bookmark not defined.
3.1.4 Communications Interfaces........................................................Error! Bookmark not defined.

3.2 Functional Requirements ..........................................................................................................4

3.3 Nonfunctional requirements ......................................................................................................5


3.3.2 Logical Database Requirements…………………………………………………………………….5
3.3.3 Design Constraints ……………………………………………………………….…….…………….5
3.3.4 Standards Compliance ……………………………………………………..…………….………….5
3.3.5 Reliability ………………………………………………………………………………….….……….5
3.3.6 Availability…………………………………………………………………………………….…….….5
3.3.7 Security …………………………………………………………………………………………….….5
3.3.8 Maintainability ……………………………………………………………………………………..….5
3.3.9 Portability…………………………………………………………………………………………...….5

Appendix A: Glossary....................................................................................................................6
Appendix B: Analysis Models .......................................................................................................7
Appendix C: To Be Determined List ............................................................................................7

Revision History
Name Date Reason For Changes Version
Media Player System Requirements

1. Introduction:
The following subsections of the Software Requirements Specifications (SRS) document
provide an overview of the entire SRS.

1.Purpose:
The Software Requirements Specification (SRS) will provide a detailed description
of the requirements for the MP4 Music Player System. This SRS will allow for a
complete understanding of what is to be expected of the system to be constructed. The
clear understanding of the player and its’ functionality will allow for the correct software
to be developed for the end user and will be used for the development of the future
stages of the project. This SRS will provide the foundation for the project. From this
SRS, the player can be designed, constructed, and finally tested.

This SRS will be used by the software engineers constructing the and the hotel end
users. The software engineers will use the SRS to fully understand the expectations of
this HMS to construct the appropriate software. The hotel end users will be able to to
their bexpectations. If it is not to their expectations the end users can specify how it is
not to btheir liking and the software engineers will change the SRS to fit the end users’
needs.

2.Document conventions:
The SRS document is written in regular Font style of size 11.For stating terms having high
significance and to state high level requirements,we are using different font with size 12 and
bold.

3.Intended audience and reading suggestions:

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy