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 set of capabilities a solution must deliver in order to meet the business need.






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






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






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






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






6. Information that is used to understand the context and validity of information recorded in a system.






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






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






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






10. A set of requirements grouped together in a document or presentation for communication to stakeholders.






11. The number of employees a manger is directly (or indirectly) responsible for.






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






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






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






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






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






17. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






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






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






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






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






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






24. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






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






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






27. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






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






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






30. The features and functions that characterize a product service or result.






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






32. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






33. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






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






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






37. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






39. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






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






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






43. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






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






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






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






47. A prototype developed to explore or verify requirements.






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






49. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






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