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 business benefits that will result from meeting the business need and the end state desired by stakeholders.






2. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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






6. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






8. A prototype developed to explore or verify requirements.






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






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






11. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






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






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






14. Work carried out or on behalf of others.






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






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






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






18. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






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






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






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






23. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






24. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






25. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






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






27. A group of related tasks that support a key function of business analysis.






28. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






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






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






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






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






33. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






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






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






36. A system trigger that is initiated by humans.






37. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






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






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






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






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






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






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






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






47. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






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






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






50. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.







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