| | |
1 | | INTRODUCTION |
|
|
|
> | Each student is required to complete a project, which will form 42 credits of the qualification. Projects should be drawn from "real life" situations and be of significant proportions, testing the student's ability to apply the principles and skills they have gained to an original piece of work, while under supervision. |
|
|
|
> | As a guideline, an approximate time for such a project might be the equivalent of approximately 55 working days (420 hours). |
|
|
|
> | Projects must be approved as being of a suitable standard, as outlined below, by the local Advisory Committee, and a similar standard maintained throughout the country by the moderation process. |
|
|
|
> | Projects should be based on a students existing skills and knowledge, and may be influenced by their work situation, if they are in work. Projects will normally be completed by individuals, but under certain circumstances may be done by a group of students. |
|
|
|
> | Students who do not have a real work situation to draw on for project work, should, wherever possible, be assigned projects drawn from sympathetic employers. |
|
|
|
> | The project must be of sufficient complexity to stretch the student. The MINIMUM standard for Project work is at least the level of Case Study material used in level 300 modules. Projects should be significantly different from any major case study or practical work undertaken in subjects of CBC/DipBC. With a Programming Project, particular emphasis should be placed on structured techniques, standards and conventions. |
|
|
|
|
|
| 2 | PROJECT PREREQUISITES |
|
|
|
> | The Project cannot be commenced until at least 50% of the credits for the National Diploma have been completed. |
|
|
|
> | As part of the approval process, confirmation must be given that the student has completed sufficient subjects at appropriate levels in the area(s) in which the project lies. |
|
|
|
|
|
| 3 | APPROVAL PROCESS |
|
|
|
> | Before a project is started, the student must complete a Project Proposal, which must then be submitted to, and formal approval for the project obtained from, the following: |
|
|
|
| | - THE TUTOR - who will act as a preliminary screener to check that the project meets the necessary complexity and work content standards. |
|
| | - THE EMPLOYER (if there is one) - to agree that the project is in the interests of the employer. |
|
|
|
| | - THE CUSTOMER - to agree that the project meets their business requirements. Note: even where the customer is a part of the employer's organisation it will still be necessary to obtain agreement from a separate person to the one agreeing as employer. |
|
|
|
| | - THE LOCAL ADVISORY COMMITTEE - approval of the LAC will be required to confirm that the project meets the standard required. |
|
|
|
> | The student's employer (where there is one) must still give their approval even if the project is undertaken on someone else's work. |
|
|
|
> | In the case of a student without an employer, the tutor is likely to undertake the employer's role. |
|
|
|
> | Because of the time required for the Project Proposal to go through an approval process, students must identify their projects and prepare their proposal well in advance of its actual commencement. The possibility that the project proposal may need to be amended and resubmitted must be born in mind. |
|
|
|
|
|
| 4 | PROJECT PROPOSALS |
|
|
|
> | These documents must cover the following areas: |
|
|
|
| | - PROJECT TYPE - eg. Systems Analysis, Systems Programming. |
|
|
|
| | - SCOPE AND PURPOSE - detailing precisely what the project will achieve (from the Customer's perspective). |
|
|
|
| | - SKILLS/KNOWLEDGE INVOLVED - precisely what skills and knowledge the student will demonstrate by completing the project. |
|
|
|
| | - PROJECT PLAN - a detailed plan showing all the major activities and time requirements, including a clear indication of what the student will be responsible for (this is particularly necessary for projects where the student may be working in cooperation with others) and the "deliverables" of the project. |
|
|
|
| | - PROJECT OWNERSHIP - The ownership of the deliverables of the project should be clearly stated. |
|
|
|
> | The Proposal form will have provision for the necessary sign-offs as indicated above. |
|
|
|
|
|
| 5 | CONTROL OF THE PROJECT |
|
|
|
> | Progress on the project must be reviewed at regular intervals with the tutor - a weekly status review would seem appropriate given the importance of the project for the qualification. Such a review would include examination of the students Project Log Book and their completed “timeline”. Tutors may also visit the student on-site, if appropriate. |
|
|
|
> | Formal milestone reviews should also be undertaken: milestone points would be agreed as part of the project plan and then the student would make a report at these points to the employer/customer/tutor. |
|
|
|
> | Detailed records must be kept of all the above reviews so that an accurate picture of the project can be obtained once it has finished. To this end a Project Log Book should be developed: this should contain: |
|
|
|
| | - a week-by-week breakdown of activities actually completed and by whom they were completed. This should include notes on any noteworthy problems encountered and how they were overcome (may be helpful later too, if others are extending or maintaining the project). |
|
|
|
| | - identification of variances or exceptions to expectations (e.g. activities that were significantly more complex than expected, extra (unanticipated) activities that had to be done). |
|
|
|
> | An allowance for Project renegotiation in the event of significant unforeseen circumstances (e.g. team member leaves course, project disappears, complexity of project much less/greater than originally thought) must be made, through which Project person/team reaches an amended set of requirements with the Supervising Project Tutor. |
|
|
|
|
|
| 6 | COMPLETION OF THE PROJECT |
|
|
|
> | Upon completion of the project, the student will conduct a formal Project Completion Review. |
|
|
|
> | The Review will require a formal presentation to a selected audience (fellow students, LAC members, tutors, employer's representatives, etc.) of a report on the project, including what went right, what went wrong etc., followed by a question and answer session. |
|
|
|
> | After this session, the student would obtain all the necessary project sign-offs and a formal assessment of the student's performance on the project will then take place. |
|
|
|
|
|
| 7 | ASSESSMENT |
|
|
|
> | At the time the Supervising Project Tutor agrees to the Project Proposal they will determine the exact way in which the project will be assessed (i.e. at what points, what items, by whom etc.). |
|
|
|
> | In the situation where a group of students wish to operate as a team for a Project, the way in which assessment will be completed for individual team members must be clearly understood (e.g. all get the same assessment grade, total for team given and each member gets the same etc.). |
|
|
|
> | In general, it will be the Supervising Project tutor who makes the assessments, with input from the employer and customer. |
|
|
|
> | Items likely to be assessed include: |
|
|
|
| | - project proposal |
|
| | - each milestone |
|
| | - adherence to project plan |
|
| | - presentation and report |
|
| | - review |
|
|
|
| | as well as how well the overall objectives have been reached. |
|
|
|
> | The Supervising Project Tutor would be expected to meet with the student at regular and frequent intervals (e.g. weekly). A report from the employer and customer should form part of the assessment. |
|
|
|
> | The overall review format would thus be: |
|
|
|
| | Project Proposal Approved by: |
|
| | Purpose/Scope Cust/Emp/Tutor |
|
| | Skills/Knowledge Tutor |
|
| | Plan Tutor |
|
|
|
| | Milestones Cust/Emp/Tutor |
|
|
|
| | Presentation/Report Cust/Emp/Tutor |
|
|
|
| | Project Review Tutor |
|
|
|
> | (In practice milestone reviews could be amalgamated with the tutor's weekly review of progress). |
|
|
|
> | The Project Supervising Tutor will decide on Merit passes for projects. |
|
|
|
|
|
| | DESCRIPTION OF ASSESSMENT POINTS: |
|
|
|
> | Project Proposal - this report will be prepared and vetted by the tutor(s) before being presented to the Project Supervising Tutor (PST). All projects have gained a Pass in this assessment once the PST has formally approved it. |
|
|
|
> | Assessment Schedule - each student or project group is required to produce an assessment schedule for their project. This schedule should define at least four assessment points (these assessment points may in fact coincide with milestones). For each of these points the following should be provided: |
|
|
|
| | - a detailed description of the objectives of the work to be completed |
|
| | - completion date |
|
| | - What this assessment point contributes to the overall project |
|
| | - who is to conduct the assessment (eg. tutor, customer). |
|
|
|
> | Project Completion Review - a committee comprising tutor(s), the customer (or nominee) and student(s) are required to review the project on completion. The project must be formally presented to this committee. An end-of-project report (approximately 20-40 pages) will also be required. |
|
| Assessment Point | Suggested/AssessmentPercentages | Initial projectproposal | 5 | Assessment points as defined bythe project teamin an assessment schedule | 65-75 | Project completion review | 10-15 | Presentationof ProjectReview | 10-20 |
|
|
|
CRITERIA USED IN AWARDING GRADES |
|
|
|
> | Each assessment point: |
|
|
|
| UNSATISFACTORY | - Indicates that the assessment point has not been completed satisfactorily. Further work and a resubmission will be required. |
|
| PASS | - The objectives of the listed assessment point have been successfully completed AND the project log book is up-to-date and shows consistent and regular work. |
|
| NOTE | Because of the difficulty of making accurate time estimates for complex activities and students’ inexperience at doing this, time will not be used as an assessment criteria. |
|
| MERIT | - Criteria above for a Pass both met AND completion of the activities within the estimated time (having due regard for unforeseen external circumstances) AND allowance for the amount of effort required by the student(s) to achieve the assessment point measured in terms of new skills/knowledge gained in completion of activity beyond that covered in course, or the inherent complexity of the task (how quickly could the project tutor have completed the task ?). |
|
|
|
| ASSESSMENT OF THE PROJECT COMPLETION (by committee at end of project): |
|
|
|
| UNSATISFACTORY | - Project does not meet the needs of the customer or the presentation was not satisfactory. |
|
| PASS | - Project adequately meets needs of customer and the presentation was satisfactory. |
|
| MERIT | - Project is judged to be significantly complex or it significantly exceeds customer's initial requirements. An excellent presentation is also required. |
|
|
|
| AWARDING OF GRADES OVERALL FOR THE PROJECT |
|
|
|
| UNSATISFACTORY | - One or more assessment areas have not been passed and further work followed by resubmission is required. |
|
| PASS | - All assessment areas have been passed. |
|
| MERIT | - A Merit pass in the project completion phase was obtained in at least 60% of the project work from the assessment points defined in the assessment schedule (the project team may bear this in mind when submitting the schedule).
|