Skip to main content
CBE Nexus · Undergraduate Software Engineering

Chapter 5: Requirements Engineering and Specification

Undergraduate requirements engineering notes on stakeholders, elicitation, functional and non-functional requirements, user stories, use cases, modelling, prioritisation, validation, traceability, change management and specification.

Back to Software Engineering course guide

Chapter overview and learning outcomes

This chapter develops foundational undergraduate knowledge in requirements engineering and specification, connecting theory with practical software engineering decisions. It is designed for active study: read each section, work through the examples, draw the diagrams from memory and complete the revision questions.

1. Purpose and scope of requirements engineering

Requirements engineering is the systematic process of discovering, analysing, documenting, validating and managing what stakeholders need from a software system and the constraints under which it must operate. It reduces the risk of building the wrong product. Requirements connect business goals to technical design, implementation, testing and acceptance. They are not simply a list of features: they include quality attributes, interfaces, data rules, regulatory obligations and operational constraints. Requirements evolve as users learn, markets change and technical assumptions are tested. A managed process makes change visible and assesses its consequences.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

2. Stakeholders, users and context analysis

Stakeholders are individuals or groups who affect or are affected by a system. They may include end users, customers, sponsors, administrators, developers, support teams, suppliers, regulators and members of the public. Identify user groups and their goals, skills, environments and accessibility needs. Context analysis defines the system boundary, external actors, neighbouring systems, business processes and constraints. A stakeholder register can record interests, influence, communication needs and unresolved concerns. Do not confuse the sponsor's requested features with the full set of user and public needs.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

3. Requirements elicitation techniques

Elicitation gathers information through interviews, workshops, observation, questionnaires, document analysis, interface analysis, brainstorming and prototyping. Interviews uncover individual goals but may be influenced by memory or assumptions. Workshops expose disagreement and support shared understanding. Observation reveals actual work practices that users may not mention. Questionnaires reach larger groups but require careful wording. Prototypes make ideas tangible and expose usability issues, but stakeholders may mistake a prototype for a finished commitment. Use multiple methods and record source, context and confidence.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

4. Functional requirements and use cases

Functional requirements describe services or behaviours a system must provide, such as registering a user, generating a report or approving a request. They should identify the actor, trigger, expected response and relevant business rules. Use cases describe interactions between actors and a system to achieve a goal. A use-case specification may include preconditions, main success flow, alternative flows, exceptions and postconditions. Avoid vague requirements such as 'the system should be user friendly'; define observable behaviour and acceptance conditions.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

5. Non-functional requirements and quality attributes

Non-functional requirements specify qualities or constraints such as performance, reliability, security, usability, accessibility, maintainability, scalability, portability, interoperability and legal compliance. They are often system-wide and cross-cutting. A measurable requirement identifies a condition, metric, threshold and context: for example, a defined proportion of requests should complete within a stated response time under a specified load. Avoid arbitrary numbers without stakeholder rationale. Quality scenarios help connect stimulus, environment, response and measurable response measure.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

6. Requirements modelling and specification languages

Models represent requirements from complementary perspectives. Context diagrams show system boundaries and external entities. Use-case diagrams show actors and goals. Activity diagrams describe workflows. State machines model behaviour across states and events. Data models describe entities and relationships. Sequence diagrams show interactions over time. Natural language is accessible but may be ambiguous; structured templates improve consistency. Formal methods can express precise constraints for safety-critical or complex systems, but require suitable expertise and stakeholder communication.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

7. User stories, acceptance criteria and backlog management

A user story commonly describes a capability from a user's perspective, accompanied by acceptance criteria that define observable conditions of satisfaction. A story should be small enough to discuss, estimate and test. Acceptance criteria may use examples or structured Given-When-Then scenarios. A product backlog orders work by value, risk, dependencies and learning. Story points or other estimation techniques are planning aids, not direct measures of productivity. Backlog refinement clarifies scope and uncovers assumptions before work is committed.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

8. Prioritisation, negotiation and conflict resolution

Stakeholders often request more features than a project can deliver within available time and budget. Prioritisation techniques include MoSCoW, value-versus-effort analysis, risk-based ranking and weighted scoring. Negotiation explores underlying goals and acceptable alternatives rather than treating every request as fixed. Conflicts may concern cost, privacy, usability, speed, security or organisational policy. Record decisions, rationale, affected stakeholders and deferred needs. A transparent trade-off is preferable to an undocumented compromise that later appears as a defect.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

9. Requirements quality, validation and verification

A high-quality requirement is necessary, clear, unambiguous, feasible, consistent, verifiable, traceable and appropriately prioritised. Validation asks whether the documented needs represent what stakeholders actually require. Verification checks whether the specification is well formed and internally consistent. Techniques include reviews, walkthroughs, prototypes, model analysis, test-case derivation and acceptance scenarios. Ambiguity should be resolved before implementation where possible. Stakeholder sign-off should identify the version and scope being accepted.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

10. Traceability, change control and requirements management

