SAVE International VMA Dumps

The diagram provided is a Function Analysis System Technique (FAST) diagram, a key tool in Value Methodology’s Function Analysis phase, as taught in the VMF 1 course. FAST diagrams map the relationships between functions of a system, showing “how” and “why” relationships to identify the critical logic path (the primary sequence of functions that achieve the system’s basic function) and minor logic paths (supporting functions). In FAST diagramming, functions are represented by boxes (e.g., G, H, J, K), and their relationships are shown with arrows.

Yis a red arrow connecting function G to function J, running horizontally across the diagram. In FAST diagrams, the horizontal path from left to right represents thecritical logic path, which answers the question “how” each function is achieved to fulfill the system’s primary purpose. Here, the path from E to F to G to J to L to M to N to O is the main sequence of functions, indicating the critical logic path.

Z(another red arrow) points to a vertical connection between J and K, which represents a minor logic path—supporting functions that occur simultaneously or are secondary to the main path.

Option A ("AND" Gate) and Option D ("OR" Gate) are incorrect because FAST diagrams use logic gates to show relationships between functions (e.g., AND for concurrent functions, OR for alternatives), but Y is an arrow on the main path, not a gate. Gates are typically symbols (e.g., triangles or diamonds) at junctions, not arrows.

Option B (Minor Logic Path) is incorrect because minor logic paths are vertical connections in FAST diagrams (e.g., Z pointing to J-K), not the horizontal path that Y indicates.

Option C (Critical Logic Path) is correct because Y lies on the main horizontal path, which represents the critical sequence of functions in a FAST diagram.

Value Methodology (VM) is a versatile methodology, as taught in the VMF 1 course (Core Competency #1: Value Methodology Overview). According to SAVE International’s Value Methodology Standard, “the unique aspect of the Value Methodology is its focus on function analysis, making it applicable to anything that performs a function—whether a product, process, system, or service.” VM’s core principle is to improve value (function/cost) by analyzing what something does (its functions) and finding better ways to achieve those functions at lower cost without sacrificing performance. This focus on functions (e.g., “mark surface” for a pen, Question 38; “contain liquid” for a teacup, Question 44) allows VM to be applied universally to anything with a definable function, distinguishing it from other methodologies like Lean or Six Sigma, which focus on process efficiency or quality.

Option A (includes an activity) is incorrect because, while activities describe how functions are performed, VM’s unique aspect is its focus on functions, not activities.

Option B (performs a function) is correct, as VM’s defining feature is its application to anything with a function, per SAVE International’s standards.

Option C (is goal-oriented) is incorrect because many methodologies are goal-oriented; VM’s uniqueness lies in its function-based approach.

Option D (is a subject of study) is incorrect because being a subject of study is too broad; VM specifically targets subjects that perform functions.

In Value Methodology’s Function Analysis, the concepts of functions and activities are distinct but related, as taught in the VMF 1 course (Core Competency #2: Function Analysis). According to SAVE International’s Value Methodology Standard, “a function is defined as what a product, process, or system does, expressed in a verb-noun format (e.g., ‘contain liquid’), while an activity is a task, action, or operation that describes how a function is performed.” For example, the function of a teacup might be “contain liquid,” and the activity to achieve that function could be “holding the liquid in a ceramic structure.” Activities are the actionable steps or processes that enable the function, often identified during the creation of a FAST diagram or Random Function Identification table (as noted in Question 19). The “how” aspect aligns with the How-Why logic of FAST diagrams, where activities detail the practical execution of a function.

Option A (A task, action, or operation that describes why a function is performed) is incorrect because “why” relates to the higher-order function or purpose (e.g., Question 20), not the activity, which focuses on “how.”

Option B (A specific task, action, or operation that is generic and changes viewpoints) is incorrect because activities are not about changing viewpoints; they are specific actions to perform a function.

Option C (A task, action, or operation that describes how a function is performed) is correct, as it aligns with the definition of an activity in VM.

Option D (A specific task, action, or operation with a high level of abstraction) is incorrect because activities are practical and specific, not abstract; functions are more abstract (e.g., verb-noun format).