1. What is the main purpose of requirements specification in real-time systems?
(A) To define what the system must do, including functional and timing constraints
(B) To reduce CPU idle exclusively
(C) To perform batch processing only
(D) To ignore deadlines
2. Which type of requirements specify the system’s expected behavior?
(A) Functional requirements
(B) CPU idle exclusively
(C) Disk batch-only operations
(D) Memory-only allocation
3. Non-functional requirements in real-time systems include:
(A) Timing constraints, reliability, and fault tolerance
(B) CPU idle exclusively
(C) Disk batch-only safety
(D) Memory-only performance
4. Hard real-time systems have:
(A) CPU idle exclusively
(B) Strict deadlines that must always be met
(C) Disk batch-only schedules
(D) Memory-only constraints
5. Soft real-time systems are characterized by:
(A) Deadlines that should be met, but occasional misses are tolerable
(B) CPU idle exclusively
(C) Disk batch-only timing
(D) Memory-only optimization
6. Requirements specification serves as a basis for:
(A) Disk batch-only tasks
(B) CPU idle exclusively
(C) Design, implementation, verification, and validation
(D) Memory-only allocation
7. Temporal requirements specify:
(A) Disk batch-only operations
(B) CPU idle exclusively
(C) Timing constraints such as deadlines, periods, and response times
(D) Memory-only timing
8. Reliability requirements describe:
(A) CPU idle exclusively
(B) How often the system should perform correctly without failures
(C) Disk batch-only reliability
(D) Memory-only safety
9. Fault-tolerance requirements indicate:
(A) CPU idle exclusively
(B) How the system should behave in the presence of failures
(C) Disk batch-only safety
(D) Memory-only protection
10. Safety requirements in real-time systems ensure:
(A) The system avoids catastrophic failures that can harm people or property
(B) CPU idle exclusively
(C) Disk batch-only safety
(D) Memory-only protection
11. Correctness requirements specify:
(A) Disk batch-only correctness
(B) CPU idle exclusively
(C) The system’s outputs and behavior must be accurate and consistent
(D) Memory-only snapshots
12. Requirements specification can be documented using:
(A) Disk batch-only documentation
(B) CPU idle exclusively
(C) Natural language, formal methods, or semi-formal models
(D) Memory-only diagrams
13. A key challenge in specifying real-time requirements is:
(A) Memory-only snapshots
(B) CPU idle exclusively
(C) Disk batch-only tasks
(D) Accurately capturing both functional and timing constraints
14. Formal specification methods help in:
(A) Memory-only sequences
(B) CPU idle exclusively
(C) Disk batch-only operations
(D) Precisely defining system behavior and enabling verification
15. Semi-formal methods, like UML diagrams, are useful for:
(A) Communicating requirements clearly to stakeholders
(B) CPU idle exclusively
(C) Disk batch-only diagrams
(D) Memory-only representations
16. Requirements validation ensures:
(A) CPU idle exclusively
(B) The specified requirements accurately reflect stakeholder needs
(C) Disk batch-only verification
(D) Memory-only validation
17. Prioritization of requirements is important because:
(A) Not all requirements may be feasible under time and resource constraints
(B) CPU idle exclusively
(C) Disk batch-only tasks
(D) Memory-only allocation
18. Inconsistent requirements can lead to:
(A) Disk batch-only conflicts
(B) CPU idle exclusively
(C) Design errors, missed deadlines, and unreliable systems
(D) Memory-only inconsistencies
19. Traceability in requirements specification ensures:
(A) Memory-only mapping
(B) CPU idle exclusively
(C) Disk batch-only operations
(D) Each requirement is linked to design, implementation, and testing
20. The main advantage of a well-defined requirements specification is:
(A) CPU idle exclusively
(B) Predictable, reliable, and maintainable real-time system development
(C) Disk batch-only optimization
(D) Memory-only efficiency