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






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






3. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






4. An analysis model that illustrates the architecture of the system's user interface.






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






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






7. The features and functions that characterize a product service or result.






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






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






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






11. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






12. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






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






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






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






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






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






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






19. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






20. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






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






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






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






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






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






26. Any recognized association of people in the context of an organization or enterprise.






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






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






29. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






30. A prototype developed to explore or verify requirements.






31. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






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






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






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






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






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






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






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






39. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






40. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






42. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






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






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






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






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






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






49. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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