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






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






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






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






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






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






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






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






9. The problem area undergoing analysis.






10. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






12. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






13. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






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






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






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






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






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






19. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






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






23. A system trigger that is initiated by humans.






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






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






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






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






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






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






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






31. The human and nonhuman roles that interact with the system.






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






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






34. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






35. The features and functions that characterize a product service or result.






36. A prototype that dives into the details of the interface functionality or both.






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






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






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






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






41. A type of data model that depicts information groups as classes.






42. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






43. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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






46. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






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






48. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






49. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






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