A Software Requirements Specification (SRS) – a requirements specification for a software system – is a complete description of the behaviour of a system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. In addition to use cases, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements, which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).
In KA Plus project, this document descripts all requirements from user and project team about KA Plus application. It contains all parts of a Software Requirement Specification (SRS) to make project team and involved people verify, understand this project clearly so that project team can done this project correctly as defined requirement.
2. Scope This document will include User Requirement Specification, System Requirement Specification and Software System Attribute to prepare for next step in project plan. Because this document is very important for project, it must consist of the following features: correct, unambiguous, modifiable, verifiable, consistent, complete, traceable and ranked.
II. Software Requirements Specification
1. User Requirements
These requirements came from user who uses Android mobile phone when using Karaoke service. It is main requirements because they are as end user. There are all requirements they need:
Users can view all karaoke songs that available in karaoke box or their computer
Users can know some basic information about songs to know that this song is the song they want (author, singer, lyric. . .)
Users can control when media was being played (play, pause, next, previous ... )
Users can search song from karaoke media database quickly and easily
These requirements came from owner or employee in karaoke box and user using this application at home. Users in this case seem like Admin-administrator. Almost requirements support user requirement (customers).
Admin can know all karaoke songs in their system.
Admin can view all karaoke songs including available information (title, duration , artist, gene, album, lyric )
Admin can manage karaoke songs as database
Admin can edit song’s information
Admin can rate song by the number of singing times
Admin can create all-playlist song for user make database to search
Admin can create suggest playlist for user (customer)