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






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






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






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






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






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






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






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






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






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






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






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. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






14. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






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






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






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






18. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






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






20. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






22. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






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






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






26. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






27. The set of capabilities a solution must deliver in order to meet the business need.






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






29. Software developed and sold for a particular market.






30. The problem area undergoing analysis.






31. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






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






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






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






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






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






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






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






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






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






42. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






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






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






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






48. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






50. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.