Courses / HEC NSCT – National Skill Competency Test: Complete Preparation for Computing Graduates
5.3 Requirements Engineering and UML
Area 5 – Software Engineering (10%) · 45 min read · 9 MCQs to check yourself
Requirements
| Type | Meaning | Example |
|---|---|---|
| Functional | What the system must do | "The system shall email a receipt after payment." |
| Non-functional | How well it does it (quality) | Performance (< 2 s), security, availability 99.9%, usability |
| Domain / constraints | Rules of the field, laws | PECA compliance, tax rules |
Process: elicitation (interviews, questionnaires, observation, workshops, prototypes) → analysis & negotiation → specification (SRS document) → validation (reviews, prototypes) → management (traceability, change control). Good requirements are clear, complete, consistent, verifiable, traceable – avoid vague words like "fast" or "user-friendly" without numbers.
UML diagrams
| Diagram | Shows |
|---|---|
| Use case | Actors and the goals they achieve with the system (functional view) |
| Class | Classes, attributes, methods and relationships (association, aggregation ◇, composition ◆, inheritance △) |
| Sequence | Messages between objects in time order |
| Activity | Workflow, like a flowchart with parallel paths |
| State machine | States of one object and transitions (order: placed → paid → shipped) |
| Component / Deployment | Software parts / hardware nodes |
| In use cases, «include» = always performed sub-goal; «extend» = optional behaviour. |
UML use case diagrams (Lucid Software)
This lesson ends with a quiz of 9 MCQs. Open the lesson on PrepOasis to take it and save your progress.
Previous: 5.2 Agile and Scrum · Next: 5.4 Design, Architecture and Design Patterns