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






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






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






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






5. A partial or preliminary version of the system.






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






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






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






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






10. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






12. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






14. A system trigger that is initiated by humans.






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






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






17. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






20. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






21. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






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






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






24. A person with specific expertise in an area or domain under investigation.






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






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






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






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






29. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






30. A measure of the profitability of a project or investment.






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






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






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






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






35. A description of the requirements management process.






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






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






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






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






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






41. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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






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






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






45. Information that is used to understand the context and validity of information recorded in a system.






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






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






48. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






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






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