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. The product capabilities or things the product must do for its users.






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






3. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






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






5. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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






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






8. All materials used by groups within an organization to define tailor implement and maintain their processes.






9. Any effort undertaken with a defined goal or objective.






10. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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






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






13. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






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






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






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






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






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






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






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






22. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






23. A system trigger that is initiated by humans.






24. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






25. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






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






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






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






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






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






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






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






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






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






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






37. The number of employees a manger is directly (or indirectly) responsible for.






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






39. A prototype developed to explore or verify requirements.






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






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






42. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






43. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






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






46. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






47. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






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






49. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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