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. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






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






3. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






4. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






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






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






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






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






10. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






13. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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






16. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






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






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






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






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






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






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






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






24. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






25. Ability of systems to communicate by exchanging data or services.






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






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






28. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






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






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






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






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






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






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






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






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






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






38. The area covered by a particular activity or topic of interest.






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






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






41. The set of processes templates and activities that will be used to perform business analysis in a specific context.






42. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






43. Work carried out or on behalf of others.






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






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






46. An analysis model showing the life cycle of a data entity or class.






47. An assessment of the costs and benefits associated with a proposed initiative.






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






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






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