Software Requirements Specification for HTML Based MP3 Player

Verified

Added on  2022/08/18

|6
|795
|18
Report
AI Summary
This report provides a detailed analysis of an HTML-based MP3 player, including its purpose, design methodology, and software requirements specification. The report explores the player's functionality, which is designed for music enthusiasts, particularly students, and supports various audio file formats. It outlines the use of agile methodology for development, detailing the planning, analysis, design, execution, wrapping, and closure phases. The report also covers definitions, acronyms, and abbreviations, and references relevant research. The Software Requirements Specification (SRS) document is also included, providing a comprehensive overview of the project's scope, features, and non-functional requirements, such as performance, security, and software quality attributes. The report also provides guidelines for the design document, including the system's architecture, subsystem decomposition, and persistent data management.
Document Page
Running head: HTML Based MP3 Player
HTML BASED MP3 PLAYER
Name of the Student
Name of the University
Author Note
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
1HTML Based MP3 Player
Table of Contents
Introduction:...............................................................................................................................2
Purpose of the system:...............................................................................................................2
Design methodology use:...........................................................................................................2
Definitions, acronyms, and abbreviations:.................................................................................3
Overview of document:..............................................................................................................4
References:.................................................................................................................................4
Document Page
2HTML Based MP3 Player
Introduction:
This report provides the various operation of HTML based Mp3 player and how it can
work. This is a web-based HTML application and offers an appealing interface between a
user and a server. This player can play different operations like playing Mpeg files, Mp3 files
and support most of the audio files. But all user must depend on the web browser. After
reading this report, a user, developer or any person can get detailed information about this
system
Purpose of the system:
This section of this report provides the purpose of this system. HTML based Mp3
player is mainly developed for the music university students who love music. A student can
listen to music from their computer, mobile, tablet or any device that can support web
browser (Liang and Cao. 2015). Most of the student want a music system that is simple, non-
instructive, streamlined and support most useful features like visualizer, playlist and the
recommendation list.
Design methodology use:
Agile methodology can develop the Mp3 player (Abrahamsson et al. 2017). Total six
phases are defined in agile methodology that can help to develop this system.
Planning:
Sponsors and stakeholder identification, Requirement gathering, security information
and service agreements can be done in this phase.
Analysis:
Document Page
3HTML Based MP3 Player
In this phase, a resource plan can be developed. This plan helps QA teams and
developers.
Design:
This system can successfully create by breaking down of deferent tasks. And every
task can be tested in this phase (Vijayasarathy and Butler. 2015). By using regression
automation framework, several issues can be fixed. Detecting bug and adding new feature
can be done in this phase.
Execution:
In this phase, the HTML code can be executed. Several software testing can be fix
bugs. Sometimes manual test can be done to detect bugs.
Wrapping:
In this phase, a beta version of this system can be released. A developer can gather
customer review by releasing a beta version (Altameem. 2015). New user stories are helpful
to identify the requirements.
Closure:
In this phase, the developer launches this system and offers several support option to
the users.
To develop this system, UML model such as flow chart, activity diagram, a class
diagram can be used to represent the Mp3 design.
Definitions, acronyms, and abbreviations:
Before the invention of HTML, audios can be played in the browser by using a plugin
like flash layer. HTML5 has element like <audio> that can support the audio files in the
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
4HTML Based MP3 Player
webpage. Most of the browser support this tag. HTML describes properties, DOM methods
and several event for <audio> element. This tag allows a customer to load audio, play and
pause audios.
Overview of document:
This report can provide detail information about the HTML based mp3 player. A brief
introduction is included in this report. The purpose of the HTML based mp3 player is to
explain in the purpose of the system section. The details of the methodology used in this
project are defined in this methodology used part. The definition of HTML based mp3 player
is explained in the Definitions, acronyms, and abbreviations section.
Document Page
5HTML Based MP3 Player
References:
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Altameem, E.A., 2015. Impact of Agile methodology on software development. Computer
and Information Science, 8(2), p.9.
Liang, K. and Cao, S., 2015, May. Realization of Cross-platform Video and Audio
Transmission Technology Based on HTML5. In 2015 International conference on Applied
Science and Engineering Innovation. Atlantis Press.
Vijayasarathy, L.R. and Butler, C.W., 2015. Choice of software development methodologies:
Do organizational, project, and team characteristics matter?. IEEE software, 33(5), pp.86-94.
chevron_up_icon
1 out of 6
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]