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 diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






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






3. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






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






7. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






8. A system trigger that is initiated by humans.






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






10. A shared boundary between any two persons and/or systems through which information is communicated.






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






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






13. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






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






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






16. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






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






18. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






19. A non-actionable directive that supports a business goal.






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






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






22. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






25. A state or condition the business must satisfy to reach its vision.






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






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






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






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






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






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






32. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






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






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






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






37. The problem area undergoing analysis.






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






39. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






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






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






42. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






44. A function of an organization that enables it to achieve a business goal or objective.






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






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






47. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






48. A person with specific expertise in an area or domain under investigation.






49. A specific actionable testable directive that is under the control of the business and supports a business policy.






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