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. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






4. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






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






6. A non-actionable directive that supports a business goal.






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






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






9. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






10. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






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






12. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






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






14. A practitioner of business analysis.






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






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






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






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






19. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






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






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






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






23. An informal solicitation of proposals from vendors.






24. A prototype developed to explore or verify requirements.






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






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






27. The quality attributes design and implementation constraints and external interfaces that the product must have.






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






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






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






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






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






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






34. Software developed and sold for a particular market.






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






36. A prototype that is continuously modified and updated in response to feedback from users.






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






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






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






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






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






42. The problem area undergoing analysis.






43. A state or condition the business must satisfy to reach its vision.






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






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






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






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






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






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






50. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.