That that is is. That that is not is not.

Semantics라는 것은 참 중요하다.

사람이 살아가면서, 눈에 보이는 것만 보고, 자신이 아는 한도내에서 해석하려고 한다.

하지만 조금만 더 깊이 들여다보면 더 많은 것을 볼 수 있다.

지금 하고 있는 일이 Feature Model의 semantics와 관련된 것들이다.

관우선배와 같이 이야기를 해가면서 많이 배우고 있는데, 정말 내공이 많으신 것을 몸소 느끼고 있고 학술적으로 참 깊이가 있으신 분이라 생각이 든다.

보지 못한 것들은 본래의 semantics를 파악하려고 노력해보면 어느정도 더 따라갈 수 있는 것 같다.

그런 면에서 나는 그동안 syntax에만 너무 치중해 있었던 것 같기도 하고...

Semantics라는 것도 informal하게 쓰여진 글귀나 설명, 혹은 정형화된 형태의 문구라 할 지라도 정말로 내재된 의미를 생각해보고 심지어는 느낄 수 있어야 할 것 같다.

이올린에 북마크하기

Feature Binding Analysis for Product Line Component Development
- Jaejoon Lee and Kyo C. Kang

-       Feature binding information drives product line component design.

-       In the paper, an approach was introduced to analyzing feature binding from the three perspectives and that how the analysis result can be used to develop components for a product line was illustrated.

1.1.  Feature binding can be examined from three perspectives

1.1.1.      What features are bound (feature binding units)

-       Feature binding unit (FBU)

u  A set of features that are related to each other via composed-of, generalization/specialization, and implemented-by relationship and composition rules in a feature model.

u  Features that belong to a same binding unit work for a common service and, therefore, they have to exist together for correct operation of the service.

1)     FBU identification starts with identification of independently configurable service features.

2)     To function properly a FBU can include other features which are used with the service feature.

u  These sets are the units of commonality and variability

1.1.2.      When features are bound (feature binding time)

-       Binding state of a FBU

1)     Asset development time

A.     Some FBUs may be developed and included in product line assets at asset development time.

2)     Installation time

A.     Some FBUs’ availability can be determined at installation time by enabling or disabling the feature binding units.

1)     Inclusion

A.     When, in the product lifecycle phases, a FBU is physically included in a product.

2)     Availability

A.     When, in the product lifecycle phases, those included FBUs become available to users.

B.      Once the FBU becomes available, it is now ready to be activated, as long as it abides by the activation rules among FBUs.

                                                          i.         Activation rules provide information on concurrency of FBU activation and they are defined in terms of mutual exclusion, dependency, and priority schemes.

-       To prevent from a feature interaction problem, feature binding time analysis with additional view on feature binding state provides a more precise framework for feature binding analysis.

-       Product lifecycle view

1)     Asset development

2)     Product development

3)     Pre-operation

4)     Operation

-       Binding states

-       Feature delivery method

u  One of the major drivers for binding time decision

u  It is determined during market analysis

1.1.3.      How features are bound (feature binding techniques)

1.2.  Product line component development

1.2.1.      Variation point identification

-       To manage variation points for a binding unit consistently, explicit mapping between binding units and variation points should be established.

-       The FBU dependency is preserved in the object model.

1.2.2.      Feature binding technique exploration

-       Selection of binding techniques depends both on binding time and quality attributes required for products.

u  Delaying binding time to a later phase of the lifecycle may provide more flexibility, but applicable implementation techniques are limited and they usually require more performance overheads.

1)     Inclusion

A.     To control feature inclusion by including or excluding code segments or components from products.

                                                            i.         Code generation / Pre-processing / Macro processing / ICD (Internet Component Download)

B.      Allow products to include multiple features physically but their availability can be determined at a later phase.

2)     Availability

A.     For enabling or disabling accesses to features.

                                                            i.         Load tables / Authentication based access control

1.2.3.      Component specification

-       Components and relationships among them.

-       For the product development time inclusion

u  Macro language

-       For the pre-operation time availability

u  Load table

-       To handle the feature activation rules

u  Define a policy or policies

이올린에 북마크하기