[Year 12 SofDev] Thoughts on the 2020 study design - Software Development

Tue Mar 12 03:18:27 UTC 2019

Hi all. Here are some brief observations about the 2020 SD course.

Unlike the new Informatics, SD shows its confident identity and enduring
relevance by staying relatively unchanged.

Software development (SD)

*SD U3 AOS1 - SD: programming*

*SD U3O1*
"interpret teacher-provided solution requirements and designs, and apply a
range of functions and techniques using a programming language to develop
and test working software modules."

*SD U3O1 KK*
- selection/quick sorting is now in U3 instead of U4.
- internal documentation used to include 'comments and meaningful names'.
Now it includes 'meaningful comments and syntax'. Meaningful syntax??
What's that?? **
- SD U3O1 KK14 - "purposes and characteristics of internal documentation,
including meaningful comments and syntax."
This is confusing and ambiguous. Neither interpretation makes sense.
It either means:
1. "including meaningful comments and [meaningful] syntax."
or
2. "including:
- meaningful comments
- syntax."

If it's #1, what is 'meaningful syntax'?
If it's #2, how is syntax relevant to internal documentation?

The previous design said it better: " including comments and meaningful
names". That made sense.

- Under key skills, there is an empty dot point at the end of the list.

*SD U3 AOS2*

*SD U3O2*
"analyse and document a need or opportunity, justify the use of an
appropriate development model, formulate a project plan, generate
alternative design ideas and represent the preferred solution design for
creating a software solution."

*SD U3O2 KK*

- KK01- "security considerations influencing the design of solutions,
including authentication and data protection"
Authentication of what? Users? The software? I'm not sure.
- KK02 - "techniques for collecting data to determine needs and
requirements, including interviews, observation, reports and surveys"
How can reports collect data? Don't they present data?
- KK12 - after a long hiatus, agile, spiral and waterfall development
models are back!

*SD U4*

*SD U4 AOS1 - development and evaluation*

*SD U4O1*
"develop and evaluate a software solution that meets requirements, evaluate
the effectiveness of the development model and assess the effectiveness of
the project plan."

*SD U4O1 KK*
- KK01 - "procedures and techniques for handling and managing files and
data, including archiving, backing up, disposing of files and data and
security"
This is the same bad grammar/punctuation as in Analytics U4O1. This time,
however, they are disposing of files, data AND security!
- KK02 - "ways in which storage medium, transmission technologies and
organisation of files affect access to data"
"medium" is singular. It should be "media" (plural). *Bad* VCAA. Bad.

SD U4 AOS2 - Cybersecurity

*SD U4O2*
"respond to a teacher-provided case study to examine the current software
development security strategies of an organisation, identify the risks and
the consequences of ineffective strategies and recommend a risk management
plan to improve current security practices."

*Assessment summary*

*SD U3O2*

A project plan (Gantt chart) indicating tasks, times, milestones,
dependencies and critical path
AND
A justification of the selected development model as a written report
AND
An analysis that defines the requirements, constraints and scope of a
solution in the form of a software requirements specification
AND
A folio of alternative design ideas and detailed design specifications of
the preferred design.

*SD U4O1*
A software solution that meets the software requirements specification
AND
Preparation and conduction of usability tests
AND
    • an evaluation of the efficiency and effectiveness of the software
solution
    • an evaluation of the effectiveness of the selected development model
    • an assessment of the effectiveness of the project plan (Gantt chart)
in monitoring project progress
in one of the following:
    • a written report
    • an annotated visual plan.

- "Preparation and *conduction* of usability tests" - OUCH! Conduction
refers to the transmission of heat, electricity or sound. Try 'conducting'.

I have attached a summary of the 2020 SD KK for your weekend relaxation
material.

Regards,
Mark
-- 

Mark Kelly

