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 product capabilities or things the product must do for its users.






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






3. Work carried out or on behalf of others.






4. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






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






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






8. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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






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






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






12. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






13. The features and functions that characterize a product service or result.






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






15. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






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






18. A practitioner of business analysis.






19. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






21. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






22. An assessment of the costs and benefits associated with a proposed initiative.






23. A description of the requirements management process.






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






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






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






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






28. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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






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






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






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






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






35. The quality attributes design and implementation constraints and external interfaces that the product must have.






36. A stakeholder person device or system that directly or indirectly accesses a system.






37. A prototype developed to explore or verify requirements.






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






39. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






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






41. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






44. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






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






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






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






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






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






50. The problem area undergoing analysis.