2NP/2NP3: Week 1

1. Introduction to the module

This is a week-by-week check-list for students following the module 2NP or 2NP3. It lists all the activities that you will have been expected to do during the week, and links to a number of web pages on this site that you will be expected to have read by the end of the week, with a few comments on why these will be important.

You should attend TWO lectures and (at least) ONE 2-hour computer lab each week. See Canvas for details.
You should familiarise yourself with the way the module will be run, syllabus and assessment arrangements. Details are on Canvas. These will be discussed in lectures and will be obvious during the first lab.
Ensure that you have a notebook for labs. The details for programming are important and not always easy to learn, so write them down. If you don't you will find you have to keep re-learning the same things each week which will waste time.
Make sure that you practise outside timetabled sessions. This is no different to any other module and you do have to do work to prepare for classes. You can use university computers but if you want to use your own computer there are instructions on installing the (free) software.
The assessment arrangements and a week-by-week list of activities are provided in the Module Term-plan. This web page is a good starting place for any students following the module.
The main web pages are written as an online-book and should be understandable provided you don't try to read too far ahead too quickly. They contain menus at the the top for links to other sections of the site (don't forget to check these) and other links too. They contain LOTS of examples.

All students are different and it is your task to find a way of working that suits you. However, the following points will help the vast majority of students whether or not they have done any programming work before.

Use your 2NP notebook for detailed notes of tricky commands or syntax that you need to learn. (In my opinion, a small exercise book works better than file paper or a computer file, but YMMV.)
Especially if you have not done programming before, expect that the very beginning of the module will require you to do rather more in way of background reading and (especially) practice. This is a subject where practice is very important, and the practice you put in early on will help considerably later on. Attending lectures and your computer lab only will not be enough, especially early in the term.
Unless you are a brilliant programmer or the task you are engaged on is really easy, you cannot program a computer without pencil and paper to hand. Experts always have scribble-paper available. So if you are a beginner, or even if you are not, make sure you can sketch out your ideas on paper first. You will also need paper to test out your code and understand what it is (or isn't) doing.

2. Work and web pages for week 1

Background. Everyone (except possibly direct-entry Chinese students) will have worked on the university computers using MS-Windows before. You are therefore expected to have basic skills and understanding of the computer system, in particular the file and directory system in MS-Windows. ("Files" are often called "documents". These words are interchangeable. Similarly "directories" and "folders" are the same thing.) You may need to refresh your knowledge and skills in this area. You can do one or more of:

Search the web for suitable information.
Review the materials you did in Year 1 computer labs. The current version of it is at http://web.mat.bham.ac.uk/R.W.Kaye/year1prog/
In particular you looked at how to use files and folders and commands and applications. It might be a good idea to review these. You do not have to read about "Lua", though of course you can if you wish.

Programming skills. Everyone who did year 1 mathematics will have seen some basic programming. This will probably have been done in Lua (possibly Maple) and will include the basics of loops ("while" and "for" loops) and variables. So no-one comes to this subject completely new to it. You may like to review what you did last year. However, note that this module will be taught from scratch using C++. At this stage it might be better not to muddle up two different languages and stick to C++.

Work for week 1. There is no assessment for week 1, but this is only to give you an extra week to settle into the module. It is not to give you a week off!

There are two assessments (SA1, SA2) in weeks 1,2,3. SA1 should be straightforward but you will may find that SA2 is quite challenging. Therefore the sooner you can finish SA1 and get on to SA2 the better. Many students will do SA1 in one week and then will have two weeks for SA2.

I am starting programming using Register Machines. These still use C++, but I have presented them in a much simplified syntax that should make learning the basics much easier. Register Machines also have a much-limited instruction set, which means that they are not much use for professional programming but will be easier to understand for beginners. (They are also interesting:) As well as the background (indicated earlier) you are expected to have read and know the material in the following web pages. These will be the content of lectures and labs this week.

Register machines
Compiling and running register machines
Register machine examples
More on register machines, if time permits

3. Assessments for week 1

Assessments and assignments are all issued via Canvas. There are no assessments in week 1, but you are strongly advised to finish SA1 as soon as possible so that you can get on to SA2 in week 2.