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 person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






3. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






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






6. A fixed period of time to accomplish a desired outcome.






7. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






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






10. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






12. Any recognized association of people in the context of an organization or enterprise.






13. Any effort undertaken with a defined goal or objective.






14. A use case composed of a common set of steps used by multiple use cases.






15. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






17. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






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






19. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






20. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






22. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






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






25. A prototype that is continuously modified and updated in response to feedback from users.






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






27. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






28. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






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






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






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






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






34. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






35. A group or person who has interests that may be affected by an initiative or influence over it.






36. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






38. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






39. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






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






41. A description of the requirements management process.






42. A practitioner of business analysis.






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






44. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






46. The problem area undergoing analysis.






47. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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






49. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






50. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).