General Planning Implementation Tasks of Managing Play List in Chinook

[jthompsonnait]

This task list will be completed once the implementation plan has been outlined. This area is where one creates the task list that is associated with the milestone.

• Data Model
• [x] TrackSelection
• [ ] task a.2
• [ ] #3
• Task B
• [ ] task b.1
• Task C
• [ ] task c.1
• [ ] task c.2

[jthompsonnait]

UI Experience

This comment outlines the actions that can happen on the forms. Actions are in response to the user interacting with the form, pressing buttons or controls.

PRG Post Redirect Get

• Using routing parameters {searchtype?}/{searchvalue?}/{playlistname?}
• PRG clicking the Clear empties bound properties and routing parameters (page only)
• PRG clicking the Fetch will retrieve the existing playlist for the specified playlist name {playlistname?}
• PRG Clicking the Fetch Artist or Fetch Album track will retrieve the tracks for the indicated search and display in a table {searchtype?}/{searchvalue?}

• Post/PRG clicking the Add [+] on the track will attempt to add the track to the playlist <<>>
• rule: unique track on the playlist
• rule: playlist name needs to be unique for user
• rule: appended track to playlist
• Post/PRG clicking the Remove Track will attempt to remove 1 or more tracks from the playlist <<<???>>>
• rule: re-sequence the playlist track number leaving no gaps.

• Post/PRG MoveTrack

  Managing the playlist.

[jthompsonnait]

Data Models

The data models are the C# classes that will be coded in the folder (ViewModels) that holds the data classes in our solution. These classes represent the query class models and the command class models (CQRS).

---

Query Models

Artist and Album Track Fetch

public class TrackSelection
{
    public int TrackID {get; set;}
    public string SongName {get; set;}
    public string AlbumTitle {get; set;}
    public string ArtistName {get; set;}
    public int Milliseconds {get; set;}
    public decimal Price {get; set'}
}

Current Playlist Tracks

public class PlayListTrackInfo
{
   public int PlayListID {get; set;}
   public int TrackID {get; set;}
   public int TrackNumber {get; set;}
   public string SongName {get; set;}
   public int Milliseconds {get; set;}
}

---

Command Models

Add Tracks

No model class, individual parameters

Username and PlaylistName and TrackID

No model class, individual parameters

PlaylistID and List (TrackIDs)

Move Tracks (re-sequence playlist)

public class PlaylistTrackMove
{
   public int PlayListTrackID {get; set;}
   public int TrackNumber {get; set;}
}

[jthompsonnait]

Business Processing Requirements

This comment will describe the various methods that will be used for Command (CQRS) that alter the database. Queries are read-only and require on average no complex processing. However, commands require business rules validations and manipulations of one or many tables and/records. Therefore, the processing of commands should be outlined.

Include the method signature and a bullet list of processes

Add Track

void PlaylistTrack_AddTrack(string playlistName, string username, int trackid)

• check track exists (trackid)

  • [NO] add an exception

• check if playlist exist (username, playlistName)

  • [YES]
    • check track is already on the playlist
      • [YES]
        • add an exception
      • [NO]
        • generate the next track number

  • [NO]

    • create a new playlist record

    • set track number to 1

    • add track to playlist tracks (append)

• check for any errors

  • [YES]
    • throw list of all collected exceptions
    • [NO]
      • save all changes to database.