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






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






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






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






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






6. Software developed and sold for a particular market.






7. A practitioner of business analysis.






8. The human and nonhuman roles that interact with the system.






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






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






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






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






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. A stakeholder who uses products or services delivered by an organization.






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






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






17. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






18. A temporary endeavor undertaken to create a unique product service or result.






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






20. A system trigger that is initiated by humans.






21. A set of requirements grouped together in a document or presentation for communication to stakeholders.






22. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






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






25. A group of related tasks that support a key function of business analysis.






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






27. The set of capabilities a solution must deliver in order to meet the business need.






28. An assessment of the costs and benefits associated with a proposed initiative.






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






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






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






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






33. Limitations on the design of a solution that derive from the technology used in its implementation.






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






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






36. A solution or component of a solution that is the result of a project.






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






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






39. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






40. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






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






43. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






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






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






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






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






48. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






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