Computer Fundamentals

 

Solent University Coursework Assessment Brief

1 Assessment Details

1.1 Module designator: COM709 Summer 2020

Unit Title: Computer Fundamentals

Unit Code: COM709

Level: 7

Assessment Title: Personal Learning Record

Assessment Number: 1

Assessment Type: AE1

Wordcount restrictions: Between 20 to 200 lines per program

Consequence of failing word count There is no penalty

Individual/Group: Individual

Assessment Weighting: 100%

Issue Date: Week commencing 21/10/2019

Hand In Date: 13 September 2020 (4 PM local time)

Planned Feedback Date: 4 weeks

Mode of Submission: On-line

Number of copies to be submitted: 1

Anonymous Marking Anonymous marking

1.2 Assessment Task

ˆ You will create several computer programs in Python.

ˆ These programs must run on the examiners computer and create the

correct output according to each given exercises requirements speci-

cation.

1

ˆ If your program does not run you will FAIL that part.

ˆ Your programs must be commented to demonstrate knowledge of the

ideas for each exercise. You will be graded on the comments too.

ˆ You should keep all the information within one folder. The nal sub-

mission is a .zip archive of this folder. Within this, each exercise should

go in its own folder along with any necessary components to run the

program.

ˆ Your zip le must be named as your student number, for example;

Q12341234.zip

ˆ Inside it, folders must be EXACTLY named "exercise-01", "exercise-

02" etc

ˆ Inside each folder your main programs must be EXACTLY named

"program-01.py", "program-02" etc.

1.3 Evidencing your learning

A learning record is to be presented in code comments. These must conform

to Python "docstring" guidelines using triple quoted docstring blocks which

must return readable values when invoked with doctest.

Your program portfolio is to be built-up as a learning record throughout

the unit. Do not attempt to write all the programs in the last week - this

assignment has a signifant workload and must be spread over a suitable time-

frame. Your commented code should show evidence of evolving engagement

with, and understanding of, techniques covered by completing a number of

given tasks using appropriate computer software, algorithms, datastructures,

and online sources.

Code and its comments should make clear:

ˆ The purpose of the program. What it does.

ˆ Methods used. What algorithms, data structures and techniques make

it work

ˆ Initial conditions or pre-requisires. Any libraries, environments, paths

needed.

ˆ Input conditions. What data goes in. What is its format. Size limita-

tions?

2

ˆ Output expected. What is the data output format?

ˆ Error conditions. Are any exceptions or bad input handled?

PLEASE for ALL activities refer to the information given on SOL where

the exercises will be described in documents and/or video lectures.

1.4 Areas of work

As a heads-up, the program exercises will apply to roughly the following

areas, which do not necessarily match one-to-one with the lecture structure.

This is not a denitive list, but a guide only. To complete the tasks you will

be required to do additional reading and research:

1.4.1 Computer hardware

This task will test you on an area related to digital hardware, architecture,

number systems, code execution etc.

1.4.2 Algorithms and data structures

One task will require you to solve a problem that requires a good understand-

ing of data structures and algorithms like searcing, sorting or comparing

values.

1.4.3 Operating systems

Completing this task will require you to understand something about oper-

ating systems, scheduling, processes, lesystem directories and paths etc

1.4.4 Computer networking

This task will involve a knowledge of networking principles, IP addresses,

ports, fetching a URL, sockets or similar

1.5 Grading criteria

The following table sumarises the grading criteria. These are explained be-

low.

3

Criteria

(percent)

F3-F1 D3-D1 C3-C1 B3-B1 A4-A1

Correctness

(70)

wont run some er-

rors

pass

most

tests

pass all

tests

perfect

output

Comments

(30)

none few, con-

fusing

many

clear

complete doc

standard

1.5.1 Correctness 70%

Correctness measures whether your progam does what it should, that it

handles all input and produces accurate and meaningful output. If a program

cannot be made to run at all you will get an F grade. This may be because

you handed in a zip le that doesn't unpack, or unpacks into incorrect folder

structure, or you used the wrong version of Python, did not include a vital

le or other reason. If your program will not run in the automated program

test suite you automatically get F grade. If your program runs but gives

the wrong answers to input then you will get a D grade. Errors may be

failures to handle input ranges, numerically inaccurate output, or failure to

terinate. If your program passes most of the tests you will get a C grade.

