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 area covered by a particular activity or topic of interest.






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. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






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






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






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






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






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






9. Any effort undertaken with a defined goal or objective.






10. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






12. A prototype developed to explore or verify requirements.






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






14. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






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






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






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






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






19. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






20. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






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






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






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






26. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






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






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






30. The problem area undergoing analysis.






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






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






33. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






36. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






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






38. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






41. A system trigger that is initiated by humans.






42. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






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






45. A practitioner of business analysis.






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






47. An informal solicitation of proposals from vendors.






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






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






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