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






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






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






4. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






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






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






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






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






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






10. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






12. Software developed and sold for a particular market.






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






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






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






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






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






18. The number of employees a manger is directly (or indirectly) responsible for.






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






20. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






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






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






24. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






26. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






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






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






30. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






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






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 set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






36. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






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






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






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






41. A measure of the profitability of a project or investment.






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






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






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






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






46. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






47. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






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






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






50. A practitioner of business analysis.