On Tue, Nov 16, 2004 at 11:45:59AM -0700, Andy Carver wrote:
> I've never modeled this before, but hey, so what? With ORM any domain is
> doable!

Thanks for taking on the challenge.


> I'd say first that we must be clear on what the scope of this model is:
> Is it, as I'd suppose, the configuration options for only one instance
> (installation) of only one software product?

Yes, you are correct. I'm not managing configuration for multiple
installations, computers, etc.


> If so, I'd guess we're just saying something like
> "ConfigurationOption(Code) has global- OptionSetting(Code)" and
> "ConfigurationOption(Code) for Person(Id) has OptionSetting(Code)".
> There may be subtleties involved that I've not realized, but for the
> scope I've assumed, this seems the basic information needed.

OK, that makes sense. So to write this out as a conceptual schema would
look something like the following:

Reference schemes: ConfigurationOption(Code), OptionSetting(Code), Person(Id)
Base fact types: F1 ConfigurationOption has OptionSetting
F2 ConfigurationOption for Person has OptionSetting
Constraints: C1
Derivation Rules: none


Next I'm going to need to allow some of the ConfigurationOption's to be
only set globally. I've tried to specify that in the following
conceptual schema. Does it make sense?

Reference schemes: OptionSetting(Code), SettingLevel(Code)
Base fact types: F1 OptionSetting has setting
F2 OptionSetting has SettingLevel
Constraints: C1
Derivation Rules: none

Reference schemes: SettingLevel(Code)
Base fact types: F1 SettingLevel has level
Constraints: C1
Derivation Rules: none


Do you use conceptual schemas when defining elementray facts in step 1
of CDSP? Or do you just write out the facts? I find that I have to put
some effort into thinking in higher level abstractions like Person
instead of User/Administrator/Customer/Agent. Is this typical for
newcomers to ORM?


Thanks,
William

--
Knowmad Services Inc.
http://www.knowmad.com