12 mins read ·
5 questions
Describe the V-Model and map each development phase to its corresponding test level.
13 mins read ·
15 questions
Describe Boehm's Spiral model and explain the role of risk analysis in each cycle.
11 mins read ·
12 questions
Distinguish iterative from incremental development and explain how each reduces the cost and risk of change.
11 mins read ·
16 questions
Explain the four values and the principles of the Agile Manifesto.
11 mins read ·
12 questions
Describe the Scrum framework: its roles (Product Owner, Scrum Master, Developers), events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective) and artefacts (Product Backlog, Sprint Backlog, Increment).
11 mins read ·
18 questions
Compare the Waterfall, V-Model, Iterative, Spiral and Agile models on requirements stability, risk handling, customer involvement, documentation, and suitability for safety-critical or regulated systems.
11 mins read ·
9 questions
Select and justify a process model for a given project scenario, considering size, criticality, requirements volatility, regulatory constraints and team distribution.
12 mins read ·
9 questions
Analyse the NASA Apollo, Healthcare.gov and Boeing avionics case studies to explain how the choice and execution of the process model contributed to success or failure.
11 mins read ·
15 questions
Distinguish user requirements from system requirements, and functional from non functional requirements; classify non-functional requirements as product, organisational or external.
11 mins read ·
12 questions
Write non-functional requirements in a verifiable, measurable form (for example response time, throughput, availability, mean time to failure).
12 mins read ·
18 questions
Describe elicitation methods (interviews, questionnaires, observation and ethnography, workshops and JAD sessions, prototyping, document analysis) and select suitable methods for a given stakeholder situation.
10 mins read ·
12 questions
Identify the stakeholders of a system and explain common elicitation problems: tacit knowledge, conflicting requirements, domain jargon and a changing business environment.