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. An assessment of the costs and benefits associated with a proposed initiative.






2. An analysis model that shows user interface dialogs arranged as hierarchies.






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






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






5. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






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






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






8. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






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






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






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






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






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






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






16. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






17. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






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






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






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






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






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






25. A practitioner of business analysis.






26. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






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






29. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






31. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






32. Work carried out or on behalf of others.






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






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






35. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






36. A prototype developed to explore or verify requirements.






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






38. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






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






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






41. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






42. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






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






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






45. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






46. A prototype that dives into the details of the interface functionality or both.






47. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






48. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






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