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 process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






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






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






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






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






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






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






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






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






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






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






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






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






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






15. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






17. An informal solicitation of proposals from vendors.






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






19. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






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






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






23. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






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






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






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






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






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






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






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






31. A structured examination of an identified problem to understand the underlying causes.






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






33. A prototype developed to explore or verify requirements.






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






35. An analysis model describing the data structures and attributes needed by the system.






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






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






38. The problem area undergoing analysis.






39. A practitioner of business analysis.






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






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






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






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






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






45. The number of employees a manger is directly (or indirectly) responsible for.






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






47. A description of the requirements management process.






48. A non-actionable directive that supports a business goal.






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






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