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. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






2. A partial or preliminary version of the system.






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






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






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






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






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






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. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






10. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






12. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






13. An informal solicitation of proposals from vendors.






14. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






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






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






18. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






20. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






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






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






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






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






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






27. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






29. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






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






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






33. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






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






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






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






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






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






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






40. A system trigger that is initiated by humans.






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






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






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






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






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






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






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






48. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






49. The product capabilities or things the product must do for its users.






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