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 work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






2. A type of data model that depicts information groups as classes.






3. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






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






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






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






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






9. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






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






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






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






13. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






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






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






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






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






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






20. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






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






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






24. Work carried out or on behalf of others.






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






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






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






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






29. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






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






31. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






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






33. Limitations on the design of a solution that derive from the technology used in its implementation.






34. A use case composed of a common set of steps used by multiple use cases.






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






36. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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






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






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






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






41. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






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






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






44. A stakeholder who provides products or services to an organization.






45. A system trigger that is initiated by time.






46. A system trigger that is initiated by humans.






47. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






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






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






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