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






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






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






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






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






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






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






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






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






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






11. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






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






14. A system trigger that is initiated by time.






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. A structured examination of an identified problem to understand the underlying causes.






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






18. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






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






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






21. A stakeholder who uses products or services delivered by an organization.






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






23. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






24. A partial or preliminary version of the system.






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






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






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






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






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






30. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






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






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






33. The problem area undergoing analysis.






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






35. Any unique and verifiable work product or service that a party has agreed to deliver.






36. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






38. Work carried out or on behalf of others.






39. An informal solicitation of proposals from vendors.






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






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






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






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






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






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






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






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






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






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






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