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






2. A system trigger that is initiated by time.






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






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






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






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






7. A practitioner of business analysis.






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






9. A prototype developed to explore or verify requirements.






10. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






11. A specific actionable testable directive that is under the control of the business and supports a business policy.






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






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






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






15. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






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






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






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






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






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






21. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






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






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






24. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






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






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






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






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






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






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






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






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






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






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






35. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






36. Metadata related to a requirement used to assist with requirements development and management.






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






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






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






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






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






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






43. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






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






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






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






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






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






50. The human and nonhuman roles that interact with the system.