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. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






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






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






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






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






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






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






9. A prototype developed to explore or verify requirements.






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






11. Software developed and sold for a particular market.






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






13. A system trigger that is initiated by time.






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






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






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






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






18. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






19. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






20. A stakeholder who provides products or services to an organization.






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






22. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






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






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






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






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






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






29. An informal solicitation of proposals from vendors.






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






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






32. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






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






34. Any unique and verifiable work product or service that a party has agreed to deliver.






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






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






37. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






38. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






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






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






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






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






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






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






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






47. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






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






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






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