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






2. The set of capabilities a solution must deliver in order to meet the business need.






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






4. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






6. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






7. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






8. A system trigger that is initiated by time.






9. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






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






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






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






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






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






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






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






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






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






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






20. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






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






22. The problem area undergoing analysis.






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






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






25. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






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






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






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






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






30. Ability of systems to communicate by exchanging data or services.






31. A person with specific expertise in an area or domain under investigation.






32. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






33. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






35. Information that is used to understand the context and validity of information recorded in a system.






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






37. A prototype developed to explore or verify requirements.






38. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






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






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






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






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






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






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






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






47. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






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






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