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. Ability of systems to communicate by exchanging data or services.






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






3. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






4. Any effort undertaken with a defined goal or objective.






5. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






7. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






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






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






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






13. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






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






16. A prototype developed to explore or verify requirements.






17. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






19. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






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






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






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






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. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






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






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






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






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






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






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






32. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






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






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






36. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






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






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






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






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






42. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






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






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






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






46. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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






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






49. An informal solicitation of proposals from vendors.






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