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 defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






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






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






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






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






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






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






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






10. A use case composed of a common set of steps used by multiple use cases.






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






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






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






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






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






16. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






17. A solution or component of a solution that is the result of a project.






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






19. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






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






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






23. Software requirements that limit the options available to the system designer.






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






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






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






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






28. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






29. An informal solicitation of proposals from vendors.






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






31. The set of capabilities a solution must deliver in order to meet the business need.






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






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






34. A description of the requirements management process.






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






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






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






38. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






40. A person with specific expertise in an area or domain under investigation.






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






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






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






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






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






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






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






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






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