Internal Assessment 100%

Project (80%)

1.1 Project Assessment

Project assessment is divided into the three-
mark categories of Analysis, Design and
Implementation, and Project Management as
below:

Analysis 40%

- Initial Study
- Feasibility Study
- Analysis

Design and Implementation 30%

- Detailed System Design
- Coding and Testing
- Implementation

Project Management 10%

- Attitude to project
- Setting and meeting deadlines

The distribution of marks within these three
groupings will need to be allocated by the
lecturer with due consideration as to the
nature and magnitude of the project undertaken.
Not all sub-topics need to be addressed by
students dependent upon the nature of the
problem (e.g. the Feasibility study may be
omitted because management did not require
one).

Due to time constraints, it is suggested that when a Feasibility Study is
undertaken, that it be combined with the Analysis report so that a separate
Analysis Report is not required. The recommended breakdown of marks is 10% for
the Initial Study and 30% for the Feasibility/Analysis Report.

1.2 Project Selection

The project may be either a lecturer-approved
project of the student's choosing, or a
lecturer-provided project. Projects may be on-
campus or external to the college, and be on an
individual or group participation basis.

For off-campus projects, any developed systems
must be compatible with and able to be
demonstrated on available TAFE computing
equipment. Should this not be the case, then it is the student's
responsibility to make alternative arrangements, which are to be agreed to by
the lecturer prior to project commencement.

All projects should involve significant systems
development work, and not just be an extended
programming exercise.

1.3 Project Teams

Project may be undertaken by students on either
a group basis or individually. Project teams
of three or over require the nomination of a
Project Leader. It is suggested that project
teams consisting of more than three people be
avoided due to co-ordination problems.

Provision should be made to allow for
individual differences in both attitude and
contribution for group projects. It is
possible and acceptable that some students
working on a group project may pass and others
on the same project may fail. Being a member
of a successful project should not guarantee a
pass.

1.4 Project Content

All projects should be completed to the
implementation stage, inclusive of user
documentation. Some discretion can be exercised for larger outside (i.e.
off-campus) projects, with the minimal requirement for project completion being
the detailed design for the new system. However, students should be actively
encouraged to break larger projects into smaller stages that can be completed
and implemented as their major project.

Systems Analysis Micro Skills
(20%)

Each student is expected to document and present to their classroom group a
Systems Analysis micro skill relevant to their particular project. Their
presentation may be a summary or overview of a data gathering technique carried
out for their project or may be a structured walkthrough. All students
participate in the presentation of micro skills by other students.

2.1 Micro Skills Assessment

The assessment should not be made in terms of
the success or failure of the attempted
technique nor of the smoothness of the
presentation delivery to the class group.
Assessment should be based upon the quality and
degree of preparation by the student.

The purpose of the data gathering Micro Skills
presentations is to encourage a cross-
fertilisation of ideas and experiences amongst
students, rather than for any particular
assessment purpose. For this reason the
emphasis during the micro skill presentations
is to be on learning and sharing experiences
and observations rather than upon assessment.
Assessment is in terms of the quality of the
micro skill preparation rather than factors
related to the presentation performance.

2.2 Micro Skill Topics

The micro skill presentation should take the
form of either:

a review of a data gathering activity
undertaken as part of the project

OR

a Structured Walkthrough of some particular aspect of their project.

A summary of these options follows:

2.2.1 An Interview Review

Summary of an interview conducted by
the student for the major project.

The presentation should include:

- Statement of interview purpose
- The Interview plan
- Necessary supporting documentation
- Delivery summary
- Anecdotal review of problems encountered.

2.2.2 A Forms Analysis Overview

A detailed analysis of data input
forms associated with the student's
project.

The presentation should include:

- Description and explanation of the (intended) purpose and
content of forms
- An indication of problems with the form and suggest
improvements
- An indication of any editing/conversion requirements for
the forms
- Discuss the relevance of the forms to the DFDs and ERDs
for the system.

2.2.3 Survey (Questionnaire) Overview

Description of a (proposed)