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 horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






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






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






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






5. A description of the requirements management process.






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






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






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






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






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






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






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






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






14. The quality attributes design and implementation constraints and external interfaces that the product must have.






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






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






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






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






19. Work carried out or on behalf of others.






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






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






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






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






24. A prototype developed to explore or verify requirements.






25. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






26. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






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






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






30. Ability of systems to communicate by exchanging data or services.






31. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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






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






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






35. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






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






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






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






39. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






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






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






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






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






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






45. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






46. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






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






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






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