Summary

This presentation covers different types of requirements in software engineering, focusing on functional, quality, and constraint requirements. It also examines methods for documenting and modeling these requirements, including natural language and modelling techniques.

Full Transcript

ISB26404 SOFTWARE REQUIREMENTS ENGINEERING Sugi Requirements types Content Documenting Requirements 2 Functional Requireme Quality nts types Constraints 3 Definition:...

ISB26404 SOFTWARE REQUIREMENTS ENGINEERING Sugi Requirements types Content Documenting Requirements 2 Functional Requireme Quality nts types Constraints 3 Definition: Describe what the system should do— specific actions, features, and behaviors. Functional Examples: The system shall allow users to reset passwords via email. The system shall generate weekly performance reports for managers. 4 Definition: Describes system attributes that define how well the system performs a function. Often relates to performance, security, usability, and reliability. Quality Examples: The system shall respond to user requests within 2 seconds. The system shall handle up to 10,000 concurrent users without performance degradation. 5 Definition: Limitations or restrictions imposed on the system design, often external. Examples: Constraint Budget Constraint: The overall project budget shall not exceed RM500,000. Technological Constraint: The application shall run on Android and iOS only. 6 Types of Requirement Documenti Documentation: ng  Natural Language Requireme  Modelling Techniques nts 7  Definition: Describing requirements in plain text, Documenti often in the form of "shall" statements. ng  Characteristics: Requireme Simple, easy to understand, even for nts: non-technical audiences. Natural  Common Format: Language The system shall [do something]. The user shall be able to [do something]. 8  Definition: Using visual or graphical representations Documenti to describe requirements, which provides ng a structured approach. Requireme  Characteristics: nts: Easier to visualize complex systems. Modelling  Common Modelling Techniques: Technique Use Case Diagrams Entity-Relationship Diagrams (ERD) Data Flow Diagrams (DFD) 9 Functional Requirements: Use Cases, User Stories, Requirement Specifications. Documenti ng Quality Requirements: Quality Attribute Requireme Scenarios, Service-Level Agreements. nts: Examples Constraint Requirements: Project Charter, Legal Agreements, Compliance Documentation. 10 Conclusion 11

Use Quizgecko on...
Browser
Browser