TEACHERS COMMENTS AND JUSTIFICATION OF AWARDED MARKS 9691/04

SUMMARY:
Candidate ID: Candidate Name: 03 08 07 02 02 08 05 03 05 05 03 02 02 55 (a) Definition, Investigation and Analysis (i) Definition nature of the problem (ii) Investigation and Analysis (b) Design (i) Nature of the solution (ii) Intended benefits (iii) Limits of the scope of the solution (c) Software Development, Testing and Implementation (i) Development and Testing (ii) Implementation (iii) Appropriateness of structure and exploitation of available facilities (d) Documentation (i) Technical Documentation (ii) User (e) Evaluation (i) Discussion of the degree of success in meeting the original objectives. (ii) Evaluate the users response to the system (iii) Desirable extensions Total Marks:

DETAILS:
DEFINITION, INVESTIGATION AND ANALYSIS
Definition nature of the problem Evidences Seen:
A description of the organization that has the problem and the place of the problem within it. A description of how the chosen problem is dealt with at the moment. A CLEAR description of the data that is used in the area of the problem. A clear indication of where the data came from. How it is collected.

Awarded Marks Justification:

3 Full description of the organization and methods currently in use in the area of the chosen project, with a description of the origin of the data to be used and some indication of the form that data takes.

Investigation and Analysis Evidences Seen:

Detail relating to the planning of the enduser interview. The original plan of the questions, showing that all areas had been planned to be covered and that sensible follow up questions had been considered. Transcript of the interview itself, including an element of later analysis and isolation of important facts. Further evidence of information collection relevant to the problem area. A flow diagram showing how the present system works. Consideration of different methods of solving the problem, together with end users signature for evidence that the end user has been involved in the decision making. Hardware and software requirements of the system with discussion about the needs for each.

Commentary:
Perhaps a little more evidence of the end user would have been appropriate, there is a hint here of the student making most of the decisions.

Awarded Marks Justification:

8 Excellent user involvement with detailed recording of the users requirements. Alternative approaches have been discussed in depth. The report demonstrates a thorough analysis of the system to be computerised. A detailed requirements specification based on the information collected has been produced.

DESIGN
Nature of the solution Evidences Seen:
A list of objectives against which the final product can be measured. This report is signed by the enduser. An explanation of the way that the data is to be collected and to be input to the system together with initial plans of input screens, and explanation of intended means of validation. An explanation of the output that should be expected and initial screen designs for the output of data. File structures that are to be used and the links between them. Diagrammatic representation of the data through the system.

Commentary:
Candidate has thoroughly covered every item.

Awarded Marks Justification:

7 A clear set of objectives with a detailed and complete design specification, which is logically correct. There is complete definition of any data structures. The specification is sufficient for someone to pick up and develop an end result using the software and hardware specified in the requirements specification.

Intended benefits Evidences Seen:

4 specific improvements that the new system will make to the running of the old system.

Awarded Marks Justification:

2 The benefits of the new system have been comprehensively described.

Limits of the scope of the solution Evidences Seen:

A description of the contents and data types stored in each of the files to be used together with an approximation of their size. Adjustments that the student thinks are necessary to their solution compared to the real thing. Limitations that have been placed on the solution because of the hardware available and the software available.

Awarded Marks Justification:

2 A detailed description of the system limitations has been given, including the estimate of the size of the files required for the implemented system.

SOFTWARE DEVELOPMENT, TESTING AND IMPLEMENTATION

Development and Testing Evidences Seen:
A testing plan covering different areas of the solution to be tested, including what is expected as the outcome. Data structures are described and their existence is proved by printing them out.

Input and output screens are described and produced. They are fully/partially/less annotated to show their effectiveness. For each of the tests planned the candidate has shown intention of the test run and the reason with a clear idea of what the expected result is.

Commentary:
The student has included enough testing to be able to test all the different areas of the solution, though, remember, it is not possible to test every aspect of the solution with all possible values. Development of work is evident; much evidence is in previous sections. Much evidence of software being tailored and hard copy demonstrate system well.

Awarded Marks Justification:

8 Evidence of tailored software packages are provided in the form of printouts. Data structures are illustrated detailing their purpose. There is a full set of printouts showing input and output as well as data structures. All hardcopy is fully annotated and cross-referenced. A comprehensive test plan, with evidence of each test run is present in the report, together with the expected output. The test plan has covered cover as many different paths through the system as is feasible, including valid, invalid and extreme cases.

