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 software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






2. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






4. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






5. Formal approval of a set of requirements by a sponsor or other decision maker.






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






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






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






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






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






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






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






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






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






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






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






17. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






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






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






21. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






22. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






24. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






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






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






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






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






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






31. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






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






34. A unit of work performed as part of an initiative or process.






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






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






37. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






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






41. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






42. A practitioner of business analysis.






43. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






46. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






47. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






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






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






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