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. Something that occurs to which an organizational unit system or process must respond.






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






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






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






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






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






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






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






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






10. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






12. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






13. A description of the requirements management process.






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






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






16. Any effort undertaken with a defined goal or objective.






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






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






19. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






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






21. A function of an organization that enables it to achieve a business goal or objective.






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






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






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






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. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






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






29. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






31. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






32. An analysis model describing the data structures and attributes needed by the system.






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






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






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






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






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






38. A group of related tasks that support a key function of business analysis.






39. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






40. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






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






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






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






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






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






46. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






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






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






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