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 requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






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






3. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






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






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






6. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






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






9. A prototype developed to explore or verify requirements.






10. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






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






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






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






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






15. The problem area undergoing analysis.






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






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






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






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






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






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






22. A type of data model that depicts information groups as classes.






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






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






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






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






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






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






29. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






30. Software requirements that limit the options available to the system designer.






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






32. A stakeholder who provides products or services to an organization.






33. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






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






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






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






37. Limitations on the design of a solution that derive from the technology used in its implementation.






38. An actor who participates in but does not initiate a use case.






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 real or virtual facility where all information on a specific topic is stored and is available for retrieval.






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






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






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






44. A practitioner of business analysis.






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






46. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






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






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






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