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 analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






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






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






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






5. A prototype developed to explore or verify requirements.






6. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






7. A description of the requirements management process.






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






9. Something that occurs to which an organizational unit system or process must respond.






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






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






12. The problem area undergoing analysis.






13. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






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






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






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






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






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






20. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






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






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






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






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






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. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






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






28. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






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






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






31. A system trigger that is initiated by time.






32. Software developed and sold for a particular market.






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






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






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






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






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






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






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






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






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






42. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






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






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






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






47. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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






50. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.