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. Formal approval of a set of requirements by a sponsor or other decision maker.






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






3. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






4. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






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






7. A description of the requirements management process.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






22. A group or person who has interests that may be affected by an initiative or influence over it.






23. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






24. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






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






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






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






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






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






31. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






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






35. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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






37. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






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






40. The number of employees a manger is directly (or indirectly) responsible for.






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






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






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






44. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






45. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






47. An analysis model showing the life cycle of a data entity or class.






48. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






50. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.