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






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






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






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






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






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






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






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






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






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






11. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






12. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






13. An informal solicitation of proposals from vendors.






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






15. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






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






17. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






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






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






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






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 description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






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






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






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






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






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






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






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






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






32. A fixed period of time to accomplish a desired outcome.






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






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






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






36. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






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






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






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






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






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






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






44. The problem area undergoing analysis.






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






46. A system of programming statements symbols and rules used to represent instructions to a computer.






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






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






49. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






50. A target or metric that a person or organization seeks to meet in order to progress towards a goal.







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests