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 shared boundary between any two persons and/or systems through which information is communicated.






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






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






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






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






6. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






7. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






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






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






11. A system trigger that is initiated by time.






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






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






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






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. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






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






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






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






21. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






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






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






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






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






27. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






28. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






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






31. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






32. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






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






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






36. Work carried out or on behalf of others.






37. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






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






39. A measure of the profitability of a project or investment.






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






41. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






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






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






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






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






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






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






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






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






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