It's UWAweek 17 (1st semester, week 8)

help3007

This forum is provided to promote discussion amongst students enrolled in CITS3007 Secure Coding. If posting a question, it's suggested you check first whether your question is answered in the unit Frequently Asked Questions (FAQ) list, and use the search box (on the right) to see if an answer to your question has already been posted.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

Note that any posts must comply with the UWA Code of Conduct and the UWA Academic Conduct Policy. That means you should (a) treat everyone with respect and courtesy, and (b) not post your solutions to an assessment that's in progress.

If asking a programming question, it's recommended you read How do I ask a good question? If reporting or troubleshooting a bug in software used in the unit, it's recommend you read How to report bugs effectively.
Displaying selected article
Showing 1 of 42 articles.
Currently no other people reading this forum.


 UWA week 15 (1st semester, week 6) ↓
SVG not supported

Login to reply

👍?
helpful

Hi all,

I'll discuss the upcoming mid-semester test and the project a bit more in tomorrow's lecture, but here is some basic information about them.

Mid-sem test

The test will have mostly multi choice and short answer questions, similar to the week 4 quiz, but also several long answer (English or coding questions) at the end. (Typically I include 3-4 long-form questions.)

For long answer questions, you can get partial marks for a partly correct attempt (unlike multi choice, which are "all or nothing") - so make sure you plan your time, and at least attempt them.

For coding questions - if you can't get your code to compile, it's generally better to comment out any non-compiling parts, and explain in comments what you were trying to do, than to leave compilation errors in your code.

As with all tests, the assessable content is everything up to the end of the prior week (i.e. this week).

The best guide to what sort of coding questions you might be asked is to look at C code from the labs and Moodle.

Project

For the project, we'll be implementing a cryptographic cipher, the Vigenère cipher. It's actually an extremely old cipher (16th century), but variations of it were still being used well into the 20th century – and if used with a long enough random key, it's equivalent to a one-time pad and thus would still offer effective security today.

However, the main point of the project is really to demonstrate that you can apply good practices from the labs and lectures – like static and dynamic analysis (which we'll look at in the next few labs) and running tests.

I'm aiming to have the project out by early week 8, so that there are 4 weeks to complete it in (it's due week 11). For a student with a pretty good knowledge of C (i.e. at least a credit in CITS2002), then as long as they've kept up with labs, then an afternoon or two's work each week should be enough to complete it to a reasonable standard. If you have more or less familiarity than that, it might take you more or less time.

Make sure you start early and ask lab facilitators for feedback – it's not intended to be super difficult, but trying to cram the work into the last week is likely to leave you with subtle bugs that will lose marks.

 

Happy to answer questions about either the test or the project, but unless they're particularly urgent, maybe hold off until after tomorrow's lecture, as they may be answered then.

Cheers!

Arran

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  5:07AM Sep 06 2023
Privacy policy