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






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






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






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






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






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






7. The degree to which a set of inherent characteristics fulfills requirements.






8. The process of examining new business opportunities to improve organizational performance.






9. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






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






11. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






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






14. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






16. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






17. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






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






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






20. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






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






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






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






24. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






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






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






27. Something that occurs to which an organizational unit system or process must respond.






28. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






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






31. An informal solicitation of proposals from vendors.






32. A system of programming statements symbols and rules used to represent instructions to a computer.






33. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






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






35. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






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






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






39. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






40. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






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






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






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






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






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






47. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






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






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