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 data element with a specified data type that describes information associated with a concept or entity.






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






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






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






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






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






8. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






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






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






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






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






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






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






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






17. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






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






20. A prototype that is continuously modified and updated in response to feedback from users.






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






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






23. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






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






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






26. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






27. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






29. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






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






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






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






34. A system trigger that is initiated by humans.






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






36. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






38. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






39. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






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






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






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






43. A system trigger that is initiated by time.






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






45. A group of related tasks that support a key function of business analysis.






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






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






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






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






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