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 structured examination of an identified problem to understand the underlying causes.

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

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

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

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

6. A group or person who has interests that may be affected by an initiative or influence over it.

7. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.

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

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

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

11. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.

12. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.

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

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

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

16. The set of processes templates and activities that will be used to perform business analysis in a specific context.

17. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.

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

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. A system trigger that is initiated by humans.

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

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

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

24. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme

25. The area covered by a particular activity or topic of interest.

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

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

28. A specific actionable testable directive that is under the control of the business and supports a business policy.

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

30. A prototype developed to explore or verify requirements.

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

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

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

34. An informal solicitation of proposals from vendors.

35. A measure of the profitability of a project or investment.

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. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.

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

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

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

41. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.

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

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

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

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

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

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

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

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

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