Designing of media player

7,138 views

Published on

0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
7,138
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
475
Comments
0
Likes
5
Embeds 0
No embeds

No notes for slide

Designing of media player

  1. 1. Presented ByGroup-4: 1 .Nur Islam (110810017) 2. AshisMondal (110810014) 3. Rahmotulla Sk (110810001) 4. Sumanta Haldar (110810013)
  2. 2. INTRODUCTION  OBJECTIVE : our objective of this project is to design and implement user friendly , platform independent media player which can play most of the audio files like .mp3,.wav etc and some video files in addition to view images .
  3. 3.  Media player is a term typically used to describe computer software for playing back multimedia files. While many media players can play both audio and video, others focus only on one media type or the other. Such players are known as either audio players or video players and often have a user interface tailored for the specific media type.  Major Function This media player will provide the user better audio and video quality and it will be easy to handle i.e more user-friendly also it will be include some interesting feature. It is completely an implementation of interfaces ,pakages, classes and methods inbuild in JAVA media framework for data reading, processing and controlling.
  4. 4. We use AWT library for presenting to the users. The major functions we will implement in our media player are: 1.JMF : Java Media Framework API is an application programming interface (API) for incorporating timebased media into java applications and applets.We use some class of JMF in our project –Player,Manager
  5. 5. 2.GUI :We will explore some Graphical User Interface API’s swing classes and AWT.TheMediaPlayerFrame we define the class and extend the javax.swing.JFrameclass, event handling.  Performance Issues The application will be user-friendly, portable, platform independent(Here we are using windows7), fast. The main purpose of this player to provide simple realiable .
  6. 6. Major functions The functions which we are used  Create Player() -to creating media player.  OpenFile()  Start()  getControlPanelComponent() -to control audio,video  Close()
  7. 7. PROJECT SCHEDULING  It is the important project planning activity ->Identify all the tasks -> Break down the large task into small activity ->Establish the most likely estimates for the time durations necessary to complet the activities ->allocate resources to activities ->determine the critical path
  8. 8.  WBS (WORK BREAKDOWN STRUCTURE)  Level One: Organizational Level 1. “MEDIAPLAYER” 120 days  Level Two: Higher Level Functionalities 1.1 Requirement & Specifications. 10 days 1.2 Designing. 30 days 1.3 Coding.(it will be done in parallel with Designing) 60 days 1.4 URL connections. 10 days 1.5 Integration & Testing. 10 days 1.6 Documentations.(it will be done in parallel with all above jobs) 60 days
  9. 9.  Level Three: Functional Level 1.1 Requirement & Specifications.  1.1.1 Client Requirements. 2 days 1.1.2 Developer Requirements. 2 days 1.1.3 Requirement Analysis . 3 days 1.1.4 Proposal Discussion . 1 days 1.1.5 Proposal Finalization . 2 days __________ 10 days  1.2 Designing. 1.2.1 Design of GUI frame. 5 days 1.2.2 Design of GUI functions. 5 days 1.2.3 Video display function. 10 days 1.2.4 Additional feature Design. 10 days
  10. 10.  1.3 Coding 1.3.1 GUI frame coding. 10 days 1.3.2 Coding of GUI functions . 10 days 1.3.3 Coding of Video display functions . 20 days 1.3.4 Coding of additional features. 20 days _____________ 60 days  1.4 URL connections 1.4.1 Path setting 1.4.2fetching file from path 5 days 5 days
  11. 11.  1.5 Integration & Testing. 1.5.1 Integration of function 1.5.2 Testing of software 5 days 5 days ___________ 10 days  1.6 Documentations. It will be done throughout whole project duration. Estimated time for it is 60 days. TOTAL TIME REQUIRED is 120 DAYS
  12. 12. WBSHIERARCHY: MEDIA PLAYER RECUIRMENT AND SPECIFICATION DESIGN FRAME CODING FUNCTI ONS URL CONNECTION ADDITIO NAL FUNCTIO NS INTEGRATING AND TESTING TESTING URL DOCUME NTATION
  13. 13. TASK NETWORK REPRESENTATION FRAME DESIGN 10 DAYS RECUIRMENT AND SPECIFICATION 10 DAYS FRAME CODING 20 DAYS URL 10 DAYS INTEGRATION 5 DAYS FUNCTIONS 10 DAYS ADDITIONAL FUNCTIONS 10 DAYS DOCUMENTATION 60 DAYS FUNCTIONS CODING 20 DAYS ADDITIONAL FUNCTIONS CODING 20 DAYS TESTING 05 DAYS FINISH
  14. 14. GANTT CHARTS
  15. 15. FUNCTIONAL REQUIREMENT:  R1.GRAPHICAL INTERFACE: R1.1 MENUBAR: DESCRIPTION: The menu bar will be displayed at the upper position of the media player where all the option regarding the software and the files will be given. For a particular task the user have to choose the proper option only. INPUT: User need to click the option button as displayed in the software. OUTPUT: The specific task will be performed. R1.2 STATUS BAR DESCRIPTION: The status bar use for displaying the duration of the running file. User can also seek in different position of the file during run time through this status bar. INPUT: The mouse click on any position on the status bar. OUTPUT: the running file will be seek to that time duration.
  16. 16. R1.3 INTERMEDIATE FRAME DESCRIPTION: This is required for displaying the fame of the video file and the picture contain by the audio file. INPUT: The audio or video file will be the input. OUTPUT: The content of that input file. R1.4 VOLUME CONTROL DESCRIPTION: It gives the facility to the user to control the volume of the video or audio file when it running.  R2 PROTABILITY: R2.1 MEMORY REQUIREMENT: DESCRIPTION: Memory required for this software is very low. The code of this software is made by java and it very logical. OUTPUT: very flexible to use.
  17. 17. R2.2 DIFFERENT MODE DESCRIPTION: This software is able to work in three different mode. 1>Video 2>Audio 3>Photo viewer; According to the file type it will automatically run in its suitable mode. INPUT: The file name is the input. OUTPUT: It will show the Content of the supportive file. Otherwise an error message will be shown to the user.
  18. 18.  R3-FACILITIES : R3.1 - PLAYLIST : INPUT : Any media file. OUTPUT : Next time when users will play the same media file , it is not require them to select the file from the specific folder. Because this software is given the facility of playlist of the earlier played media file. R3.2 – RESOLUTION CONTROL : INPUT : Any media file. OUTPUT : The users can change the colour , contrast & brightness when require. R3.3 – FAST FORWARD : INPUT : Any media file. OUTPUT : They can forward the media file with respect to the time when they want.
  19. 19. R3.4 – SMART STYLE : DESCRIPTION: The color interface of this software is not static. There are 7 different types of interface color are given . The users can change the interface color of their own choice. R3.5 – DEDICATED HELP OPTION : DESCRIPTION : All function of the keys is described in the help option. So if a user face some problem due to use of this software , they can visit in help option and it will provide a reliable service. R3.6 – UPDATE LINK : DESCRIPTION: Like other famous software , it will give a link for update of this software for better experience.
  20. 20.  R.4: ADD MULTIPLE FILES R.4.1: ADD FILES BY DRAG AND DROP User can directly add those files which he wants to play by drag and drop with the mouse. User can only add some limited file type like .mp3,.wav INPUT: Drag & Drop of the file . OUTPUT: Display the content of the file. R.4.2: ADD FILES BY BROWSING DESCRIPTION: User will input the file by browsing the different directory or path of the file where it is located. The software automatically fetch the file from the given path.
  21. 21.  R.5: FEASIBLE TO ACCESS R.5.1: Open File DESCRIPTION: user will select the media file which he/she want to play by opening their computer directory. INPUT: user will add one or more file by mouse as interface with the media player. OUTPUT : The selected file will be add to the player library and shows the chosen file into the list. R.5.2: Start Option DESCRIPTION: The selected or the added media files will be played one by one after the user press the start button by mouse click. So, there will be a start button. INPUT: User can play the current music selected in the play list by clicking the start button.
  22. 22. OUTPUT: The played media file will run and shows video along with it’s sound if it is video file , if it is audio file it will play that particular music, song or sounds. If the file is not supported then a error message will be displayed. R.5.3: Pause/Resume Option DESCRIPTION: There will a button which will pause and resume the running file, by clicking that button user can pause/resume the running media file. INPUT: A mouse click is needed for pause the running audio or video file. OUTPUT: After the clicking of pause button the running audio or video file will be paused and if the user again clicks then the audio or video file will be resumed.
  23. 23. Data Flow Diagram  DFD(data flow diagram) is a hierarchical model of a system showing different activities of functions that the system performs and data interchange among these functions .  We have considered each function as a processing station that consume some input and produce some output. Here all the Level of DFD:
  24. 24. Testing Of Media Player Levels : Media player goes through three levels of Testing :-  Unit Testing  Integration Testing  System Testing
  25. 25. TESTING UNIT TESTING :  Driver and Stub Modules INTEGRATION TESTING  Big-bang testing  Top-down Integration Testing  Bottom-up Integration Testing  Mixed Integration Testing
  26. 26. TESTING SYSTEM TESTING :    Alpha Testing Beta Testing Acceptance Testing UNIT Testing : Unit testing is undertaken when a module has been coded and successfully reviewed.  we parted our media player project into various modules .  All of those modules is described in our SRS document.  All the functional requirements are divided into 3 java files.    1.Image.java 2.Media .java 3.MediaPlayerDemo.java
  27. 27. Output of image.java file
  28. 28. Output for test suite of audio file
  29. 29. TESTING  Integration Testing :  Now we integrate each module or unit and Test it as a whole .  Integrating each unit and then test it .Here we took various file like .mp3,.jpg,.3gp ,mpeg files. We use Mixed integration testing approach. System Testing : It is designed to validate a fully developed system to ensure the SRS document requirements.  Three main kind of System Testing :  i.alpha testing:-we the team members carried out this .  ii.Beta: Our friendly customers tests this Media player.  iii.acceptance :-this is not needed here.
  30. 30. TESTING PERFORMANCE TESTING :          6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9 Stress Testing Volume Testing configuration Testing Compatibility Testing Regression Testing Recovery Testing Maintenance Testing Documentation Testing Usability Testing
  31. 31. TABS ON PLAYER MENUBAR File: There are two options – File open, Exit. file_open.jpg Edit: There are two options to editing –image mode ,audio mode . media1.jpg Opening and Playing audio files: mp3_open.JPG Opening image file :image_open.JPG Help option :help_button.JPG
  32. 32. Future plan  1.Capturing the image from playing video file.  2. Changing format of media file.  3. Supports for compressing media file.  4. Playing file backwards with multiple speeds.  5. Live broadcast over Internet  6. Zooming in and out video file.  7. Supports for capturing media device.  8- Cutting the media files into small sub media files.  9- Integration with some web browser as plug in.
  33. 33. Thank you

×