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 uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






2. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






4. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






6. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






7. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






8. Metadata related to a requirement used to assist with requirements development and management.






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






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






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






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






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






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






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






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






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






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






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






20. An informal solicitation of proposals from vendors.






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






22. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






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






25. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






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






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






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






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






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






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






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






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






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






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






36. Any effort undertaken with a defined goal or objective.






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






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






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






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






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






42. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






43. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






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






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






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






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






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






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






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