← VCE Software Development U3O2

Version and solution boundaries

A line that sets which features go in the current release and which wait for a later version. It also marks where the solution ends and other systems begin.

Part of: VCE Software Development - U3O2 - Analysis and Design — Module 37, QCE Digital Solutions Unit 1 — Understanding Digital Problems — Module 30, QCE Digital Solutions Unit 3 — Real-World Problems and Solution Requirements — Module 8

Understanding Version and solution boundaries in VCE Software Development U3O2

What it does: The two labels split features into the current release (v1) and a later version (v2), which is what a version boundary does. The bank system sits outside the solution boundary. The app only passes data across the edge to it. Version 1 should include the features that meet the core need. Extras like recommendations can wait for a future version.

Common mistakes: The first heading must be the current release. Login and borrowing are core features, so they sit under V1 (current release). Labelling them 'later release' contradicts the V2 heading below and puts the boundary in the wrong place. The council fine system is another organisation's system, so it lies outside the solution boundary. The line should read 'Outside: council fine system'.

Class: _____________________  ·  Name: _____________________  ·  Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

🖨 Print worksheet + answer key Add Version and solution boundaries to a class →

This module's key terms are also in a printable crossword (Modules 26–41) and word search (Modules 26–51).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning
Duo
A student club app has a login screen, event list and RSVP button planned. The team decides payments will wait until version 2. What does this decision set?
A version boundaryA data dictionary
Matches
Version 1 must include every feature the client has ever suggested
↓
A version boundary exists to limit version 1 to the key features. Putting every idea in the first release ignores the boundary and risks blowing out time and budget.
Applying
Meanings
Term
version boundary
Meaning
A line that sets which features go in the current release and which wait for a later version. It also marks where the solution ends and other systems begin.
Practice
Version 1 (in scope):
Testing
Gaps
: login, view marks, print report
Check Answer
Spots
1V1 (later release):
2 login, borrow books

Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.

The 'Horned Lizard' badge — Bug Squasher, one of Cloodit's 106 collectible badges
Students earn collectable badges

Over 100 of them, across seven natural biomes.

Study Buddy
Students build a real study resource

Turns their work into revision material ready for Flash Cards and Exam study.

Diamond Dash — one of Cloodit's live, competitive Sprint games
Students lock in with Sprints

Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.

A Cloodit certificate of achievement, ready to personalise and print
Custom printable certificates

Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.

Add to class →

Quick Questions

1. A student club app has a login screen, event list and RSVP button planned. The team decides payments will wait until version 2. What does this decision set?
A. A version boundary ✓
B. A data dictionary
A version boundary decides which features are in the current release and which are left for a later version.
2. Which feature belongs inside the version 1 boundary of a library book-loan system?
A. Borrowing and returning books, because it meets the core need ✓
B. A mobile app with book recommendations, listed as a nice-to-have for later
Version 1 should include the features that meet the core need. Extras like recommendations can wait for a future version.
3. True or false: Features left out of version 1 are deleted from the project forever.
A. False. They can be planned for a future version. ✓
B. True. Once they are outside the boundary they are gone.
Features outside the version 1 boundary are not deleted. They are recorded for later versions.
4. A canteen ordering system sends payments to a bank's payment system. Where does the solution boundary sit?
A. Inside the canteen system, so the team must build the bank's payment system
B. Between the canteen system and the bank's system ✓
The boundary marks where the solution ends and other systems begin. The bank's system is outside the solution.
5. Which statement best describes why a team sets a version boundary?
A. It lets the team add every idea the client mentions during development
B. It keeps the project achievable within the time, budget and skills available ✓
A boundary limits the work to what can be delivered in the release. Adding every idea leads to scope creep.

Match the Pairs

Version 1: login, add task, view task list → The features inside the version boundary. They will be built and released in the current version.
Future version: sync tasks with phone calendar → A feature outside the version boundary. It is left for a later release.
A version boundary sets which features belong in the current release and which are left for a later version. → In scope (v1): search books | Out of scope (v2): book reviews
The solution boundary marks where the solution ends and other systems begin. → Our app sends payment details to the external bank system
Version 1 must include every feature the client has ever suggested → A version boundary exists to limit version 1 to the key features. Putting every idea in the first release ignores the boundary and risks blowing out time and budget.
The school's existing payroll system is part of our new timetable app → The payroll system is a separate, existing system, so it sits outside the solution boundary. Our app may exchange data with it but does not include it.

Key Term

version boundary
A line that sets which features go in the current release and which wait for a later version. It also marks where the solution ends and other systems begin.

Fill in the Blanks

1. Version 1: login, view marks, print report
Hint: Type the label for the release being built now.
2. Version 2: parent alerts, online chat
Hint: Type the number of the later release that holds postponed features.
3. Out of scope: school payroll system
Hint: Type the label for things beyond the solution boundary.
4. IF feature is in Version 1 THEN include feature in release ELSE defer to a later version
Hint: Type the action for a feature that falls inside the version boundary.
5. Version 1 includes: login, view marks Version 1 excludes: parent alerts
Hint: Type the verb meaning a feature is left out of the current release.

Spot the Error

Question 1
A V1 (later release):
B login, borrow books
C V2 (later release):
D overdue emails
Line A — The first heading must be the current release. Login and borrowing are core features, so they sit under V1 (current release). Labelling them 'later release' contradicts the V2 heading below and puts the boundary in the wrong place.
Question 2
A Boundary: Parking App v1
B Inside: permit requests
C Inside: council fine system
D Fines: handled by the council
Line C — The council fine system is another organisation's system, so it lies outside the solution boundary. The line should read 'Outside: council fine system'.
Question 3
A Version 1 features:
B - Browse canteen menu
C - Order for pickup
D Version 1: loyalty points
E Reason: not needed at launch
Line D — Loyalty points are not needed at launch, as the Reason line says. The version boundary leaves them for a future release, so the line should say 'Version 2: loyalty points'.
Question 4
A Plan: Quiz App
B Version 3: create, take quiz
C Version 2: leaderboards
D Version 3: share results
Line B — Creating and taking a quiz is the core function, so it must be in Version 1. Pushing it to Version 3 would leave the first release with no working purpose. It should read 'Version 1: create, take quiz'.
Question 5
A Version 1 scope:
B Include: book a room
C Include: staff payroll
D Reason: separate HR system
Line C — Payroll is handled by a separate HR system, so it falls outside the solution boundary. The line should say 'Exclude: staff payroll' to match the reason given.

Student with a class code? Join your class →