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 business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






3. The area covered by a particular activity or topic of interest.






4. A shared boundary between any two persons and/or systems through which information is communicated.






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






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






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






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






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






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






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






12. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






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






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






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






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






17. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






18. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






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






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






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






23. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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






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






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






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






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






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






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






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






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






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






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






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






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






38. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






39. An analysis model describing the data structures and attributes needed by the system.






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






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






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






43. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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






45. A type of data model that depicts information groups as classes.






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






47. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






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






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