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. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






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






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






5. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






8. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






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






10. A practitioner of business analysis.






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






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






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






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






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






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






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






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






19. A system trigger that is initiated by time.






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






21. A description of the requirements management process.






22. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






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






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






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






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






27. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






28. A type of data model that depicts information groups as classes.






29. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






32. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






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






34. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






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






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






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






38. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






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






41. An informal solicitation of proposals from vendors.






42. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






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






45. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






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






48. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






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






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