VCE Software Development case studies
VCE Software Development · Put your knowledge to work in context.
VCE Software Development is a Victorian Certificate of Education study concerned with how software is designed, built, tested and managed. It suits senior secondary students in Victoria who want to understand the whole software development lifecycle rather than only writing code, and it also appeals to students preparing for further study or entry-level work in information technology. Because the study is administered by the Victorian Curriculum and Assessment Authority, the authoritative statements about the study are published in the VCE study design, which this page does not replace. The material here is organised around four areas: software design and development; programming and algorithms; data and information management; and software project management. The VCE Software Development case studies are 4 cases and about 1,790 words.
1The Library App That Nobody Could Log Into
A Year 12 team is building a school library booking app for their SAC. Their design uses three layers: a presentation layer (the web forms), a business layer (booking rules such as 'a student may hold at most three active bookings'), and a data layer (database access).
449 words, about 2 min2Sorting the Canteen Queue Data
A student writes an algorithm to process canteen orders stored as a list of records (order ID, timestamp, item, quantity). The program must output the ten most recent orders, grouped by item, with a total quantity per item.
446 words, about 2 min3The Shared Spreadsheet That Became the Database
A small sports club asks a student to build a membership system. The club currently keeps everything in one spreadsheet: one row per member, with columns for name, address, phone, team name, coach name, coach phone, and a comma-separated list of events the member has entered.
469 words, about 2 min4The Sprint That Kept Slipping
A team of four students is building a quiz app over six weeks for an assessed project. They chose an iterative approach with one-week sprints.
426 words, about 2 min