← CSC 311 Software Engineering
Requirements Engineering and System Specification
Notes
Fundamentals of Requirements Engineering
Requirements engineering is the systematic process of discovering, analyzing, documenting, and validating the services that a software system should provide along with the constraints under which it must operate. Failures in software projects are predominantly attributed to poor requirements elicitation, misunderstandings between clients and engineers, and unmanaged scope creep. The requirements lifecycle consists of four primary activities: requirements elicitation, requirements analysis and negotiation, requirements specification, and requirements validation.
Functional Versus Non-Functional Requirements
Requirements are broadly divided into functional and non-functional categories. Functional requirements describe specific behaviors, computations, inputs, and outputs of the software. They define what the system must do. For instance, a system must generate an automated invoice upon successful payment receipt. Non-functional requirements (NFRs) specify systemic quality attributes, constraints, and performance metrics. They define how the system must behave. NFR categories include security, availability, throughput, maintainability, and legal compliance. In East Africa, legal compliance often centers on data protection mandates such as the Kenya Data Protection Act of 2019, which strictly governs the collection, processing, and localized storage of personal identifying information.
Modeling and Specification Techniques
Engineers specify requirements using structured natural language alongside Unified Modeling Language (UML) diagrams. Use Case Diagrams establish boundary contexts and actor interactions, while Sequence Diagrams detail time-ordered message passing between objects. Formal validation checks requirements for consistency, completeness, realism, and verifiability.
Practical example
Consider the engineering of an automated online clearance system for graduating students at a Kenyan public university, integrating with the Higher Education Loans Board (HELB).
A primary functional requirement states: The clearance module shall query the HELB verification API using the student's Kenyan National ID number and return loan compliance status within three seconds. If clearance is denied, the system shall display a breakdown of unserviced loan accounts and redirect the user to the eCitizen payment gateway.
A critical non-functional requirement dictates: The system must adhere to the Kenya Data Protection Act 2019 by encrypting student national identification numbers and academic transcripts at rest using AES-256 and ensuring ninety-nine point nine percent availability during the peak graduation clearance window in November and December, handling up to ten thousand concurrent requests without latency exceeding two seconds. Engineers model this interaction using a UML Sequence Diagram showing the Student actor, the Clearance Portal Controller, the University Database, and the external HELB API gateway.
Quiz
1. Which of the following is categorized as a non-functional software requirement?
2. What does the Kenya Data Protection Act of 2019 primarily impose on software requirement specifications?
3. Which Unified Modeling Language diagram is best suited for illustrating chronological message interactions between system components?
Sign in to submit and securely grade your quiz.