Assessment Description
Course: Information Software and Technology
Task Topic: Independent Development Project
Year: 10 2021
Task Details:
Assessment Task No. 3. Individual Project
Due Date: Term 4 Week 1
Submission Instructions
1.
This is an assessment task and will contribute
towards your FINAL assessment.
2. It is vital that
your work is continually saved to Cloud Storage (GitHub, Google Drive etc), on
a USB stick or to the network.
No excuses are acceptable for loss of work due to computer or student error. All
of your work should be done on school equipment.
3. Students must submit all the work into GitHub (and share Repository URL with
Teacher) or in a Google Drive folder
(sharing with Teacher).
No submission by
email is accepted.
4. Work must be
easily viewed using any school computer
Outcomes being assessed
1. knowledge and understanding of a
range of computer software and hardware, 5.1.1, 5.1.2
2. problem-solving and critical
thinking skills in order to design and develop creative information and
software technology solutions for a variety of real-world problems,
5.2.2
3. responsible and ethical attitude
related to the use of information and software technology, 5.3.1,
5.3.2
Task Description
Summary:
Students will define and plan a
project of their own choosing. They
may choose any suitable technology as long as it is approved by the teacher.
The students will
need to
· Define
their own Requirements (identifying the main success criteria) for a
software product,
· Design
the solution and Implement the software product.
· They will also need to Test and Evaluate
their system against their original success criteria in the Requirements
definition and then propose some relevant extension features for future
developments of their product.
In order to undertake
this task you need to:
Task 1: Define and Analyse Problem / Requirements
1.
In this section of the document the Student will need to Identify the Problem.
One of the first tasks that must be done before we can solve any problem is to
identify the need for a solution or work out exactly what the problem is
a.
Define Key Stakeholders
i. Who is the Target Audience of the system?
ii. Who is going to benefit/impacted directly by the
system you are defining - what are their current circumstances
iii. Who is it that is having a problem that you would
wish to solve
E.g.
A Year 5 student needs to practice the spelling of basic words given in his
weekly vocabulary lists. The student
finds it tedious to just simply look up a dictionary and learn to spell words. They do not have family or friends that will
help them learn to spell.
b.
Define the Needs
i. Define, from the point of view of the Key
Stakeholder what their real-world need/problem is
- 1. The key stakeholder needs to …
- 2. For example…
- a. The student needs tobe able to learn the spelling of the words given in a weekly vocabulary list
- ii. have the words randomly stored and then chosen and presented to them for spelling.
- iii. Needs to make it fun and challenging to learn the spelling of the words
ii. Success Criteria for New System
1.
Create a detailed list of functions the system will need to have to
satisfy the needs / problems of the key stakeholder
2.
E.g.
a.
The system must be able to
i. Store a list of words
ii. Randomly choose words
iii. Speak the Words that
needs to be spelt
iv. Provide a means of
entering the letters that spell the words in a challenging and engaging way.
v. Give a score on how
close their were able to spell the words
vi. Store scores and show
them again to allow the student to see if they have improved the next time.
Marking Criteria
You will attract a range of marks depending on you satisfying the
following criteria
|
Marking
Criteria
|
Max Mark
|
|
Key Stakeholders
|
|
|
Identifies, with
specific detail, the Key Stakeholder who will use the system
|
Describes in detail
the Key Stakeholder's current circumstance
|
|
|
|
|
|
0-3
|
0-5
|
|
|
|
8
|
|
Key Stakeholder's Needs
|
|
|
Clearly
identifies Stakeholder needs in detail
|
Explains how the
Client Needs relate to the Key Stakeholder's current circumstances
|
Provides a
Comprehensive List of System Requirements as Success Criteria for the new
System
|
Students clearly link
which Client Need the System Requirement will satisfy
|
|
|
|
0-5
|
0-10
|
0-10
|
0-5
|
|
30
|
|
Factors that impact on Problem solving
|
|
|
Students identify at
least one Factor that impacts solving of problem
|
Student explains how
the factor will impact on problem solving
|
|
|
|
|
|
0-2
|
0-5
|
|
|
|
7
|
|
|
|
|
|
MAX
|
45
|
Task2: Identify and Design Solutions
1.
In this section of the document the Student will need to Identify and Design A Solution to the
Problem.
To demonstrate you know how to solve a problem, you must firstly be able to
briefly describe what the system is going to do. This can be documented, in words as a Story,
and graphically as a Storyboard
a.
Story
Document
a set of Scenarios that explain how a User may use the new system. Summarise how a user may interact with the
system in each scenario.
For example,
i. Scenario 1: User starts up system
1.
User starts system and is shown a splash screen and Main Menu
2.
Dramatic music will be playing in the background
3.
User is prompted to either Start Game, View High Score or Exit the Game
ii. Scenario 2: User chooses to
starts game
1.
The User is displayed the game screen and plays game until they win or
lose
iii. Scenario 3: User chooses to View
High Score
1.
High scores are retrieved from the database
2.
Scores are formatted and displayed on screen
3.
User is prompted to return to Main Menu
iv. Scenario 4: User chooses to Exit Game
1.
User is thanked for playing the game
b.
Storyboard
i. For each of the
scenario's written above, create a Storyboard
1.
Each screen is drawn showing the main
screen elements - detailed text/words
not necessary.
2.
Each main screen element is annotated (
a.
Briefly describing what it is.
E.g.
i. an image of a … ,
ii. a button navigating to…,
iii. a video/animation
showing …,
iv. text briefly saying …
3.
Non-screen elements are documented
a.
If a backing sound track used, then please indicate the title of sound
track and artist
c.
Input Process Output Diagrams
i. For each scenario
document the user interactions using an Input
Process Output (IPO) Table
1.
E.g. A slightly modified IPO table includes the Source User or the
Destination (Sink) User for each interaction
|
Source
|
Input
|
Process
|
Output
|
Sink
|
|
Student
|
Vocabulary List
|
·
Store Vocabulary List
·
Randomly choose a word
·
Say word
|
Chosen Word is said
|
Student
|
|
Student
|
Letters that spell word that was heard
|
·
Letters entered are compared against Chosen Word.
·
The percentage match is calculated using Fuzzy
Logic
·
Percentage match is displayed to User
·
Store Percentage
Match with each word attempted
·
If not 100%, then the User is asked if they want
to try again
·
If 100% match, then congratulate student and say
next word
|
You managed to get X% Percentage
Match
You did not spell word correctly, try again
Congratulations, you spelt it correctly.
|
Student
Student
Student
|
|
Student
|
Try Again
|
·
Failed word is spoken again
·
Repeat above process to guess the spelling of
word
|
Chosen Word is said
|
Student
|
|
Student
|
Try Next
|
·
Randomly chose another word that is not the same
as previously used words
·
If no more words, then Congratulate, print
summary of attempts
·
Say next Chosen Word
·
Repeat process above to guess word
|
Congratulations! All words completed.
Chosen Word is said
|
Student
Student
|
|
Student
|
Exit Requested
|
·
Gather percentages and produce Statistics on
success rates for each word attempted
|
Percentage Match Statistics Displayed for each word attempted
|
|
|
Student
|
View High Score Request
|
·
Data store accessed to return the high scores
·
Names & Scores are sorted from highest to
lowest
·
Data is formatted & displayed
|
Names and Scores
|
Student
|
|
Marking Criteria
|
Max Mark
|
|
Task 2. Identify and Design Solution
|
|
|
Story
|
|
|
Story is structured
well, using different Scenarios that describes each interaction with the
sytem
|
Each Scenario
identifies which Key Stakeholder/User is creating the interaction
|
Each scenario
describes the actions (in simple non technical terms) that result from the
initial interaction
|
|
|
|
|
0-3
|
0-5
|
0-7
|
|
|
15
|
|
Storyboard
|
|
|
Clearly drawn
storyboard that shows the main elements
|
Navigation is clearly
shown
|
Screen Elements are
annotated with meaningful descriptions
|
Non Screen Elements,
e.g. Sound tracks, are annotated on relevant Screen
|
|
|
|
0-5
|
0-3
|
0-5
|
0-2
|
|
15
|
|
Input-Process-Output Diagram
|
|
|
IPO correctly created
with appropriate Inputs, Processes and Outputs
|
Each Scenario is
clearly documented
|
Source and Sink Users
have been identified
|
|
|
|
|
0-5
|
0-8
|
0-2
|
|
|
15
|
|
|
|
|
|
MAX
|
45
|
Task 3: Creates Solution
1.
In this section of the document the Student will provide copies in an
accessible area for the Teacher to be able to mark.
a.
All source code/executables must be provided in either/both GitHub or
Google Drive
b.
Your GitHub repository and/or Google Drive folder must be shared with
your teacher
|
Marking Criteria
|
Max Mark
|
|
Task 3. Creates Solution
|
|
|
Application works
without any runtime errors
|
Application works
without any logic errors – e.g. incorrect values calculated, unexpected
behaviour
|
Application fulfils all
the Success Criteria/requirements
|
Application closely follows
stories and storyboards
|
Graphical User
Interface looks good and is user friendly
|
|
|
0-10
|
0-10
|
0-10
|
0-10
|
0-10
|
50
|
Task4: Critical Evaluation
1.
In this section of the document the Student will evaluate the success
of their application, in regards to the initial Requirements and Designs, as
well as highlighting and justifying any future enhancements that they feel
would be beneficial to the future success of the application.
a.
Each Success Criteria is discussed examining how well or how not well
they were catered for
i. Describe aspects of the
Application or Development Process that contributed to the success/failure of
the Success Criteria
b.
Explain what type of improvements you could make to the Application in
future versions.
i. Include a reference to
the existing Success Criteria that is relevant to the enhancement
ii. If a new Success
Criteria, explain how that new criterion will contribute to satisfying the
Client Needs.
|
Marking Criteria
|
Max Mark
|
|
Task 4. Critical Evaluation
|
|
|
Evaluates the success
or failure of the Application.
|
Relates the
Evaluation to the relevant Success Criteria
|
Describes how well
the Application fulfils requirements. Describing the aspect of the
Application that contributed to the Success Criteria being satisfied
|
Describes Future
Enhancements that could be made
|
Future enhancements
are justified and tied back to Success Criteria
|
|
|
0-5
|
0-5
|
0-10
|
0-5
|
0-05
|
30
|
Project Portfolio Template
Please find a copy of a template document for the Requirements Document, Design Document and Critical Evaluation
https://drive.google.com/open?id=1HWLAPOmtgGFBhqlaM85hgcPBQe7sczp1
