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






2. A prototype developed to explore or verify requirements.






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






4. Creating working software in multiple releases so the entire product is delivered in portions over time.






5. A system trigger that is initiated by time.






6. A link between two elements or objects in a diagram.






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






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






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






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






11. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






12. A measure of the profitability of a project or investment.






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






14. A model that defines the boundaries of a business domain or solution.






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






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






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






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






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






20. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






22. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






23. A partial or preliminary version of the system.






24. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






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






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






28. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






30. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






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






33. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






34. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






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






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






37. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






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






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






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






42. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






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






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






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






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






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






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






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






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