The project that our team is proposing is that of a mobile music application. This application will be a front end application that uses already in place internet services. The project involves. The mobile will contain free listening for radio and a paid listening subscription for user selected content. The application will be multiplatform based and be useable on iOS, Android, Windows 8.x. The application will also be integrated with social media sites such as Facebook and Google +, to name a few. There will be 6 phases for this project to include the following;

1. Pilot Application

2. Radio module

3. Subscription module

4. Social Media Module

5. Project Close

Development Methodology

The development methodology will be that of Iterative/Incremental that allows for breaking up the project into small digestible chunks and is easy to understand. This method is similar to making small waterfalls out of each iteration of the software. This method allows for quick testing and customer feedback. This is best suited for small teams that support parallel coding and testing which will be used in this project. The ability to release the product in 90 to 120 days below budget is planned.

Phase 2 Software Production

Requirements

The requirements gathering sessions will be completed by formal meetings, chat and email interaction. This will be done due to the various locations of the stakeholders and team members in this project. The original project inception and the requirements for the agreed upon project were gathered by email correspondence between the team members. The group leaded compiled a list of the initial requirements and this was discussed during a live chat meeting. The requirements are as follows;

· Initial pilot app (includes account creation)

· Player Module to include equalizer module ( Includes 5 bans of equalization)

· Radio module (search for music interest)

· Subscription module (create playlists, add music to library)

· Social media module

· Project close

· Application will operate across multiple platforms (Supports iOS, Android, Windows 8.x)

· Paid subscription for direct listening

· Free listening for radio playlists

· App will use backend services already exist from current website

· App will integrate into existing backend services

The first 5 requirements are functional requirements and the remaining 7 requirements are non functional requirements. The functional requirements are listed in the priority in which they will be developed.

1. Initial Pilot Application

2. Player/Radio Module

3. Subscription Module

4. Media Module

The requirements are arranged by level of importance to the project. The account must be created by the user before a download of the player can take place. The player module will allow the music to be streamed to the mobile device. The Radio module will allow free access to radio services offered on the internet and other mobile devices. The subscription module will allow the user to create playlists, pick songs and add music to a personal library on the cloud. The media module that is the last to be developed will allow integration of the player into personal social media sites

Design

The architecture of this design will be built from 6 independent modules. The modules will interface to each other to perform the desired results for the user. The main screen will include account creation areas for user input. Once the account is created the device will allow remember the user account information for the device that it is installed on. The Player screen will then show the player controls at the bottom as well as touch screen buttons to allow the user to choose between radio, free listening playlists and the paid subscription module. The subscription module will open an addition screen to allow the creation of playlists and search functions to locate and play music on demand. The media module will allow the players function to be used on social media sites such as Facebook. This will allow integration of the module onto the personal FB site of the user.

Application Architecture

Music Player Main Screen

Class Diagram

Use Case Diagram

Phase 3 Rapid Development (TBD)

Phase 4 Project Scheduling (TBD)

Phase 5 Project Risks (TBD)

References

(Jeffery Sanford, 2014). Live Chat 1,

Retrieved from: http://ctuadobeconnect.careeredonline.com/p72if5shtwi/?launcher=false&fcsContent=true&pbMode=normal

(Roger Pressman, 2012). Software_Engineering_A_Practitioner's_Approach_7th_Edition

Retrieved from: http://wow.coursesmart.com/007767412X/?CSTenantKey=coloradotech&spid=

(Jeffery Sanford, 2014). Live Chat 2,

Retrieved from: http://ctuadobeconnect.careeredonline.com/p72if5shtwi/?launcher=false&fcsContent=true&pbMode=normal

Initial Application Module

1. Account Creator

2. Login

3. Enter Splash

Player/Radio Module

1. Play

2. Pause

3. Rewind

4. Fast Forward

5. Equalizer

6. Search Radio

Subscription Module

1.Search Music and Play

2. Create Playlists

Social Media Module

1. FaceBook

2. Google+

3. Twitter

Backend Cloud Service

Pilot Application Core

Twitter

Google+

FaceBook

Media

Radio+

Account

Radio (Base)

User