Version and solution boundaries

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

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

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

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.

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

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

Match the Pairs

Draw a line connecting each item on the left to its match on the right.

Left column		Right column
1Version 1: login, add task, view task list		AA feature outside the version boundary. It is left for a later release.
2Future version: sync tasks with phone calendar		BThe 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.
3A version boundary sets which features belong in the current release and which are left for a later version.		CIn scope (v1): search books \| Out of scope (v2): book reviews
4The solution boundary marks where the solution ends and other systems begin.		DThe features inside the version boundary. They will be built and released in the current version.
5Version 1 must include every feature the client has ever suggested		EA 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.
6The school's existing payroll system is part of our new timetable app		FOur app sends payment details to the external bank system

Definitions

version boundary

Fill in the Blanks

Complete each line of code by filling in the missing parts.

_________: login, view marks, print report

Version _: parent alerts, online chat

____________: school payroll system

IF feature is in Version 1 THEN _______ feature in release ELSE defer to a later version

Version 1 includes: login, view marks Version 1 ________: parent alerts

Spot the Error

Shade in the letter of the line that contains an error.

Question 1

A V1 (later release):

B login, borrow books

C V2 (later release):

D overdue emails

Question 2

A Boundary: Parking App v1

B Inside: permit requests

C Inside: council fine system

D Fines: handled by the council

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

Question 4

A Plan: Quiz App

B Version 3: create, take quiz

C Version 2: leaderboards

D Version 3: share results

Question 5

A Version 1 scope:

B Include: book a room

C Include: staff payroll

D Reason: separate HR system

Answer Key

Version and solution boundaries

Section A: Quick Questions

A — A version boundary

A — Borrowing and returning books, because it meets the core need

A — False. They can be planned for a future version.

B — Between the canteen system and the bank's system

B — It keeps the project achievable within the time, budget and skills available

Section B: 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.

Section C: Definitions

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.

Section D: Fill in the Blanks

Version 1: login, view marks, print report

Version 2: parent alerts, online chat

Out of scope: school payroll system

IF feature is in Version 1 THEN
  include feature in release
ELSE defer to a later version

Version 1 includes: login, view marks
Version 1 excludes: parent alerts

Section E: Spot the Error

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.

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'.

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'.

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'.

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.