Projects

Project Description
The emphasis of the project is on solving a problem, set firmly in a social context, that affects the ways in which individuals, organizations and groups access and use information. Only projects that solve an actual problem should be undertaken. Although a simple solution can often be an appropriate response to a particular problem, candidates are encouraged to undertake challenging tasks to develop their IT skills and increase their awareness of the social impact of providing a feasible IT solution to a specific social problem. The making of the product, the writing of the report, and the keeping of the log book must be undertaken by the candidate on an individual basis. Collaborative work is not allowed. In identifying a problem set in a social context, candidates can select any topic that interests them. It need not be related directly to any of the areas of impact in the syllabus and the problem identified can be inside or outside the school environment. One approach which candidates may find helpful and which is quite acceptable is to draw on material from other parts of the Diploma Program where an IT solution could be found to a social problem. Examples could include: > theatre arts
 * collecting data from a biology field trip for use as preparatory material in an interactive presentation for the following year’s students
 * mapping backstage activities in an IT format for use in a drama production in
 * identifying an IT solution to a problem encountered in creativity, action, service
 * (CAS), such as teaching a child to recognize colours, do simple arithmetic or compose a simple tune.

Requirements CRITERIA
The project consists of three parts (product, report, log book), all of which must be submitted for moderation.

Product
The end product is the IT solution to the problem. This must include the integration of at least three different IT skills. The product can be submitted on paper; as a URL address (web site); on a CD-ROM; on a video tape.

Report
The report is a document of 2000–2500 words describing the process involved in the development, testing and implementation of the project. The report must be written in the order of the assessment criteria and the assessment criteria headings must be used as sub-headings in the report. Visual documentation from the product in the form of screenshots, graphs, storyboards, photographs and similar visual evidence must be integrated into the body of the report under the appropriate sub-headings. The text in the report should refer to the visual evidence. Appropriate annotated documentation from the development and formal testing of the product may be included in appendices. Any appendices will not be included in the word count of the report.

Log book
The log book is a chronological record of the entire process used by the candidate throughout the development of the product. The log book is assessed and maintaining it is mandatory. The log book contains regular, dated entries from analysing, planning, testing, implementing and evaluating the process and product. Regular dated entries of the process and product must be recorded in the log book. These include references for information, sketches and designs, evaluative comments, crossings out, subject statements and other appropriate entries. It will document the candidate’s actions and thoughts throughout the development process. It is normal for the log book to be handwritten. The log book is intended primarily as a means of improving skills of organization, documenting the process of development and as an aid to problem solving for the student.