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 representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






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






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






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






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






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






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






8. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






9. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






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






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






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






14. A description of the requirements management process.






15. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






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






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






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






20. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






22. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






25. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






26. The number of employees a manger is directly (or indirectly) responsible for.






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






28. A system trigger that is initiated by time.






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






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






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






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






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






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






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






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






37. The features and functions that characterize a product service or result.






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






39. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






40. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






41. An actor who participates in but does not initiate a use case.






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






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






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






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






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






47. A practitioner of business analysis.






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






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






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