The University of the South Pacific

School of Computing, Information & Mathematical Sciences

IS104: Computing for Science and Technology

Assignment 3
Learning Outcome:
 Describe the fundamentals of computing and programming.
 Apply programming skills to applied science problems
Weight: 30%
Due Date: 12th June, 2020.

Part 1: Programming – Syracuse Sequence (20%)

1.1 Problem Statement

The Syracuse (also called the Collatz Hailstone) sequence is generated by starting with a
natural number and repeatedly applying the following function:
𝑥/2, 𝑖𝑓 𝑥 𝑖𝑠 𝑒𝑣𝑒𝑛
𝑠𝑦𝑟(𝑥) =
3𝑥 + 1, 𝑖𝑓 𝑥 𝑖𝑠 𝑜𝑑𝑑

For example the Syracuse sequence starting with number 5 is: 5,16,8,4,2,1. This is an open
question in mathematics whether this sequence will always go to 1 for every possible starting
value.

1.2 Problem to be Solved

You will find a data file on Moodle alongside your assignment specifications called “data.txt”.
This data file contains natural numbers, one on each line.

1. Your role as a programmer is to create a program that will read all this data from the file
and generate the Syracuse sequence for each of those numbers.
2. Additionally, you have to write every one of these Syracuse sequences into a file called
Syra.txt using your code.

Task 1: Write an algorithm to solve the problem mentioned above. Your algorithm must
have a file reading loop as well as the calculation for Syracuse. This should be written as
pseudocode and added as comments in your python file.

Task 2: Translate your algorithm into a Python program. The python

implementation must have try ... except block to catch the runtime errors to make the
program safe from any unwanted crashes.
1.2.2 Use of Functions in Assignment:
It is necessary that you implement this assignment using functions. To obtain the maximum
score you must demonstrate some ability to create and use functions of your own.
1.3 Important Note:
In your program you must write comments where necessary. Don’t write comments for obvious
code, but segments of code which seem complex. Also include your name, student id# and
tutorial group as comments at the top of your program code.
Partial Credit:
Even if your program does not work perfectly, you will receive partial credit for each part you get
to work. For example, if your program compiles but gives incorrect results, you can still receive
a mark provided that your code is well-written.

Part 2: Fundamentals of Programming (10%)

Most important basic elements for programming languages are:

 Programming Environment
 Data Types
 Variables
 Keywords
 Logical and Arithmetical Operators
 If else conditions
 Loops
 Numbers, Characters and Arrays
 Functions
 Input and Output Operations

In Part 1 of this assignment, you have used all of these fundamental parts of the program. Your
task now is to create a report on each of the aforementioned fundamentals and give examples
from you code where and why you have used them. You must also do a general discussion on
what is meant by each of the fundamentals.

Your report will need to have a cover page and a bibliography section for listing any and all
components that you have referenced in this assignment.

The body of the report will just be the 10 sub headings listed above and your discussion on
these programming fundamentals with direct reference to you code from part 1.

Part 3: Assignment Rules and Submission Instruction

