(See the IB document: d_5_comsc_tsm_0505_1_e.pdf for the full version)
Criterion A1: Analyzing the problem
Total = 12 pts.
(See pages 67- 90 in the IB document: d_5_comsc_tsm_0505_1_e.pdf)
The documentation should be completed first and contain a thorough discussion of the problem that is being solved. This should concentrate on the problem and the goals that are being set, not on the method of solution. A good analysis includes information such as sample data, information and requests from the identified end-user, and possibly some background of how the problem has been solved in the past. A systematic method is one that takes into account what input and output will occur and what calculations and processes will be necessary to obtain the desired output.
Achievement levels Descriptor
0 The student has not reached a standard described by any of the descriptors given below. For example, the student has simply described the programmed solution.
1 The student only states the problem to be solved or shows some evidence that relevant information has been collected. 2 The student describes the problem to be solved. 3 The student describes the problem and provides evidence that information relating to the problem has been collected. 4 The student provides evidence that a systematic method has been used in the analysis of the problem.
This section of the program dossier would typically be two to three pages in length. It should include a brief statement of the problem as seen by the end-user. A discussion of the problem from the end-user’s point of view should take place, including the user’s needs, required input and required output. For example, evidence could be sample data, interviews and so on, and could be placed in an appendix.
Criterion A2: Criteria for success
This section of the program dossier will clearly state the objectives/goals of the solution to the problem. The expected behavior of the solution should be clearly described and the limits under which it can operate outlined.
Achievement levels Descriptor
0 The student has not reached a standard described by any of the descriptors given below.
1 The student states some objectives of the solution. 2 The student describes most of the objectives of the solution. 3 The student relates all of the objectives of the solution to the analysis of the problem.
4 The student relates all of the objectives of the solution to the analysis of the problem, and outlines the limits under which the solution will operate.
This section of the program dossier would typically be one to two pages in length. Objectives should include minimum performance and usability. These criteria for success will be referred to in subsequent criteria, for example criterion C2 (usability), C4 (success of the program); D2 (evaluating solutions) and D3 (including user documentation).
The limits under which the solution will operate will vary. Some examples are: • time taken to return a research result from a data file • the response of the program to invalid and extreme data input • limitations on the volume of data stored in the program • usability of user input screen
• the proper response of the program to user input.
Criterion A3: Prototype solution
The prototype solution must be preceded by an...