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






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






3. An analysis model showing the life cycle of a data entity or class.






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






5. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






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






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






9. An analysis model describing the data structures and attributes needed by the system.






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






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






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






13. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






14. A structured examination of an identified problem to understand the underlying causes.






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






16. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






17. An informal solicitation of proposals from vendors.






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






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






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






21. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






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






24. A state or condition the business must satisfy to reach its vision.






25. The work that must be performed to deliver a product service or result with the specified features and functions.






26. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






28. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






29. The set of capabilities a solution must deliver in order to meet the business need.






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






31. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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






33. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






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






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






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






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






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






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






40. A prototype that is continuously modified and updated in response to feedback from users.






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






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






43. A group or person who has interests that may be affected by an initiative or influence over it.






44. A description of the requirements management process.






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






46. Work carried out or on behalf of others.






47. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






49. The process of examining new business opportunities to improve organizational performance.






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