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. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






3. An informal solicitation of proposals from vendors.






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






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






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






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






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






9. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






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






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






13. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






15. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






16. A prototype that is continuously modified and updated in response to feedback from users.






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






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






19. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






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






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






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






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






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






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






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






27. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






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






30. The problem area undergoing analysis.






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






32. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






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






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






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






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






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






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






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






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






41. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






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






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






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






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






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






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






50. A stakeholder with legal or governance authority over the solution or the process used to develop it.