alvaro/git-flight-rules
1
0
Fork 0
mirror of https://github.com/k88hudson/git-flight-rules.git synced 2025-06-17 05:21:35 -03:00
Code Issues Releases Wiki Activity

Created Analysis (markdown)

Cam Bartell
2021-07-09 16:52:19 +02:00
parent 16ce3e1c0a
commit 2cbb45b184
1 changed files with 46 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
Analysis.md Normal file

@ -0,0 +1,46 @@
During the analysis, different analysis tools form both software design and UI/UX design. To start off the analysis the group looked at how Spotify, our biggest competitor, has designed their user experience. On that basis there will be made a use case diagram to analyse how our microservices could be implemented.
# 2.1 Spotify UX Analysis
### 2.1.1 The user
![Capture](uploads/648784177f0a41d8a4c790060ec72495/Capture.PNG)
### 2.1.2 User Goals
![Capture1](uploads/e6b4265f23ec73f9f3ffc5baad575b5c/Capture1.PNG)
### 2.1.3 Information Architecture
![1](uploads/b4359148a47a37d5ea78d67e0f7dd103/1.PNG)
### 2.1.4 Main issues
![capture3](uploads/bbc7df79511b699d38556190e9f9271e/capture3.PNG)
### 2.1.5 User Journey Map
A user journey map allows you to identify and strategize for key moments. We mapped out the top three user flows with user goals and pain points at each step in order to define key opportunities to improve the overall user experience.
**2.1.5.1** Spotify User Experience Map 1: Listen to saved songs
![2](uploads/8fbe92965a9076e738203e4270d57d98/2.PNG)
**2.1.5.2** Spotify User Experience Map 2: Search for a song and save it
![3](uploads/39a8f55c2e08ae32407247a64ef34c91/3.PNG)
**2.1.5.3** Spotify User Experience Map 3: Explore Discover Weekly
![4](uploads/2b351cc757231129ca2e99c07798c457/4.PNG)
### 2.1.6 Main User Pain Points
![Capture2](uploads/60cc1d8fbcccd989f3bffe74fed6fec3/Capture2.PNG)
# 2.2 Use Case
The process of creating the use case diagram begins with a quick brainstorm based on the project kickoff slides regarding the functionality of the playlist integration and language support. With the listing of different functionalities, it is possible to draft the use case diagram. An example of this type of use case is “display hint-text when hovering over icons”, the general conclusion of the discussion is that it is expected of a web browser to display the hint-text automatically. It is the group's responsibility to translate the hint-text but not displaying it to the user.
A use case list is then created containing every use case with an designated id, name, and description.
![use_case](uploads/445232a82ca38c1e4a7564d482f82d8f/use_case.PNG)
Green = Language support requirements
Blue = Playlist requirements
## 2.3 Group analysis
Through discussion internally in the group about what functions a playlist API and language API should contain, and some inspiration from other streaming services, the group came up with a set of requirements the group saw as crucial for the implementation of playlists and the changing of languages.
These requirements are not based on a specific analysis tools but rather what features the group considers a “must”, and what requirements makes sense to include to secure a smooth and easy user experience, thus making our service able to compete with the big streaming services already on the market.
The groups that we had specific requests from were the web team, the data search team, the media player team, and the data collection team. Web needed a access to all playlists from a specific user, data searched needed a way to find playlists by name, media player needed to access a specific playlist so they could play the songs from it, and the data collection team would like a way of getting all playlists.
## 2.4 Conclusion
This analysis of Spotify’s UX can help the group understand the important and main points of focus. This includes what features the group might want to “borrow” from Spotify and what features that can be improved upon. Exactly why Spotify was chosen for this kind of analysis, is because of their very well known interface and minimalistic/modern design. These things may play a part in Spotify’s success, but which can always be improved. This analysis lays the foundation for the design-wise requirements later defined in the Requirements Specification. The use case also defines Create Playlist- and Language Settings requirements found under Functionality in Requirements Specification.