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 deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






2. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






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






4. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






5. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






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






7. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






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






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






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






12. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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






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






15. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






18. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






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






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






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






23. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






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






25. A system trigger that is initiated by humans.






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






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






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






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






30. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






32. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






34. The process of examining new business opportunities to improve organizational performance.






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






36. Work carried out or on behalf of others.






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






38. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






39. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






40. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






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






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






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






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






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






47. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






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






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






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