Stage 6 Software Design and Development

HSC Assessment Task 3

Topic: Developing a Solution Package

Task Name: Analyst Report

Weighting: 15%

Date Received: 9th December 2008

Date Due: 4th May 2009

Submission Instructions:
1. Students are required to hand their assignments to their teacher during
class time on the specified day.
2. Students are required to submit their marking criteria and sign the
confirmation below.

Student Confirmation:

I, ___________________________ have completed this task without

plagiarising the work of others. It is all my own work. I am also aware
that a non-submission on or before the due date will incur a penalty of
100% of total marks.
Signature:____________________

Outcomes Being Assessed:

This assessment will establish whether the student understands the following outcomes:
H3.1, H3.2, H4.1, H4.2, H4.3, H5.1, H5.2, H5.3, H6.3, H6.4

1
 TASK DETAILS

Cross Curriculum Links

 KC1 Research skills, KC3 Organising, KC6 Solving algorithm problems
and KC7 Using technology.
 Literacy – Report and folio writing.
 ICT – Word-processing and graphs.

Context for the Task

Students will receive guidance through the steps of the software
development cycle. All aspects needed to create the documentation will be
scaffolded in class time. All students will be expected to utilise class time for
the completion of this project which will require good time management
skills. Students will also be expected to integrate the programming skills
they have learnt in class with skills researched outside of school.

Task Description
You are required to follow the Software Development Cycle to create a
piece of computer software with a purpose of your own choosing. The
software should meet either a personal or local need and should be coded
in Visual Basic.NET. As a minimum requirement, the software should read
from and write to a file or database, utilise complex data types and show
advanced programming features expected of year 12 SDD student. Your
task is to design and create a program to achieve this purpose. This project
is to be submitted separately in two parts on the dates given.

2
 Task Rubric

Analyst Report

Your report will document the stages in the software development cycle.

Stage 1: Defining and Understanding the problem

i. Problem Definition – Define the problem.

ii. Preliminary Analysis - User needs, system needs, developer
needs.
iii. Objectives - Clear list of objectives.
iv. Feasibility Study - Conduct a feasibility study, which can be used
to address all the necessary constraints and conclude results.
v. Modelling - Representation using appropriate diagrams.
vi. Project Management - Application of project management
techniques. (Gantt Chart & Diary1)

Stage 2: Planning and designing of software solutions

i. Storyboard - Documentation of Interface design and navigation

ii. Data Dictionary - Create a data dictionary describing the data
types and data structures to be used.
iii. Algorithms - Provide a detailed description of the logic of each
module in the form of an algorithm in either Flowchart or
Pseudocode. Evidence of a modular approach to your software
development is required during this section.
iv. Structured Walkthrough / Peer checking – Demonstrate thorough
peer checking of algorithms through desk checking or other suitable
documentation.
v. Screen Designs - Create a set of final screen design diagrams and
highlight appropriate screen elements.

1
The assessment of the project diary will be an ongoing process from the beginning of Term 1 2009.
Students must post their project diary entries on Google Blogger - http://www.blogger.com/home [All
students are required to create an account. Accounts MUST be registered as InitialSurname (or
FirstnameSurname) to make students easily identifiable.]

3
 Marking Criteria

Assessment Task 3

Name: ________________________________________________________

Report Stage 1

(i) Problem Definition (5 Marks)

Outcome Criteria Mark
Student presents a comprehensive definition of a suitable
problem. 4–5
H4.1 Student presents a satisfactory definition of problem. 2–3
Student presents a poor definition of a problem 1

(ii) Preliminary Analysis (5 Marks)

Outcome Criteria Mark
Student presents a comprehensive analysis of the needs of the
intended software solution, including user and developer needs. 4–5
Student presents a satisfactory analysis of the needs of the
H4.1 intended software solution. 2–3
Student presents a poor analysis of the needs of the intended
software solution. 1

(iii) Objectives (5 Marks)

Outcome Criteria Mark
Student presents a comprehensive and thoughtful list of
objectives required to solve the software solution. 4–5
H3.1 Student presents a satisfactory list of objectives required to
solve the software solution. 2–3
Student presents a poor list of objectives. 1

(iv) Feasibility Study (15 Marks)

Outcome Criteria Mark
Student presents a comprehensive and well researched
feasibility study, by analysing operational, technical, scheduling 13 – 15
and economic feasibilities of the solution.
Student presents a thoroughly researched feasibility study that
H3.1 demonstrates basic analysis of operational, technical, 10 – 12
scheduling and economic feasibilities.
Student presents a satisfactorily researched feasibility study. 7–9
Student presents a limited feasibility study. 4–6
Student presents a poor feasibility study. 1–3

