Computer Systems and Networks

 IMAT5122 – Computer Systems and Networks

Deferral/Resit COURSEWORK 2020/2021

 

Module name:		Computer Systems and Networks
Module code:		IMAT5122
Title of the Assignment:		Deferral/Resit CW - Linux System Change Logger Script
This coursework item is:				Summative
This summative coursework will be marked anonymously								No
The learning outcomes that are assessed by this coursework are: 1.     Demonstrate a systematic understanding of knowledge and show a critical awareness of current problems in computer systems and networks. 2.     Show originality in the application of knowledge as well as systematic understanding of knowledge and comprehension of the underlying concepts and principles associated with computer systems and networks. 3.       Critically evaluate current computer system and networking technologies and methodologies and develop critiques of them.
This coursework is:			Individual
This coursework constitutes 50 % of the overall module mark (and will be capped if it is a resit).
Date Set:	7th December 2020
Date & Time Due:	11th January 2021 at 14:00
Marked coursework and feedback will be available to you on: If for any reason this is not forthcoming by the due date your module leader will let you know why and when it can be expected. The Head of Studies (headofstudies-tec@dmu.ac.uk) should be informed of any issues relating to the return of marked coursework and feedback. note: All marks and grades are provisional until moderation is complete and confirmed by the relevant Assessment Board, and may change.					Feedbacks will be available within four weeks after submission.
When completed you are required to submit your coursework to: The report needs to be uploaded to Turnitin via a link on Blackboard
Late submission of coursework policy: Late submissions will be processed in accordance with current University regulations which state: “the time period during which a student may submit a piece of work late without authorisation and have the work capped at 40% [50% at PG level] if passed is 14 calendar days. Work submitted unauthorised more than 14 calendar days after the original submission date will receive a mark of 0%.  These regulations apply to a student’s first attempt at coursework. Work submitted late without authorisation which constitutes reassessment of a previously failed piece of coursework will always receive a mark of 0%.”
Academic Offences and Bad Academic Practices: These include plagiarism, cheating, collusion, copying work and reuse of your own work, poor referencing or the passing off of somebody else's ideas as your own. If you are in any doubt about what constitutes an academic offence or bad academic practice you must check with your tutor. Further information and details of how DSU can support you, if needed, is available at: http://www.dmu.ac.uk/dmu-students/the-student-gateway/academic-support-office/academic-offences.aspx and http://www.dmu.ac.uk/dmu-students/the-student-gateway/academic-support-office/bad-academic-practice.aspx
Tasks to be undertaken: See detailed description on next pages.
Deliverables to be submitted for assessment: Report and any supporting material required to assess the work
How the work will be marked: See marking scheme on next pages
Module leader/tutor name:		Bello Shehu / Tarjana Yagnik
Contact details:		belloshehu.bello@dmu.ac.uk / tarjana.yagnik@dmu.ac.uk

 

You are an IT support engineer and you have been asked to build a GNU/Linux bash script that monitors a computer system and user activity regularly and logs key information. You need to create a script “SysMonitor.sh” that automatically and regularly writes to a log file “SysMonitor.log”. The log file will need to contain time-stamped detailed information about significant changes to the following:

a)    Users currently logged in

b)    Current processes

c)    Top 5 RAM utilizing processes

d)    Devices plugged in (e.g. USB)

e)    Disk usage

1.    Overall disk usage

2.    The user’s home directory (/home/someuser…)

3.    Other key directories

f)     Network interfaces and their states

g)    Any other relevant information…

The script will need to be written to extract only key details about the changes to the computer system such as listed above and add them to an ever-growing log file. Hence the log file should consist of easily readable key details only. For pass level you are expected to write a script that satisfies a) to e) listed above. For higher marks you are expected to add relevant extra information (e.g. monitoring OS system file changes, monitoring installed applications, etc.) and relevant features, more easily readable output (e.g. HTML), configurable log levels (e.g. verbose, debug, standard and key-details only), etc.

 

Note that you should only use common pre-installed command line tools and your work should not rely on additional programs / tools / libraries / etc. If you are unsure about any detail of this coursework please ask your tutor.

Also you may be called to present and demonstrate the system and report if your module tutor is in doubt. Failure to proof ownership of your coursework may lead to a fail!

 

What should be submitted to Blackboard before the due date:

1. Documentation (5 pages maximum (excluding title page, bibliography, appendices etc.) , minimum font size 10):

a)    A specification of how to install and use the script(s) (max 1 page)

b)    Design consideration – what commands you used, how you constructed your script(s) and justification why you chose these techniques. (1 page)

c)    Extensive test results with exemplary log and screen output. (1 page)

d)    Conclusion / Reflection – Advantages and disadvantages of your techniques / work (1 page)

e)    Bibliography – An exhaustive list of references you used in your work (1 page)

    II.        One ZIP file will need to be uploaded to Blackboard, containing all coursework relevant files including scripts and exemplary log files.

The documentation needs to be submitted to Turnitin assignment submission link on blackboard while the ZIP file needs to be uploaded separately via the Upload link on blackboard.

 

 

Marking Scheme

 

	0-5	6-11	12-17	18-23	24-30
GNU/Linux Command Usage	No or only little ability to use basic GNU/Linux commands. No or only little attempt solving the coursework problem.	Little use of basic GNU/Linux commands. Little attempt solving the coursework problem.	Fair use of basic and more advanced GNU/Linux commands. Fair attempt to solve coursework.	Good use of basic and more advanced GNU/Linux commands. Well executed piece of coursework.	Very good use of basic and more advanced GNU/Linux commands. Very well executed piece of coursework.
	0-3	4-7	8-11	12-16	17-20
GNU/Linux Bash Scripting	No or only little ability to use basic GNU/Linux bash scripting.	Little use of basic GNU/Linux bash scripting.	Fair use of basic and more advanced GNU/Linux bash scripting.	Good use of basic and more advanced GNU/Linux bash scripting.	Very good use of basic and more advanced GNU/Linux bash scripting.
	0-4	5-9	10-14	15-19	20-25
Extra relevant information / extra relevant features	No, only little or non-relevant extra information or extra features added to the work	Only little or not very relevant extra information or extra features added to the work	Some extra information or extra features added to the work. These extras are fairly relevant.	Good extra information or extra features added to the work. These extras are mostly relevant.	Excellent extra information or extra features added to the work. These extras are highly relevant.
	0-4	5-9	10-14	15-19	20-25
Report and Referencing	Poorly written, unstructured, unclear justification, no testing, none or entirely inappropriate referencing.	Understandable, little structure, some justification, little testing, adequate coverage of sources but lacking sufficient detail in referencing.	Reasonably written, adequate structure, good justification, well tested, adequate coverage of sources but lacking some detail in referencing.	Well written, good structure, good justification, thorough testing and coverage of sources with sufficient detail in referencing.	Very well written, very good structure and excellent justification, thorough testing, comprehensive, informative and relevant referencing.
Marking comments and feedback:					Final Mark