FIT2001 Chap.3 Requirements Elicitation and Evidence
Requirements Elicitation and Evidence
Define elicitation
The course material gives this chapter a concrete anchor: Week 3 focuses on information-gathering techniques for investigating requirements.
That elicitation anchor controls how functional requirement is explained and how non-functional requirement is tested in changed practice.
Requirements Elicitation and Evidence turns elicitation, functional requirement and non-functional requirement into executable reasoning.
The chapter's practical target is to use interviews, observation, documents and workshops to discover testable requirements, so every explanation should connect syntax to program state, control flow and observable output.
Treat elicitation as a precise program object, not a loose label. Identify the value or responsibility of elicitation 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 functional requirement to explain the program's next move. Work through one representative functional requirement input by hand and name the branch, iteration or call that follows.
If the functional requirement trace cannot be stated, the code may run by accident rather than by understood design.
Trace functional requirement
Bring in non-functional requirement as the test of structure.
Compare normal, boundary and invalid inputs for non-functional requirement; state the expected behaviour first; then use the mismatch between expectation and result to localise the defect.
For the application — use interviews, observation, documents and workshops to discover testable requirements — write the smallest complete example that exposes the rule.
Explain why the non-functional requirement result works, what would break it and how the program should signal or recover from that failure.
Before running an example involving elicitation, make a trace table with the important state before and after each operation.
Include the value associated with elicitation, the control decision governed by functional requirement and the output or object affected by non-functional requirement. The elicitation 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 non-functional requirement result for each before execution, then compare it with what the program actually does. A useful test of functional requirement isolates one rule; changing several conditions at once cannot reveal which condition caused the failure.
Test with non-functional requirement
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 use interviews, observation, documents and workshops to discover testable requirements.
This non-functional requirement 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 functional requirement, and use non-functional requirement to test the result.
The final sentence about non-functional requirement should answer the question actually asked rather than merely repeat the topic.
The controlling limit is specific: One stakeholder statement is evidence but not automatically a complete or agreed requirement.
Keep that non-functional requirement 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 elicitation, functional requirement and non-functional requirement without notes, explain their relationship aloud, then complete a changed version of the application: use interviews, observation, documents and workshops to discover testable requirements.
Record the first failed functional requirement reasoning move and repair it before attempting another case.
What this chapter covers
- 01
elicitation
- 02
functional requirement
- 03
non-functional requirement
- 04
Applying elicitation
- 05
Limits of functional requirement and non-functional requirement
Elicit a returns workflow
- 1Ask who can approve and under which conditions.
- 1Observe exceptions and actual system steps.
- 1Inspect policy and transaction records.
- 1Separate functional approval from time, security and audit qualities.
Key terms
- elicitation
- Purposeful discovery of needs, rules, constraints and disagreement through stakeholder and artefact evidence. This chapter uses the concept when students use interviews, observation, documents and workshops to discover testable requirements. Use this definition when the task is to use interviews, observation, documents and workshops to discover testable requirements.
- functional requirement
- A capability or behaviour the system must provide under stated conditions. It helps explain the reasoning required to use interviews, observation, documents and workshops to discover testable requirements. Use this definition when the task is to use interviews, observation, documents and workshops to discover testable requirements.
- non-functional requirement
- A quality, constraint or operating condition such as security, performance, accessibility or reliability. Its limit matters because one stakeholder statement is evidence but not automatically a complete or agreed requirement. Use this definition when the task is to use interviews, observation, documents and workshops to discover testable requirements.
Requirements Elicitation and Evidence FAQ
What is the main task in Requirements Elicitation and Evidence?
Use interviews, observation, documents and workshops to discover testable requirements.
How do elicitation and functional requirement work together?
Use elicitation to establish the object or condition, then use functional requirement to explain how it changes the outcome being analysed.
What must a fit2001 answer qualify here?
One stakeholder statement is evidence but not automatically a complete or agreed requirement.
How should I revise Requirements Elicitation and Evidence?
Retrieve elicitation, functional requirement and non-functional requirement, apply them to a changed case, and correct the first point where the evidence no longer supports the conclusion.
Exam move
Reconstruct the relationship among elicitation, functional requirement and non-functional requirement; complete the chapter application without notes; then test the result against this limit: One stakeholder statement is evidence but not automatically a complete or agreed requirement.
Working through Requirements Elicitation and Evidence in FIT2001? Sia is AskSia’s AI Information Technology tutor — ask any FIT2001 Requirements Elicitation and Evidence 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.
