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. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






4. A structured examination of an identified problem to understand the underlying causes.






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






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






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






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






9. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






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






12. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






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






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






15. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






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






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






18. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






19. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






20. A practitioner of business analysis.






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






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






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






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






25. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






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






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






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






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






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






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






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






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






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






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






37. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






38. A solution or component of a solution that is the result of a project.






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






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






41. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






42. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






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






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






46. A data element with a specified data type that describes information associated with a concept or entity.






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






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






49. A system of programming statements symbols and rules used to represent instructions to a computer.






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