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. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






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






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






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






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






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






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. The area covered by a particular activity or topic of interest.






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






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






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






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






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






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






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






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






17. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






19. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






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






23. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






24. A system trigger that is initiated by time.






25. Something that occurs to which an organizational unit system or process must respond.






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






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






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






29. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






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






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






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






34. A practitioner of business analysis.






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






36. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






38. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






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






42. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






43. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






44. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






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






46. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






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






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






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