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 process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






2. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






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






4. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






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






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






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






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






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






10. A non-actionable directive that supports a business goal.






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






12. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






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






15. Software requirements that limit the options available to the system designer.






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






17. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






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






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






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






23. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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






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






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






28. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






30. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






31. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






32. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






33. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






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






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






36. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






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






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






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. The process of examining new business opportunities to improve organizational performance.






42. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






43. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






44. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






46. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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






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






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






50. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.