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. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






3. A shared boundary between any two persons and/or systems through which information is communicated.






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






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






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






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






8. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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






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






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






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






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






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






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






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






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






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






19. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






21. A data element with a specified data type that describes information associated with a concept or entity.






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






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






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






26. An actor who participates in but does not initiate a use case.






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






28. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






29. A function of an organization that enables it to achieve a business goal or objective.






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






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






32. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






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






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






36. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






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






38. A system trigger that is initiated by humans.






39. A stakeholder person device or system that directly or indirectly accesses a system.






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






41. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






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






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. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






45. A system trigger that is initiated by time.






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






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






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






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






50. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.