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 structured examination of an identified problem to understand the underlying causes.






2. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






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






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






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






6. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






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






9. A link between two elements or objects in a diagram.






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






11. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






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






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






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






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






16. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






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






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






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






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






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






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






24. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






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






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






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






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






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






31. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






32. A description of the requirements management process.






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






34. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






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






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






38. A stakeholder person device or system that directly or indirectly accesses a system.






39. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






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






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






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






44. A partial or preliminary version of the system.






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






46. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






47. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






49. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






50. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.