FIT2001 Chap.4 User Stories and Activity Models

User Stories and Activity Models

Define user story

The course material gives this chapter a concrete anchor: Week 4 joins user stories with activity diagrams so textual goals and process behaviour can cross-check.

That user story anchor controls how acceptance criterion is explained and how activity diagram is tested in changed practice.

User Stories and Activity Models turns user story, acceptance criterion and activity diagram into executable reasoning.

The chapter's practical target is to connect user goals to testable criteria and process flow, so every explanation should connect syntax to program state, control flow and observable output.

Treat user story as a precise program object, not a loose label. Identify the value or responsibility of user story before execution, then trace what can read it, change it or depend on it.

This makes state changes visible before they become debugging guesses.

Use acceptance criterion to explain the program's next move. Work through one representative acceptance criterion input by hand and name the branch, iteration or call that follows. If the acceptance criterion trace cannot be stated, the code may run by accident rather than by understood design.

Bring in activity diagram as the test of structure.

Compare normal, boundary and invalid inputs for activity diagram; state the expected behaviour first; then use the mismatch between expectation and result to localise the defect.

For the application — connect user goals to testable criteria and process flow — write the smallest complete example that exposes the rule.

Explain why the activity diagram result works, what would break it and how the program should signal or recover from that failure.

Trace acceptance criterion

Before running an example involving user story, make a trace table with the important state before and after each operation.

Include the value associated with user story, the control decision governed by acceptance criterion and the output or object affected by activity diagram. The user story table turns an unexplained result into a sequence that can be tested one transition at a time.

Test three inputs: an ordinary case, a boundary case and an invalid case.

State the expected activity diagram result for each before execution, then compare it with what the program actually does. A useful test of acceptance criterion isolates one rule; changing several conditions at once cannot reveal which condition caused the failure.

Practise explaining the solution without reading the code.

For fit2001, name the data representation, the control flow, the responsibility of each function or class and the reason the chosen design supports connect user goals to testable criteria and process flow.

This activity diagram rehearsal matters when a written test or interview asks why the program works rather than whether it produces one correct output.

A complete response should make the task visible before the detail: identify what must be decided, define the relevant terms, connect the evidence to acceptance criterion, and use activity diagram to test the result.

The final sentence about activity diagram should answer the question actually asked rather than merely repeat the topic.

The controlling limit is specific: A story card without conditions and alternate paths is not a complete specification.

Keep that activity diagram limit beside the worked example, because it separates a careful fit2001 answer from one that sounds confident but claims more than the task or evidence supports.

For revision, retrieve user story, acceptance criterion and activity diagram without notes, explain their relationship aloud, then complete a changed version of the application: connect user goals to testable criteria and process flow.

Record the first failed acceptance criterion reasoning move and repair it before attempting another case.

What this chapter covers

• 01

  user story

• 02

  acceptance criterion

• 03

  activity diagram

• 04

  Applying user story

• 05

  Limits of acceptance criterion and activity diagram

Repair a vague story

Key terms

user story

Short requirement expression connecting a user role, desired capability and value, refined through acceptance criteria. This chapter uses the concept when students connect user goals to testable criteria and process flow. Use this definition when the task is to connect user goals to testable criteria and process flow.

acceptance criterion

Observable condition used to decide whether a story's behaviour is satisfactory. It helps explain the reasoning required to connect user goals to testable criteria and process flow. Use this definition when the task is to connect user goals to testable criteria and process flow.

activity diagram

Behavioural model showing actions, decisions, concurrency and flow through a process. Its limit matters because a story card without conditions and alternate paths is not a complete specification. Use this definition when the task is to connect user goals to testable criteria and process flow.

User Stories and Activity Models FAQ

Exam move

Reconstruct the relationship among user story, acceptance criterion and activity diagram; complete the chapter application without notes; then test the result against this limit: A story card without conditions and alternate paths is not a complete specification.

Working through User Stories and Activity Models in FIT2001? Sia is AskSia’s AI Information Technology tutor — ask any FIT2001 User Stories and Activity Models question and get a clear, step-by-step explanation grounded in how FIT2001 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.