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 specific actionable testable directive that is under the control of the business and supports a business policy.






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






3. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






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






6. Something that occurs to which an organizational unit system or process must respond.






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






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






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






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






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






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






13. A stakeholder person device or system that directly or indirectly accesses a system.






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






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






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






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






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






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






20. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






21. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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






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






24. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






25. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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 real or virtual facility where all information on a specific topic is stored and is available for retrieval.






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






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






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






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






32. Metadata related to a requirement used to assist with requirements development and management.






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






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






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






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






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






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






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






40. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






42. A link between two elements or objects in a diagram.






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






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






45. A prototype developed to explore or verify requirements.






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






47. A unit of work performed as part of an initiative or process.






48. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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






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