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. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






2. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






4. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






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






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






9. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






10. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






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






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






14. Software developed and sold for a particular market.






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






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






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






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






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






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






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






22. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






23. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






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






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






26. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






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






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






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






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






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






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






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






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






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






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






37. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






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






40. A practitioner of business analysis.






41. Work carried out or on behalf of others.






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






43. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






44. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






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






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






48. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






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






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