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 set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






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






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






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






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 prototype that dives into the details of the interface functionality or both.






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






8. Software developed and sold for a particular market.






9. An informal solicitation of proposals from vendors.






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






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






12. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






13. A practitioner of business analysis.






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






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






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






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






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






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






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






21. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






22. A type of data model that depicts information groups as classes.






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






24. Metadata related to a requirement used to assist with requirements development and management.






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






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






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






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






29. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






31. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






32. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






34. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






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






37. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






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






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






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






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






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






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






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






45. Work carried out or on behalf of others.






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






47. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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






49. A system trigger that is initiated by humans.






50. The degree to which a set of inherent characteristics fulfills requirements.