The learning outcomes that are assessed by this coursework are:
| ||||||||
This coursework is: | Individual | Group | ||||||
For the implementation part, you must work in groups and submit your codes as a group. For the security analysis report part, you must submit individually. Make an appointment with your lecturer to get help with problems you run into.
| ||||||||
This coursework constitutes 50% of the overall module mark. | ||||||||
Date Set: | 01/03/21 | |||||||
Date & Time Due: | 24/03/21 unless otherwise agreed | |||||||
Your 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 Associate Professor Student Experience (studentexperience-tech@dmu.ac.uk) should be informed of any issues relating to the return of marked coursework and feedback.
Note that you should normally receive feedback on your coursework by no later than 20 University working days after the formal hand-in date, provided that you have met the submission deadline.
| 14/05/21 | |||||||
When completed you are required to submit your coursework via:
If you need any support or advice on completing this coursework please visit the Student Matters tab on the Faculty of CEM Blackboard page.
| ||||||||
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%] 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%.”
Word Limits The policy is to allow answers to exceed the word limit by up to 10% without penalty, and then a penalty of up to 20% of the marks for answers that exceeded the word limit by up to 30%. Any content that exceeds the word limit by over 30% would not be marked and hence not contribute to the final mark.
| ||||||||
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
| ||||||||
Tasks to be undertaken:
This assignment consists of three parts:
NOTE: All letters should be first converted to their uppercase equivalents before encryption and decryption. White-spaces should be maintained while all other characters should be discarded. Your program is expected to be an elegant program that minimizes the repetition of common code. Note that the best program is rarely one with the most lines of code, but rather one that accomplishes the task most simply and with the least code. Comments should be used to explain everything which is not obvious from the code, e.g. why you are doing something, not exactly what it does. (40 MARKS)
(30 MARKS)
| ||||||||
Deliverables to be submitted for assessment:
You must submit the implementation codes (for encryption/decryption and cracking a given ciphertext) as a group and the Individual Security Analysis Report. The security analysis report of the Affine Cipher should not exceed 1000 words. A brief explanation is also necessary for the design of your code (functional design). A design document should contain a diagram of the functions you are planning to implement. Try to eliminate redundant code.
| ||||||||
How the work will be marked: See Marking Grid. | ||||||||
Module leader/tutor name: | Dr. Mehmet Sabir Kiraz | |||||||
Contact details: | mehmet.kiraz@dmu.ac.uk |
0 comments:
Post a Comment