Software Design &
Development
HSC ASSESSMENT TASK 1
Design
and development of educational software
|
Assessment
task 1 Time
allowed 6 weeks Due
date Week 6, Term
4, 2000 Marks 15 Weighting 15% |
Outcomes to be assessed: H4.3 applies a modular approach to implement well structured software solutions and evaluates their effectiveness H6.4 uses a collaborative approach during the software development cycle H6.4 develops effective user interfaces, in consultation with appropriate people |
This assessment task relates to your group project, designing and
developing a piece of educational software suitable for use by a selected group
of students and their teacher.
This assessment task involves you and your team in submitting specific
material that demonstrates your progress towards achievement of the above
outcomes.
As an individual you are required to submit:
1. An
individual module report that documents the module you developed as part
of the group solution. The report should include:
Ř
the specifications for the module
Ř
evidence of your initial attempts at the module
Ř
the source code for the module (in hard copy
and digital format)
Ř
an explanation of any differences between the
initial attempts and the implemented solution
Ř
test data used and the results from testing
your module
Ř
an explanation of how your module interfaces
with the rest of the solution.
3. Team member
evaluation sheets that evaluate the performance of other members in your
team.
As a group you are required to submit:
1. A group technical report
that documents the entire solution to the problem. The report should include:
Ř
a description of the problem and the
specifications for its solution
Ř
a representation of the solution using a
recognised design tool
Ř
test data used and the results from testing the
solution
Ř
details of any changes made to the problem’s
specifications during the project
Ř
the source code for the solution (in hard copy
and digital format).
2.
Minutes of
all group meetings, including individual responsibilities, decisions made and
reasons.
3.
The finished product: educational software and
user manual.
4. End
user evaluation sheets completed by the teacher and students for whom the
solution was developed.
Student feedback sheet Student’s
name: _________________________
H4.3 Applies a modular approach to implement well structured software
solutions and evaluates their
effectiveness
The minutes of meetings, individual module report, group technical
report and finished product will be used to
look for evidence of:
• appropriate planning for your module
• the correct use of control structures in your module
• efficient and elegant code
• evaluating the module to see that it meets initial specifications
• testing the module
• appropriate connection of the module to the
rest of the code.
|
Comments: /5 marks |
H6.3 Uses a collaborative approach during the software development cycle
The minutes of meetings, self-evaluation form, team problem
• consultation with team members
• participation in group decision-making
• completion of an adequate share of the work
• identification of individual strengths and weaknesses
• identification of strengths and weaknesses in
other team members.
|
Comments: /5 marks |
H6.4 Develops effective user interfaces, in consultation with
appropriate people
The minutes of meetings, individual module report, finished product and
end users’ evaluation forms will be
used to look for evidence of:
• user requirements being met
• user interface being well documented
• user interface being appropriate for age group
• involvement in the consultation with the end user
• involvement in the development of the user interface
• involvement with other members of the team to
develop the user interface.
|
Comments: /5 marks |
TOTAL MARKS: /15 MARKS
(Note: 5 marks indicates that the criteria have
been soundly addressed and 0 marks indicates that no relevant evidence was
found.)