📋 Requirements Engineering
155 words
1 min read
Visual companion
Python
Type and operator map
Python Week 1: the first filter for runtime behavior
View
Revision summary
What this note is really saying
Short form
# 📋 Requirements Engineering ## 1. 🎯 Learning Objectives - Distinguish functional from non-functional requirements - Write effective user stories (INVEST criteria) - Apply MoSCoW prioritization - Understand SRS document structure ## 2.
📋 Requirements Engineering
1. 🎯 Learning Objectives
- Distinguish functional from non-functional requirements
- Write effective user stories (INVEST criteria)
- Apply MoSCoW prioritization
- Understand SRS document structure
2. 📖 Core Content
3.1 Functional vs Non-Functional Requirements
| Type | Description | Example |
|---|---|---|
| Functional | What the system does | "User can login with email and password" |
| Non-functional | How the system performs | "Page loads in under 2 seconds" |
3.2 User Stories
Format: "As a [role], I want [goal] so that [benefit]"
INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
3.3 MoSCoW Prioritization
- Must have: Critical for launch
- Should have: Important but not critical
- Could have: Nice to have
- Won't have: Explicitly out of scope
4. 📝 Practice Questions
Q1: Is "System should be available 99.9% of the time" functional or non-functional?Answer: Non-functional (availability requirement). It describes how the system performs, not what it does. Join Discord PreviousSDLC & Process ModelsNextAgile & Scrum