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 collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






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






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






5. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






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






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






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






12. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






13. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






14. A practitioner of business analysis.






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






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






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






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






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






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






21. A link between two elements or objects in a diagram.






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






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






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






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






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






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






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






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






30. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






31. A system trigger that is initiated by time.






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






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






34. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






35. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






36. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






37. Software developed and sold for a particular market.






38. A type of data model that depicts information groups as classes.






39. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






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






42. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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






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






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






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






47. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






48. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






49. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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