1. Online Jam Space

2. Operational Concept
Playing music alone is not fun!!! (except for octopuses)
Develop your talents
Share musical ideas

3. Project Components
Network (P2P)
Server
GUI
Integrator
MIDI IO

4. User Interface
Create Profile
Extraneous Confirmation!!!

5. User Interface
View Buddy List

6. User Interface
Try to Connect

7. User Interface
Rejection! Just like in real life!

8. System Architecture

9. Network Architecture
Client (P2P)

10. Network Architecture
Server

11. Team Schedule July 18 – Skeleton Code Completed
July 20 – Zero feature release
July 24 – Web server completed
July 27 – Individual Modules completed
July 28 – Unit testing begins
July 30 – Integration testing begins
August 1 – System testing begins
August 3 – Beta release
August 7 – Acceptance testing begins
August 15 – Final release

12. Team Structure and Assignments
Networking Team – Andy, Kinson
GUI/Integration Team – Aeden, Patrick
MIDI Processing Specialist - Sheng

13. Test Plan Using SFDPO and Multi-level V Model…
Acceptance Test (Covers Operation Aspect)
Musicians simulate jam session
Test GUI, reliability of connections and midi transfer in real-time
Delays must not exceed reasonable sound delay in normal rehearsal
System Test (Covers Platform, Data Aspects)
Portability test – Cross Platform?
Connection/Networking test – test cases that send MIDI data across network, convert data packets to real-time audio and check for quality of audio

14. Test Plan cont. Integration Test (Covers Function Aspect)
Test Integration Module
Test interface between modules
Test basic cross-module operations such as error handling and event handling
Unit Test (Covers Structure Aspect)
Individual test class to test each module independently
Test cases exploit potential weaknesses
Simulate input/output to each module
Test for coupling

15. Risk Assessment
Latency
Dropped Packets