(T1) Assessment Brief
Description
Throughout the module you will be provided with a set of three “practical project options” sheets. These sheets will detail a set of projects which can be chosen focused around the main topic groups and learning outcomes covered in this module.
Each of these sheets will contain one or more “projects” for you to choose, complete and document for the main assessment. Details of the projects available within each sheet, along with specific requirements on what is expected from each of these projects, will be available on Moodle.
You will be expected to choose and attempt at least one of the projects from the three task sheet and to document your efforts in a project log report. Though for those students who wish to attempt multiple projects, this will also be allowed, we recommend you consolidate and detail at least one of these projects to the best quality possible before moving to another. The highest quality project attempt within your submission will be used as the mark for grade calculation of the coursework. You will not be penalised for only attempting one project, the choice is solely up to your preference.
D1 Milestone quizzes
A series of milestone quizzes will be ran in-class throughout the semester, these will be attempted via Moodle in your scheduled lab session.
We will use Bloom’s Taxonomy (see Figure 1) as a model to structure your learning encouraging you to develop your basic knowledge and skills in; remembering, understanding and applying the basic ideas based on assessing these within the Moodle quizzes spread throughout the semester. After you have had the opportunity to develop your base-level skills and knowledge you will then be asked to; analyse (requirements analysis), create (design and develop the system) and evaluate (judge how well the final system meets the requirements) your system.
Figure The assessment structure attempts to leverage Bloom’s taxonomy of learning to allow you to effectively build your skills and knowledge with the content
Students who are late to their quizzes will be offered the opportunity to request a catch-up quiz for that quiz instance by filling out a form discussing their reason behind issues with engagement, they will also be asked as part of this to produce an action plan to clearly discuss how they will work on improving their engagement in future labs / quizzes.
Students who do not achieve a threshold mark of 60% average in the in-semester quizzes, may be offered a retrieval quiz capped at 60% in the semester 2 assessment period during May. Catch-up quiz forms for late students will be available for the retrieval quiz, but this will result in a capping for your awarded quiz mark to 60%.
Figure How the quiz retrievals work
D2.1 Draft project log report and planning document [20%]
Each project will consist of multiple stages, for this submission we are only looking for evidence, discussion and reflection on the initial setup of your base operating system environment along with a discussion and justification of your plans to complete the rest of the project.
This document should be submitted by you individually whether you have worked on your own or in a pair and should contain reflections and justifications from your perspective along with a clear indication of who did what (when relevant). This allows us to clearly understand how you specifically are engaging with the assessment and what you understand so far about it. It also helps us to individually assess your contributions to completing the project to ensure students are marked fairly for their contributions.
The submission should contain:
Project title page
Your name and student ID
(Possibly) your partners name and student ID (when relevant)
Discussion and reflection of progress thus far: The discussion should attempt to detail the what, why and how of this stage, i.e.,
What?
What are the key components, systems or concepts under scrutiny when installing this base operating system environment?
Why?
Why is it important for this project stage be undertaken?
Why do we want to have these particular key components setup and configured?
Why is setting up this base system important to lay a strong foundation for the rest of the project?
How?
How did you setup this base operating system environment thus far?
How do the components, systems or concepts under discussion relate to each other to form a more coherent ‘whole’?
This should be accompanied by reflective comments
Discussion and justification of planning for the rest of the project
What is the overall aim of the project?
What are the objectives that should be achieved as part of this?
Why is this valuable?
To demonstrate how your learning will improve your skills and knowledge
To demonstrate the ability to meet the needs of the identified stakeholders for the project
How are you planning to complete the rest of the project stages to meet the aim and objectives identified?
What is your “roadmap” to complete the project?
Note for each of these aspects there should be
• Evidence: Provide appropriate evidence to support the case that the base operating system environment has been successfully installed and can be built upon for the rest of the project. Also provide appropriate evidence of the planning undertaken thus far. Each screenshot / figure of evidence should clearly indicate the student ID of the person presenting this evidence – e.g. you may set up the user account for the operating system to specify your student IDs for the username.
• Justification:
All relevant major decisions, actions taken, or arguments put forth should be justified in a clear and rational manner where the reader is able to understand the reasoning behind your thoughts
• Citations and Referencing:
The discussion should be supported by appropriate use of referencing and citations, this can be used to provide further external evidence for your justification
• Structure:
The report should be structured in a clean, clear and coherent style in a manner that makes it easy for the reader to follow.
We will be looking for:
Clarity and structure of report presentation.
A compelling and engaging report that details both practical and theoretical aspects of the tasks undertaken.
Use of formal, professional and technical language
Inserting Tables, Graphs and Figures with clear units of measure in visualisations
Discussing the significance of evidence presented
Use of academic references to support the discussion thus far.
Students who do not achieve a threshold mark of 60% average in the draft and planning document, may be offered the ability to resubmit this document capped at 60% within the semester 2 assessment period during May. This updated planning document should aim to take on board the feedback provided both on-line and in-class to students to discuss their plans of how the project would be completed, along with justifications of their approach.
Figure How the planning document retrieval works
D2.2 Final Project log report [60%]
This will be the completed final project log report containing the evidence, discussion, justification and reflection across the entire project.
Each project will consist of multiple stages, when attempting and discussing each stage of the project, try to ensure that you have covered the following key areas within your discussion:
• Evidence: Provide appropriate evidence to support the case that the stage has been attempted and completed successfully. Each screenshot / figure of evidence should clearly indicate the student ID of the person presenting this evidence – e.g. you may set up the user account for the operating system to specify your student IDs for the username.
• Discussion and reflection: The discussion should attempt to detail the what, why and how of the stage, i.e.,
What: What project stage is being undertaken? What are the key components, systems or concepts under scrutiny?
Why: Why would the project stage be undertaken? Why do we have these key components or systems? Or why is the concept being explored important to understand / relevant to the topic area?
How: How was the project stage attempted? How do the components, systems or concepts under discussion relate to each other to form a more coherent ‘whole’? This should be accompanied by reflective comments
Discussing the significance of results reported
Use of academic references to support the discussion of all relevant tasks.
Referencing Style
BCU Harvard
More information on referencing is available here: https://www.bcu.ac.uk/library/services-and-support/referencing
Use of Artificial Intelligence
Whilst AI tools can be helpful in assisting learning, when it comes to assessment, the Academic Misconduct Procedure is clear that this should be a student’s own original work and not the work of other people or AI tools. The Use of AI Tools – Student Guidelines follows the same guidelines your lecturers use. If you are unsure of whether AI is appropriate within your work, please read the guidelines or ask your lecturer. For advice and guidance around academic writing, please visit the Centre for Academic Success.
RESTRICTED; You MUST NOT use any form of Artificial Intelligence in this assessment unless specifically authorised for reasonable adjustments. You MAY use non-generative tools such as a spell-check, basic grammar check (non-generative), calculator or similar. If you have any doubts about using an AI tool, please consult the Student AI Guidelines or ask your tutor.
Academic Integrity Guidance
Academic Integrity means completing and submitting your own original work while properly acknowledging sources. Following academic conventions, such as referencing and citation, helps avoid plagiarism. The Centre for Academic Success offers resources on Moodle, workshops and 1-2-1 support to improve skills like paraphrasing and referencing.
Academic Misconduct
Academic misconduct is conduct that has or may have the effect of providing you with an unfair advantage by relying on dishonest means to gain advantage and which therefore compromises your academic integrity.
The Academic Misconduct Procedure sets out the process we will follow, and the penalties we may apply, in cases where we believe you may have compromised your academic integrity by committing academic misconduct.
Word Count
The maximum word count for this module assessment is shown on Page 1. A +10% margin of tolerance is applied, beyond which nothing further will be marked. Marks cannot be awarded for any learning outcomes addressed outside the word count.
The word count refers to everything in the main body of the text (including headings, tables, citations, quotes, lists etc.). Everything before (i.e. abstract, acknowledgements, contents, executive summaries etc.) and after (i.e. references, bibliographies, appendices etc) is not included in the word count limit.
Submission Information
Present any written aspects of the assessment using font size 11 and using 1.5 spacing to allow for comments and annotations to be added by the markers. Complete the appropriate cover sheet for this assessment and append your work. This assessment will be marked anonymously and should show your student number only.
Submit this coursework assessment task via Moodle. Submissions should be provided in Microsoft word (.docx) or (text-based) PDF format.
Late Submission
Where you are required to submit assessment by a certain deadline but you fail to meet the deadline, your mark will be reduced in accordance with the Late Submissions Policy. This Policy does not apply where the assessment is ‘in-person’ such as exams and in-class tests.
For support on submission, please review the Submitting Your Assignment e-learning resource.
if the submission is made between 1 and 24 hours after the published deadline the original mark awarded will be reduced by 5%. For example, a mark of 60% will be reduced by 3% so that the mark that the student will receive is 57%.
if the submission is made between 24 hours and one week (5 working days) after the published deadline the original mark awarded will be reduced by 10%. For example, a mark of 60% will be reduced by 6% so that the mark the student will receive is 54%.
if the submission is made after 5 days following the deadline, your work will be deemed as a fail and returned to you unmarked.
The reduction in the mark will not be applied in the following two cases:
the mark is below the pass mark for the assessment. In this case the mark achieved by the student will stand.
where a deduction will reduce the mark from a pass to a fail. In this case the mark awarded will be the threshold (i.e.,40%).
Please note: If you submit a re-assessment late, then it will be deemed as a fail and returned to you unmarked.
D2.1 Project Log report draft (base configuration) with Planning
D2.2 Final Project Log report [60%]
——————————————- FOR STAFF ONLY——————————————-
Module Title: Applied Operating Systems
Module Code: CMP4265
Assessment Type (delete as appropriate)
Coursework | Level
4 | Weighting
100% | Word Count
D1 N/A
D2.1: 1500 Words
D2.2: ~5000 words
Submission Date
D1: Until 04/05/2026
D2.1: 27/03/2026
D2.2: 18/05/2026 | Submission Time
D1: N/A
D2.1: 15:00
D2.2: 15:00 | Module Leader
E Cooper | Time Limit (for in person or oral assessments)
D1: 20-30 minutes
D2.1: N/A
D2.2: N/A
Assessment Information
Assessment Task (with genre/type) | Project Log Report – Individual/Paired Coursework
Assessment Title | Applied Operating Systems: Practical Project Log Report and Reflection
Things to include: | This is an “optionally individual or group-based”, but still individually-assessed coursework assessment where your project will be selected from those listed within the 3 “practical project options” task sheets (which are available on Moodle). Starting from week 4, the module team will begin issuing a “practical project options” sheet over the subsequent weeks. You must select your practical project from the list of options available in these sheets.
You may work on this project individually or in a pair (up to 2 students), if working in a pair you must submit your own copy of the log report which emphasises your specific contributions to the project.
You are required to attempt at least one project from the three “practical project options” sheets issued and document your work in the form of a log report, with supporting screenshots and reflective comments. If you wish to attempt more than one of the projects, then the project attempt which is of the highest quality will be what provides your mark for the coursework.
For each project, you will need to include the following in your project log report:
Evidence of Project Planning (e.g. did you do any background research into the project? what resources were needed?, what design considerations are there?, justifications of your planned approach, etc)
Evidence of Project Completion (e.g. detailed screenshots which walk through any coding, setup, configuration and deployment/running of your system with the relevant commands/output shown)
Discussion and Reflection on what, why, how and when the project was completed
Justification of key actions or decisions you took
Use of References and background research to support your approach and to understanding
Clear structure, using technical and academic language where relevant
Screenshots and other relevant supporting evidence are mandatory to demonstrate your work clearly and must be labelled/captioned appropriately.
You must perform these tasks in an Operating System installation which you have set up yourself. You are required to create and use a user account based on your student ID (e.g. S123456789), and this student ID must be clearly visible in all screenshots (especially those involving the terminal/shell) as verification of ownership and originality of your work.
Completion of this assessment will address the following learning outcomes:
1 | Administer an operating system using appropriate tools and techniques.
2 | Troubleshoot simple hardware and software issues using appropriate methods.
3 | Deploy and configure software to meet a defined need.
4 | Adhere to appropriate professional and academic standards.
Learning Outcomes | 1,2,34 | 1,2,3,4
Assessment
Criteria | Base system setup | Planning the project
This will involve showing some initial discussion and evidence of system setup, namely installation of the base Operating System which will be used for the project along with making it clear which project you have chosen.
This should follow the needs of the project selected from the project sheet. | This will involve presenting a concrete and well justified plan of how you will complete the project.
What background research have you performed?
What software will be used?
How will you setup and configure this system?
How will you evaluate what you have done against the project criteria?
Weighting: | 10%
(50% of 20)
Grading
Criteria
0 – 29%
F | The evidence provided is highly unsatisfactory based on what would be expected at your level of study and has many major issues.
No discussion present.
The discussion makes no attempt at citation or referencing of appropriate sources.
The discussion has no apparent consistent structure.
30 – 39%
E | The evidence provided is not yet to a satisfactory level of quality and major issues are present.
Very little to no discussion present.
The report has no apparent consistent structure
40 – 49%
D | The evidence presented is to an emergent/satisfactory level of quality based on what would be expected at your level of study, though various issues may still be present and improvements made.
Some surface level discussion may be present which suggests some basic, emergent understanding of topic content but this could be greatly expanded in terms of the depth/breadth of knowledge presented. Little to no reflection is present.
Very few points are justified in appropriate detail and they could be expanded upon further.
Very little to no use of appropriate citations and referencing is evidenced.
The discussion has some aspects of consistent structure but this could be greatly improved.
50 – 59%
C | The evidence presented is to a reasonable level of quality based on what would be expected at your level of study, though some issues may still be present and improvements made.
A reasonable level of discussion is presented which suggests a decent grasp of some of the core concepts, but this could be expanded further in terms of the depth / breadth of knowledge presented. Some very minor examples of reflection are present.
Some major points are justified in appropriate detail, but this could be expanded upon further.
The discussion includes some attempt at citing and referencing external sources, though this could be greatly improved. There may be various issues with citations and reference formatting, along with how the few sources presented are leveraged.
The discussion has a reasonably consistent structure but this could be somewhat improved, as some issues may still be present or improvements made.
60 – 69%
B | The evidence presented is to a good level of quality based on what would be expected at your level of study, though some reasonably minor issues may still be present and improvements made.
A good level of discussion is presented which suggests a grasp of many of the core concepts, but this could be expanded upon further in terms of the depth / breadth of knowledge presented.
The discussion is accompanied by some examples of reflective comments regarding how you have approached enhancing your understanding of the topic and how you might further work on enhancing your skills and knowledge in the future.
Attempts are made to justify points in a reasonably logical manner, supported by evidence. Though this could be improved further.
The discussion is supported by some appropriate references and citations of external sources. There may be some issues with the way that your discussion leverages these sources as well as the citation and referencing style presented.
The discussion has a consistent structure which makes it easy for the reader to follow, some minor issues may still be present or improvements made.
70 – 79%
A | The evidence presented is to a very good level of quality based on what would be expected at your level of study, though some reasonably minor issues may still be present and improvements made.
A very good level of discussion is present which suggests a grasp of almost all the core concepts, however the depth of knowledge presented could be enhanced further.
The discussion is accompanied by high-quality reflective comments regarding how you have approached enhancing your understanding of the topic and how you might further work on enhancing your skills and knowledge in the future.
Most major points are justified in appropriate detail.
Much of the discussion is supported by appropriate references and citations of external sources. There may be some very minor issues with the way that your discussion leverages these sources as well as the citation and referencing style presented.
80 – 89%
A+ | The evidence presented is to a very high level of quality based on what would be expected at your level of study, though some very minor issues may still be present and improvements made.
An excellent level of discussion is present which suggests a grasp of all the core concepts, however the depth of knowledge presented could be enhanced further.
All major points are justified in appropriate detail.
Most of the discussion is supported by appropriate references and citations of external sources. There may be a few very minor issues with the way that your discussion leverages these sources as well as the citation and referencing style presented.
90 – 100%
A* | The evidence presented is to an excellent level of quality based on what would be expected at your level of study, though some reasonably minor issues may still be present.
An outstanding level of discussion is present, which suggests a grasp of all the core concepts, however the depth of knowledge presented could be enhanced further.
All of the discussion is supported by appropriate references and citations of external sources. There are little to no issues with the way that your discussion leverages these sources, as well as the citation and referencing style presented.
Administering:
Managing manipulating and optimising | Troubleshooting: Managing, manipulating and optimising | Deploying | Adherence to appropriate professional and Academic standards
This will involve detailing the process by which you complete the project stage | This will involve assessing the justification of your approach taken, and also your thought process when attempting to resolve any issues which might occur | This will involve you demonstrating the functionality of the finalised product | This will involve you presenting the report and its results in such a way that informs and justifies the value to stakeholders
30%
(50% of 60) | 12%
(20% of 60) | 6%
(10% of 60)
The evidence provided is highly unsatisfactory based on what would be expected at your level of study and has many major issues.
The discussion has no apparent consistent structure
Staff Use Only: Retained Work Record
Details of Retained Work: | Final written assignment (Log Report) for module CMP4265 – Applied Operating Systems.
Location of Retained Work: | Moodle (Module CMP4265 – Assignment Submission Point)
Type of Work Retained (tick all that apply): | Written, Photo (screenshots within report), Source code
The main component of the submission is a written log report) documenting the student’s understanding and execution of practical operating system tasks. The report includes technical explanations and reflective commentary.
Screenshots are embedded throughout the report to provide visual evidence of task execution, such as terminal commands, code outputs, configuration changes, and system monitoring. Each screenshot is labelled and discussed within the text.
Students must perform tasks in an Operating System environment which they have set up themselves. They are required to create and use a user account based on their student ID, and this student ID must be clearly visible in all terminal screenshots.
Contact us via WhatsApp or email with this assignment title and we'll send you the complete solution — including step-by-step explanation, references, and Turnitin report.