O Home O Newsletters O Conference 2002 O
O Past Conferences O PC Drivers Licence O National Moderation O CIC O Bluebook O Forum O Job Vacancies O

	Prescription:BC100 Business Communication Aim of Module To enable students to make effective use of written communications through the study of basic English language skills, techniques for writing and interpreting simple business and technical communications, and through writing documentation. Credits 7 Suggested Time 70 student learning hours Prescription Expiry Date Nov 2002 Note THIS IS A COMPULSORY CBC MODULE Level and Assessment Schedule Topics Highest Skill Level Suggested Assessment Percentage 1 Written Skills A 50 2 Technical Writing A 50 100 LEARNING OUTCOMES The Student Will A 1 Demonstrate effective and correct written skills in a variety of documents common in the workplace. A 2 Demonstrate an understanding of the process and demonstrate practical skills in writing technical documentation for a predetermined audience. CONTENT 1  Written Skills > The characteristics of good written business communications will be described. > The characteristics and uses of standard business communications will be described. (eg. Memo, report, letter, curriculum vitae) > The different techniques involved in efficient reading, and when to use them, will be outlined. > Effective note taking methods will be explained. > The concept of proof-reading and how to approach the proof-reading of a document will be explained. > A structured report, based on research or a case study, identifying major segments and separating major content and appendices, will be composed. Content must be logically sequenced. > A report to an audience will be presented. (maybe combined with IP100) top 2  Technical Writing > The approaches to technical writing and in particular to producing user documentation will be explained. > The effect of various approaches on the quality and completeness of information obtained will be explained. > The structuring of documentation for effective use will be described. > The appropriate options for gathering technical information (user procedures, etc) for producing user documentation will be discussed. > When writing technical documentation, the following steps will be performed: -gathering the information required to prepare a user guide -outlining the initial documentation -considering the process involved and the effect of various approaches on the quality and completeness of information obtained > A technical document will be designed. > A technical document will be written. top		Introduction Regulations Module Prescriptions   Back to list of Prescriptions
Introduction O Regulations O Module Prescriptions O O Home O Newsletters O Conference 2002 O Past Conferences O PC Drivers Licence O National Moderation O CIC O O Bluebook O Forum O Job Vacancies O