ICT3 Coursework Guidelines

[ Home ] [ Up ] [ General Coursework Guidelines ] [ Computer Disasters ] [ Computer Hoaxes ] [ 'A' Level Links ] [ Theory Notes ] [ Web Design Project ] [ Database Project ] [ Presentation Graphics Project ] [ Word Processing Project ] [ DTP Project ] [ Spreadsheet Project ]

 

1.      Specification (13 marks)

Problem Statement:

  • Name your end-user and explain the problem to be solved. 

  • Describe the organisation involved and the sort of business it is engaged in. 

  • Describe the information used by this organisation.

  • Conduct an interview to examine the problem in depth and draw conclusions from this interview.
Requirements Specification:
  • Investigate available software, available hardware, end-user's skills/training needs, security, data protection requirements and potential costs.
  • Create a list of end-user requirements.
  • Draw up a list of evaluation criteria for your project (should be as clear and specific as possible).
Inputs, Outputs and Processes:
  • Describe your task in detail (create a list of tasks and sub-tasks).
  • Compare and contrast the existing system with your proposed system (flowcharts/DFDs are useful here if they are supported with a written explanation).
  • Consider sample documents.
  • List inputs, outputs and processes in detail.
System Design:
  • Create detailed designs of every aspect of your proposed system.
  • Include a commentary justifying your choice of designs (i.e. explain why you have designed things in this way)
  • Revisit the design section every time you make a change, thereby showing progression of designs.
  • End-user involvement in designs should be shown.
Test Plan:
  • Start by writing a "Test Strategy" that is specific to your project (explaining how you will go about doing the testing e.g. who will be involved, what sort of data will be used, what aspects of the system will be tested, what involvement there will be from the end-user?)
  • You need a table with the following headings:  Test Number, Purpose of Test, Test Data, Expected Result, Actual Result.  Leave the "Actual Result" column clear for now. 
  • Make sure the test plan is closely related to your quantitative evaluation criteria (cross-reference it).
  • It is important to include a range of extreme/erroneous test data (not just button-clicks).
  • It is important to test the functionality of the system (does it actually solve your "problem"?).

 

2.      Implementation (20 marks)

Selection of Hardware and Software:
  • Explain the hardware and software you have chosen to use and give reasons for your choices.
Progression, Evidence and Annotation:
  • A vast array of screenshots and printouts are probably required but nothing should be left unannotated.
  • You should aim to show that you solved your problem and how you solved it.
  • Don't be afraid of showing the mistakes you made and the problems you encountered as long as you then explain how you solved these problems.
  • Make sure you include a printout of the final output.
  • Don't write your implementation like a user guide!

 

3.  Testing (12 marks)

Test Table:
  • Copy and Paste your test plan, conduct the tests and fill in the "Actual Result" column.
Test Evidence:
  • An annotated screenshot is required for each test. 
Corrective Action:
  • Where tests have not produced the expected result, corrective action should be taken and this should be fully evidenced.

 

4.      Evaluation (6 marks)

Use the Evaluation Criteria:

  • List your Evaluation criteria and evaluate them in as much depth as possible.  Cross-reference to the testing and implementation sections to prove that your objectives were achieved.
Identify Limitations and Suggested Enhancements:
  • Show that you appreciate the imperfections of your system and suggest how these could be improved.
End-User Evaluation:
  • A letter of acceptance from your end-user is useful.  Consider what your end-user says.

 

5.  User Guide (9 marks)

Extensive User Documentation:

  • User Guide should be separately bound with numbered pages and a table of contents.

  • Write an introduction explaining the purpose of the system and the scope of the guide.

  • Include screen-shots.

  • Explain every option available to the user.
Troubleshooting:
  • Show screen-shots of potential problems that might be encountered by the user and then explain how to solve the problem.
  • An "FAQ" (Frequently Asked Questions) section might be useful.
  • Explain how the user could obtain technical support.