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 target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






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






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






6. A practitioner of business analysis.






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






8. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






9. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






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






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






14. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






15. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






16. Any recognized association of people in the context of an organization or enterprise.






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






18. The problem area undergoing analysis.






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






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






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






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






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






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






25. Software developed and sold for a particular market.






26. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






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






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






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






30. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






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






33. A stakeholder who uses products or services delivered by an organization.






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






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






36. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






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






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






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






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






42. A prototype that dives into the details of the interface functionality or both.






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






44. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






45. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






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






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






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






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