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. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






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






4. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






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






7. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






8. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






10. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






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






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






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






15. A practitioner of business analysis.






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






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






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






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






20. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






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. A prototype that is continuously modified and updated in response to feedback from users.






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






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






25. A partial or preliminary version of the system.






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






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






28. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






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






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






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






33. An analysis model describing the data structures and attributes needed by the system.






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






35. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






36. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






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






39. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






41. Any recognized association of people in the context of an organization or enterprise.






42. A shared boundary between any two persons and/or systems through which information is communicated.






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






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






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






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






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






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






49. A system trigger that is initiated by time.






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