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.
- Colours
- Fonts or styles screens.
- Graphis and multimedia
- Arrange all these elements into an
attractive layout
Elements
of user interface.
- Background (colours or images)
- Foreground (content and links – titles,heading,
sub headings, body text, illustrations, captions)
- 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
- Keep it simple
- Limit number
of fonts per screen and per courseware.
- Use the
same fonts consistently.
- 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.
- 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)
- 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.
- Self testing (individual test their own
product)
- Peer review (to get colleagues to test our product)
- Concept testing (focus groups) – try out the main project ideas on selected groups
of people representative.
- 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.
- Alpha testing (developmental testing)
- Conducted when the prototype is ready.
- Take inputs and generate outputs.
- Not fully functional.
- Tested inside the organization.
- Beta testing
- After alpha testing
- Form of external user.
- Beta version software are released to limited
audience.