Across
- 3. A practitioner of business analysis
- 7. CCB. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements
- 9. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure, policies and operations of an organization, and recommend solutions that enable the organization to achieve its goals
- 11. A system trigger that is initiated by humans
- 12. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst, business integrator, requirements analysis, requirements engineer, and systems analyst
- 14. A stakeholder who uses products or services delivered by an organization
- 15. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Processes are triggered by events any may have multiple outcomes. A successful of a process will deliver value to one or more stakeholders
- 16. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flow and concurrent activities. Steps can be superimposed onto horizontal swim lanes for the roles that perform the steps. A graphical representation that shows the steps of a workflow of components or processes
- 17. The set of processes, templates, and activities that will be used to perform business analysis in a specific context
- 18. 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
- 20. 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
- 21. A subset of the enterprise architecture that defines an organization’s current and future state, including is strategy, its goals and objectives, the internal environment through a process or functional view, the external environment in which the business operates, and the stakeholders affected by the organization’s activities
- 25. A system of programming statements, symbols and rules used to represent instructions to a computer
- 26. A description of the types of communication the business analyst will perform during business analysis, the recipients of those communications, and the form in which communication should occur
- 27. 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
- 29. The number of occurrences of one entity in a data model that are linked to a second entity. Shown on a data model with a special notation, number (e.g. 1), or letter (e.g. M for many)
- 31. 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
- 33. A specific, actionable, testable directive that is under the control of the business and supports a business policy
- 35. Influencing factors that are believed to be true but have not been confirmed to be accurate
- 38. Tests written without regard to how the software is implemented. These tests how only what the expected input and outputs will be
- 39. A link between two elements or objects in a diagram. A commonly used name for this term is “relationship”
- 40. A unit of work performed as part of an project/initiative or process
Down
- 1. 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
- 2. A descriptor for a set of system objects that share the same attributes, operations, relationships, and behaviors. A class represents a concept in the system under design. When used as an analysis model, will correspond to a real-world entity
- 4. Limitations placed on the solution designed by the organization that needs the solution. Describe limitations on available solutions, or an aspect of the current state that cannot be changed by the deployment of the new solution.
- 5. 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
- 6. A non-actionable directive that supports a business goal
- 7. Describes any limitations imposed on the solution that do not support the business or stakeholders needs
- 8. 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. Useful to validate the solution scope with the business and technical stakeholders
- 10. 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
- 13. A requirements package that describes business requirements and stakeholders requirements (it documents requirements of interest to the business, rather than documenting business requirements)
- 19. Commercial-off-the-Shelf Software. Software developed and sold for a particular market
- 22. A higher level business rationale that, when addressed, will permit the organization to increase revenue, avoid costs, improve service, or meet regulatory requirements
- 23. A team activity that seeks to produce a broad diverse set of options through the rapid and uncritical generation of ideas
- 24. The human and nonhuman roles that interact with the system
- 26. An assessment of the costs and benefits associated with a proposed initiative
- 28. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development
- 30. A type of data model that depicts information groups as classes
- 32. A state or condition the business must satisfy to reach its vision
- 34. 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
- 36. A data element with a specified data type that describes information associated with a concept or entity. Data that defines the characteristic properties of objects, concepts, or entities. They are fields in a physical file or table.
- 37. A function of an organization that enables it to achieve a business goal or objective