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 model that defines the boundaries of a business domain or solution.






2. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






4. A partial or preliminary version of the system.






5. A prototype developed to explore or verify requirements.






6. A shared boundary between any two persons and/or systems through which information is communicated.






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






8. A stakeholder person device or system that directly or indirectly accesses a system.






9. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






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






12. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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






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






15. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






16. An analysis model describing the data structures and attributes needed by the system.






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






18. The set of capabilities a solution must deliver in order to meet the business need.






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






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






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






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






23. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






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






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






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






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






29. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






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






32. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






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






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






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






37. A description of the requirements management process.






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






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






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






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






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






43. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






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






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






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






49. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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