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






2. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






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






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






6. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






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






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






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






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






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






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






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






14. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






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






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






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






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






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






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






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






22. A measure of the profitability of a project or investment.






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






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






25. An analysis model showing the life cycle of a data entity or class.






26. Any unique and verifiable work product or service that a party has agreed to deliver.






27. A structured examination of an identified problem to understand the underlying causes.






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






29. A practitioner of business analysis.






30. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






31. A system trigger that is initiated by humans.






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






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. A stakeholder who provides products or services to an organization.






35. An informal solicitation of proposals from vendors.






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






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






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






39. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






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






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






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






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






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






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






46. The human and nonhuman roles that interact with the system.






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






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






49. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






50. Information that is used to understand the context and validity of information recorded in a system.