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 analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






2. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






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






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






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






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






7. The degree to which a set of inherent characteristics fulfills requirements.






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






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






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






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






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






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






14. A system of programming statements symbols and rules used to represent instructions to a computer.






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






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






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






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






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






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






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






22. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






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






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






26. An analysis model that illustrates the architecture of the system's user interface.






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






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






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






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






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






32. A solution or component of a solution that is the result of a project.






33. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






34. An analysis model that shows user interface dialogs arranged as hierarchies.






35. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






36. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






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






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






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






40. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






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






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






44. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






46. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






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






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






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