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






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






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






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






5. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






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






8. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






9. A description of the requirements management process.






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






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






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






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






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






15. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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






17. A prototype developed to explore or verify requirements.






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






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






20. A non-actionable directive that supports a business goal.






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






22. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






23. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






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






25. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






26. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






28. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






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






30. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






31. A practitioner of business analysis.






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






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






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






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






36. Limitations on the design of a solution that derive from the technology used in its implementation.






37. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






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






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






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






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






43. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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






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






47. An actor who participates in but does not initiate a use case.






48. The process of examining new business opportunities to improve organizational performance.






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






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