It will be advantageous to have completed COMP2303 - Network & Operating System Principles or its equivalent. This will be compulsory in 2007.
It is desirable to have completed COMP3301 - Operating Systems or its equivalent OR completion of COMS3200 Computer Networks I or its equivalent
This course introduces students to the use of a real-time operating system to the control of some simple peripherals. Students get to work with a a commercial quality RTOS (uC/OS-II). The laboratory work centres around an "Internet Telephone". We do not study VoIP, but just get a small number of PCs to communicate over an Ethernet in the laboratory. Experiments start out with students building up parts of the RTOS to work with the hardware supplied. The final part of the course is less structured and students get to add features to enhance the product. No hardware construction is required; all programming is in C.
| GRADUATE ATTRIBUTE | LEARNING OBJECTIVES |
| A. IN-DEPTH KNOWLEDGE OF THE FIELD OF STUDY | |
| A1. A comprehensive and well-founded knowledge in the field of study. | 1, 2, 3, 4, 5, 6 |
| A4. An understanding of how other disciplines relate to the field of study. | |
| A5. An international perspective on the field of study. | |
| B. EFFECTIVE COMMUNICATION | |
| B1. The ability to collect, analyse and organise information and ideas and to convey those ideas clearly and fluently, in both written and spoken forms. | 2, 4, 6 |
| B2. The ability to interact effectively with others in order to work towards a common outcome. | 2, 6 |
| B3. The ability to select and use the appropriate level, style and means of communication. | 6 |
| B4. The ability to engage effectively and appropriately with information and communication technologies. | 2, 6 |
| C. INDEPENDENCE AND CREATIVITY | |
| C1. The ability to work and learn independently. | 1, 2, 3, 4, 5, 6 |
| C3. The ability to generate ideas and adapt innovatively to changing environments. | 2, 3, 4, 5 |
| C4. The ability to identify problems, create solutions, innovate and improve current practices. | 1, 2, 3, 4, 5 |
| D. CRITICAL JUDGEMENT | |
| D1. The ability to define and analyse problems. | 1, 2, 3, 4, 5, 6 |
| D2. The ability to apply critical reasoning to issues through independent thought and informed judgement. | 3, 4, 5, 6 |
| D3. The ability to evaluate opinions, make decisions and to reflect critically on the justifications for decisions. | |
| E. ETHICAL AND SOCIAL UNDERSTANDING | |
| E1. An understanding of social and civic responsibility. | |
| E2. An appreciation of the philosophical and social contexts of a discipline. | |
| E4. A knowledge and respect of ethics and ethical standards in relation to a major area of study. | |
| E5. A knowledge of other cultures and times and an appreciation of cultural diversity. | |
| GRADUATE ATTRIBUTE | LEARNING OBJECTIVES |
| 1. Ability to apply knowledge of basic science and engineering fundamentals | 2, 3 |
| 2. Ability to communicate effectively, not only with engineers, but also with the community at large | 2, 3, 6 |
| 3. In-depth technical competence in at least one engineering discipline | 1, 2, 3, 4, 5, 6 |
| 4. Ability to undertake problem identification, formulation and solution | 1, 2, 3, 4, 5, 6 |
| 5. Ability to utilise a systems approach to design and operational performance | 1, 2, 4, 5 |
| 6. Ability to function effectively as an individual and in multi-disciplinary and multi-cultural teams, with the capacity to be a team leader or manager as well as an effective team member | 1, 2, 6 |
| 7. Understanding of the social, cultural, global and environmental responsibilities of the professional engineer, and for the need for sustainable development | |
| 8. Understanding of the principles of sustainable design and development | |
| 9. Understanding of and commitment to professional and ethical responsibilities | |
| 10. Expectation and capacity to undertake life-long learning |
All of the necessary material is available on the course web pages.
|
|
| Jean J. Labrosse, MicroC/OS-II , (November 1998), R&D Books | |
| Jean J. Labrosse, Embedded Systems Building Blocks : Complete and Ready-To-Use Modules in C , 2nd Ed. (January 2000), R&D Books | |
| David E. Simon, An Embedded Software Primer, Addison-Wesley Pub Co; 1st edition | |
| |||||||||||||||||||||||||||||||||
Your final grade will be the highest grade for which your overall percentage and component results satisfy the criteria in the following table. For example, if you achieve Final Exam, Assignments, and Project results of 45, 80, and 85 respectively, your overall percentage will be 72% (45%*0.3 + 80%*.3 + 85%*.4). Thus for each component the grades were 4, 6, 7, 5; with your final grade a 4@64% due to the 45% in the final examination. Thus, the final grade is the minimum of the four components, and this is set at the upper bounday of the lowest grade if rounding down has taken place on the final grade.
Any work submitted which has no academic merit attributable to the student submitting the work will receive a mark of 0% for the assessed item. Also note the references to plagiarism elsewhere in this document.
| To be awarded this | requires that you achieve this... | |||
| Final Grade | Overall Percentage | Final Exam | Assignments | Project |
| 7 (High Distinction) | 85% or higher | 75% or higher | 85% or higher | 80% or higher |
| 6 (Distinction) | 75% or higher | 65% or higher | 75% or higher | 70% or higher |
| 5 (Credit) | 65% or higher | 55% or higher | 65% or higher | 60% or higher |
| 4 (Pass) | 50% or higher | 45% or higher | 50% or higher | No requirement |
| 3 (Fail) | 45% or higher | No requirement. | ||
| 2 (Fail) | 20% or higher | No requirement. | ||
| 1 (Fail) | At least one item of work submitted or exam/test/labs attempted. | |||
| X | No work submitted or tests/exams/labs attempted. | |||
Each assignment is designed to build on material provided or developed in previous assignments. Because of this approach, no late assessment of the assignments can be conducted, i.e., a mark of 0% is recorded for each of the components for the late assignment.
Up to one assignment can be waived with suitable evidence that there was a medical condition that made attendance at the demonstration impossible or that the required written material could not be prepared for submission. Any subsequently missed assignments will be awarded 0% even with medical evidence within 24 hours of the demonstration.
Late submission of the project will be penalised by 1/5th of the contribution of the project (not of the mark you were awarded) per working day or part thereof. Requests for extensions should be made to the course coordinator (before the due date) and be accompanied by documentary evidence of extenuating circumstances (e.g. medical certificate).
Late submission should be made to the school office.
| Demonstration | 2% |
| Workbook | 2% |
| Technical Brief | 2% |
| Achievement | Result |
|---|---|
| Software is poorly coded. Software does not compile or link. Software does not work, nor exhibits any possibility of working. Software has been plagiarised. |
|
| Some attempt to maintain the coding style (with relevant comments). Software compiles and links with some warnings. Software works in most areas required, or has indication of substantial proportion working. |
|
| Software adheres to the coding style and has excellent comments. Software compiles and links without any warnings or errors. Software works completely. |
Each student's workbook is marked individually. If work is included which is not original, then the source of that material needs to be accurately referenced.
The workbook will be marked out of 2 and no part-marks will be given. The following table defines the criteria by which the workbook will be assessed.
| Achievement | Result |
|---|---|
| Little or no material to show development of the software. Material has been plagiarised. |
|
| Some material to show the development of the software. | |
| Detailed material that shows the development of the software which includes: pseudo-code, flowcharts and diagrams. |
Every student is expected to submit a technical brief, and each brief will be marked individually. The material is either original, or the source of the material is accurately cited.
The technical brief is intended as an opportunity to provide evidence of the work you have achieved in the assignment. The technical brief also provides a chance for you to critically analyse the results of your experimentation and present them in a clear, logical and concise manner. A person with a similar background should be able to utilise the information presented in the technical brief to develop applications to interface with your design.
The technical brief should be:
The technical brief should also include the following sections:
Each student's technical brief will be marked individually. The technical brief will be marked out of 2 and no part-marks will be given. The following table defines the criteria by which the technical brief will be assessed.
| Achievement | Result |
|---|---|
| Student makes no submission. Little or no attempt has been made to meet the above guidelines. Submission has been plagiarised. |
|
| A reasonable attempt has been made to meet the above guidelines. Submission is not necessarily presented in a clear, logical and concise manner. |
|
| Submission meets the above guidelines completely. Submission is presented in a clear, logical and concise manner. |
| Demonstration | 2% |
| Workbook | 2% |
| Technical Brief | 2% |
| Achievement | Result |
|---|---|
| Software is poorly coded. Software does not compile or link. Software does not work, nor exhibits any possibility of working. Software has been plagiarised. |
|
| Some attempt to maintain the coding style (with relevant comments). Software compiles and links with some warnings. Software works in most areas required, or has indication of substantial proportion working. |
|
| Software adheres to the coding style and has excellent comments. Software compiles and links without any warnings or errors. Software works completely. |
Each student's workbook is marked individually. If work is included which is not original, then the source of that material needs to be accurately referenced.
The workbook will be marked out of 2 and no part-marks will be given. The following table defines the criteria by which the workbook will be assessed.
| Achievement | Result |
|---|---|
| Little or no material to show development of the software. Material has been plagiarised. |
|
| Some material to show the development of the software. | |
| Detailed material that shows the development of the software which includes: pseudo-code, flowcharts and diagrams. |
Every student is expected to submit a technical brief, and each brief will be marked individually. The material is either original, or the source of the material is accurately cited.
The technical brief is intended as an opportunity to provide evidence of the work you have achieved in the assignment. The technical brief also provides a chance for you to critically analyse the results of your experimentation and present them in a clear, logical and concise manner. A person with a similar background should be able to utilise the information presented in the technical brief to develop applications to interface with your design.
The technical brief should be:
The technical brief should also include the following sections:
Each student's technical brief will be marked individually. The technical brief will be marked out of 2 and no part-marks will be given. The following table defines the criteria by which the technical brief will be assessed.
| Achievement | Result |
|---|---|
| Student makes no submission. Little or no attempt has been made to meet the above guidelines. Submission has been plagiarised. |
|
| A reasonable attempt has been made to meet the above guidelines. Submission is not necessarily presented in a clear, logical and concise manner. |
|
| Submission meets the above guidelines completely. Submission is presented in a clear, logical and concise manner. |
| Demonstration | 2% |
| Workbook | 2% |
| Technical Brief | 2% |
| Achievement | Result |
|---|---|
| Software is poorly coded. Software does not compile or link. Software does not work, nor exhibits any possibility of working. Software has been plagiarised. |
|
| Some attempt to maintain the coding style (with relevant comments). Software compiles and links with some warnings. Software works in most areas required, or has indication of substantial proportion working. |
|
| Software adheres to the coding style and has excellent comments. Software compiles and links without any warnings or errors. Software works completely. |
Each student's workbook is marked individually. If work is included which is not original, then the source of that material needs to be accurately referenced.
The workbook will be marked out of 2 and no part-marks will be given. The following table defines the criteria by which the workbook will be assessed.
| Achievement | Result |
|---|---|
| Little or no material to show development of the software. Material has been plagiarised. |
|
| Some material to show the development of the software. | |
| Detailed material that shows the development of the software which includes: pseudo-code, flowcharts and diagrams. |
Every student is expected to submit a technical brief, and each brief will be marked individually. The material is either original, or the source of the material is accurately cited.
The technical brief is intended as an opportunity to provide evidence of the work you have achieved in the assignment. The technical brief also provides a chance for you to critically analyse the results of your experimentation and present them in a clear, logical and concise manner. A person with a similar background should be able to utilise the information presented in the technical brief to develop applications to interface with your design.
The technical brief should be:
The technical brief should also include the following sections:
Each student's technical brief will be marked individually. The technical brief will be marked out of 2 and no part-marks will be given. The following table defines the criteria by which the technical brief will be assessed.
| Achievement | Result |
|---|---|
| Student makes no submission. Little or no attempt has been made to meet the above guidelines. Submission has been plagiarised. |
|
| A reasonable attempt has been made to meet the above guidelines. Submission is not necessarily presented in a clear, logical and concise manner. |
|
| Submission meets the above guidelines completely. Submission is presented in a clear, logical and concise manner. |
| Demonstration | 2% |
| Workbook | 2% |
| Technical Brief | 2% |
| Achievement | Result |
|---|---|
| Software is poorly coded. Software does not compile or link. Software does not work, nor exhibits any possibility of working. Software has been plagiarised. |
|
| Some attempt to maintain the coding style (with relevant comments). Software compiles and links with some warnings. Software works in most areas required, or has indication of substantial proportion working. |
|
| Software adheres to the coding style and has excellent comments. Software compiles and links without any warnings or errors. Software works completely. |
Each student's workbook is marked individually. If work is included which is not original, then the source of that material needs to be accurately referenced.
The workbook will be marked out of 2 and no part-marks will be given. The following table defines the criteria by which the workbook will be assessed.
| Achievement | Result |
|---|---|
| Little or no material to show development of the software. Material has been plagiarised. |
|
| Some material to show the development of the software. | |
| Detailed material that shows the development of the software which includes: pseudo-code, flowcharts and diagrams. |
Every student is expected to submit a technical brief, and each brief will be marked individually. The material is either original, or the source of the material is accurately cited.
The technical brief is intended as an opportunity to provide evidence of the work you have achieved in the assignment. The technical brief also provides a chance for you to critically analyse the results of your experimentation and present them in a clear, logical and concise manner. A person with a similar background should be able to utilise the information presented in the technical brief to develop applications to interface with your design.
The technical brief should be:
The technical brief should also include the following sections:
Each student's technical brief will be marked individually. The technical brief will be marked out of 2 and no part-marks will be given. The following table defines the criteria by which the technical brief will be assessed.
| Achievement | Result |
|---|---|
| Student makes no submission. Little or no attempt has been made to meet the above guidelines. Submission has been plagiarised. |
|
| A reasonable attempt has been made to meet the above guidelines. Submission is not necessarily presented in a clear, logical and concise manner. |
|
| Submission meets the above guidelines completely. Submission is presented in a clear, logical and concise manner. |
| Demonstration | 2% |
| Workbook | 2% |
| Technical Brief | 2% |
| Achievement | Result |
|---|---|
| Software is poorly coded. Software does not compile or link. Software does not work, nor exhibits any possibility of working. Software has been plagiarised. |
|
| Some attempt to maintain the coding style (with relevant comments). Software compiles and links with some warnings. Software works in most areas required, or has indication of substantial proportion working. |
|
| Software adheres to the coding style and has excellent comments. Software compiles and links without any warnings or errors. Software works completely. |
Each student's workbook is marked individually. If work is included which is not original, then the source of that material needs to be accurately referenced.
The workbook will be marked out of 2 and no part-marks will be given. The following table defines the criteria by which the workbook will be assessed.
| Achievement | Result |
|---|---|
| Little or no material to show development of the software. Material has been plagiarised. |
|
| Some material to show the development of the software. | |
| Detailed material that shows the development of the software which includes: pseudo-code, flowcharts and diagrams. |
Every student is expected to submit a technical brief, and each brief will be marked individually. The material is either original, or the source of the material is accurately cited.
The technical brief is intended as an opportunity to provide evidence of the work you have achieved in the assignment. The technical brief also provides a chance for you to critically analyse the results of your experimentation and present them in a clear, logical and concise manner. A person with a similar background should be able to utilise the information presented in the technical brief to develop applications to interface with your design.
The technical brief should be:
The technical brief should also include the following sections:
Each student's technical brief will be marked individually. The technical brief will be marked out of 2 and no part-marks will be given. The following table defines the criteria by which the technical brief will be assessed.
| Achievement | Result |
|---|---|
| Student makes no submission. Little or no attempt has been made to meet the above guidelines. Submission has been plagiarised. |
|
| A reasonable attempt has been made to meet the above guidelines. Submission is not necessarily presented in a clear, logical and concise manner. |
|
| Submission meets the above guidelines completely. Submission is presented in a clear, logical and concise manner. |
Each student is required to submit a separate report.
Students will not be demonstrating their project. Students will only need to submit their report and project source code by the due date/time. The workbook will not be submitted for assessment. Demonstration of the students' projects will be carried out by the lecturer and tutor after the submission date. Both students in the group will receive the same mark for the project demonstration.
Each student will submit a report for the project along with a virus-free floppy disk (not a flash disk) containing a zipped archive of the source code. The report will be submitted with a cover sheet showing the names and student numbers of both members of the group. The appendix of the report will contain a User's Manual and the printed listing of their source code.
Each student's report will be marked individually. The marking criteria for the project demonstration and report will be posted on the course web pages when the details of the project are released.
It is primary to capture the readers attention here whilst providing some general and background information.
You should give an overview of what you are doing which includes some sort of diagrams. It is recommended that the structure of the document be outlined here.
Note that it is not essential to have an abstract. Many reports have one because of it's effectiveness, however, it usually is kept very short.
It cannot be stressed enough that you must capture the readers interest in the introduction, this can easily be done by making them aware of how exciting, consequential, advantageous, useful and important the subject matter is to them. This is where you sell your product and not where you rattle off bits and pieces about your design/spec/problems.
It is expected that the entire report, and especially the introduction, should be able to be read by a person who has some knowledge of the topic/field that your report is covering. You do not have to explain everything step by step, but building on from basic explanations and finally leading into the finer points of interest.
There shouldn't be a formal theory section (i.e. it should be throughout the document) however it is important that basic relevant theory be discussed where appropriate but not so as to make the report read like a text book.
Make sure you clearly point out the fundamental theories, methodologies and ideas that form the backbone of why and what your doing.
It is most important for your explanations to logically follow your design steps so that the reader may not only correctly arrive at your design but also understand how you got there. This means that you must explain clearly, the reasoning behind any design decisions you have made. Make sure this is done effectively by being concise, structured and trying to make design issues plainly obvious. (This can be quite challenging !)
Be consistent with the style and tense used in the article.
Mention any problems that are usually encountered in any part of the design.
Diagrams are an indispensable aid to the reader so make sure you use them to full effect (i.e. make sure you use flow charts for code, block diagrams, schematics etc.)
Make sure all your diagrams and code listings (be they in the document or in the appendix) are integrated into your discussion.
Watch for mistakes in your spelling and your grammar. If you have problems with this use a grammar and spelling checker or better still, get a friend to proof read your document.
A separate conclusion is always good, even if only to make your report draw to a natural end.
All figures, diagrams and tables must be numbered and have appropriate captions. The quality of these will also be considered, e.g. correct units of measure used where appropriate.
Code listings of your work should be found in the appendices but feel free to integrate important pieces of code as figures into your document to aid the reader. Remember that all appendices and references in your bibliography must be referred to within the report.
No hand written amendments to your report.
Make sure the document is structured in a logical manner and pages are numbered.
The code format must follow the recommended C coding standard as detailed in the Required Coding Style document. The code must be well commented with no debug information. Present only that code that you have written or modified as listings in the appendices.
A two hour final examination will be held during the final examination period. This exam will be closed-book and will require written-answer questions. You may bring a battery-operated non-programmable calculator, but I do not anticipate it will be needed. Programmable calculators and other computing or communication devices are NOT permitted.
The final examination will be based only on material provided and learnt in the laboratory sessions. The intention of the examination is two-fold:
1) to ensure that the team members have equal knowledge of the work undertaken in the laboratory and presented in all the written reports; and
2) that each member of the team is able to apply this knowledge to a set of problems very closely related to those undertaken during the course.
An overview of the University’s assessment-related policies can be found on myAdvisor (http://www.uq.edu.au/myadvisor/index.html?page=2910).
Academic Integrity
It is the University's task to encourage ethical scholarship and to inform students and staff about the institutional standards of academic behaviour expected of them in learning, teaching and research. Students have a responsibility to maintain the highest standards of academic integrity in their work. Students must not cheat in examinations or other forms of assessment and must ensure they do not plagiarise.
Plagiarism
The University has adopted the following definition of plagiarism:
Plagiarism is the act of misrepresenting as one's own original work the ideas, interpretations, words or creative works of another. These include published and unpublished documents, designs, music, sounds, images, photographs, computer codes and ideas gained through working in a group. These ideas, interpretations, words or works may be found in print and/or electronic media.
Students are encouraged to read the UQ Academic Integrity and Plagiarism policy (http://www.uq.edu.au/hupp/index.html?page=25128) which makes a comprehensive statement about the University's approach to plagiarism, including the approved use of plagiarism detection software, the consequences of plagiarism and the principles associated with preventing plagiarism.
As a student you have a responsibility to incorporate feedback into your learning; make use of the assessment criteria that you are given; be aware of the rules, policies and other documents related to assessment; and provide teachers with feedback on their assessment practices.
There are certain steps you can take if you feel your result does not reflect your performance. Please refer to the myAdvisor web site. (http://www.uq.edu.au/myadvisor/index.html?page=2953&pid=2910)Further to the statement on academic integrity and plagiarism above, students are required to read and understand the ITEE policy on Student Misconduct (http://www.itee.uq.edu.au/about_ITEE/policies/student-misconduct.html).
The policy and procedure for late arrival or non-attendance at centrally controlled examinations is set out in the University's Examinations policy (HUPP 3.30.5), sections 8 and 10.2.
The way in which late arrival at a School-controlled examination is dealt with will be at the discretion of the course coordinator, who may be guided by the policy for centrally controlled exams.
Where an adjustment is made to an accredited program, it is the responsibility of the relevant Faculty to liaise with professional and registration bodies regarding the acceptability of the change/s.
Below is a table showing the relationship between the learning objectives for this course and the broader graduate attributes developed, the learning activities used to develop each objective and the assessment task used to assess each objective.
| Learning Objectives | ||||||
| 1 | 2 | 3 | 4 | 5 | 6 | |
| Learning Activities | ||||||
| Assignment 1 (Discussion) |
 |
|||||
| Assignment 1 (Laboratory ) |
|
|
|
|
||
| Assignment 2: (Discussion) |
|
|||||
| Assignment 2: (Laboratory ) |
|
|
|
|
||
| Assignment 3 (Discussion) |
|
|
||||
| Assignment 3 (Laboratory ) |
|
|
|
|||
| Assignment 4 (Discussion) |
|
|
||||
| Assignment 4 (Laboratory ) |
|
|
|
|
||
| Assignment 5 (Discussion) |
|
|
||||
| Assignment 5 (Laboratory ) |
|
|
|
|
||
| PROJECT (Discussion) |
|
|
||||
| PROJECT (Laboratory ) |
|
|
|
|
|
|
| Assessment Tasks | ||||||
| Assignment 1 - Serial Port |
|
|
|
|
||
| Assignment 2 - Netphone: LCD, Keypad and Heartbeat |
|
|
|
|||