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 set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.

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. Something that occurs to which an organizational unit system or process must respond.

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

5. A structured examination of an identified problem to understand the underlying causes.

6. A prototype that dives into the details of the interface functionality or both.

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

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

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

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

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

12. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.

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

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

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

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

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

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

19. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.

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

21. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.

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

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

24. An analysis model describing the data structures and attributes needed by the system.

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

26. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.

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

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

29. A description of the requirements management process.

30. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.

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

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

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

34. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.

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

36. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.

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

38. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.

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

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

41. A data element with a specified data type that describes information associated with a concept or entity.

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

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

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

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

46. Software requirements that limit the options available to the system designer.

47. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.

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

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

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