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






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






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. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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






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






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






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






10. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






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






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






14. The set of capabilities a solution must deliver in order to meet the business need.






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






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






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






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






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






20. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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






22. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






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






24. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






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






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






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






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






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






31. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






32. A system of programming statements symbols and rules used to represent instructions to a computer.






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






34. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






36. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






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






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






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






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






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






42. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






44. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






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






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






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






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






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