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. Any unique and verifiable work product or service that a party has agreed to deliver.






2. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






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






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






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






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






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






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






11. A state or condition the business must satisfy to reach its vision.






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






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






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






15. Software requirements that limit the options available to the system designer.






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






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






18. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






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






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






21. A model that defines the boundaries of a business domain or solution.






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






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






24. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






25. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






26. An analysis model describing the data structures and attributes needed by the system.






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






28. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






29. Work carried out or on behalf of others.






30. A partial or preliminary version of the system.






31. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






33. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






35. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






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






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






38. A structured examination of an identified problem to understand the underlying causes.






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






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






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






42. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






43. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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 showing the life cycle of a data entity or class.






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 stakeholder responsible for assessing the quality of and identifying defects in a software application.






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






49. A practitioner of business analysis.






50. A system trigger that is initiated by humans.