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 graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






3. Work carried out or on behalf of others.






4. The work that must be performed to deliver a product service or result with the specified features and functions.






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






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






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






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






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






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






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






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. An assessment of the costs and benefits associated with a proposed initiative.






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






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






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






17. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






18. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






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






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






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






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






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






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






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






26. A practitioner of business analysis.






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






28. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






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






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






31. A partial or preliminary version of the system.






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






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






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. The degree to which a set of inherent characteristics fulfills requirements.






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






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






38. A use case composed of a common set of steps used by multiple use cases.






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






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






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






42. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






43. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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






45. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






47. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






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






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