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 stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






4. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






19. Limitations on the design of a solution that derive from the technology used in its implementation.






20. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






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






22. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






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






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






25. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






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






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






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






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






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






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






33. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






34. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






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






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






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






39. A fixed period of time to accomplish a desired outcome.






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






41. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






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






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






45. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






46. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






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






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






49. A system trigger that is initiated by humans.






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