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. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






4. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






5. Software requirements that limit the options available to the system designer.






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






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. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






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






10. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






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






14. A prototype that is continuously modified and updated in response to feedback from users.






15. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






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






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






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






20. An informal solicitation of proposals from vendors.






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






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






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






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






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






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






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






28. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






30. A prototype that dives into the details of the interface functionality or both.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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