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 condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






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






6. The features and functions that characterize a product service or result.






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






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






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






10. A practitioner of business analysis.






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






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






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






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






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






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






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






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






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






20. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






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






22. A data element with a specified data type that describes information associated with a concept or entity.






23. Software developed and sold for a particular market.






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






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






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






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






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






29. Information that is used to understand the context and validity of information recorded in a system.






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






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






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






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






34. Limitations on the design of a solution that derive from the technology used in its implementation.






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






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






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






38. A state or condition the business must satisfy to reach its vision.






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






40. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






41. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






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






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






45. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






46. The degree to which a set of inherent characteristics fulfills requirements.






47. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






48. A system trigger that is initiated by time.






49. The process of examining new business opportunities to improve organizational performance.






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