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






2. A person with specific expertise in an area or domain under investigation.






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






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






5. Work carried out or on behalf of others.






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






7. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






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






9. An assessment of the costs and benefits associated with a proposed initiative.






10. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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 graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






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






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






16. A prototype that is continuously modified and updated in response to feedback from users.






17. An analysis model that illustrates the architecture of the system's user interface.






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






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






20. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






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






23. A system trigger that is initiated by time.






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






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






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






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






28. The process of examining new business opportunities to improve organizational performance.






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






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






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






32. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






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






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






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






36. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






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






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






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






42. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






43. A description of the requirements management process.






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






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






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






47. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






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






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