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 system trigger that is initiated by time.






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






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






4. A prototype that dives into the details of the interface functionality or both.






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






6. A partial or preliminary version of the system.






7. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






8. Ability of systems to communicate by exchanging data or services.






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






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






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






12. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






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






14. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






15. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






16. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






17. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






18. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






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






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






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






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






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






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






26. A prototype developed to explore or verify requirements.






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






28. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






30. A temporary endeavor undertaken to create a unique product service or result.






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






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






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






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






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






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






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






38. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






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






40. An analysis model that illustrates the architecture of the system's user interface.






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






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






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






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






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






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






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






48. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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. The work that must be performed to deliver a product service or result with the specified features and functions.