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






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






3. A prototype developed to explore or verify requirements.






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






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






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






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






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






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






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






11. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






13. A system trigger that is initiated by time.






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






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






16. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






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






19. A use case composed of a common set of steps used by multiple use cases.






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






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






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






23. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






24. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






27. A description of the requirements management process.






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






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






30. Work carried out or on behalf of others.






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






32. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






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






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






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






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






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






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






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






41. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






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






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






44. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






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 brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






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






49. A practitioner of business analysis.






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