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 stakeholder who provides products or services to an organization.






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






3. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






5. Work carried out or on behalf of others.






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






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






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






9. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






10. A prototype that dives into the details of the interface functionality or both.






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






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






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






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






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






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






17. An analysis model showing the life cycle of a data entity or class.






18. A system trigger that is initiated by humans.






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






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






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






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






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






24. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






25. A description of the requirements management process.






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






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






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






29. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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






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






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






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






34. A partial or preliminary version of the system.






35. A prototype developed to explore or verify requirements.






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






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






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






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






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






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






42. Any unique and verifiable work product or service that a party has agreed to deliver.






43. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






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






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






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






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






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






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