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. Information that is used to understand the context and validity of information recorded in a system.






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






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






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






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






7. Work carried out or on behalf of others.






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






9. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






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






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






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






14. Formal approval of a set of requirements by a sponsor or other decision maker.






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






17. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






18. A structured examination of an identified problem to understand the underlying causes.






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






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






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






22. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






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






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






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






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






27. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






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






30. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






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






32. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






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






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






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






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






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






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






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






40. The problem area undergoing analysis.






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






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






43. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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






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






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






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






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






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






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