[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[List Home]
|
Re: [featuremodel-dev] Variability
|
- From: Holger Papajewski <holger.papajewski@xxxxxxxxxxxxxxxx>
- Date: Thu, 21 Oct 2010 17:13:07 +0200
- Delivered-to: featuremodel-dev@eclipse.org
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
Hallo Andreas,
that is right. The reason is quit simple. The variability is defined by the semantic of
the group to which a feature belongs. A feature is an alternative feature because it is
part of a group of features from which exactly one feature has to be selected. The
variability method is only a shortcut and easier to understand:
feature.getVariabilityType() == ALTERNATIVE
vs.
feature.getParentGroup().getLower() == 1 && feature.getParentGroup().getUpper() == 1
Best regards,
Holger
Am 21.10.2010 16:57, schrieb Andreas Graf:
> Hello,
>
> ok, I see that the variability is actually reflected by the values of upper and lower in
> the parent group. Is there an information about the rationale behind this design?
>
> Thanks,
>
> Andreas
>
>
>> Hello,
>>
>> I was wondering why variability is reflected as a method in Feature, but not as an
>> attribute?
>>
>> Best Regards,
>>
>> Andreas
>>
>
>
--
Holger Papajewski
Phone: +49-391-54456920 Fax: +49-391-54456990
--
pure-systems GmbH
Geschäftsführung: Danilo Beuche, Holger Papajewski
Sitz der Gesellschaft: Magdeburg
Registergericht: Amtsgericht Magdeburg, HRB 13044