IREB Fundamentals Practice Exam

These questions are part of the practice quiz. Start practicing

• Which documentation method is specifically used to represent entity behavior and functions?
• Which of the following is an expected benefit of prototyping?
• What role does configuration management play in project management?
• What is the role of the actor in a use case diagram?
• How should a requirements engineer best handle conflicts in projects?
• How can you demonstrate the impact of usability on user acceptance of a system?
• What is an excitement factor in the context of software?
• Which statement about business, implementation, and user requirements is true?
• Which requirement aligns with the state diagram for an order management system?
• "Restrictions or limitations on the solutions" define which of the following terms?
• Who should sign off on the final requirements document?
• In what way does a glossary help to reduce redundancy?
• When you obtain a sign-off indicating that the requirements are clear, can be implemented and tested, what type of sign-off do you have?
• Which two essential tasks for requirements management are least supported by text processing tools?
• Which technique is best suited for a creative group of stakeholders who have knowledge regarding the requirements?
• Which definition best characterizes the term "traceability" in terms of requirements engineering?
• What is the primary reason for tracking traceability during the requirements elicitation process?
• What is the meaning of two parallel lines on a data flow diagram?
• Which technique is most effective for a detailed gathering of requirements in a short timeframe?
• What are the prospective modelling elements in a use case diagram?
• Who is primarily concerned with the requirements being correct?
• Consider the following activities: I. Identify II. Resolve III. Document in the requirements issue log IV. Escalate to management and project manager V. Document resolution. Which of the above must occur in conflict resolution prior to the implementation of requirements?
• What is described in the class methods definitions?
• Which statement is wrong regarding the documentation format of requirements?
• Who usually creates the physical model of the system being defined?
• Which of the following can be determined through good traceability of the requirements?
• Which of the following is not an IREB validation quality criteria for specification content?
• Which statement is true regarding technically relevant terms in a project?
• What should be documented in a requirements management plan?
• What role does the requirements engineer play in negotiating requirements?
• Which of the following statements is true regarding the goals of the elicitation process?
• Why should functional requirements dictate the solution design?
• Should managers attend the reviews?
• What type of requirement is illustrated by the following: 'The first page of report Y will be displayed for the user within 5 seconds of the request'?
• Which two pieces of information should always be recorded in the stakeholder list?
• What can result from poor requirements definition on a project?
• What approach to requirements gathering focuses on user stories and direct input from users?
• Which of the following are elements of a state diagram?
• What type of scenario describes a step-by-step operation of a proposed system within defined circumstances?
• In the context of requirements, what defines a 'use case'?
• Which document outlines the changes made to requirements during a project?
• Which of the following conflict resolution techniques is the least suitable for conflicts between clients and developers regarding a value conflict in requirements?
• Which statement is false regarding requirements checking techniques?
• What is a frequent outcome of poor requirements communication?
• What best describes non-functional requirements?
• Which of the following are appropriate interview questions for requirements elicitation?
• What is the primary relationship between a requirements engineer and a stakeholder in the role of a tester?
• Which diagram is least suited for representing system and context delimitation?
• Which of the following is a true statement regarding configuration management?
• What is the most precise definition of a sentence-template used for requirements?
• What is meant by a use case that is classified as "extend"?
• Which of the following criteria is NOT suitable for prioritizing requirements?
• Which aspect is least likely to be considered a result of quality of service requirements?
• You have found that a term you defined has been used to represent two different things. What should you do?
• If the purpose of our review is to determine if we are building the right product, what are we focused on?
• Which of the following is not a valid class relation in a class diagram?
• What is a common pitfall when writing requirements?
• Which of the following is an important aspect of the data requirements for a system?
• When analyzing functional requirements, why does uniqueness matter?
• What guideline should be followed when writing a requirements specification?
• You have reviewed your requirements and discovered that you have two requirements that conflict. What should you do now?
• Which of the following is a disadvantage to conducting reviews in emails?
• Why is it important to specify acceptance criteria for each requirement?
• If the team has an aversion to processes, which type of review will probably be the most successful?
• You neglected to track the origin of your requirements. Will producing a traceability matrix be a significant task for you?
• Which of the following is crucial for successful requirement engineering?
• What is the least suitable means to document details of a single use case?
• Which of the following is a rule of prioritization?
• Which of the following activities usually spans the entire project?
• If changes are required to the requirements during the implementation phases of the project, what should the analyst do?
• During an elicitation session, which technique will work best for eliciting, analyzing, and documenting requirements?
• What is the purpose of the alternate flows in a use case?
• When eliciting requirements from a large set of potential users with limited time, which technique is the best choice?
• How is a poor requirement best described?
• Where should we document conflicts?
• Which type of testing involves validating the system's functionality against the requirements?
• How are requirements typically documented during system development?
• Which one is the least important reason for documenting requirements?
• If there is a need to gather metrics from the review, which type of review will probably be the most effective?
• If developers are decompiling the code of a legacy system with no documentation, this is an example of which technique?
• Which two statements are correct regarding the introduction of a requirements engineering tool?
• Which strategy is most effective for managing changing requirements?
• Which of the following is a true statement regarding state transition diagrams?
• If you observe users of an existing product without interacting with them, which elicitation technique are you using?
• Which approach significantly minimizes scope creep?
• Should each requirement have a version identifier?
• Which statement accurately reflects data requirements for a system?
• Which of the following should be included in the glossary?
• What is the primary purpose of requirement traceability?
• What is commonly required for requirements to be effective for developers?
• What is the name of the diagram that graphically shows the sequence of activities and logic that controls the flow?
• Should multiple views of the requirements be prepared and maintained?
• When should traceability start and stop for a requirement?
• What is considered an advanced analyst skill?
• Why is it difficult to quantify the cost of a bug found in production?
• What is the main purpose of using sentence-templates in requirements writing?
• Which techniques are suitable for validating requirements?
• Which of the following best describes the importance of documenting constraints during requirement analysis?
• What are the most important quality criteria for requirements documents?
• In a UML class diagram of invoices, what model element describes the relationship between an invoice and its items?
• What is the proper use of the IEEE template?
• Which of the following is a benefit of having good requirement traceability?
• What type of requirements would you expect least in a SOA package focused on stock trade transactions?
• What requirements technique is commonly used to describe user requirements?
• What role does traceability play in requirements management?
• In a requirements specification, which is a fundamentally desirable attribute of requirements?
• Which statement correctly defines user requirements?
• "The system should have a fast response time" is an example of what type of requirement?
• The acceptance criteria for a use case must minimally include which of the following?
• Which of the following is a true statement about the identification of requirements?
• When is the best time to integrate usability into a product development cycle?
• What is the consequence of inadequate time allocated for requirement gathering?
• In a conflict situation about requirements, how should you best react?
• Why is stakeholder involvement crucial in the requirements gathering phase?
• When dealing with old requirements documentation from a legacy system that lacks current information, which technique should be used?
• Which of the following is a true statement regarding conflict in requirements?
• Which is more important?
• What does the stability attribute of a requirement indicate?
• Based on the context of system X, which statement is most accurate regarding the relationship with system Y and system Z?
• What are two effective approaches to detail and refine specified goals in system development?
• What does it mean when a requirement is deemed "traceable"?
• What happens when you overlook a source of requirements?
• Which statement is true regarding the interfaces of the system being defined?
• Why must assumptions be clearly documented during requirement analysis?
• If a missing requirement was detected during user acceptance testing, what does this imply about the requirements process?
• In what situation should the requirements document be updated?
• Which technique is commonly used for requirements elicitation?
• Which of the following sections is the core of the IEEE 830 document?
• In a context diagram for a logistics system, which statement is true regarding the problem assignment of the system?
• What elicitation technique is being utilized when developers create a mock-up for stakeholders to visualize the new product?
• Which of the following best describes the role of a requirements workshop?
• Does risk analysis consider both constraints and assumptions in a project?
• What does scope creep refer to?
• What best defines the acceptance criteria for a data requirement?
• Why is documenting requirements systematically important in requirements engineering?
• What role does a "context diagram with data flows" serve in requirements engineering?
• How is a "stakeholder" best characterized?
• What type of requirement is characterized as "what a system must do"?
• What happens to the cost of a bug the longer it goes undetected and unfixed?
• Which of the following is a true statement regarding the requirements baseline?
• What is the main goal in involving testers early in the requirements elicitation process?
• In requirements engineering, which statements about grey zones in system and context scope are true?
• Which elicitation technique would be less effective for a diverse group of stakeholders?
• In requirements documentation, which statements are true regarding model-based versus natural language?
• When testing data transferred via an interface, what should be done?
• What is the primary focus when defining non-functional requirements?
• Why would you want to conduct multiple presentations for the requirements?
• Which of the following should be avoided to prevent ambiguity in requirements?
• What is one of the difficulties with determining acceptance criteria for non-functional requirements?
• Quality of service requirements are a subset of which types of requirements?
• In which of the following activities should the analyst participate?
• What are the main components of an entity relationship diagram?
• Which of the following is an example of how good engineering practices can help avoid project problems?
• What is the objective of requirements validation?
• Why is it important for technical terms to be clearly defined in requirement documents?
• To clarify the boundaries of a system being defined, which technique is most appropriate?
• Why is it important to determine elicitation techniques during the requirements planning phase?
• What is the best definition of the elicitation process?
• Which of the following statements accurately describes the influence of quality of service (QoS) requirements on user acceptability?
• What cost is incurred if a bug in the requirements is not detected until code implementation?
• In terms of software development, what does SRS stand for?
• Suitability of the software to fulfill the needs of the user exemplifies a quality attribute of what type of requirement?
• What role does a requirements analyst play in managing change?
• What does MTTR measure in terms of system attributes?
• During implementation, who should the analyst represent?
• What likely occurred if a requirement appears between the product requirement and detailed design documents?
• At what point in a project should stakeholders be involved?
• What should an analyst ensure regarding requirements traceability?
• If performance requirements are not correctly specified and the resultant software is too slow, what is likely to happen?
• What techniques are best suited to identifying user requirements for a new system aimed at monitoring patients?
• When using open-ended interviews for elicitation, what is the primary advantage?
• From the provided quality characteristics, which is the least important when specifying requirements?
• According to the Kano model, which category of system attributes has an almost linear satisfaction compliance relationship?
• Why are different views of individual components of requirements used?
• What does a Change Control Board (CCB) do?
• Should analysts plan for scope changes during a project?
• Requirements are grouped into which three categories according to Kano?
• Which of the following class diagrams correctly represents the student-lecturer relationship?
• Which of the following can be considered as requirement attributes?
• You have obtained the complete sign-off of your requirements. Now what?
• When should requirements documentation start?
• You are reading a state transition diagram and have found the following identifier: Payment received[invalid]/error message. What is the correct interpretation of this label on a transition?
• Which diagrams help represent the structural perspective of a requirements model?
• Why should we use a checklist when reviewing requirements?
• Which combination of statements is true about creating testable requirements?
• In a situation requiring feature ideas from potential customers, which technique is the least suitable?
• Which factors must be considered as part of enterprise analysis to influence project success?
• What is one key advantage of using a model for requirements documentation?
• Which of the following describes inspection as a checking technique?
• If most of the stakeholders have signed off on the requirements, but one customer representative wants a change leading to increased scope, what should you do?
• Which factor is a major reason for late discovery of missing requirements?
• What should a requirements engineer prioritize when managing stakeholder communication?
• Which of the following review types is least formal?
• What must be analyzed when evaluating a change request?
• Which one is not a problem described in the transformational process?
• Which of the following is a particular concern for third-party interfaces?
• Which of the following is not an expected feature of a requirement management tool?
• What property of requirements is particularly essential for testers?
• What three capabilities should a modeling tool possess for creating traceable models in requirements engineering?
• What is the main purpose of using mock-ups during the requirements elicitation phase?
• Which of the following is a true statement regarding requirement management tools?
• Which statements about natural language documentation of requirements do not apply?
• What attribute of the requirements engineer poses the greatest risk?
• In a browser-based application for managing investment portfolios, how should requirements be categorized?
• If a requirement changes so that only the bank identification code must be entered, what part of your documentation must be updated?
• What two statements about the system and context boundary are correct?
• Modeling tools are most effectively used by which stakeholders?