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. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.

2. The problem area undergoing analysis.

3. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.

4. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin

5. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.

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

7. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.

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

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

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

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

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

13. A practitioner of business analysis.

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

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

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

17. A stakeholder with legal or governance authority over the solution or the process used to develop it.

18. Software developed and sold for a particular market.

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

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

21. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.

22. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various

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

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

25. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.

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

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

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

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

30. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project

31. A partial or preliminary version of the system.

32. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.

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

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

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

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

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

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

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

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

41. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.

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

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

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

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

46. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.

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

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

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

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