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 fixed period of time to accomplish a desired outcome.






2. An analysis model showing the life cycle of a data entity or class.






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






4. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






5. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






6. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






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






9. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






10. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






11. The area covered by a particular activity or topic of interest.






12. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






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






14. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






16. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






17. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






18. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






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






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






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






23. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






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






25. A data element with a specified data type that describes information associated with a concept or entity.






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






27. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






28. Information that is used to understand the context and validity of information recorded in a system.






29. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






31. An informal solicitation of proposals from vendors.






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






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






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






35. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






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






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






39. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






40. The process of examining new business opportunities to improve organizational performance.






41. An assessment of the costs and benefits associated with a proposed initiative.






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






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






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






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






46. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






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






48. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






49. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






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