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






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. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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. A non-actionable directive that supports a business goal.






6. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






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






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






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






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






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






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






14. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






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






16. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






17. Metadata related to a requirement used to assist with requirements development and management.






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






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






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






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






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






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






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






25. The number of employees a manger is directly (or indirectly) responsible for.






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






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






28. A description of the requirements management process.






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






30. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






32. A model that defines the boundaries of a business domain or solution.






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






34. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






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






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






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






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






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






40. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






41. A system trigger that is initiated by time.






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






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






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






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






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






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






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






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






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