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. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






2. A structured examination of an identified problem to understand the underlying causes.






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






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






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






6. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






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






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






10. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






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






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






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






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






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






16. A system trigger that is initiated by humans.






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






18. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






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






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






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






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






25. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






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






28. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






29. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






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






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






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






34. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






35. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






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






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






38. The set of capabilities a solution must deliver in order to meet the business need.






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






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






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






42. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






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






44. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






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






47. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






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






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