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 means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






3. A solution or component of a solution that is the result of a project.






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






5. The product capabilities or things the product must do for its users.






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






7. A prototype developed to explore or verify requirements.






8. The problem area undergoing analysis.






9. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






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






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






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






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






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






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






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






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






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






20. A description of the requirements management process.






21. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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 group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






24. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






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






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






27. A stakeholder with legal or governance authority over the solution or the process used to develop it.






28. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






29. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






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






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






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






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






34. A system trigger that is initiated by humans.






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






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






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






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






39. An analysis model showing the life cycle of a data entity or class.






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






41. The number of employees a manger is directly (or indirectly) responsible for.






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






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






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






45. A person with specific expertise in an area or domain under investigation.






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






47. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






48. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






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






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