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 deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






3. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






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






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






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






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






8. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






10. Any recognized association of people in the context of an organization or enterprise.






11. A system trigger that is initiated by humans.






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






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






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






15. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






18. A prototype developed to explore or verify requirements.






19. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






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






22. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






23. A description of the requirements management process.






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






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






26. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






27. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






28. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






29. A partial or preliminary version of the system.






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






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






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






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






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






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






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






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






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






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






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






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






42. A practitioner of business analysis.






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






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






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






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






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






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






49. A link between two elements or objects in a diagram.






50. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.