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 list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






3. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






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






7. A practitioner of business analysis.






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






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






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






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






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






13. A stakeholder who uses products or services delivered by an organization.






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






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






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






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






18. A measure of the profitability of a project or investment.






19. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






20. The quality attributes design and implementation constraints and external interfaces that the product must have.






21. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






22. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






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






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






25. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






27. Formal approval of a set of requirements by a sponsor or other decision maker.






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






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






30. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






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






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






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






34. A shared boundary between any two persons and/or systems through which information is communicated.






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






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






37. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






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






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






40. A temporary endeavor undertaken to create a unique product service or result.






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






42. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






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






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






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






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






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






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






49. A link between two elements or objects in a diagram.






50. A solution or component of a solution that is the result of a project.