mark at vceit.com
http://vceit.com
Twitter @vceitcom
<https://twitter.com/intent/follow?original_referer=http%3A%2F%2Fvceit.com%2Fwp%2F&ref_src=twsrc%5Etfw&region=follow_link&screen_name=vceitcom&tw_p=followbutton>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://edulists.com.au/pipermail/sofdev/attachments/20190312/457894bc/attachment-0001.html>
-------------- next part --------------
SD u3o1 - 
SD U3O1 KK01 - characteristics of data types
SD U3O1 KK02 - types of data structures, including associative arrays (or dictionaries or hash tables), one-dimensional arrays (single data type, integer index) and records (varying data types, field index)
SD U3O1 KK03 - methods for documenting a problem, need or opportunity
SD U3O1 KK04 - methods for determining solution requirements, constraints and scope
SD U3O1 KK05 - methods of representing designs, including data dictionaries, mock-ups, object descriptions and pseudocode
SD U3O1 KK06 - formatting and structural characteristics of files, including delimited (CSV), plain text (TXT) and XML file formats
SD U3O1 KK07 - a programming language as a method for developing working modules that meet specified needs
SD U3O1 KK08 - naming conventions for solution elements
SD U3O1 KK09 - processing features of a programming language, including classes, control structures, functions, instructions and methods 
SD U3O1 KK10 - algorithms for sorting, including selection sort and quick sort
SD U3O1 KK11 - algorithms for binary and linear searching
SD U3O1 KK12 - validation techniques, including existence checking, range checking and type checking
SD U3O1 KK13 - techniques for checking that modules meet design specifications, including trace tables and construction of test data 
SD U3O1 KK14 - purposes and characteristics of internal documentation, including meaningful comments and syntax.
Sd u3o2 - 
SD U3O2 KK01 - security considerations influencing the design of solutions, including authentication and data protection
SD U3O2 KK02 - techniques for collecting data to determine needs and requirements, including interviews, observation, reports and surveys
SD U3O2 KK03 - functional and non-functional requirements
SD U3O2 KK04 - constraints that influence solutions, including economic, legal, social, technical and usability
SD U3O2 KK05 - factors that determine the scope of solutions
SD U3O2 KK06 - features and purposes of software requirement specifications
SD U3O2 KK07 - tools and techniques for depicting the interfaces between solutions, users and networks, including use case diagrams created using UML
SD U3O2 KK08 - features of context diagrams and data flow diagrams
SD U3O2 KK09 - techniques for generating design ideas
SD U3O2 KK10 - criteria for evaluating the alternative design ideas and the efficiency and effectiveness of solutions
SD U3O2 KK11 - methods of expressing software designs using data dictionaries, mock-ups, object descriptions and pseudocode
SD U3O2 KK12 - factors influencing the design of solutions, including affordance, interoperability, marketability, security and usability
SD U3O2 KK13 - characteristics of user experiences, including efficient and effective user interfaces
SD U3O2 KK14 - development model approaches, including agile, spiral and waterfall
SD U3O2 KK15 - features of project management using Gantt charts, including the identification and sequencing of tasks, time allocation, dependencies, milestones and critical path
SD U3O2 KK16 - goals and objectives of organisations and information systems
SD U3O2 KK17 - key legal requirements relating to the ownership and privacy of data and information.
Sd u401 - 
SD U4O1 KK01 - procedures and techniques for handling and managing files and data, including archiving, backing up, disposing of files and data and security
SD U4O1 KK02 - ways in which storage medium, transmission technologies and organisation of files affect access to data
SD U4O1 KK03 - uses of data structures to organise and manipulate data
SD U4O1 KK04 - processing features of a programming language, including classes, control structures, functions, instructions and methods
SD U4O1 KK05 - characteristics of efficient and effective solutions
SD U4O1 KK06 - techniques for checking that coded solutions meet design specifications, including construction of test data
SD U4O1 KK07 - validation techniques, including existence checking, range checking and type checking
SD U4O1 KK08 - techniques for testing the usability of solutions and forms of documenting test results
SD U4O1 KK09 - techniques for recording the progress of projects, including adjustments to tasks and timeframes, annotations and logs
SD U4O1 KK10 - factors that influence the effectiveness of development models
SD U4O1 KK11 - strategies for evaluating the efficiency and effectiveness of software solutions and assessing project plans.
Sd u4o2 - 
SD U4O2 KK01 - physical and software security controls used to protect software development practices and to protect software and data, including version control, user authentication, encryption and software updates
SD U4O2 KK02 - software auditing and testing strategies to identify and minimise potential risks
SD U4O2 KK03 - types of software security and data security vulnerabilities, including data breaches, man-in-the-middle attacks and social engineering, and the strategies to protect against these
SD U4O2 KK04 - types of web application risks, including cross-site scripting and SQL injections
SD U4O2 KK05 - managing risks posed by software acquired from third parties
SD U4O2 KK06 - characteristics of data that has integrity, including accuracy, authenticity, correctness, reasonableness, relevance and timeliness
SD U4O2 KK07 - reasons why individuals and organisations develop software, including meeting the goals and objectives of the organisation
SD U4O2 KK08 - key legislation that affects how organisations control the collection, storage (including cloud storage) and communication of data: the Copyright Act 1968, the Health Records Act 2001, the Privacy Act 1988 and the Privacy and Data Protection Act 2014
SD U4O2 KK09 - ethical issues arising during the software development process and the use of a software solution
SD U4O2 KK10 - criteria for evaluating the effectiveness of software development security strategies
SD U4O2 KK11 - the impact of ineffective security strategies on data integrity
SD U4O2 KK12 - risk management strategies to minimise security vulnerabilities to software development practices.