Info Sys - Applied Multimedia - Testing/ Doc/Eval

Testing involves examining eachfunction to check it meetsthe specified performance & quality level.

Testing will also ensure that all components and functions work individually and together aspart ofthe original design

Four types of testing:

• screen testing

• integration testing

• acceptance testing

• usability testing

Each separate screen must be tested in the application to ensure it matches the design and functions correctly

Some standard screen tests:

• does the layout match the design
• do buttons & navigational functions work
• does the text, fonts, colours & sizes match design
• do scroll functions, videos and audio clips run
• do non-functioning controls grey out
• is there visible continuity between screens
• do applets work properly
• has it been spell checked

INTEGRATION

after individual screens are tested, integration testing ensures they all work together

ACCEPTANCE

done by the client, they ensure the product does what the original contract specifies

satisfactory acceptance testing will result in the client signing off the project - formally agreeing that the contract has been succesfully completed

USABILITY

a group of independent testers will work on typical tasks relevant to the application

they evaluate how easily the application allows users to recover from mistakes, whether the UI is user friendly & aesthetically pleasing

attention should be given to the needs of disabled users

During development documentation should be produced at all stages.

Documentation falls into two categories:

• project development documentation - for use by the present and future developers
• user documentation - for use by users of the application

Project development documentation includes:

• requirements specification
• navigational maps
• storyboards
• record of testing

User documentation will include:

• hardware/software system requirements
• user guide/instructions

REQUIREMENTS SPEC

formal document agreed between client and developer

canbe used as a checklist to ensure all criteria have been met

NAVIGATIONAL MAPS

shows the links between screens

should define thestructure and flow of the presentation/application

structure can be linear, hierarchical, web, composite/hybrid

STORYBOARDS

created during the design stage they show:

• how GUI will look
• animations & duration
• video stills & duration
• text design
• layout of all screens

RECORD OF TESTING

a careful record of all tests should be made,detailing expected and actual results

if there are differences in expected & actual results they should be explained

HARDWARE/SOFTWARE SYSTEM REQUIREMENTS

minimum requirements the user's system needs to run the application. May include:

• processor speed
• platform & OS version
• RAM/hard disk capacity
• CD-ROM/DVD-ROM drive
• Sound/video card
• monitor resolution

USER GUIDE/INSTURCTIONS

instructons for running the application have to be included in the finished documentation 

should include a detailed set of instructions for running software andhighlighting FAQs

for example: switch system on, insert CD-ROM/disk/navigate to website,click on start button, navigate to tutorial section

Every MM application should be evaluated terms of fitness for purpose, accesability (how easy it is for disabled users to use), clarity of presentation

FITNESS FOR PURPOSE

• does the application do what it was intended to do
• has the best possible solution to the problem been designed
• does it work efficiently
• is it robust
• is it easily maintained
• has a technical anduser guide been provided

ACCESABILITY

• text- clear and resizable fonts
• audio - include captions, avoid conveying information with sound only
• Images - best possible resolution & provide zoom feature & provide full descriptions for graphs and diagrams
• avoid flickering on screen
• choose good colour combinations

CLARITY OF PRESENTATION

• navigational elements should always be visible
• screenshould be arranged symmetrically
• transitions should flow coherently
• colours should be appropriate to the topic

Evaluation of a MM application is iterative and may leadto improvments and developments of the application in future versions