Last Presentation ( 11 December 2012 )

Salam.....

Hari ini merupakan hari terakhir kelas. Hari ini juga sangat penting kerana setiap kumpulan perlu membentangkan Projek Akhir mereka.

Perbentangan 1 : Tajuk : Suku Kata.

-  Kumpulan ini membentangkan hasil projek yang sangat hebat.
-  CD ini sesuai untuk murid di tahap prasekolah, Linus, Galus & Pendidikan Khas.
-  Selain daripada belajar mengenai suku kata, pengguna juga dapat belajar mengenal kenderaan.
- Kandungan perisian yang mengandungi semua elemen multimedia yang dapat menarik perhatian murid
   untuk menggunakannya.

Perbentangan 2 : Tajuk : Lambaian Kaabah
-Kumpulan 2 membentangkan projek mereka yang sesuai bagi pelajar sekolah menengah untuk subjek
  Pendidikan Islam tingkatan 4.
- CD ini menerangkan mengenai Ibadah Haji.
- Kandungan CD ini sangat sesuai dengan pelajar tingkatan 4.
- Bagi pendapat saya, mereka telah melakukan sesuatu yang sangat hebat dimana kandungan CD ini sangat
   menarik dan hebat.

Perbentangan 3 : Tajuk : Water Cycle
- Tajuk ini dibentangkan  oleh kumpulan kami.
- Beberapa komen yang kami terima daripada rakan-rakan dan En.Juhazrin iaitu :
   1) Penggunaan Font yg kurang jelas bagi paparan respon jawapan.
   2) Penggunaan jenis 'typeface' yang kurang sesuai untuk nama pengguna.
   3) Penggunaan "anak panah" pada butang 'exit' tidak sesuai & dikhuatiri akan mengelirukan murid.
- Keseluruhannya, Alhamdulillah...segala pengorbanan & kepayahan telah terbalas. Kami amat berpuas hati
   dengan hasil projek ini...


Perbentangan 4 : Tajuk : Kemahiran Hidup :

- CD ini sesuai untuk untuk murid pendidikan khas untuk belajar mengenai kemahiran hidup.
- Paparan Grafik yang menarik.
- CD ini dibangunkan dengan penuh teliti.
- Aplikasi pilihan menu penggunaan yang sangat menarik.
- Secara keseluruhannya, aplikasi yang dibangunkan oleh kumpulan ini sangat menarik dan hebat!.Tahniah!!

Kami amat gembira kerana berjaya menyiapkan projek ini. Terima Kasih kepada En.Juhazren yang telah membantu kami dalam menyiapkan projek ini. Alhamdulillah...Sekarang, bersedia utk final exam!

Week 11 : Documentation Of Multimedia Project (04 December 2012 )

Salam... This week, we learned about project Documentation for any Multimedia Project.

# Documentation is another important matter to be performed.
# Allow all facts and figures regarding the development and process to be documented.
# Skipping could cause problem in the future.
   - important for upgrading in future
# To be kept properly and systematically.

Three type of Document :
#  Planning / Design Document

#  Support Document
  - document prepared with the Multimedia Program to provide additional information for using the program.
  - Normally contain :
     1) How to use this CD/Program/Product
     2) Technical Requirement ( Software or Hardware ) eg: FLV Player.
     3) Installation Guide ( if Necessary )

#  Final Document
    - Reports the improvements that reports the improvement.
    - Includes all formative assessments outcomes, reviews, test reports, minutes of group meetings and
       decisions made, and improvements made to the project.( what did you add/remove)
    - Completed multimedia courseware.
    - Reports all activities & tasks undertaken by each group member throughout the development process.
    -   Element :
         a) An Introduction to the report
         b) Group meetings (date, discussion topic, decision )
         c) Suggestion gathered from peers.(if any)
        d) Comments and suggestions from prototype presentation
        e) Testing & Formative evaluation report.
        f)  Improvement/changes made from the original planning document. (eg: new desidn, flowchart 
             storyboard)
        g) Problem & issues faced throughout the development process.
        h) Reflection of group members on the Multimedia Project development product.

Medical Leave ( 27 November 2012 )

Salam....Sorry but i'm on MC Today.

Evaluation in Multimedia Courseware (20/11/2012)

Salam.....after a week break, this week we learned about evaluation in Multimedia Course ware Development. 

Why we need to evaluate multimedia courseware?

•  Ensure functionality (effectiveness)
•  Ensure performance (efficiency)
•  Customer / User acceptance 

Formative Evaluation & Summative Evaluation 

 

Formative Evaluation

• Identification of lesson features that need modification.
• Ongoing process

 Summative Evaluation

•  Signature authority
•  Not used for modification
•  Used for purchase or adoption decisions

Using ADDIE Model, evaluation is one of the step that dev. should apply.
 

Prototype Presentation ( 06 / 11 / 2012 )

Minggu ini kami 4 kumpulan membentangkan prototaip multimedia yang telah disiapkan.

Kumpulan pertama - Tajuk : Belajar Suku Kata ( Kenderaan )
    - mereka telah menghasilkan bahan yang menarik yang mungkin dapat diaplikasikan kepada murid-murid 
       di Pra Sekolah. Penggunan warna yang menarik dapat menarik perhatian penggunanya.

Kumpulan Kedua  - Tajuk : Water Cycle
    -  kami telah menghasilkan CD untuk murid di tahun 5. Ini dapat membantu murid memahami dgn lebih   
        mudah berkaitan kitaran air. Komen yang diterima sgt positif dan kami akan melakukan
        penambahbaikan supaya ia lebih baik.

Kumpulan Ketiga   - Tajuk : Kemahiran Hidup ( Peralatan  Tangan )
    - kumpulan ini telah menghasilkan CD yg menarik. Tugasan mereka hampir 90% siap dan sgt kreatif.
       Tahniah!!..Masalah yang dihadapi adalah dari segi interaktiviti sahaja.

Kumpulan Keempat : Tajuk : Pendidikan Islam ( Haji )
     - Kumpulan ini juga kreatif , montaj yang mereka hasilkan menarik dan cantik. Masalah cuma dari segi
        penggunaan warna dan typeface.

Testing & Evaluation ( 30/10/1012 )

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!!

WEEK 6 : PROJECT NEED ANALYSIS PRESENTATION (16/10/2012)

Salam...

This week, all of the group present their need analysis for their project.

4 group presents their findings.

we also learned about flowchart & their symbol...

Thats all....TQ