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 quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






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






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






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






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






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






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






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






10. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






11. A person with specific expertise in an area or domain under investigation.






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






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






14. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






15. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






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






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






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






20. A system trigger that is initiated by time.






21. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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






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






24. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






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






26. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






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






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






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






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






31. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






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. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






35. A measure of the profitability of a project or investment.






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






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






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






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






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






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






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






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






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






45. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






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






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






50. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.