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. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






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






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






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






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






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






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






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






10. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






12. The set of capabilities a solution must deliver in order to meet the business need.






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






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






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






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






17. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






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






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






21. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






22. A stakeholder who uses products or services delivered by an organization.






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






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






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






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






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






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






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






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






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






32. A system trigger that is initiated by time.






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






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






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






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






37. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






39. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






40. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






41. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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






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






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






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






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






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






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






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






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