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 solution or component of a solution that is the result of a project.






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






3. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






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






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






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






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






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






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






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






12. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






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






14. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






15. A practitioner of business analysis.






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






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






18. The problem area undergoing analysis.






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






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






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






22. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






23. Formal approval of a set of requirements by a sponsor or other decision maker.






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






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






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






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






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






29. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






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






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






32. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






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






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






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






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






37. A partial or preliminary version of the system.






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






39. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






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






42. The degree to which a set of inherent characteristics fulfills requirements.






43. A system trigger that is initiated by humans.






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






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






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






47. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






48. A state or condition the business must satisfy to reach its vision.






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






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