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 condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






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






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






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






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






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






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






10. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






11. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






13. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






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






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






16. A partial or preliminary version of the system.






17. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






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






19. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






20. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






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






22. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






23. A system trigger that is initiated by humans.






24. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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






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. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






28. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






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






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






31. A system of programming statements symbols and rules used to represent instructions to a computer.






32. An analysis model that shows user interface dialogs arranged as hierarchies.






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






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






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






36. A prototype that is continuously modified and updated in response to feedback from users.






37. A shared boundary between any two persons and/or systems through which information is communicated.






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






39. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






40. An informal solicitation of proposals from vendors.






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






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






43. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






44. A state or condition the business must satisfy to reach its vision.






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






46. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






48. Work carried out or on behalf of others.






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






50. All materials used by groups within an organization to define tailor implement and maintain their processes.