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. The features and functions that characterize a product service or result.






2. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






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






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






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






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






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






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






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






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






11. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






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






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






15. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






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






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






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






19. A partial or preliminary version of the system.






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






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






22. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






23. A shared boundary between any two persons and/or systems through which information is communicated.






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






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. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






27. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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






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






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






31. A fixed period of time to accomplish a desired outcome.






32. A prototype developed to explore or verify requirements.






33. A unit of work performed as part of an initiative or process.






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






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






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






37. A system of programming statements symbols and rules used to represent instructions to a computer.






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






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






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






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






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






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






44. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






45. A system trigger that is initiated by time.






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






47. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






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






50. Influencing factors that are believed to be true but have not been confirmed to be accurate.