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 description of the requirements management process.






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






3. A prototype developed to explore or verify requirements.






4. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






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






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






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






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






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






12. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






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






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






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






16. A group or person who has interests that may be affected by an initiative or influence over it.






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






18. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






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






21. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






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






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






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






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






27. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






29. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






30. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






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






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






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






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






35. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






37. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






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






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






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






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






42. An actor who participates in but does not initiate a use case.






43. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






44. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






45. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






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






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






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






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