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. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






3. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






4. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






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






6. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






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






9. A stakeholder who provides products or services to an organization.






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






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






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






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






14. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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






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






18. Information that is used to understand the context and validity of information recorded in a system.






19. A non-actionable directive that supports a business goal.






20. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






22. Software developed and sold for a particular market.






23. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






24. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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






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






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






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






29. Something that occurs to which an organizational unit system or process must respond.






30. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






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






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






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






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






35. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






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






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






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






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






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






41. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






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






44. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






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






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






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






50. A system trigger that is initiated by humans.