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 technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






2. A temporary endeavor undertaken to create a unique product service or result.






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






4. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






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






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






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






8. Software developed and sold for a particular market.






9. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






10. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






11. A practitioner of business analysis.






12. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






13. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






15. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






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






17. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






18. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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






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






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. The set of capabilities a solution must deliver in order to meet the business need.






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






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






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






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






28. Work carried out or on behalf of others.






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






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






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






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






33. The features and functions that characterize a product service or result.






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






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






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






37. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






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






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






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






42. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






43. The problem area undergoing analysis.






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






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






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






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






48. A system trigger that is initiated by humans.






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