1 / 17

Antoine GUEDON Benjamin PAPILLAULT Kévin BAUDRY Nicolas FLORES

WEB P RTAL. Multimedia quality measurement. Antoine GUEDON Benjamin PAPILLAULT Kévin BAUDRY Nicolas FLORES. Contents. Project Objectives and Overview Project Schedule System Architecture Database Design Tests and Validations Conclusion. Overview Schedule Architecture DB Design

bernardj
Télécharger la présentation

Antoine GUEDON Benjamin PAPILLAULT Kévin BAUDRY Nicolas FLORES

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. WEB P RTAL Multimedia quality measurement Antoine GUEDON Benjamin PAPILLAULT Kévin BAUDRY Nicolas FLORES Software Engineering – Web Project– English M1 IT

  2. Contents Project Objectives and Overview Project Schedule System Architecture Database Design Tests and Validations Conclusion Software Engineering – Web Project– English M1 IT

  3. Overview • Schedule • Architecture • DB Design • Tests • Conclusion Project Objectives • Objectives: • To design a WEB PORTAL dedicated to Multimedia quality measurement • Overview of results as a benchmark • Registration and user login • Image upload by users • Calculation of image quality for sent images Software Engineering – Web Project– English M1 IT

  4. Overview • Schedule • Architecture • DB Design • Tests • Conclusion Overview - Context Software Engineering – Web Project– English M1 IT

  5. Overview • Schedule • Architecture • DB Design • Tests • Conclusion Image quality – How ? • Subjective method - Psychophysical tests • Human evaluators (> 15) • Experiment room - Standard conditions (lighting, distance, resolution ...) • Produces results MOSs • Very expensive (time, money) • Objective method - Quality metrics • List of metrics literature (> 100) • Implementations (> 25) • Produces results MOSp Software Engineering – Web Project– English M1 IT

  6. Overview • Schedule • Architecture • DB Design • Tests • Conclusion Expected Result - Benchmark Mosp Metric Performance measurement Only one metric Software Engineering – Web Project– English M1 IT

  7. Overview • Schedule • Architecture • DB Design • Tests • Conclusion Online quality measurement Software Engineering – Web Project– English M1 IT

  8. Overview • Schedule • Architecture • DB Design • Tests • Conclusion Schedule • Design of Architecture & Database • Set up of three virtual servers (Web server, Windows, Linux) • Development cycles: • Initialisation • Implementation • Optimisation • Final Validation Software Engineering – Web Project– English M1 IT

  9. Architecture • Overview • Schedule • Architecture • DB Design • Tests • Conclusion Software Engineering – Web Project– English M1 IT

  10. Overview • Schedule • Architecture • DB Design • Tests • Conclusion Detailed architecture Software Engineering – Web Project– English M1 IT

  11. Overview • Schedule • Architecture • DB Design • Tests • Conclusion Database Design 2 Databases : general & user Software Engineering – Web Project– English M1 IT

  12. Overview • Schedule • Architecture • DB Design • Tests • Conclusion User Database Software Engineering – Web Project– English M1 IT

  13. Overview • Schedule • Architecture • DB Design • Tests • Conclusion Fill General Database • Already Data stored in XML files • Migration done through PHP Scripts • Insert data of the Images, ExperimentalEvaluation parts and MOSs results • Insert data of the Metrics parts and MOSp results • Insert data of PerformanceTool and performance scores between metrics and image collections Software Engineering – Web Project– English M1 IT

  14. Overview • Schedule • Architecture • DB Design • Tests • Conclusion Tests • PHP scripts • Unit tests • Integration tests • Functional tests • Python scripts • Unit tests • Integration tests • Functional tests Software Engineering – Web Project– English M1 IT

  15. Overview • Schedule • Architecture • DB Design • Tests • Conclusion Conclusion • User requirements are met • Functionalities completed : • Overview of results as a benchmark • Registration and user login • Image upload by users • Calculation of image quality for sent images Software Engineering – Web Project– English M1 IT

  16. Overview • Schedule • Architecture • DB Design • Tests • Conclusion What we have learned • Work on a distributed architecture • Formed a group dynamic • Work with subcontractor • Provide an additonal difficulty • Dealing with human problems • One member left the team Software Engineering – Web Project– English M1 IT

  17. Overview • Schedule • Architecture • DB Design • Tests • Conclusion Future work • Extend the application to other Multimedia • Movies • Sounds • ... • Implementation of the application in other online systems as Google Picasa Software Engineering – Web Project– English M1 IT

More Related