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






2. A measure of the profitability of a project or investment.






3. Any unique and verifiable work product or service that a party has agreed to deliver.






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






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






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






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






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






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






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






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






12. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






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






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






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






17. Metadata related to a requirement used to assist with requirements development and management.






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






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






20. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






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






23. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






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






26. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






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






29. A stakeholder person device or system that directly or indirectly accesses a system.






30. An analysis model that illustrates the architecture of the system's user interface.






31. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






32. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






33. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






36. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






38. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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






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






41. A stakeholder who provides products or services to an organization.






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






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






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






45. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






46. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






47. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






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






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






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