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






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






3. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






5. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






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






8. A partial or preliminary version of the system.






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






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






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






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






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






14. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






15. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






16. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






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






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






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






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






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






23. A measure of the profitability of a project or investment.






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






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






26. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






28. Ability of systems to communicate by exchanging data or services.






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






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






31. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






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






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






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






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






37. Software developed and sold for a particular market.






38. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






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






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






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






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






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






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






45. A practitioner of business analysis.






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






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






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






49. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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