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






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






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






4. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






5. A description of the requirements management process.






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






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






8. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






9. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






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






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






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






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






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






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






17. The area covered by a particular activity or topic of interest.






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






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






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






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






22. Software developed and sold for a particular market.






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






24. A stakeholder who uses products or services delivered by an organization.






25. The product capabilities or things the product must do for its users.






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






27. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






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 means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






31. A function of an organization that enables it to achieve a business goal or objective.






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






33. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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






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






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






37. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






38. A shared boundary between any two persons and/or systems through which information is communicated.






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






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






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






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






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






44. A partial or preliminary version of the system.






45. Work carried out or on behalf of others.






46. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






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






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






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