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






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






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






4. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






5. Work carried out or on behalf of others.






6. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






7. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






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






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






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






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






13. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






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






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






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






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






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






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






20. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






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






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






24. An informal solicitation of proposals from vendors.






25. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






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






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






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






29. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






30. The product capabilities or things the product must do for its users.






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






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






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






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






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






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






37. A stakeholder who provides products or services to an organization.






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






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






40. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






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






43. Software developed and sold for a particular market.






44. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






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






46. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






47. A data element with a specified data type that describes information associated with a concept or entity.






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






49. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






50. A description of the requirements management process.