IS5411 Chap.4 Functional Requirements and Business Processes
Functional Requirements and Business Processes
Functions and qualities are separate claims
Functional requirements describe activities the system must perform, often represented as use cases. Non-functional requirements describe qualities and constraints such as usability, reliability, performance and security.
The distinction lets reviewers determine whether the required behaviour exists and whether it operates to an acceptable standard without confusing either question with a chosen platform.
Business value sets the use-case size
The course uses the elementary business process as the sizing rule.
One actor completes a coherent response to a triggering event, the response yields an outcome the organisation values, and its records finish in a consistent state. Broad labels such as manage orders contain several outcomes, while interface actions such as click submit are too small.
A verb-noun name should identify the meaningful response.
Technology limits wait for design
The perfect technology assumption postpones functions created only by current technical or human limitations until design. It protects the essential business response while alternatives are considered.
Non-functional requirements are still recorded with owners and measures, then linked to the functions they constrain so later trade-offs remain visible.
What this chapter covers
- 01
Functional requirements
- 02
FURPS+ qualities
- 03
Elementary processes
- 04
Business events
- 05
Stable states
- 06
Verb-noun names
- 07
Perfect technology
- 08
CRUD validation
Worked example · free
Right-size a maintenance use case
- 3Identify the event, actor and value.
- 3Name the stable result with a verb and noun.
- 2Separate later qualities from the function.
Key terms
- Functional Requirement
- An activity the system must perform in response to a user or business need.
- Non-functional Requirement
- A quality or constraint governing how a system behaviour must operate.
- Elementary Business Process
- A meaningful task producing value and a stable business result in one coherent episode.
- Stable State
- A consistent condition in which process data can remain until another event occurs.
- Perfect Technology
- An analytical assumption that postpones technology limitations until design.
- CRUD Analysis
- A coverage check across the creation, reading, updating and deletion of remembered information.
Functional Requirements and Business Processes FAQ
How do functional and non-functional requirements differ?
Functional requirements state the activities the system performs. Non-functional requirements state qualities or constraints such as reliability, security and response performance. A quality should qualify an identified behaviour, while the behaviour can be reviewed without assuming one technical implementation.
What makes a use case elementary?
It responds to a business event, is pursued by one person in one coherent time and place, adds measurable value and leaves system data stable. The test prevents broad management labels and tiny interface gestures from being treated as equivalent functions.
Why use the perfect technology assumption?
It stops current platforms, interfaces or staffing limits from creating false business functions during analysis. The team first establishes the essential response, then design compares feasible ways to deliver it under real constraints. The assumption delays constraints; it does not erase them. Reintroduce each real constraint explicitly when comparing design alternatives and acceptance criteria.
Exam move
Collect a dozen candidate functions from an everyday service. For each, write the trigger, actor, value and stable result, then reject names that describe a department or interface gesture. Add one measurable usability, reliability, performance or security requirement to the remaining functions without turning the qualities into new use cases. Rewrite every surviving name as a verb and business noun.
If several functions share an umbrella label, decide whether the umbrella is a subsystem heading or an oversized use case. If a candidate ends with no durable result, either combine it with the process that gives it value or identify the missing outcome.
Next apply the perfect technology assumption: remove steps that exist only because the current tool is slow, fragmented or manual, while retaining the underlying response the business needs. Carry the non-functional requirements forward in a separate list with an owner and a review method. The goal is to practise keeping behaviour, quality and implementation distinct while still connecting them.
In a case answer, that separation allows you to justify why a proposed function belongs in analysis and why a quality target belongs in later design and testing. Finish with a two-column review. On the left, place observable system responses; on the right, place the qualities that constrain each response. Any row containing only a technology or adjective needs rewriting before it can guide modelling or testing.
Working through Functional Requirements and Business Processes in IS5411? Sia is AskSia’s AI Information Technology tutor — ask any IS5411 Functional Requirements and Business Processes question and get a clear, step-by-step explanation grounded in how IS5411 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.