Question: Create a System Requirements Document for a Radio Station Play List.

Use this for a sample: http://1000projects.org/system-requirements-document-for-invoice-creation-for-company.html

System Requirements Document Description

1. Problem

This section is a prose description of the problem that is to be solved by the system including background and context for the problem and a clear statement of the main problem(s) to overcome.

2. Objectives

This section is a list of objects that the solution is required to achieve.

3. Existing system

This section describes how the existing system or process works today. This could include proses and/or swim-lane flowchart.

4. Functional Requirements

This section is a list of functions the system is required to meet. Each of these functions will be support by a Use Case in a later section.

5. Non-Functional Requirement

This section is a list of non-functional requirements the system is required to meet. This would include: usability, reliability, performance, supportability, interface, training, operations, and legal.

6. Target Environment

This section is describes the required system operating environment if there is one.

7. Use Cases

This section describes the Use Cases that support the functional requirements. Each Use Case includes: name, initiating actor, participating actors, diagram, list and details of each scenarios.

8. Glossary

This section is a list of terms used in the document with their definition. This would include actors and data elements.