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






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






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






4. A system trigger that is initiated by time.






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






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






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






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






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






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






11. A shared boundary between any two persons and/or systems through which information is communicated.






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






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






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






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






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






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






18. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






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






21. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






23. A person with specific expertise in an area or domain under investigation.






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






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






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






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






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






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






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






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






32. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






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






34. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






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






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






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






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






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






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






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






43. A non-actionable directive that supports a business goal.






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






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






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






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






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






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






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