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 set of requirements grouped together in a document or presentation for communication to stakeholders.






2. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






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






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






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






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






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






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






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






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






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






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






13. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






14. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






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






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






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






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






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






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






24. The human and nonhuman roles that interact with the system.






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






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






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






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






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






30. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






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






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






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. Metadata related to a requirement used to assist with requirements development and management.






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






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






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






38. An analysis model that shows user interface dialogs arranged as hierarchies.






39. A practitioner of business analysis.






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






41. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






42. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






44. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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






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






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






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






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






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