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 software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






2. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






4. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






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






7. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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






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






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






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






13. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






15. An analysis model showing the life cycle of a data entity or class.






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






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






18. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






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






21. The problem area undergoing analysis.






22. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






23. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






24. A link between two elements or objects in a diagram.






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






26. A description of the requirements management process.






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






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






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






30. A prototype developed to explore or verify requirements.






31. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






32. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






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






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






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






38. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






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






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






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






42. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






44. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






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






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






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






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






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