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






2. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






4. Any effort undertaken with a defined goal or objective.






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






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






7. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






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






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






12. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






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






16. A stakeholder who provides products or services to an organization.






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






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






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






20. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






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






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






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






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






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






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






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






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






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






32. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






36. A data element with a specified data type that describes information associated with a concept or entity.






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






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






39. A specific actionable testable directive that is under the control of the business and supports a business policy.






40. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






41. Software developed and sold for a particular market.






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






43. Limitations on the design of a solution that derive from the technology used in its implementation.






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






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






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






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






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






49. Metadata related to a requirement used to assist with requirements development and management.






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