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






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






3. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






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






5. A structured examination of an identified problem to understand the underlying causes.






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






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






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






9. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






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






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






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






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






14. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






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






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






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






19. A practitioner of business analysis.






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






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






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






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






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






25. A description of the requirements management process.






26. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






28. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






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






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






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






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






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






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






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






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






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






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






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






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






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






43. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






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






46. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






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






49. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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