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 validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






2. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






3. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






4. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






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






8. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






9. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






10. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






11. Ability of systems to communicate by exchanging data or services.






12. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






13. The human and nonhuman roles that interact with the system.






14. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






15. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






16. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






17. 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.






18. A group of related tasks that support a key function of business analysis.






19. Software requirements that limit the options available to the system designer.






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






21. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






22. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






23. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






24. Something that occurs to which an organizational unit system or process must respond.






25. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






27. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






28. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






29. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






30. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






31. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






32. A person with specific expertise in an area or domain under investigation.






33. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






34. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






35. A system trigger that is initiated by humans.






36. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






37. 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.






38. An analysis model describing the data structures and attributes needed by the system.






39. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






40. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






41. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






42. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






43. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






44. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






45. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






46. A non-actionable directive that supports a business goal.






47. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






48. The degree to which a set of inherent characteristics fulfills requirements.






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






50. 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.