WEEK 14 : Final Presentation

Finally..
We have done with our presentation..
But there are some technical error happen..
Maybe there are some redundant button that we did not realize..
Will do some improvement before submit to Prof Jamal..

By the way, Ismanor Fahmi and me were given the task to do the final report.
Thanks god next week is a school holiday..
got some time to settle down everything..

WEEK 13 : Final Touch Up for Courseware

This week there is no lecture..
But somehow our group decided to meet up at class to settle down everything..
We help each other to solve some of the technical problems occur in our courseware..
Besides, everyone were asked to give 4 questions from their part..
The questions will be combined and put into "Are You Sure" part..

I had been asked to create a standard button and a standard layout for our group multiple choice questions using Adobe Photoshop.
 

WEEK 12 : Testing Category

Dr Jamal revise what had we discussed in group last week..

There are 3 type of testing which are :

1.  Content testing

• A misspelled word
• Wrong picture
• Poorly written paragraph 

2. Functional testing

• A link does not work
• The site only work with windows 7
• A cool "mouse over" does not work

 3.   Usability testing

• Hard to get to page 3
• A picture has too high of resolution
• User can't tell which thing they can click on

WEEK 11 : Testing of Multimedia Project

Pssttt..Azaki wasn't in a good mood today..be careful..hehe!

The lesson today is about Testing of Multimedia Project

We are divided into 3 groups based on 3 types of articles which are:

1. Type of Courseware Testing
2. Courseware Testing Approach
3. Courseware Testing Stages 

 Let’s go through each article:

 

ARTICLE 1 : Type of Courseware Testing

2 type of courseware testing:

1.  Functionality Testing

      Meaning - focus on development function especially in programming part.

• Unit Testing -testing of the own code module by module. Each programmer tests their own modules thoroughly and does not start a new module before testing and fixing the previous one. 
• Integration Testing - testing of the full program after the modules are combined
• Compatibility Testing - testing the courseware on the various kinds of user hardware and software configuration.

2.  Usability Testing

      Meaning - a quality attribute that assesses how easy user interfaces are to use.

• Learnability: How easy is it for users to accomplish basic tasks the first time they encounter the design?
• Efficiency: Once users have learned the design, how quickly can they perform tasks?
• Memorability: When users return to the design after a period of not using it, how easily can they reestablish proficiency?
• Errors: How many errors do users make, how severe are these errors, and how easily can they recover from the errors?
• Satisfaction: How pleasant is it to use the design?

ARTICLE 2 : Courseware Testing Approach

1.  Self  Testing -  everyone in the team monitor each other's performance to spot the weaknesses of each part and correct it together.

2.  Peer Review - ask people that have more experiences to test the courseware for improvement.

3.  Concept Testing (Focus Groups) - trying out the main project ideas on selected groups of people representative of the intended user group

4.  Field Trial - test the courseware in situ with the users.

ARTICLE 3 : Courseware Testing Stages

1. Alpha Testing (Stage - Developmental Testing)

• is conducted when the prototype of the multimedia courseware is ready and the courseware can take inputs and generate outputs.
• tested inside the organization, in our context and on the peer group.
• run on a different machine in organization (to detect and eliminated bug)
• test the tools that worked and didn't work

2. Beta Testing (Stage - Acceptance Testing)

•  comes after alpha testing ( considered a form of external user acceptance testing)
• release to a limited audience outside of the programming team
• release to groups of people so that further testing can ensure the product has few faults or bugs.