Traceability links requirements to their sources, design elements, code modules, tests and release evidence. A traceability matrix helps assess coverage and impact. When a requirement changes, analyse effects on architecture, interfaces, data migration, security, testing, training, schedule and cost. Change control records the request, rationale, decision, owner and implementation status. Baselines provide a reference for controlled evolution. Requirements management tools can help at scale, but disciplined identifiers and clear ownership matter more than tool choice.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

11. Writing a software requirements specification

A software requirements specification (SRS) typically describes purpose, scope, definitions, references, overall context, user classes, constraints, assumptions, interfaces, functional requirements, quality requirements and acceptance criteria. Each requirement should have a unique identifier and clear wording. Avoid embedding design decisions unless they are genuine constraints. Use tables and diagrams to clarify complex relationships. Include unresolved questions and explicit exclusions. The SRS should be reviewed with stakeholders and maintained as the system evolves rather than treated as a document that becomes obsolete after approval.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

Figure 1. Requirements engineering cycle
Identify stakeholders and context→Elicit needs and constraints→Analyse and model→Specify and prioritise→Validate and manage change

Conceptual learning diagram; adapt it to the system or example being studied.

Figure 2. Traceability chain
Business objective→Requirement and acceptance criteria→Design and implementation→Test and release evidence

Conceptual learning diagram; adapt it to the system or example being studied.

Figure 3. Change impact analysis
Record requested change→Identify linked requirements→Assess design, cost and risk→Approve, defer or reject→Update baseline and tests

Conceptual learning diagram; adapt it to the system or example being studied.

Practical laboratory / project activity

  1. Choose a bounded problem relevant to this chapter and describe the intended users and context.
  2. Write down assumptions, constraints, inputs, outputs and measurable success criteria.
  3. Develop a small prototype, model, algorithm, specification or test artefact.
  4. Use version control and document tools, versions and important decisions.
  5. Test normal, boundary and failure conditions; retain reproducible evidence.
  6. Review the result for usability, accessibility, security, reliability and maintainability.
  7. Submit a concise report explaining the method, findings, limitations and next steps.

Only test systems and datasets for which you have permission. Protect personal information and follow institutional academic-integrity and laboratory rules.

Worked reasoning and self-assessment

Begin with a precise problem statement. Separate known facts from assumptions. Identify the relevant concepts and choose a method that fits the problem constraints. Work through a small example manually, then verify the result using a suitable tool or test. Explain why the approach works, where it may fail, and what evidence would be needed to trust it in a larger system. For a design decision, state the alternatives and the trade-offs rather than presenting one choice as universally best.

Examination and revision questions

Attempt each question before opening the answer guidance. Use examples, diagrams and precise definitions in longer responses.

  1. What is requirements engineering?

    Show answer guidance

    The process of discovering, analysing, documenting, validating and managing software requirements.

  2. Who is a stakeholder?

    Show answer guidance

    A person or group that affects or is affected by the system.

  3. Name four elicitation techniques.

    Show answer guidance

    Interviews, workshops, observation, questionnaires, document analysis and prototyping.

  4. Differentiate functional and non-functional requirements.

    Show answer guidance

    Functional requirements state behaviours; non-functional requirements state qualities or constraints.

  5. What is a use case?

    Show answer guidance

    A description of how an actor interacts with a system to achieve a goal.

  6. What makes a requirement measurable?

    Show answer guidance

    It states observable conditions, metrics, thresholds and context.

  7. What is a user story?

    Show answer guidance

    A concise description of a capability from a user's perspective.

  8. What are acceptance criteria?

    Show answer guidance

    Conditions that must be satisfied for a requirement or story to be accepted.

  9. Name two requirements modelling techniques.

    Show answer guidance

    Use-case, activity, state-machine, context, sequence and data models.

  10. Differentiate validation and verification of requirements.

    Show answer guidance

    Validation checks stakeholder need; verification checks specification quality and consistency.

  11. What is requirements traceability?

    Show answer guidance

    Linking requirements to sources, designs, implementation, tests and release evidence.

  12. Why prioritise requirements?

    Show answer guidance

    To allocate limited resources according to value, risk, dependency and urgency.

  13. What is a requirements baseline?

    Show answer guidance

    An agreed version of requirements used for controlled change.

  14. What is an SRS?

    Show answer guidance

    A structured software requirements specification describing system scope, interfaces, functions and quality constraints.

  15. Why perform change impact analysis?

    Show answer guidance

    To understand effects on architecture, cost, schedule, security, testing and stakeholders.

Revision checklist

Further reading and academic practice

Use current university textbooks, peer-reviewed software engineering research, recognised standards and official technical documentation. Verify edition, version, publication date and applicability before citing a source. Cite quotations, data, diagrams, software and ideas according to your institution's required referencing style. Do not invent references, results or test evidence. Compare sources critically and note where professional guidance differs by context or jurisdiction.

Academic note: These notes are an educational study resource, not a substitute for your institution's current course outline, assessment brief, professional standards or supervisor guidance. The course guide is an illustrative international framework.

Return to the complete Software Engineering course guide

Official Education References

Use these official organisations for curriculum guidance, examinations and further learning information.