3.1 Individual Assignment.
This is an individual assignment. You must not share your program nor your report with
anyone. You can discuss the assignments with your friends, however, if you share your code,
the it will be classed as plagiarism and you will be penalized.
3.2 Submit before the Deadline
You have to submit your work before the deadline mentioned above. Lab computers are scarce,
so the trick is to start EARLY. Also when you finish don’t hold on to your assignment till the last
moment. Submit as soon as you are satisfied with it.
3.2.1 Submitting late:
If you think that you will not be able to submit the assignment on time due to circumstances
which are beyond your control, then you will need to seek approval from the course coordinator
prior to the due date.
This means you have to ask for an extension, explaining the reasons, before the deadline, and
not after. A late submission will be penalized by 20% for each 24 hour period it is late. Where
possible, it is better to hand in your work early and get credit for partial work than handing in
late. A partial work may earn more points than a working assignment which is submitted late.
3.3 Submission
You will have to submit exactly two files on Moodle.
1. A program file for Part 1 (.py file)
2. A report for Part 2. (.pdf file or .docx file)
Note: Be sure you rename both these files using the templte; .
1. Asg_3_SXXXXXXXXX.py, where SXXXXXXXXX is your student id number
2. Asg_3_ SXXXXXXXXX.pdf or Asg_3_ SXXXXXXXXX.docx
Be sure that you submit the assignment only once you are totally satisfied. We will not accept
“corrected versions” submitted through other channels after the due date. However, you can
submit the assignment as many times as you like on Moodle before the due date!
3.4 Plagiarism
For this and other work in IS104, it is essential that you avoid plagiarism. Not only do you
expose yourself to possibly serious disciplinary consequences, but you will also cheat yourself
of a proper understanding of the concepts emphasized in the project. You will almost certainly
fail the short tests and/or the final which will test your understanding of the project. It is not
plagiarism to discuss the assignment with your friends and consider solutions to the problems
together. However, it is plagiarism for you to copy all or part of each other’s programs. If you
find somebody has stolen your assignment and produced it as their own, it will be considered
plagiarism. We are using automated tools to assist with the detection of plagiarism.
They will highlight any unusual code that is similar between students. All cases that are flagged
as potential plagiarism will be checked by hand. So do not leave your flash drives around. Be
careful with them. And make sure you log out of the lab machines when you are finished
working with them. Don’t copy part of someone solutions, and do not give somebody else an
electronic copy of your solution. If you give someone your program it is almost guaranteed that
part of it will end up in their program, no matter whether you ask them not to copy.
Any student posting code for this project on Moodle will be considered to be committing
plagiarism. Do not submit your code to any discussion group or mail it to anyone except the
lecturers or tutors.
Do not be concerned if Moodle tells you that a file cannot be checked by TurnItIn for
plagiarism. This will be your program file. We will check programs separately once
submitted.
3.5 Support
If you have a problem with the assignment, with python or IDLE the exercises, and questions in
this assignment, lecture notes, the book, please ask. First use the forum for your questions. This
will also help other students with the same questions. Then ask your tutor for help, or otherwise
the course coordinator.
If you have any problems with the assignment or the course, feel free to email, visit or call the
course coordinator. All contact information is on Moodle.
Program Marking Rubric
Exceptional
Documentation The code is well
documented. Comment
(6 Marks) describes the main
components, variables,
functions. Comments are
used to describe the
structure. The comments are
up to date. The comments
are relevant, and make
sense to someone
unfamiliar with the code
(6 Marks)
Programming The code uses layout to
Style convey the structure of the
program clearly. Different
(6.5 Marks) components are easily
recognized. Name are by
themselves meaningful if
they refer to the specific
problem and generic if they
refer to part of the code that
is reusable. The code
adheres to the given coding
guideline. All output is spelt
correctly with a proper
layout.
Acceptable
Comments describe most
components, variables and
functions. Some comments
might be dated; most
comment may make sense
to someone unfamiliar
with code
(4 Marks)
The layout of the program
makes it possible to identify
the structure of the
program. Names are
meaningful in the context
of the problem. The code
adheres to general good
coding practices, and the
output is spelled
correctly with only
minor
glitches in layout
(4 Marks)
Amateur
There is visible attempt to
comment all components
and functions. However,
some comments might be
outdated, or only relevant
to someone familiar with
the code
(2 Marks)
The layout of the program
makes it possible to identify
the structure of the
program with some effort.
Names make sense to a
person familiar with the
problem. The code makes
adheres to some good
practices, but ignores
others. Some minor spelling
mistakes, or mistakes in
layout
Unsatisfactory
There are no comments, or
poor comment; out - dated,
irrelevant, or cryptic
(0 Marks)
The layout of the program is
coincidental, and makes it
difficult to identify the
structure of the program.
Names are cryptic. No
discernible effort was made to
adhere to common coding
practices. The output
contains spelling mistakes,
and does not make an effort
to ensure proper formatting
(0 Marks)
 (6.5 Marks)
Semantics The program uses the
programming construct
(6.5 Marks) correctly and competently.
The program does avoid
programming short cuts,
and does not abuse syntax.
There are no superfluous
statements or conditions, no
dead code, no unused
variables, no uninitialized
variables, no potential
division by zero or other
run-time error
(6.5 Marks)
Functional The program satisfies all
Correctness requirements and
produces the correct
(6 Marks) behavior for all possible legal
input. It handles incorrect
input and responds
adequately
(6 Marks)
The program uses most
constructs correctly and as
intended, and is only
sometimes overly
complicated. It may
contain
a few minor semantic
errors, such as dead
code,
or unused variables, but
nothing that would cause
a run-time error
(4 Marks)
The program satisfies the
requirements almost
completely, and produces
the correct answer for
all obvious legal input.
It handles all incorrect
Input without fatal failures
(4 Marks)
(2 Marks)
The program works most of
the times correctly given
some implicit assumptions
about its use. The program
uses constructs differently
from their intended use.
There may be a few run
time errors that manifest
themselves for unusual
input or for certain
compilers
(2 Marks)
The program satisfies the
core requirements. Some
requirements might not
be addressed. It produces
the correct output for
obvious legal input
( 2 Marks)
The program has several
minor run time errors, like
use of uninitialized variables,
or one or more fatal run
time errors. It uses
programming constructs with
no regard for their semantics
or intended use
(0 Marks)
The program does not
satisfy core requirements.
It is easy to find examples
where the program
computes the wrong result.
The program does fail for
unexpected input
(0 Marks)