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 provides products or services to an organization.






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






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






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






5. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






6. A system trigger that is initiated by humans.






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






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






9. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






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






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






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






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






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






16. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






17. Any effort undertaken with a defined goal or objective.






18. Work carried out or on behalf of others.






19. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






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






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






22. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






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






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






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






26. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






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






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






30. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






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






33. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






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






35. A measure of the profitability of a project or investment.






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






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






38. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






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






40. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






41. A system trigger that is initiated by time.






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






43. The problem area undergoing analysis.






44. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






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






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






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






48. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






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