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. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






2. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






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






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






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






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






7. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






8. Influencing factors that are believed to be true but have not been confirmed to be accurate.






9. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






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






12. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






13. Any unique and verifiable work product or service that a party has agreed to deliver.






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






15. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






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






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






18. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






19. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






20. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






21. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






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






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






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






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






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






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






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






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






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






31. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






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






33. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






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






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






37. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






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






40. The degree to which a set of inherent characteristics fulfills requirements.






41. A non-actionable directive that supports a business goal.






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






43. An analysis model that shows user interface dialogs arranged as hierarchies.






44. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






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






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






48. Software developed and sold for a particular market.






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






50. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).