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






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






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






4. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






6. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






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






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






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






10. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






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






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






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






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






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






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






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






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






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






20. A description of the requirements management process.






21. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






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 means to elicit requirements by conducting an assessment of the stakeholder's work environment.






24. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






25. A partial or preliminary version of the system.






26. A stakeholder person device or system that directly or indirectly accesses a system.






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






28. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






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






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






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






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






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






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






35. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






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






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






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






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. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






41. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






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






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






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






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






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






47. A specific actionable testable directive that is under the control of the business and supports a business policy.






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






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






50. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.