Read Aloud the Text Content

This audio was created by Woord's Text to Speech service by content creators from all around the world.

Text Content or SSML code:

task within (business analysis) is defined as A discrete piece of work that may be performed formally or informally as part of business analysis. Technique is A manner, method, or style for conducting a business analysis task or for shaping its output. temporal event is An event based on time that can trigger the initiation of a process, evaluation of business rules, or some other response. Tester is An individual responsible for determining how to verify that the solution meets the requirements defined by the business analyst, and conducting the verification process. Throwaway prototype is A prototype used to quickly uncover and clarify requirements or designs using simple tools, sometimes just paper and pencil. It is intended to be discarded when the final system has been developed. Timebox is An agreed-upon period of time in which an activity is conducted or a defined deliverable is intended to be produced. transition requirement is A requirement that describes the capabilities the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but which are not needed once the change is complete. They are differentiated from other requirements types because they are of a temporary nature. unified modelling language is A notation specified by the Object Management Group for describing software application structure, behavior, and architecture. It can also be used for describing business processes and data structures. The most common U M L diagrams used by business analysts are use case diagrams, activity diagrams, state machine diagrams (also known as state diagrams), and class diagrams. use case is A description of the observable interaction between an actor (or actors) and a solution that occurs when the actor uses the system to accomplish a specific goal. use case diagram is A type of diagram defined by U M L that captures all actors and use cases involved with a system or product. user acceptance test (or UAT) is Assessing whether the delivered solution meets the needs of the stakeholder group that will be using the solution. The assessment is validated against identified acceptance criteria. user story is A small, concise statement of functionality or quality needed to deliver value to a specific stakeholder. validation within (business analysis) is defined as The process of checking that a deliverable issuitable for its intended use. validated requirement is A requirement that has been reviewed and is determined to support the delivery of the expected benefits, and is within the solution scope. value within business analysis is defined as The worth, importance, or usefulness of something to a stakeholder in a context. value stream mapping is A complete, fact-based, time-series representation of the stream of activities required to deliver a product or service. verification within (business analysis) is defined as The process of determining that a deliverable or artifact meets an acceptable standard of quality. See also requirements verification. verified requirement is A requirement that has been reviewed and is determined to be defined correctly, adheres to standards or guidelines, and is at an acceptable level of detail. vertical prototype is A prototype that is used to drill down into a proposed solution to uncover requirement and design considerations through multiple layers of a solution that are not easily understood or that are not discernible on the surface. It may include interaction between several solution components. Viewpoint is A set of conventions that define how requirements will be represented, how these representations will be organized, and how they will be related. Walkthrough is A review in which participants step through an artifact or set of artifacts with the intention of validating the requirements or designs, and to identify requirements or design errors, inconsistencies, omissions, inaccuracies, or conflicts. work breakdown structure (or WBS) is A deliverable-oriented hierarchical decomposition of the work to be executed to accomplish objectives and create the required deliverables. It organizes and defines the total scope of the project. work product within business analysis is A document or collection of notes or diagrams used by the business analyst during the requirements development process. Workshop is A facilitated and focused event attended by key stakeholders for the purpose of achieving a defined goal.