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. Something that occurs to which an organizational unit system or process must respond.






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






3. A description of the requirements management process.






4. A practitioner of business analysis.






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






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






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






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






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






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






11. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






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






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






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






16. A model that defines the boundaries of a business domain or solution.






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






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






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






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






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






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






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






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






25. A system trigger that is initiated by humans.






26. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






27. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






29. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






30. The process of examining new business opportunities to improve organizational performance.






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






32. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






34. A group or person who has interests that may be affected by an initiative or influence over it.






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






36. The area covered by a particular activity or topic of interest.






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






38. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






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. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






41. Software requirements that limit the options available to the system designer.






42. Software developed and sold for a particular market.






43. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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






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






46. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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






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






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






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