1 / 17

Digital Content Distribution and Publishing System

Digital Content Distribution and Publishing System. CS 326 Team #5. Agenda. Project Overview and Requirements Feasibility: System Architecture Use Cases Class Diagram System Mockups Project Planning. Project Overview. Digital Content Distribution and Publishing System:

Download Presentation

Digital Content Distribution and Publishing System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Digital Content Distribution and Publishing System CS 326 Team #5

  2. Agenda • Project Overview and Requirements • Feasibility: • System Architecture • Use Cases • Class Diagram • System Mockups • Project Planning

  3. Project Overview • Digital Content Distribution and Publishing System: • Centralized, controlled platform for file transfers. • Promotes sponsored content to users. • Collects and stores information about file transfers.

  4. Existing Services • Valve’s Steam – Content Delivery System (CDS)‏ • GameTap – Online Video Game Service • GameShadow – Auxiliary game file distribution • EA Link – CDS (Games)‏ • Stardock Central – Software delivery system • Direct2Drive – CDS (Games)‏ • NetFlix – Online movie watching • Itunes – CDS (Music, Video)‏

  5. Criticisms • Existing services usually exhibit one or more of the following characteristics: • Platform specific • Content-type specific • Closed-source and/or proprietary • Closed-community

  6. Project Goals • The DCDaPS aims to: • Be Cross Platform • Be Content-type Independent • Allow Open Communities • Be Open Source

  7. Requirements • Functional: • File uploads & downloads in multiple formats. • Content management at all user levels. • In-house navigation of content. • File statistics collection & reporting. • Administrative portal.

  8. Requirements • Non-Functional: • Cross Platform • Intuitive and uniform while maintaining a 'native feel' • Self-updating • Efficient file transfer and navigation • Written in C++

  9. System Architecture • WxWidgets – cross platform library for GUI's • Cmake – compiling utility which supports simultaneous program builds • LibCURL – cross platform library for HTTP/FTP transfers • LibTorrent – cross platform library for Torrent transfers

  10. Use Case Diagram

  11. Use Case – Basic User

  12. Activity Diagram – Remove File

  13. Class Diagram

  14. Interface Mockups (Vista)‏

  15. Interface Mockups (OS X)‏

  16. Project Schedule (Gantt Chart)‏

  17. Questions? Comments? CS 326 Team #5

More Related