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






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






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






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






5. Software developed and sold for a particular market.






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






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






8. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






10. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






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






14. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






17. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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






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






20. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






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






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






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






25. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






27. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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






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






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






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






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






33. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






34. The problem area undergoing analysis.






35. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






37. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






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






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






40. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






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






42. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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






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






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






46. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






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






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






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






50. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s