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 shared boundary between any two persons and/or systems through which information is communicated.






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






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






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






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






6. An informal solicitation of proposals from vendors.






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






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






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






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






11. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






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






14. A partial or preliminary version of the system.






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






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






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






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






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






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






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






22. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






23. A stakeholder person device or system that directly or indirectly accesses a system.






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






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






26. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






27. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






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






30. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






31. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






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






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






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






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






36. An analysis model showing the life cycle of a data entity or class.






37. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






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






40. An analysis model that shows user interface dialogs arranged as hierarchies.






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






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






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






44. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






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






47. Software developed and sold for a particular market.






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






49. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






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