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. Work carried out or on behalf of others.






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






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






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






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






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






7. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






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






9. A stakeholder who provides products or services to an organization.






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






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






12. A use case composed of a common set of steps used by multiple use cases.






13. The work that must be performed to deliver a product service or result with the specified features and functions.






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






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






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






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






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






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






20. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






22. A prototype developed to explore or verify requirements.






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






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






25. An informal solicitation of proposals from vendors.






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






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






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






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






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






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






32. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






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






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






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






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






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






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






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






40. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






41. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






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






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






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






45. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






46. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






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






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






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






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