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 graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.

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

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

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

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

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

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

8. Interfaces with other systems (hardware software and human) that a proposed system will interact with.

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

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

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

12. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.

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

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

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

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

17. Any recognized association of people in the context of an organization or enterprise.

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

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

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

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

22. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.

23. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.

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

25. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.

26. A system of programming statements symbols and rules used to represent instructions to a computer.

27. The number of employees a manger is directly (or indirectly) responsible for.

28. A model that defines the boundaries of a business domain or solution.

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

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

31. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.

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

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

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

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

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

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

39. Information that is used to understand the context and validity of information recorded in a system.

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

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

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

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

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

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

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

47. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.

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

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

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