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 problem area undergoing analysis.






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






3. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






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






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






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






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. Limitations on the design of a solution that derive from the technology used in its implementation.






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






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






11. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






13. A group or person who has interests that may be affected by an initiative or influence over it.






14. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






16. A structured examination of an identified problem to understand the underlying causes.






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






18. Software developed and sold for a particular market.






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






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






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






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






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






24. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






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






27. A partial or preliminary version of the system.






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






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






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






31. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






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






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






34. An informal solicitation of proposals from vendors.






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






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






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






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






39. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






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






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






42. A unit of work performed as part of an initiative or process.






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






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






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






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






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






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






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






50. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.