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 characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






3. Something that occurs to which an organizational unit system or process must respond.






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






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






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






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






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. An analysis model describing the data structures and attributes needed by the system.






10. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






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






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






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






14. A specific actionable testable directive that is under the control of the business and supports a business policy.






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






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






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






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






19. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






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






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






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






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






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






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






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






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






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






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






30. A prototype developed to explore or verify requirements.






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






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






33. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






35. Any effort undertaken with a defined goal or objective.






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






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






38. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






39. Work carried out or on behalf of others.






40. A description of the requirements management process.






41. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






42. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






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






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






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






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






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






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






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






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