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 graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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






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






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






7. A system trigger that is initiated by time.






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 prototype developed to explore or verify requirements.






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






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






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






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






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






15. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






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






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






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






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






20. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






22. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






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






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






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






26. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






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






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






30. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






32. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






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






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






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






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






38. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






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






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






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






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






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






45. Work carried out or on behalf of others.






46. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






47. A stakeholder person device or system that directly or indirectly accesses a system.






48. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






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