Test your basic knowledge |

Instructions:
  • 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 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).






2. Work carried out or on behalf of others.






3. A description of the requirements management process.






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






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






6. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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






8. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






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






10. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






11. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






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






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






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






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






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






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






20. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






21. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






22. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






24. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






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






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






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






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






29. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






31. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






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






34. The problem area undergoing analysis.






35. The process of examining new business opportunities to improve organizational performance.






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






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






38. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






40. Formal approval of a set of requirements by a sponsor or other decision maker.






41. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






42. Any unique and verifiable work product or service that a party has agreed to deliver.






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






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






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






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






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






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






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






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