Parameters in function analysis

Let’s continue with the thoughts on function analysis … The third consideration arises from my post on domain-specific function analysis:

The requirement for a function was that “A parameter of the object must be modified or maintained”. So far, it has been said that a permitted function must satisfy three guidelines:

1. function carrier and object of the function must be allowed components (domain-specific restrictions from the component analysis must be observed).
2. the function carrier and the object of the function must interact with each other (domain-specific restrictions from the interaction analysis must be observed).
3. at least one parameter of the object of the function must be changed or maintained due to the function of the function carrier.

But what do we call a parameter here? Is it a feature, an attribute, a characteristic or a property?

I argue that we should assign properties and characteristics to the components, which can take on a certain value. In the case under consideration, the value of characteristics is unchangeable and properties are changeable. The properties are particularly important for the parameters in a function analysis, as they can be changed by the function:

For example, a car could have the characteristic “color” with the value “red” and a property “speed” with the value “50 km/h”. When creating a functional analysis in which the car is analyzed in its driving state, we can influence the speed and change it, but not the color.

In another analysis, e.g. of the car’s manufacturing process, the characteristic can become a property because the color can be changed here. The combination of property (e. g. color) and value (e. g. blue) therefore results in the parameter. This changes the value of a property based on a function. This is often referred to in simplified terms as changing the parameter.

When we talk about parameters in function analysis below, we are referring to the combination of a property that has assumed a certain value that can be influenced as part of the functional analysis.

This consideration is not new. In OTSM-TRIZ, this model is referred to as the ENV model. The abbreviation ENV stands for “Element – Name – Value”. The “element” therefore refers to the component, the “name” to the property and the “value” to the value. In the fractal OTSM ENV model, properties are assigned sub-properties if required. For example, the property “taste” of the component “tomato” can be subdivided into the properties “sweetness” and “saltiness“.

This would shed some light on the aspect of the parameter. However, there are similar inconsistencies with the concept of function, which I will address in another post.

 

Does the idea of distinguishing between characteristics and properties for components help you? Does it make sense to view the parameter as a property with a changeable value? What is your experience with this?