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 measure of the profitability of a project or investment.






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






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






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






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






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






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






8. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






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






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






11. A prototype that is continuously modified and updated in response to feedback from users.






12. A function of an organization that enables it to achieve a business goal or objective.






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






14. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






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






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






17. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






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






20. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






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






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






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






25. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






26. Any effort undertaken with a defined goal or objective.






27. A partial or preliminary version of the system.






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






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






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






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






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






33. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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






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






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






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






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






39. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






42. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






44. The quality attributes design and implementation constraints and external interfaces that the product must have.






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






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






47. Metadata related to a requirement used to assist with requirements development and management.






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






49. A type of data model that depicts information groups as classes.






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







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