Thursday, June 7, 2012

Week 14 on 23rd May 2012 - Final Presentation

Woow!!.. week 14 already. So today all the group will be presenting their group project. After few month working hard to finish this project, we can see all the group come out with outstanding courseware.. Can be sell also... huhu.. Thanks to Prof Jamal and frends for the support adn comitment!

Here some capture from our group project.

Courseware Montage


Conclusion


Help Menu


About Us


Main Courseware


Main Page


Courseware Intro


Courseware Content


Courseware Content


Courseware Content


Courseware Content


Courseware Exercises


Week 13 on 16th May 2012 - Gruop Work


This week, Prof. Jamal provides an opportunity for each team to complete assigned projects ... so we agreed to come to the lab and complete the rest of the courseware development ... so many work to be complete.. Next week need to present... Huh!

Sunday, May 13, 2012

Week 12 on 9th May 2012 - Testing & Evaluation Part 2

Evaluation


The evaluation stage of the software development process requires the client and developer to review the software. Broadly speaking, they evaluate against the following questions: 
1. Does this software meet the user requirements? 
2. Is it fit for purpose? Evaluation - criteria To answer these questions, the original aims of the software must be evaluated against the following criteria. 
1. Robustness 2. Reliability 3. Portability 4. Efficiency 5. Maintainability.
there are two type of evaluation:

Formative Evaluation - Formative Evaluation is a bit more complex than summative evaluation. It is done with a small group of people to "test run" various aspects of instructional materials. For example, you might ask a friend to look over your web pages to see if they are graphically pleasing, if there are errors you've missed, if it has navigational problems. It's like having someone look over your shoulder during the development phase to help you catch things that you miss, but a fresh set of eye might not. At times, you might need to have this help from a target audience. For example, if you're designing learning materials for third graders, you should have a third grader as part of your Formative Evaluation.


Summative Evaluation - Summative evaluation provides information on the product's efficacy ( it's ability to do what it was designed to do). For example, did the learners learn what they were supposed to learn after using the instructional module. In a sense, it lets the learner know "how they did," but more importantly, by looking at how the learner's did, it helps you know whether the product teaches what it is supposed to teach.
Summative evaluation is typically quantitative, using numeric scores or letter grades to assess learner achievement

Week 12 on 9th May 2012 - Testing & Evaluation Part 1

Hi all,
This week, Prof J class, more focus on the last topic for the course "testing and evaluation".
Actually today class refresh back last week topic.
Last week, we were given three articles and required to memasterkan ourselves to one of the articles and explain back to our friends... This is the details about all three articles.



Article 1 : TYPES OF COURSEWARE TESTING

1. Functionality Testing

Testing that focuses on the development function. particularly with respect to programming language. 3 type of functionality testing

  • Unit Testing:  Focus more on the programmer or the developer to check their own code. Check the code separately between each moduls.
  • Integration Testing: More on testing the courseware when they want to merge the courseware... Whether the courseware can be merge or not, or any error occurs.
  • Compatibility Testing: Testing the courseware on the various kinds of user hardware and software configurations

2. Usability Testing

Usability is a quality attribute that assesses how easy user interfaces are to use. Usability is defined by 5 quality components:


  • Learnability
  • Efficiency
  • Memorability
  • Errors
  • Satisfaction

Article 2: COURSEWARE TESTING APPROACH
There are few ways we can used to test our courseware.. There are:
  1. Self testing - 
  2. peer testing
  3. Concept Testing (Focus Groups)
  4. Field trials
Article 3 : COURSEWARE TESTING STAGES

  1. Alpha Testing - Alpha testing is conducted when the prototype of the multimedia courseware is ready and the courseware can take inputs and generate outputs
  2. Beta Testing - Beta testing comes after alpha testing and can be considered a form of external user acceptance testing


Wednesday, May 2, 2012

Week 11 on 2nd May 2012

Today topic : Visual Design


Visual design is not about what a piece is saying literally through words, but it is everything about what a piece is saying visually and emotionally--solely through appearance.

Some basic visual design concepts include color, contrast, typography, composition, line, texture, space and shape. Color and use of white space often evoke a certain mood. Lines guide viewers through a composition. Typography---the use of type as a design element---can add visual interest.





Some elements of User Interface
  • A background that reflects the theme
  • Foreground elements that reflect the theme.
  • Other elements that support the theme.
Audience
  • Each composition uses different concepts. The intended audience for a piece can mold its visual design. A piece primarily for the elderly might place more emphasis on type size (typography) and contrast, while a piece geared toward children may make use of vivid colors and textures.
    Interface family
    Elements in an interface family must work both as a group and as independent pieces
    Unity
    Focus on meta-style and not just individual styles.™ Focus on stylistic unity NOT uniformity
    Layout
    Designer – aiming to balance bg colours or head angles. Buttons positions are the opposite of what users would expect
    Interface Element
    Background - background can be made interesting by creating areas of emphasis, rather than filling  entire screen or providinguniform coverage
    Windows – usually set aside to hold media
    ™Panels – may simply enhance the structural features of thh d  dd d  h  l e design or add depth or colour.
    Buttons & Controls - Need to be clear but doesn’t  have to mean predictable or dull

Week 10 on 25th April

Today is our 40% prototype presentation by all group..
All group have been given a piece of paper to comment on others group prototype design
Feedback from Prof Jamal All the group did a great job!!
Well Done guys...

Week 7,8 and 9

No Class for three week...

Huhuhu... Rest time... but we need to finish our 40% prototype...














Our group decide to met in Jusco Tebrau Taman University to discuss the storyboard and the design of the courseware... We agree to send the storyboard and our own design by two week and will compile by Mr Azaki