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 comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






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






3. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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






5. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






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






8. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






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






11. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






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






13. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






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






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






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






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






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






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






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






23. An informal solicitation of proposals from vendors.






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






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






26. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






27. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






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






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






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






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






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






33. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






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






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






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






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






39. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






41. A temporary endeavor undertaken to create a unique product service or result.






42. Software developed and sold for a particular market.






43. An actor who participates in but does not initiate a use case.






44. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






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






46. The product capabilities or things the product must do for its users.






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






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






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






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