Requirements Engineering

Q1. What is a functional requirement?

1. A.A constraint on the system design choices
2. B.A measurable performance goal for the system
3. C.A requirement that describes what the system should do✓ Correct
4. D.A detailed hardware specification document

Report an error in this question

Q2. What is requirements engineering?

1. A.Performing software testing and validation in the development process
2. B.Designing hardware system architectures during the software lifecycle
3. C.Writing application source code for features as part of the methodology
4. D.The process of defining, documenting, and maintaining software requirements✓ Correct

Report an error in this question

Q3. What is the difference between user requirements and system requirements?

1. A.They are fundamentally the same concept entirely in the system context
2. B.User requirements are high-level; system requirements are detailed technical specifications✓ Correct
3. C.System requirements are always much simpler overall during implementation
4. D.User requirements are far more technically detailed for quality purposes

Report an error in this question

Q4. What is the difference between verification and validation in requirements?

1. A.Verification checks if we're building the product right; validation checks if we're building the right product✓ Correct
2. B.They are fundamentally identical concepts entirely for the project goals according to best practices
3. C.Verification is testing code; validation is writing code within the system boundary
4. D.Validation always occurs before verification ever does by the development process and its related activities

Report an error in this question

Q5. What is a use case diagram?

1. A.A process execution flowchart diagram only within the given constraints
2. B.A relational database schema diagram layout in all development efforts
3. C.A UML diagram showing actors and their interactions with the system✓ Correct
4. D.A network topology and routing diagram map by the project team members

Report an error in this question

Q6. What is requirements prioritization?

1. A.Permanently deleting all unimportant requirements
2. B.Ranking requirements by importance, risk, or business value✓ Correct
3. C.Grouping requirements by assigned developer team
4. D.Alphabetical ordering of all requirements listed

Report an error in this question

Q7. What is a use case?

1. A.A description of how a user interacts with the system to achieve a goal✓ Correct
2. B.A category of reported software defect type across all phases
3. C.A specific automated test case scenario only at every stage
4. D.A step in the deployment process workflow in a systematic way

Report an error in this question

Q8. Which of the following is a requirements elicitation technique?

1. A.Interview sessions✓ Correct
2. B.Debugging errors
3. C.Coding source logic
4. D.Code compilation

Report an error in this question

Q9. What is requirements traceability?

1. A.Tracking individual developer working hours over the entire lifecycle
2. B.The ability to trace each requirement through design, implementation, and testing✓ Correct
3. C.An established coding standard for the project for all project stakeholders
4. D.A specific debugging and troubleshooting technique as defined by standards

Report an error in this question

Q10. What is a Software Requirements Specification (SRS)?

1. A.The application source code implementation
2. B.A comprehensive software test plan document
3. C.A complete end-user operational and help manual
4. D.A document describing all requirements of the system✓ Correct

Report an error in this question

Q11. Who are stakeholders in requirements engineering?

1. A.Only the programmers writing the source code
2. B.Only the paying customers of the software product
3. C.Only the project managers overseeing the work
4. D.Anyone who has an interest in or is affected by the system✓ Correct

Report an error in this question

Q12. What is requirements elicitation?

1. A.The process of gathering requirements from stakeholders✓ Correct
2. B.Performing systematic software testing runs
3. C.Writing application source code for modules
4. D.Deploying software to production servers

Report an error in this question

Q13. What is prototyping used for in requirements engineering?

1. A.Delivering the final production product to users
2. B.Performing application security penetration tests
3. C.Conducting system performance load testing runs
4. D.Helping stakeholders visualize and validate requirements✓ Correct

Report an error in this question

Q14. What is a non-functional requirement?

1. A.A requirement that specifies quality attributes like performance or security✓ Correct
2. B.A requirement that is impossible to implement for the development team
3. C.A broken or flawed software requirement only within the project scope
4. D.A specification for hardware system components throughout the project

Report an error in this question

Q15. What is requirements validation?

1. A.Implementing requirements directly into code by the organization
2. B.Initially writing new requirements documents in practice typically
3. C.Checking that requirements are correct, complete, and consistent✓ Correct
4. D.Permanently deleting unnecessary requirements as a standard approach

Report an error in this question

Q16. What is domain analysis in requirements engineering?

1. A.Studying specific programming language syntax in the engineering discipline
2. B.Studying the application domain to understand its concepts and constraints✓ Correct
3. C.Analyzing the database schema domain structure and related components
4. D.Analyzing network domain name configurations to achieve project objectives

