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 means to elicit requirements by conducting an assessment of the stakeholder's work environment.






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






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






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






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






6. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






7. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






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






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






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






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






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






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






15. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






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






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






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






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






20. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






21. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






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






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






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






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






27. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






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






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






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






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






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






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






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






36. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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






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






39. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






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






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






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






44. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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






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






47. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






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






50. A partial or preliminary version of the system.