Skip to content

SE311 Software Requirements Engineering

This course focuses on how software requirements are discovered, analyzed, documented, validated, and managed. It covers elicitation techniques, modeling methods, documentation standards, and how to handle evolving requirements in real projects.

This section contains my structured study material for SE311, including:

  • Chapter notes
  • Quizzes and practice questions
  • A midterm cheat sheet
  • Supporting diagrams and examples

The goal of this section is to provide a clear, practical study resource for understanding requirements engineering and preparing for assessments.

How to Use This Section

  • If you are following the course, start from Chapter 1 and continue in order.
  • If you are revising, use the midterm cheat sheet and the quizzes to test your understanding.
  • If you are working on modeling or analysis tasks, focus on the modeling chapters and their examples.

This page is the main entry point to all SE311 material.

Course Chapters

Chapter 1 Basics of Requirements Engineering

  • What requirements are and why they matter
  • Types of requirements, including functional, non functional, and constraints
  • The requirements engineering process
  • Main activities in requirements engineering

Chapter 2 Documentation Standards

  • IEEE 830 1998 standard
  • Relationship to ISO IEC 12207
  • Writing high quality requirements documents

Chapter 3 Requirements Inception and Problem Analysis

  • Understanding the problem domain
  • Business requirements
  • Vision and scope documents
  • Project viability analysis

Chapter 4 Requirements Elicitation

  • Goals, risks, and challenges
  • Sources of requirements
  • Elicitation tasks and techniques
  • Interviews, workshops, observation, and prototyping

Chapter 5 Requirements Analysis and Specification

  • Stages of analysis
  • Methods and tools
  • Structuring and refining requirements

Chapter 6 Requirements Modeling with UML

  • Data modeling concepts
  • Scenario based modeling using use case diagrams
  • Class based modeling including classes, objects, attributes, and operations
  • CRC models and collaboration diagrams

Chapter 7 Requirements Modeling Continued

  • Activity diagrams
  • State charts
  • Behavioral modeling

Chapter 8 Goal Modeling and GRL Workshop

  • URN and GRL frameworks
  • Modeling stakeholder goals and motivations

Chapter 9 Requirements Verification and Validation

  • Ensuring correctness, consistency, and completeness
  • Validation techniques
  • Negotiation with stakeholders

Chapter 10 Requirements Prioritization and Negotiation

  • Prioritization methods such as MoSCoW and Kano
  • Handling conflicts and trade offs

Chapter 11 Requirements Prioritization Continued

  • Refining scope
  • Release planning

Chapter 12 Requirements Management

  • Traceability
  • Baselines
  • Change management
  • Requirements management tools such as DOORS

Chapter 13 Requirements in Development Processes

  • Requirements in Agile methods
  • Requirements across software process frameworks
  • Final project presentations

Study and Revision Material

In addition to the chapter notes, this section also includes:

  • A midterm cheat sheet for focused revision
  • Quizzes and practice questions for multiple chapters

These materials are intended to support both understanding and exam preparation.

  1. Read the chapters in order, starting from Chapter 1
  2. Focus carefully on the modeling chapters when working on diagrams and analysis tasks
  3. Use the midterm cheat sheet before exams or major assessments
  4. Test your understanding using the quizzes

Notes

  • This material is based on my coursework and personal study.
  • The focus is on clarity, structure, and practical understanding.
  • The content will continue to be refined and expanded over time.