LYRICSER The Sound Mixer

Software Requirements Specification

Version 1.0

Group Id:
Supervisor Name: Shabib Aftab

Revision History
Date
(dd/mm/yyyy)
23/10/2014

Version
1.0

Description

Author

Introduction of the project

MC120402396

Table of Contents
1. Scope (of the project)

2. Functional Requirements Non Functional requirements

3. Use Case Diagram
4. Usage Scenarios

SRS Document

Purpose:
The Purpose of this document is to present the requirement specification of
software LYRICSER The Sound Mixer along with its detailed description
that software engineer plan to design; it will explain the purpose, scope &
features of the software along with its functional & non-functional
requirements. The recommended readers of the document are the developer,
stakeholders, examiners & course supervisors.

Scope of Project:
The goal of this Project is to design a Sound file mixer & player LYRICSER. It
will be created as a single tier desktop based application & user Interface.
The Application will be capable to run multiple sound files in one go &
possess ability to save sound file. During the Project the proper project
documentation will be submitted to the stakeholders.
Currently there are only limited numbers of options available with such kind
of sound mixing ability, this application can be professionally used to analyze
the impact of multiple sounds by the musicians, sound mixers etc.

Term
Active Article

Definition
The document that is tracked by the system; it is a narrative
that is planned to be posted to the public website.
Author
Person submitting an article to be reviewed. In case of
multiple authors, this term refers to the principal author,
with whom all communication is made.
Database
Collection of all the information monitored by this system.
Editor
Person who receives articles, sends articles for review, and
makes final judgments for publications.
Field
A cell within a form.
Historical Society Database The existing membership database (also HS database).
Member
A member of the Historical Society listed in the HS
database.
Reader
Anyone visiting the site to read articles.
Review
A written recommendation about the appropriateness of an
article for publication; may include suggestions for
improvement.
Reviewer
A person that examines an article and has the ability to

Software Requirements
Specification

recommend approval of the article for publication or to

request that changes be made in the article.
A document that completely describes all of the functions
of a proposed system and the constraints under which it
must operate. For example, this document.
Any person with an interest in the project who is not a
developer.
Reviewer or Author.

Stakeholder
User

Functional Requirements:
1.1User Interfaces
The software will be provided with graphical user interface very user friendly
for the person operating it. Several controls will be given:

Provided with option user can select and play 5 sound files parallel
(Software should be able to play following audio formats mp3, ra and
rm, wma).
Provided with option user can record and save mixed sound at his
desire location on hard disk.
Provided with option besides 5 sound files which can be played at the
same time, user can include any sound/his voice from microphone.
Now there are 6 parallel sounds which can be played at the same time.
(5 files selected from the hard disk and one input from the
microphone).
Provided with separate Volume Controller should be available for each
sound file.
Provided with separate Sound Graph should be available with each
volume controller for each sound file.
Provided with options for the tuning of sound effects with each volume
controller for each sound file. (User would be able to optimize the bass,
stereo, and other audio effects).
Provided with one Master Sound Controller along with sound graph and
tuning options, which would control the overall sound output from the
software. This master sound controller would also be used to play the
recorded file.

1.2Hardware Interfaces
The two main hardware devices required are a computer and an Xbox Kinect. Each
device contains several different internal and external hardware components. The
computer will need to be complete and house up to date technology. The Kinect houses

a variety of different sensors and chips. In this project we will be exploring the
functionality of the visual body tracking and audio voice recognition. Visual tracking is
dealt with using the two onboard cameras and IR projector. To implement various voice
recognition functions the Xbox Kinect encloses four microphones. The SDK allows us to
interface with these sensors using programming languages such as C++ and C#.

1.3Software Interfaces
This being a software oriented project there will be many useful software interfaces.
Many tools pertaining to our project require Windows 7, therefore this will be used as our
primary operating system. Microsoft Word will be the word processor used to document
the development of this project.
The use of the SDK will be important in testing, generating, and compiling of code.
Communications between the SDK and Xbox Kinect sensors will be done using C++ and
C# programming languages. To design the code being implemented the use of VIM
acting as a text editor is required.
Fruity loops will serve as a DAW for this project. There will be outgoing communications
with fruity loops to insure the desired musical action has been processed. MMC will
interface with fruity loops to process audio based on recorded movement and gestures.
Body motion will trigger a response to change notes. Gestures will affect the attributes to
the note/melody like increasing audio amplitude.

and non Functional Requirements:

<Write here in detail about the functional and non-functional requirements
of your system in separate headings>

Use Case Diagram(s):

<Provide here the use case diagram of your system>

Usage Scenarios:
<Provide here the usage scenarios of all use cases in table format explaining
Use Case title, Use Case Id, Actions, Description, Alternative Paths, Pre and
Post Conditions, Author, Exceptions. You are supposed to provide a usage
scenario for each of use case shown in use case diagram>

2.1.3 Hardware interfaces

The recommendation system can work on any internet connected device. These devices
should have some limit requirements to make the application run effectively. We expect
that
the processor speed and internet speed are high.
2.1.4 Software interfaces
First of all the system will work on any platform. Internet connection is a must to reach
the
system. Moreover, most of the application will be coded by Java. Java APIs of database
management tools such as Neoclipse, which is a standalone workbench application to
interact
with Neo4j. Moreover, some query languages like Cypher will be used. Some tools and
software are listed below.

Update Info
Handle Art

Ck Status

User
Send Rec
Publish Art