Specification of software requirements Quiz

What is the primary purpose of a Software Requirements Specification (SRS)?

• To provide a detailed design of the software system

• To describe the business needs and stakeholder requirements

• To outline the project timeline and budget

• To specify the coding standards and development tools

Which of the following is a source of software requirements?

• End-users

• Project managers

• Regulatory documents

• All of the above

What is an important characteristic of describing customer needs as requirements?

• Vague and open-ended

• Specific and measurable

• Technical and complex

• Brief and abstract

Which of the following is a requirements specification language?

• Java

• UML (Unified Modeling Language)

• SQL

• HTML

Which technique is commonly used for prioritizing requirements?

• Brainstorming

• MoSCoW (Must have, Should have, Could have, Won't have)

• Flowcharting

• Prototyping

What tool is often used in requirements engineering?

• Integrated Development Environment (IDE)

• Requirements Management Tool

• Version Control System

• Load Testing Tool

What is a common technique for requirements documentation and specification?

• Mind Mapping

• Prototyping

• Use Case Modeling

• Code Refactoring

Which document is typically created after the requirements have been gathered and analyzed to ensure all stakeholders have a common understanding of the project scope and details?

• Project Charter

• Software Design Document

• Requirements Traceability Matrix

• Business Requirements Document (BRD)

Which of the following best explains the difference between user stories and use cases?

• User stories are detailed descriptions of system interactions, while use cases are short, simple statements of customer needs

• User stories are written by developers, while use cases are written by stakeholders

• User stories focus on the "who," "what," and "why," while use cases provide a step-by-step interaction between the user and the system
  
  

• User stories are used during testing, while use cases are used during design

Which of the following techniques helps capture both functional and non-functional requirements effectively?

• Brainstorming

• Prototyping

• Use Case Modeling

• User Story Mapping