Report an error in this question

Q17. What is goal-oriented requirements engineering?

1. A.An approach where requirements are derived from stakeholder and system goals✓ Correct
2. B.Setting performance and speed benchmarks for quality purposes
3. C.Setting rigid project deadline target dates in the system context
4. D.Writing only goals instead of actual code during implementation

Report an error in this question

Q18. What is the Volere requirements template?

1. A.A software testing automation template setup within the project scope
2. B.A comprehensive template for organizing and documenting requirements with quality gateways✓ Correct
3. C.A deployment configuration setup template for the development team throughout the project
4. D.A source code implementation template file during the software lifecycle

Report an error in this question

Q19. What is a scenario in requirements engineering?

1. A.A real-life example describing how a system might be used✓ Correct
2. B.An established coding guideline for the teams
3. C.A comprehensive deployment plan document only
4. D.A specific automated test execution script only

Report an error in this question

Q20. What is the IEEE 830 standard?

1. A.A networking communication protocol standard
2. B.A standard for writing software requirements specifications✓ Correct
3. C.A software testing methodology and standard
4. D.A hardware design and manufacturing standard

Report an error in this question

Q21. What is a constraint in requirements engineering?

1. A.A defect discovered in the source code base for effective project outcomes
2. B.A restriction or limitation on the system or development process✓ Correct
3. C.A programming language built-in feature set in the development process
4. D.A specific type of software test case only as part of the methodology

Report an error in this question

Q22. What is requirements negotiation?

1. A.Rejecting all stakeholder proposed requirements
2. B.Resolving conflicts between stakeholders regarding requirements✓ Correct
3. C.Demanding that all requirements absolutely be met
4. D.Deliberately ignoring all stakeholder input

Report an error in this question

Q23. What is the KAOS methodology?

1. A.A deployment and release methodology guide by the organization
2. B.A goal-oriented requirements engineering methodology using formal methods✓ Correct
3. C.A specific software testing methodology only as a standard approach
4. D.A random unstructured development approach in practice typically

Report an error in this question

Q24. What is the difference between 'shall' and 'should' in requirements documents?

1. A.'Shall' indicates mandatory requirements; 'should' indicates desirable but optional✓ Correct
2. B.The two terms mean exactly the same thing always by the development process
3. C.Neither term is used in requirements documents ever over the entire lifecycle
4. D.'Should' is mandatory and 'shall' is always optional and its related activities

Report an error in this question

Q25. What is viewpoint-oriented requirements engineering?

1. A.Collecting requirements from multiple stakeholder viewpoints to ensure completeness✓ Correct
2. B.Only considering developer technical viewpoints within the system boundary
3. C.Deliberately ignoring all stakeholder views given according to best practices
4. D.Using only a single stakeholder perspective view for the project goals

Report an error in this question

Q26. What is requirements volatility?

1. A.Requirements that remain perfectly stable always at every stage
2. B.A type of volatile computer memory hardware across all phases
3. C.A recurring issue with hardware component sets in a systematic way
4. D.The tendency of requirements to change during the development process✓ Correct

Report an error in this question

Q27. What is formal specification in requirements engineering?

1. A.Drawing informal pictures of system requirements
2. B.Using mathematical notation to precisely define system requirements✓ Correct
3. C.Using programming code as the requirements source
4. D.Writing requirements in an informal manner only

Report an error in this question

Q28. What are cross-cutting concerns in requirements?

1. A.Requirements that are very easy to implement fast as defined by standards
2. B.Requirements that are considered not important for all project stakeholders
3. C.Requirements that affect multiple modules and cannot be cleanly decomposed✓ Correct
4. D.Requirements from only one single stakeholder within the given constraints

Report an error in this question

Q29. What is the i* (i-star) framework?

1. A.A numerical system for rating software products in all development efforts
2. B.A goal-oriented and agent-oriented modeling framework for requirements engineering✓ Correct
3. C.A general-purpose application programming framework by the project team members
4. D.A comprehensive software testing automation framework and related components

Report an error in this question

Q30. What is the difference between derived and imposed requirements?

1. A.Derived requirements are always considered optional in the development process during the software lifecycle
2. B.Derived requirements come from higher-level requirements; imposed requirements come from external constraints✓ Correct
3. C.They are fundamentally the same concept entirely to achieve project objectives in the engineering discipline
4. D.Imposed requirements are always derived from code for effective project outcomes as part of the methodology

Report an error in this question