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






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






3. The quality attributes design and implementation constraints and external interfaces that the product must have.






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






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






6. Work carried out or on behalf of others.






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






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






9. An analysis model describing the data structures and attributes needed by the system.






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






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






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






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






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






15. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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






17. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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






19. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






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






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






23. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






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






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






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






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






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






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






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






31. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






32. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






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






34. Metadata related to a requirement used to assist with requirements development and management.






35. A practitioner of business analysis.






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






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






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






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






40. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






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






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






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






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






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






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






48. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






50. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.