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 function of an organization that enables it to achieve a business goal or objective.






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






3. A partial or preliminary version of the system.






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






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






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






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






8. A measure of the profitability of a project or investment.






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






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






11. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






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






14. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






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






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






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






20. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






22. An informal solicitation of proposals from vendors.






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






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






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






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






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






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






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






30. The features and functions that characterize a product service or result.






31. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






32. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






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






35. The problem area undergoing analysis.






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






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






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






39. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






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






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






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






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






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






45. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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






47. A prototype that is continuously modified and updated in response to feedback from users.






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






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






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