1Agile process models support rapid software development
True
2Agile process models use incremental development models
True
3New releases in agile methods are available every two or three weeks
True
4Agile methods involve customers in the development process with rapid feedback
True
5Design and implementation are the central activities in agile development
True
6Agile methods are best for projects where requirements change rapidly
True
7Agile development cuts down on process bureaucracy
True
8Agile development avoids excessive documentation
True
9SCRUM provides a framework for organizing agile projects
True
10A sprint cycle in SCRUM usually lasts between 2 and 4 weeks
True
11The product backlog is the input for a SCRUM sprint cycle
True
12Unstable requirements do not hold up progress in SCRUM
True
13The Agile Manifesto reflects the philosophy behind agile methods
True
14Agile methods have been successful in developing small or medium-sized products for sale
True
15Continuous integration is a practice in agile development
True
16SCRUM emphasizes teamwork
True
17What is Requirements Engineering?
The process of finding out, analyzing, documenting, and checking services and constraints for a system.
18What are user requirements?
Statements in natural language plus diagrams describing what services the system should provide and under what constraints it must operate.
19What are system requirements?
Detailed descriptions of the system’s functions, services, and operational constraints.
20What is the difference between user requirements and system requirements?
User requirements provide a general overview, while system requirements are more detailed and precise.
21What is a feasibility study?
A short, focused study early in the RE process that assesses the system's alignment with organizational goals, feasibility, and integration.
22What are functional requirements?
Statements of services the system should provide, how it should react to inputs, and how it should behave in particular situations.
23What are non-functional requirements?
Constraints on system services or functions, such as timing, development process, or standards compliance.
24What are the key activities in Requirements Engineering?
Requirements Elicitation and Analysis, Requirements Specification, and Requirements Validation.
25What is the Unified Modeling Language (UML)?
A general-purpose visual modeling language used to visualize system design, similar to blueprints.
26What is a software requirements document?
An official statement of what the system developers should implement, essential when systems are outsourced or analyzed in detail.
27What is requirements validation?
The process of checking that the requirements define the system that the customer really wants.
28What are the two approaches to requirements elicitation?
Interviewing and observation (or ethnography).