Test your basic knowledge |

  • 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. All materials used by groups within an organization to define tailor implement and maintain their processes.

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

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

4. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.

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

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

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

8. A stakeholder who provides products or services to an organization.

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

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

11. The set of capabilities a solution must deliver in order to meet the business need.

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

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

14. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s

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

16. A state or condition the business must satisfy to reach its vision.

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

18. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.

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

20. The human and nonhuman roles that interact with the system.

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

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

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

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

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. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.

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

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

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

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

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

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

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

34. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.

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

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

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

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

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

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

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

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

43. A document or collection of notes or diagrams used by the business analyst during the requirements development process.

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

45. A shared boundary between any two persons and/or systems through which information is communicated.

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

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

48. An analysis model that shows user interface dialogs arranged as hierarchies.

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

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.