GR1 - Task analysis
User analysis
User Classes:
1. Party Goer
2. DJ
3. Music Enthusiasts
Personas:
1. Stacey is a female college student 18 to 22 years old. She likes to go out to parties with her friends on weekends. She likes dancing to loud music, especially songs by Keisha.
2. John is professional DJ who works weekly gigs at a downtown club. He follows music blogs to keep up with music trends and then downloads music with Amazon MP3.
3. David is a college student majoring in Electrical Engineering. He has never spent any money puchasing music. He listens to a lot of music on youtube but would prefer to have them on his iTunes so that he can listen to his playlists while jogging.
4. Tim is an audiophile. He owns a pair of headphones worth $1000 that provide hi fidelity. Unfortunately he has a rare illness in which his eyes are extra sensitive to light.
Task analysis
1. Listen to songs of various artists or genres
2. Keep music for future listening
3. Providing recommendations on songs/artists/albums for a party
1 Comment
Vijay Umapathy
User Analysis: First 3 personas make sense - is there a reason that Tim the audiophile has a vision condition? These should be derived from interviews with real users, but there is no evidence here that shows you talked to potential users to create these traits. Also, user description should have some notion of roles / traits that define patterns of use in your application.
Task Analysis: No subtasks or characteristics listed for subtasks - missing the level of depth required of the assignment.
Domain Analysis: Looks good, but possibly missing dependencies between user and playlist, or user and event