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






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






3. A temporary endeavor undertaken to create a unique product service or result.






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






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






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






7. A data element with a specified data type that describes information associated with a concept or entity.






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






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






10. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






11. A practitioner of business analysis.






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






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






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






15. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






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






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






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






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






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






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






22. A prototype developed to explore or verify requirements.






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






24. A system trigger that is initiated by time.






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






26. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






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






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






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






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






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






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






35. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






36. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






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






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






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






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






41. The human and nonhuman roles that interact with the system.






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






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






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






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






46. The area covered by a particular activity or topic of interest.






47. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






49. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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