Dot Net FM

1. DotNetFM Chris Zamanillo Ana Rodriguez Allen Lee Peter Singh Allen Vega Robert Lyn

2. Problem Statement • Problems with sharing music • Large disk space requirements • Slow downloads • Complicated software • Our solution • Small amount of disk space • Listen while you download • Easy to use interface

3. Use Case Diagram

4. Class Diagram

5. Use Cases • Customize Interface • Chris Zamanillo • Manage Playlist Content • Ana Rodriguez • Listen to Playlist • Allen Lee • Broadcast Radio • Peter Singh • Manage Station Lists • Allen Vega • Listen to Broadcast • Robert Lyn

6. Customize User Interface Scenario Masoud wants to change the look of his DotNetFM player. He presses the Skins button and is presented with alternate user interfaces. He selects the “PearTunes” theme and presses the Apply button. However, now he decides that he wants to make his own skin for the player. Once Masoud designs a custom user interface using the image template provided, he loads his newly made custom user interface, called “WinMP”, into DotNetFM by pressing the Skins button again followed by the Custom Skin button. The player now looks the way Masoud designed it to be.

7. Customize User Interface Use Case Use Case Name:CustomizeInterface Participating Actors: User Entry Condition: The User chooses to activate the Skins function. Flow of Events: 1. User presses the Skins button. 2. DotNetFM responds by presenting the user with a list of available skins. 3. User selects a skin from the list and chooses to apply changes. 4. DotNetFM responds by changing the user interface to the one the user selected. Alternative Flow of Events: 1. User presses the Skins button. 2. DotNetFM responds by presenting the user with a list of available skins. 3. User selects Add Skin and selects the file where the skin image information is stored. 4. DotNetFM responds by making the new skin available from the list of skins. Exit Condition: The user has changes the user interface, adds a new one to the list, or decides to cancel the operation. Exceptions: 1. Image file where user interface is stored is corrupted. 2. Components are misplaced because user did not follow the template. Special Requirements: 1. User must follow template provided when designing a new user interface.

8. Customize User Interface Sequence Diagram

9. Manage Playlist Content Scenario John wants to create a playlist. He launches the DotNetFM program. He creates a playlist by clicking on the Create A Playlist button. He then enters the playlist name, “Easy Listening”, and then clicks on the OK button. “Easy Listening” is now displayed in the list of playlists.

10. Manage Playlist Content Use Case Use Case Name:ManagePlaylistContent Participating Actors: User Entry Condition: The User chooses to activate the ManagePlaylist function. Flow of Events: 1. User selects a playlist. 2. User selects one of the options, add or remove content. 3. DotNetFM responds by presenting user with a confirmation message. 4. User confirms the selection. Exit Condition: Content is added or removed from the playlist.  Modifications to the play list have taken effect. Exceptions: 1. Content could not be added. 2. Content could not be removed. Special Requirements: None

11. Manage Playlist Content Sequence Diagram

12. Listen To Playlist Scenario Bob wants to listen to music. He launches the DotNetFM program. He creates a playlist from his favorite songs by clicking on the Playlists button and choosing the Create A Playlist button. He then selects the Playlists button and selects track number 3. He selects the Repeat button and presses play. The system plays the third track continuously.

13. Listen To Playlist Use Case Use Case Name:ListenToPlaylist Participating Actors: Listener Entry Condition: The User chooses to activate the Playlists button. Flow of Events: 1. User presses the Playlists button. 2. DotNetFM responds by presenting the user with a selection of playlists. 3. User selects a playlist from the display of selections. 4. DotNetFM responds by displaying the songs contained in the playlist. 5. User selects play options, such as shuffle or repeat, selects a track, and presses the play button. 6. DotNetFM responds by displaying the name of the song, the elapsed time, the total time, and begins playing audio. Exit Condition: The user changes to broadcast mode or closes the program. Exceptions: 1. Audio file is corrupted. 2. Playlist is not populated. 3. User is already connected to a DotNetFM Server Special Requirements: 1. User must have audio files on their system. 2. User must not be connected to DotNetFM Server. 3. User must have created a playlist.

14. Listen To Playlist Sequence Diagram

15. Broadcast Radio Scenario Bob wants to share his music with his brother Bill. Bob launches the DotNetFM program and begins playing a song. He then presses the On Air button and DotNetFM begins streaming the currently playing song. Bill is now able to connect to Bob’s station.

16. Broadcast Radio Use Case Use Case Name:BroadcastRadio Participating Actors: Disc Jockey (DJ) Entry Condition: The DotNetFM must have an active connection to the internet. Flow of Events: 1. DotNetFM broadcasting is currently deactivated. 2. DJ presses the “On Air” button on the DotNetFM application. 3. DotNetFM begins broadcasting. 4. The currently playing song. 5. “Dead air” if no song is playing. Alternative Flow of Events: 1. DotNetFM broadcasting is currently activated. 2. DJ presses the “On Air” button on the DotNetFM application. 3. DotNetFM stops broadcasting. Exit Condition: 1. DJ has activated or deactivated the broadcast. 2. DotNetFM responds by indicating the status of the broadcast. Exceptions: 1. Cannot Broadcast. Special Requirements: None

17. Broadcast Radio Sequence Diagram

18. Manage Station Lists Scenario John wants to create a list of his favorite stations for easy access. He launches the DotNetFM program and selects the Manage Station Lists button. He enters “My Rock’NRoll station list” in the textbox provided and selects the Create Favorite List button. My Rock’NRoll station list now appears as one of his station lists.

19. Manage Station Lists Use Case Name: ManageStationLists Participating Actor: User Entry Condition: User has started the DotNetFM program. Event Flow: 1. User selects “Manage Station Lists” option. 2. System responds with an option window containing all favorite stations lists. 3. User enters the name of a favorite station list into the textbox or user selects a favorite stations list. 4. User presses either create or delete button. 5. System responds by presenting user with a confirmation message. 6. User confirms the selection by pressing yes. Exit Condition: User has deleted, or created a station list. Exceptions: 1. User enters invalid characters in textbox when adding. 2. File for storing station lists is corrupted or missing. Special Requirements: None

20. Manage Station Lists Sequence Diagram

21. Listen To Broadcast Scenario Jane wants to listen to her friend’s music. She launches the DotNetFM program. She then clicks on the Stations button. She selects her friend’s station called “Billy’s Station” from the displayed list, and then clicks the Play button. The system connects to the stream and starts playing the music.

22. Listen To Broadcast Use Case Use Case Name:ListenToBroadcast Participating Actors: Listener Entry Conditions: 1. A known DJ is currently broadcasting music. 2. The DJ is connected to the internet. 3. The Listener is connected the internet. Flow of Events: 1. Listener presses the Stations button. 2. DotNetFM responds by presenting the user with a Stations list. 3. Listener selects a station of their choice from the list. 4. DotNetFM responds by highlighting the chosen station. 5. Listener then selects Play. 6. DotNetFM responds by displaying the message Connected Successfully, then by playing the stream. Exit Conditions: 1. DotNetFM is connected to a broadcast. 2. The DJ’s music is playing through the Listener’s speakers. Exceptions: 1. DJ is not set to broadcast. Special Requirements: None

23. Listen To Broadcast Sequence Diagram