WEEK 13

Group Discussion .

 Next week, we need to present the complete courseware.

 

WEEK 12

TESTING & EVALUATION

We start our class today with testing exercise. We need to match the multimedia courseware problem with testing category. Below are the answers.

TESTING CATEGORY	MULTIMEDIA COURSEWARE PROBLEM
Content Testing	Ø  A misspelled word
	Ø  It is the wrong picture
	Ø  A paragraph is written poorly
Functional Testing	v  A link does not work
	v  A cool “mouse over” does not work
	v  The site only works with Windows 7
Usability Testing	ü  It is hard to get to page 3
	ü  A picture has too high of resolution
	ü  Users cannot tell which things they can click on

Last week, we already discussed 3 articles about testing, so today, we learned more about evaluation.

What is Evaluation?

Evaluation is testing whether a multimedia program fulfills the objectives set, and suggesting improvements it requires to make the program useful for its target audience.

Types of Evaluation

There are certain decisions, which need to be taken before starting the process of software development. These decisions guide the process of software development. In fact these decisions become the guiding principles and the software developers have to keep asking the questions, if they are fulfilling the objectives decided upon in the planning process. Once the prototype of the software is ready, it is tested and once again the objectives can be re-examined and reformulated on the basis of feedback and evaluation. There are 2 types of evaluation which are formative and summative.

1. Formative

Ø  Formative evaluation is done as a continuous process in the development of multimedia and even before the development process actually starts.

Ø  Decisions taken at the beginning of the process of software development affect various aspects

Ø  Answers to questions like who, why, where, and how become the guidelines for the development of the software.

Ø  Depending upon the time and resources, both quantitative and qualitative methods of feedback are utilized in formative evaluation.

2. Summative

Ø  After the completion of the development of the program, the software is released for use. The actual users, then, make suggestions and these suggestions form the basis of summative evaluation.

Ø  Summative evaluation is the end of the project evaluation.

Ø  Suggestions on the basis of summative evaluation may be for short-term and long-term changes in the program.

Ø  Short-term changes may be based on your own observations and the feedback from the users and the long-term changes may be made on the basis of the decisions of the curricular design.

                                                                                                                                

Example of evaluation form.

                                                                                                                            Sources : Cemca

WEEK 11

This week, we learned about visual design. It is also known as interface design or presentation design.

Things need to plan on how your courseware will look.

1. Colours
2. Fonts or styles screens.
3. Graphis and multimedia
4. Arrange all these elements into an attractive layout

Elements of user interface.

1. Background (colours or images)
2. Foreground (content and links – titles,heading, sub headings, body text, illustrations, captions)
3. Others (text, images, buttons, navigation bars, animation, video,etc)

Critical tasks of visual design

v  Define the visual theme and style

v  Design a system of screen layouts

v  Create the structural elements of each screen

v  Create the control elements

v  Intergrate the media elements

v  Create prototype

Typography

1. Keep it simple

-        Limit number of fonts per screen and per courseware.

-        Use the same fonts consistently.

2. Make good font choices

-       Sans serif or serif

-       Commonly installed fonts

-       Mood

-       Readability

Lastly, we were given 3 articles and discuss it in our group.

  

ARTICLE 1 – Types of course ware testing.

There are 2 types of course ware testing.

1. Functionality testing (unit, integration, compatibility)

-        Functionality testing (testing the programming features)

-       Unit testing (when programmers test their own code)

-       Integration testing (when the various modules are combined and running together)

-       Compatibility testing (testing the courseware on the various kinds of user hardware and software configuration)

2. Usability testing

-       Quality attribute that assesses how easy user interface are to use.

-       5 quality components

a)    Learnability

b)    Efficiency

c)    Memorability

d)    Errors

e)    Satisfaction

ARTICLE 2 – Courseware testing approach.

1. Self testing  (individual test their own product)
2. Peer review (to get colleagues to test our  product)
3. Concept testing (focus groups) – try out the main project ideas on selected groups of people representative.
4. Field trials – the courseware is tested with the users

ARTICLE 3– Courseware testing stages.

There are 2 stages for the courseware to be testing before publish.

1. Alpha testing (developmental testing)

-       Conducted when the prototype is ready.

-       Take inputs and generate outputs.

-       Not fully functional.

-       Tested inside the organization.

2. Beta testing

-       After alpha testing

-       Form of external user.

-       Beta version software are released to limited audience.

WEEK 10

Today, we present 40% of our project courseware. We received many comments about the courseware. We need to change some of the text color and fonts. Next week, we need to submit the 40% of courseware and document proposal.

WEEK 9

Today’s class is cancel, but we need to present 40% of our project’s prototype next week.

 

WEEK 8

WEEK 7

Today’s class is cancel. So, our group do some discussions. As a conclusion , each member will design a template. Below are some of the basic design for the template that i have made.

Design 1

Design 2

Design 3

Design 4

Design 5