Test your basic knowledge |

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






2. A prototype developed to explore or verify requirements.






3. The product capabilities or things the product must do for its users.






4. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






5. A prototype that dives into the details of the interface functionality or both.






6. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






7. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






8. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






9. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






10. A model that defines the boundaries of a business domain or solution.






11. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






12. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






13. A unit of work performed as part of an initiative or process.






14. The work that must be performed to deliver a product service or result with the specified features and functions.






15. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






16. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






17. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






18. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






19. A description of the requirements management process.






20. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






21. Software developed and sold for a particular market.






22. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






23. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






24. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






25. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






26. A structured examination of an identified problem to understand the underlying causes.






27. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






28. A type of data model that depicts information groups as classes.






29. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






30. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






31. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






32. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






33. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






34. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






35. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






36. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






37. A specific actionable testable directive that is under the control of the business and supports a business policy.






38. An informal solicitation of proposals from vendors.






39. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






40. An analysis model that illustrates the architecture of the system's user interface.






41. Limitations on the design of a solution that derive from the technology used in its implementation.






42. The set of processes templates and activities that will be used to perform business analysis in a specific context.






43. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






44. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






45. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






46. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






47. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






48. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






49. Work carried out or on behalf of others.






50. The problem area undergoing analysis.