Implementation Evidences Seen:

Pictorial & letter evidence that the enduser has seen the system. Pictorial & letter evidence that the enduser has used the system and has obtained meaningful results from the system. Some evidence that the opinions of the enduser have been used to adapt the solution. Details of the training that will need to be available for the staff that must use the new system. Details of the means by which the new files are going to be created. Details of the changeover anticipated.

Commentary:
Clear and detailed implementation plan. User tested and acceptance is clear. Written evidence from user in section e. over letterhead. Training is suggested & not conducted.

Awarded Marks Justification:

5 A clear and detailed implementation plan. All aspects of user testing, user acceptance, implementation and system changeover have been documented. There is written evidence available from the user that they have used the system and agree with it.

Appropriateness of structure and exploitation of available facilities Evidences Seen:

A log of few problems that were encountered during the production of the solution.

Commentary:
Include documents about appropriate hardware as student feels it necessary. Include documents about appropriate software as student feels it necessary. This log include a detailed description of the measures taken to solve the problems found. No references to the evidence that the solutions had the desired effects. Candidate has documented problems that were met and the solutions to the problem.

Awarded Marks Justification:

3 A complete discussion of the hardware and software available together with a good, informative explanation of the problems encountered and how they were overcome.

DOCUMENTATION
Technical Documentation Evidences Seen:
A description of the records used and the fields within the records. The types of data is described as should the data structures used to hold the data. Any data handling implies that data has been stored. An explanation of the Entity relationships between the various tables. The screens used. The menu system for the input of data along with the form designs. A data dictionary and the queries employed for coding. All database objects are supported by Documenter tool of the MS Access Program. Recommended hardware and software configuration needed to run the system.

Commentary:
Annotation could never be better.

Awarded Marks Justification:

5 No major omissions, with all parts fully annotated. For full marks the guide is well presented rather than just a collection of items.

User Documentation Evidences Seen:

A contents page. Details of input requirements including examples of valid and invalid data with explanations, examples of the input screens so that the user knows what the screen will look like. How to move from input to input on the screen, how to show that the screen input is completed Methods of output and there ways and support. Explanation of the error messages that may appear. Methods that have been used to protect the data. For example passwords on files. A certain amount of onscreen help in the form of error messages. Screen dumps of these onscreen help facilities. A glossary of words.

Commentary:
All items except Backup are well presented. The user doc is useful.

Awarded Marks Justification:

5 A full user guide with all options described well presented with a glossary. No omission of any of the options available. Marks are lost for inadequate descriptions of Backup. Good on-screen help exists.

EVALUATION
Discussion of the degree of success in meeting the original objectives Evidences Seen:
A clear matching up of the agreed objectives of the project, taken from the requirements specification, with evidence that the objectives have been met. For each objective shown a discussion about the degree of success that the student believes has been achieved (with reference to the evidence in the rest of the report).

Commentary:
The results that were obtained upon using manufactured data rather than real test data. But user has tested it.

Awarded Marks Justification:

3 A full discussion, taking each objective mentioned in (a) (ii) and explaining the degree of success in meeting them, indicating where in the project evidence can be found to support this.

Evaluate the users response to the system Evidences Seen:

A letter from the enduser stating that they have used the software solution and listing the things that they managed to do and those that they could not, or that still need work to improve them. Some indication of the degree of success that the student has achieved in the opinion of the end user.

Commentary:
User accepts the system. Letter was given at the back of an empty invoice. As per the student letterhead was not available.

Awarded Marks Justification:

2 A fully user-friendly system has been produced. The user indicates that the system fully meets the specification given in section (a). Letter is given at the back of an empty invoice.

Desirable extensions Evidences Seen:

Discussion of those parts of the system that the student believes is satisfactorily completed. Discussion of those areas that have not been successful with proper reasoning. A clear indication that the student realizes that, although the project is finished, the solution is not and that there are a number of possibilities for extending the solution.

Commentary:
Desirable extensions are covered well.

Awarded Marks Justification:

2 The candidate clearly portrays the good and bad points of the system indicating the limitations, possible extensions and how to carry out the extensions.