Pocket Karaoke Integration PLANS

1. Pocket KaraokeIntegration PLANS Daniel Kirschner David Pinho

2. Project Overview • Create an application for the iPhone that will play Karaoke. • Application will remotely connect to server for song selection. • Songs will be downloaded and played in the application. • Potential to have outside monitor/speakers broadcast song.

3. Schedule • Apache Server up 1 week Complete • SQLite database 1 week Complete • Playing MP3+G’s 2 weeks Complete • Searching in Database 2 weeks Complete • UI 2 weeks Semi-Com • Integration into iPhone3 weeks • Playback MIC channel 1 week • File streaming 1 week

4. Entry Criteria • Modules being integrated completed and tested • SQLite database • Browsing • Searching • Populating • Apache Server • Accessing • Downloading • Playing of karaoke files • Ability to watch, listen and control the files.

5. Elements to be Integrated • SQLite DB into the iPhone UI • The database must work with the iPhone itself • The UI will have to change accordingly • Apache Server into the iPhone UI • The iPhone UI will need a function to download the files • Apache Server into the karaoke player • The player must be able to play files taken from server • Some other things are already integrated.

6. Integration Strategy • We will be using the Top-down approach. • With the time we are given its more important to integrate the core things first like being able to use the SQLite database on the iPhoneinstead of taking the bottom up approach. • Once the core components are done it will be easier to test the branches given our scenario.

7. Sequence of Functions • The SQLite DB working on the iPhone infrastructure • The SQLite DB functions working through iPhone UI. • The UI functions to connect and download from Apache Server. • Function to play the file taken from Apache Server.

8. Individual Test Description • The SQLite DB working on the iPhone infrastructure • Accessing all the data on the DB through the iPhone must be completely tested as it was on a PC • The SQLite DB functions working through iPhone UI. • The browse, search and get apache link functions must be tested and working as they were on a PC • The UI functions to connect and take files from Server. • The actual function themselves must be tested and the speed of the download must also be tested using all connection methods • Function to play the file taken from Apache Server. • This function should be tested just as if it was a file I put on the iPhoneitself with out downloading it from the apache server

9. Final Functional Tests • Load the application up • Find a random song on the database, by both browsing to it and searching for it. • Get the link from the database • Download it from the apache server • Play it using the karaoke player. • Repeat process with multiple simultaneous clients

10. Rework/Retest Procedures • For every change we make we will log the change and test all the functions that pertain to that change. The actual retesting of all the rest of the modules will be done with periodical regression testing.

11. Exit Criteria • All functions listed on project spec are implemented and each is working just as well as it was independently. • Each function must work at satisfactory speed with all connection speeds advertised in planning. • All functions work at a satisfactory level when many clients access DB and server at once.

12. Responsibilities • For the rest of the time left David Pinho and Daniel Kirschner will be working together to integrate all things into the iPhone. • David will be focusing more on testing the integration and updating the UI with the new integrated content. While Daniel will be focusing on the actual integration of the database and Apache server.

13. Remaining Schedule

14. Questions and Comments?