5.Structuring information on a page makes it easier to outline yourmessage to the users in a way that is both simple and effective.Without order, the user cannot comprehend the message fully.
6.They are design guidelines for the developer that work to improve theuser’s experience when it comes to interacting with the system(Nielsen& Molich, 1990).They include.
“Visibilityof system status” – Via appropriate feedback the system ought toconstantly keep its users up to date.
“Matchbetween system and the real world” – Systems ought to communicateto the user in a form that is easy for them to understand. Thesystem ought to give the impression of it being a real lifefunctional and logical organization.
“Usercontrol and freedom” – The user needs to be able to navigate backand forth comfortably while using the system.
“Consistencyand standards” – The system should stick to universal logo’sand conventions when designing its platform.
“Errorprevention” – The system should have clear labels and signs thatguide the user through each step, avoiding errors when it comes tousing the system resources.
“Recognitionrather than recall” – The user should think less when using thesystem, this is achieved by the use of familiar icons andinstructions based on real life. “Flexibility and efficiency of use– The system should be able to accommodate both expert and amateurusers. One achieves this through a multi-layered design system withshort-cuts.
“Aestheticand minimalist design” – Simplicity is preferred when it comes todesigning the system. The system should not only be simple, but itshould also contain the vital instructions and icons only.
“Helpusers recognize, diagnose, and recover from errors:” messagesshould be precise, plain and simple.
“Helpand documentation” It is essential for the system to have help andthe system documentation. Users can get help, and other developersknow the full extent of the system as they try to utilize itsresources fully.
References
Nielsen,J., & Molich, R. (1990). Heuristic Evaluation of User Interfaces.In Proceedingsof the SIGCHI Conference on Human Factors in Computing Systems(pp. 249–256). New York, NY, USA: ACM.http://doi.org/10.1145/97243.97281