Salam.....
after one week break for designing our courseware, This week we learned about Testing and Evaluation in any Multimedia Project.
Testing and Delivering
Multimedia Application
D-1 : The Evaluation
Process
Testing of a multimedia
title is essential so that the final application adheres to international
quality standards and is not infested with bugs, technical snags,
inaccurate information or simple grammatical or typographical errors.
The process of evaluating
(testing) and revising a multimedia application project is dynamic and
constant. It involves both internal and external evaluation.
D-2 : Internal Evaluation
The happens within the
multimedia development group, through internal discussions for evaluating
the aspects of the application:
- Application design : is it logical and facilitates learning
- Project goals and objectives : are the established goals and Objectives being met
- Content is the acquired content represented accurately
- Text and narration : are the text and narration grammatically Correct
- Application graphics : are the application graphics adequate To fulfill the goals and objectives
- Sound : is the background music, effects and other sounds well recorded
- Application navigation : are the navigational structures and Aids effective
- Programming code : is it working as originally planned
- Delivery : can the application be delivered via the proposed medium
- Time and budget : is the project on-time and on-budget
- Legal considerations: have all licenses and other copyrights Been procured
The prime responsibility of
this function lies with the production manager and can be most effective
if the team members are open to positive criticism of their peers.
D-3 : External Evaluation
The following are the
components of external evaluation:
- Alpha Testing
- Focus Group Testing
- Beta Testing
D-3.1 : Alpha Testing
Alpha testing takes place
when the project is considered a working model i.e. it is not finished but
it is functional. The purpose of Alpha testing is to determine if the
general direction and structure are adequate and what changes are
necessary. Members of the Alpha-testing group should include a balance of
friends and critiques.
D-3.2 : Focus Group Testing
After revising the
application based on the feedback of the Alpha test, another possible
strategy is to present the application to a focus group. These groups are
composed of individuals who represent the expected audience of the
project. Standardized forms should be used for requesting comments and
suggestions from the Focus Group.
D-3.3 : Beta Testing
Once the project is in a
final draft form, copies should be made available to a group of potential
users called a beta-testing group. Here again, standardised questionnaires
should be used for collating feedback.
Quality Assurance (QA) is
the formal name given to the process of beta testing. When the beta
version of a multimedia application is released and the functionality
testing starts, the QA process has formally begun. Beta testers check all
possible paths of navigation and log all events that strike them as
unusual. In addition they do things that users will not usually do like
multiple mouse clicking, dragging things around and entering unneeded
keystrokes. The idea is to look for things that do not work. Beta testing
can be done in-house or it can be outsourced to a professional lab,
depending on financial resources and product secrecy issues. Beta testing
includes:
- Compatibility Testing
- Functionality Testing
- Functional Localisation Testing
- Install Testing
- Performance Testing
- Stress Load Testing
- Load Testing
These are some explanation of the topic.....hope u guys satisfied!!
