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. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






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






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






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






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






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






9. A temporary endeavor undertaken to create a unique product service or result.






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






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






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






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






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






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






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






17. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






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






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






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






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






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






23. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






24. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






26. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






27. The problem area undergoing analysis.






28. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






29. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






30. A stakeholder who uses products or services delivered by an organization.






31. A description of the requirements management process.






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






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






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






35. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






36. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






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






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






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






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






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






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






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






45. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






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






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






49. A specific actionable testable directive that is under the control of the business and supports a business policy.






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