Browse all practice questions for the IREB Fundamentals Practice Exam. Search by topic, open any question and review its full explanation, then test yourself in the practice quiz.

IREB Fundamentals Practice Exam course image
More practice questions

These questions are part of the practice quiz. Start practicing

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

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy