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. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






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






5. A prototype that dives into the details of the interface functionality or both.






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






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






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






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






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






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






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






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






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






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






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






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






18. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






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






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






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






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






24. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






28. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






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






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






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






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






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






34. A unit of work performed as part of an initiative or process.






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






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






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






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






39. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






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






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






42. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






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






45. A practitioner of business analysis.






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






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






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






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






50. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.