CampusLearn
← CSC 215 Systems Analysis and Design

Requirements Engineering and Process Modeling

Notes

Requirements Determination Requirements determination is the process of discovering, analyzing, validating, and documenting the precise services a proposed system must provide and the operational constraints it must honor. Systems analysts deploy multiple elicitation techniques to gather comprehensive data, including user interviews, questionnaires, joint application development sessions, observation of current workflows, and document analysis. Elicited requirements are categorized into functional requirements and non-functional requirements. Functional requirements outline specific behaviors, calculations, and services the system must execute, such as generating an electronic receipt or authenticating a user. Non-functional requirements describe quality attributes and constraints, such as response time latency, security encryption standards, concurrent user capacity, and data accessibility. Process Modeling with Data Flow Diagrams Process modeling visually represents how data moves through an organization, how it is transformed by automated processes, and where it is permanently stored. Data Flow Diagrams use four fundamental symbols based on standard notations like Gane and Sarson or Yourdon and DeMarco: external entities, processes, data flows, and data stores. An external entity represents a person, organization, or external system that supplies input data or consumes system output. A process indicates an operational transformation of data. A data flow denotes directed data movement between components, and a data store represents a persistent repository of data, such as a database table. A Context Diagram, or Level 0 DFD, depicts the entire system as a single central process interacting with external actors, establishing system boundaries without revealing internal modular design. Practical example Consider the Nairobi City County automated parking management project, intended to modernize street parking revenue collection and curb cash misappropriation. During requirements elicitation, analysts hold interviews with county parking marshals and motorists. A key functional requirement is established: the system must process vehicle registration numbers, verify parking zone tariffs, and trigger an automated payment prompt via the eCitizen integration gateway or direct M-Pesa push through the Daraja STK Push API. A non-functional requirement specifies that payment verification must return a positive confirmation SMS to the motorist within three seconds under a concurrent load of 10,000 active street parking sessions. In the Level 0 Context Diagram, the external entities are the Motorist, the Parking Marshal, and the eCitizen Payment Gateway. The central process is Nairobi County Parking System. The Motorist provides vehicle registration and parking zone as an input data flow. The system sends an payment request data flow to the eCitizen Gateway. The eCitizen Gateway returns a payment confirmation token to the system, which then sends an electronic parking clearance receipt data flow to both the Motorist and the Parking Marshal handheld terminal.

Quiz

1. In a Level 0 Data Flow Diagram (Context Diagram), which element must NOT appear?

2. What role does an external entity play in a Data Flow Diagram?

3. Which of the following statements represents a non-functional requirement rather than a functional requirement?

Sign in to submit and securely grade your quiz.