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 characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






2. The features and functions that characterize a product service or result.






3. Software developed and sold for a particular market.






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






5. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






6. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






7. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






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






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






10. A non-actionable directive that supports a business goal.






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






12. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






13. A fixed period of time to accomplish a desired outcome.






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






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






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






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






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






19. An analysis model showing the life cycle of a data entity or class.






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






21. A structured examination of an identified problem to understand the underlying causes.






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






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






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






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






27. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






28. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






31. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






32. An analysis model that illustrates the architecture of the system's user interface.






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






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






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






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






37. A partial or preliminary version of the system.






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






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






40. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






42. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






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






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






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






46. A practitioner of business analysis.






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






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 measure of the profitability of a project or investment.






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