4
(v) Modelling (20 Marks)
Outcome Criteria Mark
Appropriate forms of modelling are used accurately and
comprehensively to represent the project. IPOs, Structure
diagrams and DFDs must be included. System flowcharts may 17 – 20
be included if appropriate to the project.
Appropriate forms of modelling are used accurately and
thoroughly to represent the project. IPOs, Structure diagrams
and DFDs must be included. System flowcharts may be 13 – 16
included if appropriate to the project.
H5.2 Student presents a satisfactory attempt at modelling the
intended project by showing at least two types of modelling 9 – 12
techniques.
Student presents a limited attempt at modelling the intended
project; there may be some minor inaccuracies in representation 5–8
or only one form of modelling is used.
There is little evidence of modelling. Techniques used may not
be accurate. 1–4

(vi) Project Management (10 Marks)

Outcome Criteria Mark
Student presents a comprehensive Gantt Chart and project
diary2 that promotes effective project management and includes
all relevant features. Project diary has been maintained 9 – 10
throughout the project.
Student presents a thorough Gantt Chart and project diary that
promotes effective project management and includes most
relevant features. Project diary has been maintained throughout 7–8
H5.1 the project.
Student presents a satisfactory Gantt Chart and diary that
includes some relevant features; OR student presents a
comprehensive project diary, but no Gantt Chart. Project diary 5–6
has been maintained throughout the project.
Student presents a limited Gantt chart and diary; OR student
presents a satisfactory project diary, but no Gantt Chart. 3–4
Student presents a poor Gantt Chart or diary. 1–2

Report Stage 2

(i) Storyboard (5 Marks)

Outcome Criteria Mark
Student presents a comprehensive storyboard that highlights
effective navigation between the screens in the proposed 4–5
interface.
H6.4 Student presents a satisfactory storyboard that shows
navigation. 2–3
Student presents a poor storyboard. 1

2
See point 1.

5
(ii) Data Dictionary (10 Marks)
Outcome Criteria Mark
Student presents a comprehensive data dictionary that
describes all data types and data structures that are required to 8 – 10
create the software solution.
H5.2 Student presents a satisfactory data dictionary that attempts to
describe either data types or data structures used. 4–7
Student presents a poor data dictionary. 1-3

(iii) Algorithms (20 Marks)

Outcome Criteria Mark
Student presents a detailed set of algorithms describing each
module required to solve the solution and displaying the passing
of parameters between sub-modules. Methods of algorithm 17 – 20
description are accurately applied.
Student presents a clear set of algorithms describing most
modules required to solve the solution and displaying the
passing of parameters between sub-modules. Methods of 13 – 16
algorithm description are accurately applied.
H4.2, H4.3 Student presents a satisfactory set of algorithms describing most
modules required to solve the solution and attempting to display
the passing of parameters. Methods of algorithm description are 9 - 12
essentially accurate.
Student presents a basic set of algorithms describing some
modules required to solve the solution. 5–8
Student presents a poor set of algorithms descriptions, not
showing any modules. 1–4

(vi) Structured Walkthrough / Peer checking (10 Marks)

Outcome Criteria Mark
Student presents comprehensive documentation demonstrating
thorough peer checking that tests all possible paths that the 8 – 10
algorithms can take.
H4.2 Student presents satisfactory documentation demonstrating peer
4–7
checking that tests most paths that the algorithms can take.
Student presents documentation demonstrating limited peer
checking. 1-3

(vii) Screen Designs (10 Marks)

Outcome Criteria Mark
Student presents a comprehensive set of final screen designs,
detailing all screen elements required in each screen. 8 – 10
H6.4 Student presents a satisfactory set of final screen designs,
detailing some screen elements required in each screen. 4–7
Student presents a poor set of final screen designs. 1-3

6
(viii) Quality project (10 Marks)
Outcome Criteria Mark
Student presents a comprehensive report that plans a
sophisticated project. 8 – 10
Student presents an effective report that plans a project showing
H4.3 some sophistication. 4–7
Student presents a clear report for a project that demonstrates
limited sophistication. 1-3

/125

7
 Student Evaluation
Circle a number (1 = strongly agree to 5 = strongly disagree)

This is my best work 1 2 3 4 5

I was organised 1 2 3 4 5

I understood the task 1 2 3 4 5

I took notice of marking guidelines 1 2 3 4 5

The outcomes I feel I have demonstrated best was outcome number________

The outcome I found most challenging was outcome number________

This assessment took me 0-1 2-3 4-5 6-7 8+ hours to complete

Next time I will:

At the time of review of the task:

I could improve the following skills by-

Skill Method of Improvement

I would like to seek further clarification or assistance with:

Please complete the following section following the return of the task:

Student Name :

Student Signature:

Parent Signature:

Parent Comment (optional):