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. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






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






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






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






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






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






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






8. Metadata related to a requirement used to assist with requirements development and management.






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






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






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






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






13. The quality attributes design and implementation constraints and external interfaces that the product must have.






14. A group of related tasks that support a key function of business analysis.






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






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






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






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






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






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






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






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






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






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






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






26. A link between two elements or objects in a diagram.






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






28. A system trigger that is initiated by time.






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






30. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






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






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






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






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






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






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






38. An analysis model that illustrates the architecture of the system's user interface.






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






40. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






43. A stakeholder who provides products or services to an organization.






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






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






46. A stakeholder person device or system that directly or indirectly accesses a system.






47. Limitations on the design of a solution that derive from the technology used in its implementation.






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






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






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