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






2. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






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






6. The features and functions that characterize a product service or result.






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






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






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






10. Software developed and sold for a particular market.






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






12. A group of related tasks that support a key function of business analysis.






13. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






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






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






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






17. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






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






19. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






21. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






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






24. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






26. An assessment of the costs and benefits associated with a proposed initiative.






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






28. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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






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






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






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






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






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






35. An informal solicitation of proposals from vendors.






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






37. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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. The problem area undergoing analysis.






40. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






42. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






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






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






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






46. A unit of work performed as part of an initiative or process.






47. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






48. The area covered by a particular activity or topic of interest.






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






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