Download Media Player System Analysis: Features, Benefits, and Testing Strategies and more Summaries Java Programming in PDF only on Docsity!
CONTENTS
- Introduction….…….…………………………...…………………………………...3-
- 1.1.Problem Definition…….….………….……………………………………..........
- 1.2.Objectives.…………………….……………………………………………….....
- 1.3.Organization of Project Report..…………………………………………………
- Review…………………..……………………………………………………............
- 2.1.Motivation…………..…………………………………………………….…......
- 2.2.Benefits of the system………….………………………………………………..
- Requirement Specification……..………………………………………………….6-
- 3.1.Functionality Requirements…………………………………………….............
- 3.2.Performance Requirements…………….………………………………….........
- 3.3.External Interface Requirements.……….……………………………………...
- Design………………..…………………………………………………………..9-
- 4.1.Software Engineering Paradigm...……………………………………………...
- 4.2.DFD Diagrams…….…………………………………………………………..
- 4.3.State Transition Diagram………….….…………………………………….....
- Implementation.…………………………………………………………...........17-
- 5.1.System Implementation.…………………………………………………........
- 5.2.Snapshots……………………………………………………………………..
- Analysis………………………………………………………………………..35-
- 6.1.System Analysis……………………………………………………………...
- 6.2.System Study………………………………………………………………...
- 6.3.System Maintenance…………………………………………………………
- Testing……………………………………………………………………..40-
- 7.1.The Testing Process………………………………………………………
- 7.2.Testing Strategies…………………………………………………………
- Conclusion…………………………………………………………………….
- References ……………………………………………………………………
The main purpose of Media Player is to produce an audio (MP3) and video (MPG) player. The goals of Media Player are:
- Provide a platform to play audio (MP3) file.
- Provide a platform to play video (MPG) file.
- Support playlist (M3U) file.
- Provide playlist management.
- Provide online searching for music and videos. 1.3. Organization of Project Report The main purpose of this document is to present a detailed description of the functionalities offered by Media Player. It will explain the purpose and features of the system, the interfaces of the system, what system will do, the constraints under which it must operate and how the system will react to external stimuli. This document is intended for both the developers and users of the system.
2. Review 2.1. Motivation Presently users use software like Winamp, Windows Media Player and Open Source’s VLC Player. Plug-ins for these software are available to control these players. The good thing with these popular software is, they are rich in features. They have graphic equalizer and support for custom skins, custom plug-ins for extensibility. 2.2. Benefits of the system Media Player has been developed using Java which offers the following properties: - Simple - Secure - Portable - Object-oriented - Robust - Multithreaded - Architecture-neutral - Interpreted - High Performance
applied specifically to the analysis proper (as opposed to elicitation or documentation of the requirements, for instance). 3.3. External Interface Requirements 3.3.1. User Interface: The user will interact with the system through the modules designed in NetBeans IDE which provide a Graphical User Interface (GUI). The user can play audio/ video files, create playlists, manage playlists and search online. 3.3.2. Hardware Interface: Hardware is the backbone of any up and running software. It becomes more so important in case the applications are on a network or the size of the database and system is very large. Every system is very large. Every system demands a good hardware to support its functions. The hardware requirements are as follows: a) Processor:
- Minimum: 733 MHz Pentium.
- Recommended: 1 Ghz or higher. b) Memory:
- Minimum: 256 MB (Application Area) and 128 MB (development purposes).
- Recommended: 512 MB or higher. c) Disk:
- Minimum: 20 MB
- Recommended: For install it need free space with 30MB. 3.3.3. Software Interface: This deals with defining software resource requirements and pre-requisites that need to be installed on a computer to provide optimal functioning of an application. These requirements or pre-requisites are generally not included in the software installation package and need to be installed separately before the software is installed. For developing this website we use .net framework. This framework includes an in-built function and it is very user friendly environment. The project has been developed using the following programming environment:
- Java Environment: Java environment includes a large number of development tools and hundreds of classes and methods. The development tools are part of the system known as Java Development Kit (JDK) and the classes and methods are part of the Java Standard Library (JSL), also known as the Application Programming Interface (API).
4. Design 4.1. Software Engineering Paradigm A software engineer or a team of engineers must incorporate a development strategy that encompasses the process, methods, tools and layers. This strategy is often known as the process model or a software engineering paradigm. A process model for software engineering is chosen based on the nature of the application, the methods and tools to be used, and the controls and deliverables that are required. In the development of Media Player, the Linear Sequential Model has been applied. This model suggests a systematic, sequential approach to software development that begins at the system level and progresses through analysis, design, coding, testing and supports. The Linear Sequential Model encompasses the following activities: - System/ Introduction engineering and modeling: System engineering and analysis compasses requirement gathering at the system level with small amount of top - level design and analysis. - Software requirement analysis: The requirement gathering process is intensified and focused specifically on software. To understand nature of program, our team has made information domain for the software, as well as required function, behavior, performances and interface.
Requirements for both the system and application documented and reviewed with the customer by the team of the team of engineers.
- Design: Application design is a multi-step process in which we focused on four distinct attributes of program: Form Properties, software architecture, interface representation, procedure details.
- Code Generation: The Design is performed into the detailed manner so that code generation can be accomplished mechanistically.
- Testing: After the generation of code program testing begins. The testing process focuses on the logical internals of the application, ensuring that all the statements have been tested fully. Our team conducted test to uncover errors and ensure that defined input will produces actual results that agree with required results.
- Supports: The team provides software supports as errors may be encountered after the delivery of the software to the customer as customer requires functional or performances enhancements. 4.2. DFD Diagrams 4.2.1. DFD Level 0:
4.2.2. DFD Level 1: The following diagram as depicted in Fig. 4.2.2 sites out three processes:
- Initialize.
- Play.
- Manage Play-List. The Initialize process collects system information and initializes GUI (Graphical User Interface) of our Media Player. It also loads previous settings. The Play process has all the functionalities required for playback like Play, Pause, Stop, Next, Previous, etc. The Manage Playlist process gives facility to Load a saved playlist, Save a playlist, Build a playlist by adding files and folders to it. It also provides an additional facility to edit ID3 header information of MP3 file and save them.
Control Info File Info Audio/ Video Data Audio/Video File File Info MP3 (audio) File Info
Playlist
Control
Interface
Speakers
File System
Play
Initialize
Manage
Playlist
Fig. 4.2. 4.2.4. DFD Level 2 (Manage Playlist): The Manage Playlist process has been depicted in Fig. 4.2.4. This process performs three tasks:
- Open Playlist.
- Save Playlist.
- Edit ID3 tags of a file. The Open playlist process opens previously saved playlist files of standard type, .m3u. The Save playlist save the currently loaded playlist as .m3u file on the file system. The Edit Id3 tag process is used to edit metadata about mp3 files like album, author, title, duration, year, etc. 16 Open Playlist Load Playlist Edit ID Tags File System Playlist Fig. 4.2.
4.3. State Transition Diagram The State Transition Diagram shows various states of the Media Player when user takes different commands. From the diagram shown below in Fig. 4.3, the programmer can easily interpret the required objective and easily understand the functionality. We have three states in the Media Player:
- Play
- Pause
- Stop The Play state is achieved by taking play action. It can be directed from stop state as well as paused state. The Pause state is achieved when user takes pause command. Commonly there is play- pause state interchange done frequently. The Stop state activates when user takes stop command or playing song finishes.
user's computer. After loading the system, training of the users starts. The main topics of such type of training are:
- How to execute the package.
- How to enter the data.
- How to process the data (processing details).
- How to take our reports. After the users are trained about the computerized system, manual working has to shift from manual to computerized working. The following two strategies are followed for running the system: a) Parallel Run: In such a run for a certain defined period, both the systems, i.e. computerized and manual are executed in parallel. This strategy is helpful because of the following:
- Manual results can be compared with the results of the computerized system.
- Failure of the computerized system at the early stage, does not affect the working of the organization, because the manual system continues to work, as it used to do. b) Pilot Run: In this type of run, the new system is installed in parts. Some part of the new system is installed first and executed successfully for considerable time period. When the results are found satisfactory then only other parts are implemented. This strategy builds the confidence and the errors are traced easily.
5.2. Snapshots 5.2.1. Home Page:
