Summary of "Requirements Engineering lecture 1: Overview"

Summary of Requirements Engineering Lecture 1: Overview

Main Ideas and Concepts:

Definition of Requirements Engineering:
- Requirements Engineering is a crucial early phase in software engineering focused on understanding what stakeholders want from a software system.
- It involves eliciting, documenting, and managing requirements throughout the software development lifecycle.
Components of Requirements:
- Wants and Needs: Requirements include what stakeholders want, what they may wish for but are unaware of, and their actual needs.
- Constraints: These are limitations imposed by technical environments, integration with other systems, and operational contexts.
Engineering Practices:
- Engineering applies systematic methods, guidelines, frameworks, and best practices developed over years of experience to ensure effective requirements management.
Learning Goals:
- The course aims to develop skills in:
  - Eliciting requirements using various techniques.
  - Documenting requirements in both natural language and modeled formats (e.g., UML diagrams, formulas, pseudocode).
  - Understanding the distinction between quality requirements and non-functional requirements.
Artifact-Based Requirements Engineering:
- The course will focus on creating and managing artifacts, which include any documentation or notation that captures customer requirements, such as diagrams, code snippets, and presentations.
Communication in Requirements Engineering:
- The requirements engineer acts as a communication bridge between stakeholders (non-technical) and technical teams (developers, testers).
- Effective communication is essential for translating stakeholder needs into technical specifications and vice versa.

Methodology and Instructions:

Eliciting Requirements:
- Use interviews, surveys, and discussions with stakeholders to gather information.
Documenting Requirements:
- Write requirements in natural language for clarity.
- Use modeled requirements (UML diagrams, mathematical representations) for precision, especially in high-stakes systems.
Communicating Requirements:
- Develop skills to translate technical language into understandable terms for stakeholders.
- Ensure that both technical and non-technical teams understand the requirements and constraints.