ODC for Digital Music Software Development Based on C++

Client Overview
Our client is a global company providing leading technology, software products and platforms designed to enable the secure delivery of digital music and multimedia content to wireless customers. The company is focused on providing wireless operators and handset manufacturers' with world-class solutions to power advanced digital music and entertainment content services. It has set up partnerships with many enterprises and organizations, such as Warner Music Group and SONY BMG MUSIC ENTERTAINMENT

Project Overview
The project is an integrated solution to ensure that customers can receive and enjoy their music whenever and wherever the desire. Our work is to develop the application named AMPlayer, providing consumers with the highest-quality music experience. AMPlayers play the digital music supported by a multi media provider. While protecting its copyright, consumer's also benefit from DRM (Digital Right Management) technology. AMPlayer can also connect to the Web Store enabling users to search for music information in which they are interested, then allowing the user to subscribe, buy and preview. Furthermore, users can synchronize digital music players or other mobile devices with their handsets.

Solution

Development Process

1. Get Issues:
A developer will choose issues as his assignment from the issue list with management tool and carefully read the detail of it.

2. Design:
Per understanding of the issue, the developer should complete some detail level design.
Design includes the following: Description of design, Class Diagram, Sequence Diagram, and Protocol to talk to the server.

3. Design review:
Every feature's detail design must be reviewed.
A review team includes the designer, the developers of the same module and affected modules, architecture owner, PM. The review will examine if the design fully satisfies the requirements, following the architecture style. 
An accurate effort estimation based on the design should be one output.

4. Coding:
A developer needs to convert the design into code. 
It is required that the developer should apply the predefined coding style, and follow the development rules. During the coding, all concerned parties continue enriching the design document to include more detailed information, such as Customize Windows Messages that would be sent to UI plug-ins, etc.

5. Code review:
Code will be randomly selected and will examine each other.

 System test and Bug fix
After the feature complete milestone, executable software plus features and use case documents will be delivered to the QA team. The QA team will execute several rounds of system tests, and report any bugs to the development team. A bug will be triaged and assigned to a developer. The developer should find the cause of the bug, fix it, run a smoke test, check in to new version, and set the issue status as RESOVLED. Only QA can close the bug.

 Sample issue: Activate mechanism
For user customizing personal services and performing safely on high-level, the activate mechanism will be in the solution.
At this time, there are two approaches to activate AMPlayer, with PC Portal (Web Store) and phone server (music provider).

1. Send the activation SMS to the PC portal, and the PC portal will forward the SMS to phone server, note that PC portal shall auto add the phone number and device ID in the HTTP header. This is what we did in server development. But since the connection between AMPlayer and PC portal is sessionless, PC portal doesn't know which AMPlayer is talking to now. This approach is kind of impossible.

2. The other approach is for the update client DRM agent to send the phone number and device ID in the HTTP activation request. This is workable, but with a little more core changes.

We will adopt the later approach for AMPlayer.
 
Points of the project

Industry:                   Digital music, DRM tech, synchronize
Development Tools: Microsoft Visual Studio
Language:               C++
Operating System:   Windows series
Management Tools: Subversion, Jira, Confluence, Subversion