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 business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






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






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






4. A prototype that dives into the details of the interface functionality or both.






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






6. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






7. A description of the requirements management process.






8. A system trigger that is initiated by humans.






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






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






11. A system trigger that is initiated by time.






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






13. The work that must be performed to deliver a product service or result with the specified features and functions.






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






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






16. A practitioner of business analysis.






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






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






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






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






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






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






23. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






24. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






25. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






28. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






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






31. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






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






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






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






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






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






37. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






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






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






40. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






42. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






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






45. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






46. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






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






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






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






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