units 3 and 4 software development · prepare project plans ! software for ! programming language...

Units 3 and 4 Software development

Implementation program April to May 2015

VCAA and Digital Learning and Teaching Victoria (DLTV)

q Software Development has experienced a 9% increase in numbers since last year

q IT Applications has experienced a 9.5% increase in numbers since last year

The Good News

Agenda

q Important information q Changes for 2016 q Structure of Software Development q School-based assessment q School Assessed Coursework q School Assessed Task q Delivering a course q Units 3 & 4 Outcomes q Examination

Study Design

Study Design

q Accreditation period (Study Design) •  1st January 2016 – 31st December 2019

q SAT training day in February 2016 q Visit the VCAA webpage regularly q Subscribe to and read the VCAA Bulletin q Advice for Teachers (coming out in Term 4)

•  Assessment Criteria

Important Information

Changes for 2016

Why change?

q More coding •  Students want more

q Options for new languages and flexibility •  Possibility for students in one class to be using different

languages q Future proofing q Decent sized software solutions

•  Apps/games/robotics etc

Source: Paula Christopherson

Key changes

q No approved programming languages list q U4O2 – change of focus (report – no longer a test) q School-assessed Task (project over two

outcomes) q Introduction of types of thinking

Source: Paula Christopherson

Questions

Structure of Software Development

Sof Dev focus – software solutions and systems

Programming practice

Analysis and design

Software solutions

Interactions and impact

Source: Paula Christopherson

U3 AoS 1 Programming

practice

U3 AoS 2 Analysis and

design

U4 AoS 1 Software solutions

U4 AoS 2 Interactions and impact

SAC Set of code

modules SAC

written report or visual report

U3 O1 U3 O2 U4 O1 U4 O2

SAT Solution analysis Software

Folio of design solution ideas written report or Project plan visual plan

Software for -­‐ Programming language

Software to -­‐ Prepare project plans

Software for -­‐ Programming language -­‐ Document project progress

Exam

Source: Chris Bucknell

Software Development Structure

School–based Assessment

School-based assessment

U3O1(SAC) 10% study

score

U3O2 (SAT) 15% of study

score

U4O1 (SAT) 15% of Study

score

U4O2 (SAC) 10% study

score

GA1 (SACs) 20% GA2 (SAT) 30% GA3 (Exam) 50%

Source: Paula Christopherson

School Assessed Coursework

Unit 3 Outcome 1 - SAC

Unit 4 Outcome 2 - SAC

Assessing SACs

q There will be Advice for Teachers q Rubrics have been written by the VCAA q Teacher still has control of SACs q Similar to Performance Descriptors in current

Assessment Handbook, but as a rubric q Descriptors will be read from left to right against

the Outcome statement (similar to the SAT) q More on the next slide

Assessing SACs

q Just to give you some idea of the descriptors: •  They will be a five point system from:

– Very Low, Low, Medium, High, Very High •  Include:

– Software designs – Appropriately selected data types and data structures – Use of appropriate processing features – Appropriate range of test data – Tests successfully applied – Complete internal documentation – Modules that meet requirements of designs

Questions

School Assessed Task

School-assessed Tasks

Extended project – over two outcomes

Mandated assessment criteria

Scores for each outcome are reported separately (see informatics)

Ongoing teaching/learning/assessing process

Individual projects for authentication (e.g. app; planning project; web service, SML stream, games

Source: Paula Christopherson

SAT components

SAT U4 O1 U3 O2

Analyse and document a need

or opportunity; generate

alternative design ideas;

preferred solution design

Create a solution that

fulfils requirements.

Formulate project plan

Evaluate project plan

project plan

U3O2 -  Analysis (SRS) -  Folio of design

ideas -  Detailed design U4O1 -  Software solution -  Annotated

project plan

Source: Chris Bucknell

Unit 3 Outcome 2 & Unit 4 Outcome 1 - SAT

Assessing the SAT

Sample Assessment Criterion from Algorithmics

Sample Assessment Sheet from Algorithmics

Sample Authentication Record from Algorithmics

SAT documentation

http://www.vcaa.vic.edu.au/Documents/vce/algorithmics/SBA_algorithmics.pdf

Questions

Developing your course

q VCAA Workshop 2016 q Study Design

•  Glossary •  Problem-solving methodology •  Units 3 & 4 O1 & O2s Key Knowledge and Key Skills

q Advice for Teachers •  Sample activities

q Assessment Criteria

Developing the course

q Look at each semester in the school calendar q Give around:

•  40% to U3 O1 60% to U3 O2 •  60% to U4 O1 40% to U4 O2

q Work out how many Key Knowledge points you can deliver each week •  Mix practical and theory

q Assign time for a Practice SAC (S/N) q Assign time for the SAC/SAT q Put into a course timeline/outline

Allocating time to the course

q Create a table and focus on: •  Week no •  Dates for each week •  Interruptions for each week (school) •  Key Knowledge to be delivered each week •  Practical work to be delivered each week •  Timing of the Practice task •  Timing of the SAC/SAT

Developing the course outline

Unit 3 – Outcome 1

Unit 3 Outcome 1

Unit 3 Outcome 1

New terminology: q XML file formats

•  Structured data file format •  Office documents and web services

q Linear searching •  Searching for an element in an array element-by-

element q Trace tables

•  Techniques for testing algorithms using a table

Unit 3 – Outcome 2

Unit 3 Outcome 2

Unit 3 Outcome 2

New terminology: q Techniques for idea generation q Interoperability and marketability q User experience q Project management concepts and processes q Application architecture q Legal requirements re: ownership and privacy of

data

Questions

Have a bit of a read over Unit 3

Unit 4 – Outcome 1

Unit 4 Outcome 1

Unit 4 Outcome 1

New terminology: q Associative arrays

•  Arrays with named keys that are associated with a known value

q Usability testing •  More in the next few slides

http://www.slideshare.net/esnowdon/prototyping-and-usability-testing-your-designs

What is usability? – U4O1

Source: Paula Christopherson

Usability techniques

recording

listening

observing http://www.shutterstock.com/

Source: Paula Christopherson

Based on: http://www.slideshare.net/esnowdon/prototyping-and-usability-testing-your-designs

Planning

Test environment

Recruiting

Test materials

Test conduct & debriefing

Analyse results

Report & presentation

Usability test process

U4O1: techniques for testing the useability of solutions and forms of documenting test results

Source: Paula Christopherson

Unit 4 – Outcome 2

Unit 4 Outcome 2

Unit 4 Outcome 2

New terminology: q Types of interactions (inputs and outputs) q Characteristics of data integrity

•  Accuracy •  Timeliness •  Reasonableness •  Authenticity •  Correctness

Analyse and explain the dependencies between two information systems that share data, and discuss the extent to which one information system relies on

the integrity of the data from the source system.

Questions

Have a bit of a read over Unit 4

Examination

Examination

Examination

q Process for writing sample questions for the 2016 Examination is about to begin

q Aiming to be available in Term 4

Questions

Regarding the presentation

Copyright © Victorian Curriculum and Assessment Authority (2015). Third parties may own copyright in some content included in this presentation, as indicated. The term VCE and associated logos are registered trademarks of the VCAA. VCAA content may be used in accordance with the VCAA’s Intellectual Property and Copyright Policy http://www.vcaa.vic.edu.au/Pages/aboutus/policies/policy-copyright.aspx