Software Requirements Engineering Quiz

Software Requirements Engineering

• Course code: ISB26404
• Instructor: Sugi

Content

• Requirements types
• Documenting requirements

Requirements Types

• Functional
• Quality
• Constraints

Functional Requirements

• Definition: Describes what the system should do—specific actions, features, and behaviors.
• Examples:
  • The system shall allow users to reset passwords via email.
  • The system shall generate weekly performance reports for managers.

Quality Requirements

• Definition: Describes system attributes that define how well the system performs a function. Often relates to performance, security, usability, and reliability.
• Examples:
  • The system shall respond to user requests within 2 seconds.
  • The system shall handle up to 10,000 concurrent users without performance degradation.

Constraint Requirements

• Definition: Limitations or restrictions imposed on the system design, often external.
• Examples:
  • Budget Constraint: The overall project budget shall not exceed RM500,000.
  • Technological Constraint: The application shall run on Android and iOS only.

Documenting Requirements

• Types of Documentation:
  • Natural Language
  • Modelling Techniques

Documenting Requirements: Natural Language

• Definition: Describing requirements in plain text, often in the form of "shall" statements.
• Characteristics: Simple, easy to understand, even for non-technical audiences.
• Common Format:
  • The system shall [do something].
  • The user shall be able to [do something].

Documenting Requirements: Modelling Technique

• Definition: Using visual or graphical representations to describe requirements, which provides a structured approach.
• Characteristics: Easier to visualize complex systems.
• Common Modelling Techniques:
  • Use Case Diagrams
  • Entity-Relationship Diagrams (ERD)
  • Data Flow Diagrams (DFD)

Documenting Requirements: Examples

• Functional Requirements: Use Cases, User Stories, Requirement Specifications
• Quality Requirements: Quality Attribute Scenarios, Service-Level Agreements
• Constraint Requirements: Project Charter, Legal Agreements, Compliance Documentation

Conclusion

• Functional: Focus: What the system does. Examples: User login, data processing. Impact on System: Defines system functions.
• Quality: Focus: How well it performs. Examples: Response time, security, usability. Impact on System: Defines user satisfaction, system behavior.
• Constraint: Focus: Limits on design/development. Examples: Budget, platform, compliance. Impact on System: Limits choices and design flexibility.

Test your knowledge on various types of software requirements, including functional, quality, and constraints. This quiz covers key definitions and examples to enhance your understanding of documenting requirements in software engineering.