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 small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






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






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






4. A fixed period of time to accomplish a desired outcome.






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






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






7. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






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






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. Work carried out or on behalf of others.






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






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






14. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






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






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






17. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






19. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






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






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






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






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






24. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






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. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






28. An analysis model showing the life cycle of a data entity or class.






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






30. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






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






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 group of related tasks that support a key function of business analysis.






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






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






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






37. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






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






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






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






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






42. The work that must be performed to deliver a product service or result with the specified features and functions.






43. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






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






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






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






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






48. A group or person who has interests that may be affected by an initiative or influence over it.






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






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