ITGS Internal Assessment Guidelines
| File |
|Nature of Submission |
| Criterion |
| Initial Investigation (of problem) |
|Text || A |
| Initial consultation (with client) |
|Methods such as a written record of the interview (either a |
summary or transcript), a sound file, a video, or an exchange
of emails that may be supported by a questionnaire
| Analysis ||Analysis form including additional text || B |
| Project Schedule |
|Project schedule form || C |
| Product Design |
|Product design form || D |
|Product Development |
|Text with screenshot evidence |
| E |
|Feedback from Client |
|Methods such as a written record of the interview (either a summary or transcript), a sound file, a video, or an exchange of emails that may be supported by a questionnaire || F |
|Product evaluation |
and future product
|Text || |
Development of the project
Students are advised to use the following guidelines to produce their project. This will ensure it fulfills the requirements of the criteria.
When developing the ITGS project, the student must follow the processes as set out in each of the criteria. Criteria A–D inclusive must be reviewed by the teacher before allowing the student to proceed to making the product in criterion E.
Criterion A: Initial investigation and initial consultation with client - Due October 31, 2011
The client and the information problemThe student must identify a specific client who has a problem with the present situation that can be best addressed by an IT solution. The client is the person(s) who needs the IT solution (product). After consulting with the client, the student must explain the inadequacies of the present situation, which may or may not involve the use of an IT system.
The following key questions should be considered.
• Who is the client?
• What is the present situation?
• What are the inadequacies of the present situation?
Internal assessmentInformation technology in a global society guide 63This information must be obtained from the client and can be presented in a variety of ways, such as a written record of the interview (either a summary or transcript), a sound file, a video, or an exchange of emails that may be supported by a questionnaire.
Criterion B: Analysis - Due November 18, 2011
The student must ensure that the proposed IT solution addresses the inadequacies identified in criterion A.
The analysis must consist of the following two parts, which must be submitted as a single document.
• A completed requirements specification using the first section of the form
• Justification for the proposed solution, as extended writing using the second section of the form
The following information must be included.
• System interaction
• Input and output requirements
• Specific performance criteria that are evaluated in criterion F to determine the effectiveness of the
Justification of proposed solution
The rationale behind the choice of the proposed solution must be in extended writing justifying how the
choice of this particular product is the most effective IT solution to the problem identified in criterion A. It is
expected that this is based largely on the information within the requirements specification.
Other information that can be included in the justification for the proposed IT solution may refer to:
• whether the student has the IT skills and access to the software required to develop the IT solution
• whether the client’s hardware and software is compatible with the IT solution
• the level of training necessary for the client to use and maintain the proposed IT solution
• to what extent the input and output requirements of the client are met by the IT solution
• whether the data required for the IT solution can be obtained by either the client or the student
• how any security implications for the development and operation of the IT solution can be resolved.
Criterion C: Project schedule - Due November 30, 2011
The project schedule must be implemented for the proposed IT solution in criterion B.
A plan based on the research into the proposed IT solution and the factors involved (stakeholders, software,
hardware, network requirements, data, input and output, processes and policies) is developed that
• the key events in planning, designing, developing, testing and implementing the product in the form
of a timeline
• any other issues that may arise which may affect the development of the product.
Criterion D: Product design - Due December 16, 2011
• design methodologies appropriate to the type of IT product being designed
• different levels of draft design, such as the overall structure as well as the internal layout of the product
itself. This can also include investigation into specific elements used within the product (such as fonts,
graphic elements, effects)
• identification of a range of appropriate resources and techniques required for the development of the
• evidence of a test plan that addresses the main areas of functionality of the product
• evidence of the agreement of the client to develop the product.
The product design should be in sufficient detail so the product could be independently created by an ITliterate third party.
Criterion E: Product development - Due January 20, 2012
The product is created using the information submitted in the requirements specification (criterion B),
project schedule (criterion C) and the product design (criterion D).
The student must present a list of the techniques used in the product at the start of this criterion.
A complex product is defined as one that includes at least three appropriate advanced techniques. The list
of techniques will be posted on the OCC annually.
A simple product cannot be awarded more than 4 marks for criterion E.
The information in the documentation linked to the development of the product must provide a detailed
account, using extended writing, to justify the following.
• The structure of the product and why it is appropriate
• The techniques used (see the list on the OCC), including screenshots, in the development of the
product, and reasons why they are appropriate to it
• Additional technical information, if appropriate, that will support the functionality of the product,
such as web hosting or security information
Any reference material such as templates, program code, applets or other materials that have been used or
modified must be acknowledged. Failure to do so will be considered a significant omission.
Criterion F: Product evaluation and future product development - Due January 30, 2012
This criterion should be completed as two parts. The first part deals with the evaluation of the product by
the client, including any feedback given and including any problems identified. The second part makes
recommendations for the future development of the product.
Feedback from client
This information must be obtained from the client and can be presented in a variety of ways, such as a
written record of the interview (either a summary or transcript), a sound file, a video, or an exchange of
emails that may be supported by a questionnaire.
The evaluation of the completed product should refer directly to the specific performance criteria that form
part of the requirements specifications in criterion B, as well as any other appropriate feedback obtained
from the client at handover.
Recommendations for the future development of the product
The student will use the client feedback and the evaluation of the specific performance criteria to
recommend possible future developments to the product. These recommendations should succinctly
explain how possible future developments of the product will be of benefit to the client and/or other
Criterion G: Required elements - Due February 13, 2012 (Initial Rough Draft Due)
The three required elements are marked independently.
1. The content and functionality of the product are sufficient to reliably evaluate its effectiveness.
If the product contains insufficient content to reliably evaluate its effectiveness, such as a database
with insufficient records to test the output of queries or a single-page website, this required element
has not been fulfilled and no marks will be awarded.
If the product does not function as intended, this required element has not been fulfilled and no
marks will be awarded.
2. The prescribed cover page is used and functions as required.
The prescribed cover page has been used and the moderator can successfully use this to navigate to
both the product and the documentation.
– If the links do not function, this required element has not been fulfilled and no marks will be
– If the nature of the product means it cannot be directly accessed by the link, there must be clear
and concise instructions on the cover page. If they are not sufficiently clear for the moderator
to easily locate the product, this required element has not been fulfilled and no marks will be
3. Folder structure and file naming.
The project should be organized in such a way that there is evidence of the use of appropriate folder
names and structures that enable individual files to be located if links fail.
The project should be organized in such a way that there is evidence of:
– the use of appropriate file names to enable the client or an IT-literate third party to be able to
locate and modify files if necessary
– the use of an appropriate file-naming convention that would allow either the client or an ITliterate third party to make future modifications to the product.
If the product does not demonstrate appropriate file names and folder structures, this required
element has not been fulfilled and no marks will be awarded.