You can create test output files by cutting and pasting from your terminal

You can create test output files by cutting and

This preview shows page 10 - 14 out of 14 pages.

You can create test output files by cutting-and-pasting from your terminal output into a text file. Alternatively, you may use the command script to record terminal input and output. Please do not modify the test output. You must make sure that your program can be compiled and run on other machines. Do not use any non-standard feature or any feature that is only available on your machine. Do not hard-code any directory path into your program otherwise your program may not run on someone else's machine. The file "Assignment1.docx" This file should contain the documents in the following order: 1. ICT310 Major Assignment One Check List : all students (internal and external) must complete this check list and include it in your Word file. 2. Extension Granted: if you have been granted an extension, include the email from your Unit Coordinator after the declaration form. 3.List of Files: list the name and purpose of each file included in the tar archives. 4. Include documents for each question in the order of question numbers . For each question, you must include: a. The question itself : you can cut-and-paste the question from this file to your Word file.
Image of page 10
Image of page 11
Image of page 12
b. Your answer (theory question only) : please note the marks are not awarded purely based on the length of your answer. Most questions can be answered in a half to one page. c. Self diagnosis and evaluation (programming questions only) : a statement giving the following details for each requirement of the question: what has been fully completed and working, and what have been fully completed but not fully working, and what has not been fully completed or not attempted. This statement is essential . You will lose at least 50% of the mark allocated to the question if this statement is missing, misleading, or too vague. d. Test evidence (programming questions only) : depending on the nature of the problem, you may need one or more test cases to demonstrate that your program has met all requirements. When testing your program, please turn on the gcc warning ( gcc -Wall ... ), and make sure you fix all warnings before submitting your program. For each test case, you should 1) explain the purpose of the test, 2) provide the test output including the command line used, and 3) give an explanation on what the test has achieved based on the test results. It is important that you present a sufficient number of test cases to convince your tutor that your solution works in all situations. Please note that although your tutor may test your program to verify the evidence presented in your documentation, it is not the responsibility of your tutor to test your program for the purpose of finding marks for you. It is up to individual students to mount a convincing case that the submitted solution works as required. You will be awarded marks based on the test evidence you present. Therefore, if you do not provide test evidence, you do not get marks regardless of whether your program works or not, or if the test evidence you have provided is not sufficient, your marks will be substantially reduced.
Image of page 13
Image of page 14

You've reached the end of your free preview.

Want to read all 14 pages?

  • Winter '18
  • Mandy
  • Virtual memory, Central processing unit, Global variable

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture