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 system of programming statements symbols and rules used to represent instructions to a computer.






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






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






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






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






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






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






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






9. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






11. A prototype that dives into the details of the interface functionality or both.






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






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






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






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






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






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






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






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






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






21. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






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






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






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






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






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






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






29. Something that occurs to which an organizational unit system or process must respond.






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






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






32. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






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






34. The problem area undergoing analysis.






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






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






37. A description of the requirements management process.






38. An analysis model that illustrates the architecture of the system's user interface.






39. The work that must be performed to deliver a product service or result with the specified features and functions.






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






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






42. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






43. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






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






45. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






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






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






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