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






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






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






4. Software requirements that limit the options available to the system designer.






5. The work that must be performed to deliver a product service or result with the specified features and functions.






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






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






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






9. A solution or component of a solution that is the result of a project.






10. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






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






13. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






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






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






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






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






19. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






21. A unit of work performed as part of an initiative or process.






22. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






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






25. The human and nonhuman roles that interact with the system.






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






27. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






29. A system trigger that is initiated by time.






30. A partial or preliminary version of the system.






31. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






32. A data element with a specified data type that describes information associated with a concept or entity.






33. Information that is used to understand the context and validity of information recorded in a system.






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






35. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






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






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






39. An analysis model that illustrates the architecture of the system's user interface.






40. Formal approval of a set of requirements by a sponsor or other decision maker.






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






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






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






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






45. A practitioner of business analysis.






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






47. Work carried out or on behalf of others.






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






49. The problem area undergoing analysis.






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