Most peoples programs will pass some but not all tests. Tests may include

malformed strings, very large or small numbers, incomplete or missing input

parameters and so on. If your program passes some or moat of these attempts

to trick it you will get a B grade. If you program produces perfect output,

eciently, and cannot be hacked or made to break in any way you will be

awarded an A grade.

1.5.2 Comments (30%)

Comments are the documentation that explain your code, how it works, what

input it should be able to handle, what output the user can expect and so on.

In Python there is a very specic set of rules for creating good comments.

You need to use triple quoted "docstrings" which will be explained in a

lecture. Comments provide evidence that you know what your code does

and did not just copy it from a website. They help other programmers (and

professors marking your work) to understand what you were thinking when

you wrote some code. Therefore they help other programmers, and yourself

at a later date, to debug faulty code. In python, docstrings can be turned

into readable documentation by an automated process. This will be used in

the marking process. If your comments are missing you will get an F grade.

4

A few comments that don't really help, or seem confused will earn you a

D grade. If you include a fair amount of docstring comments, at least for

each function and the main program, you will get a C. Extensive comments

that describe the algorithm and input-output conditions will be worth a B.

Finally, if you include a complete, well written doctest suite that performs

you own automated testing of the program and writes its own report you

can have an A grade.

1.6 Academic context

1.6.1 Learning Outcomes

This assessment will enable students to demonstrate in full or in part the

learning outcomes identied in the unit descriptors.

Late Submissions

Students are reminded that:

If this assessment is submitted late i.e. within 5 working days of the sub-

mission deadline, the mark will be capped at 40% if a pass mark is achieved;

If this assessment is submitted later than 5 working days after the submission

deadline, the work will be regarded as a non-submission and will be awarded

a zero; If this assessment is being submitted as a referred piece of work (sec-

ond or third attempt) then it must be submitted by the deadline date; any

Refer assessment submitted late will be regarded as a non-submission and

will be awarded a zero.

http://portal.solent.ac.uk/documents/academic-services/academic-handbook/

section-2/2o-assessment-principles-and-regulations.pdf?t=1534423842941

1.6.2 Extenuating Circumstances

The University's Extenuating Circumstances procedure is in place if there are

genuine circumstances that may prevent a student submitting an assessment.

If students are not 't to study', they can either request an extension to

the submission deadline of 5 working days or they can request to submit

the assessment at the next opportunity (Defer). In both instances students

must submit an EC application with relevant evidence. If accepted by the

EC Panel there will be no academic penalty for late submission or non-

submission dependent on what is requested. Students are reminded that EC

covers only short term issues (20 working days) and that if they experience

longer term matters that impact on learning then they must contact the

Student Hub for advice.

A summary of guidance notes for students is given below:

5

http://portal.solent.ac.uk/documents/academic-services/academic-handbook/

section-2/2p-extenuating-circumstances.pdf?t=1534423896787

1.6.3 Academic Misconduct

Any submission must be students' own work and, where facts or ideas have

been used from other sources, these sources must be appropriately referenced.

The University's Academic Handbook includes the denitions of all practices

that will be deemed to constitute academic misconduct. Students should

check this link before submitting their work.

Procedures relating to student academic misconduct are given below:

http://portal.solent.ac.uk/support/official-documents/information-for-students/

complaints-conduct/student-academic-misconduct.aspx

1.6.4 Ethics Policy

The work being carried out by students must be in compliance with the

Ethics Policy. Where there is an ethical issue, as specied within the Ethics

Policy, then students will need an ethics release or an ethical approval prior

to the start of the project.

The Ethics Policy is contained within Section 2S of the Academic Hand-

book: http://portal.solent.ac.uk/documents/academic-services/academic-handbook/

section-2/2s-university-ethics-policy.pdf

1.6.5 Grade marking

The University uses a letter grade scale for the marking of assessments.

Unless students have been specically informed otherwise their marked as-

signment will be awarded a letter grade. More detailed information on grade

marking and the grade scale can be found on the portal and in the Student

Handbook.

http://portal.solent.ac.uk/documents/academic-services/academic-handbook/

section-2/2o-annex-2-assessment-regulations-grade-marking-scale.

pdf?t=1534424273208

Guidance for online submission through Solent Online Learning (SOL)

http://learn.solent.ac.uk/onlinesubmission

6