> I'm fairly clear on an approach for the bits other than the low level
> model to create network services out of individual devices and their
> connections. I think an ER type of approach would be general enough
> to solve the problem. What material should I be reading to get a
> better handle on this? :-)
Oh yes, one other vague "helpful" (hah!) comment:
As you have your m4/make layer figured out, try to figure out the
mathematical version of what it's doing. The set of problems that the
union of your m4/make layer has determines what you really require of
your low level model.
E/R is just another language of expressing the boundary between these
parts; it isn't the only way. You can always invent your own
language, and then invent means of mapping it onto established
languages like E/R. Doing it this way has the benefit of helping you
figure out what you're really asking of your low level layer, and just
what it is you lose when you try to fit it in a particular model that
wasn't designed to be more general at the cost of some sacrifice
(e.g. E/R).
Really, note how much of a market their is for object/relational
mapping products. A lot of people don't actually want to work in a
relational model, despite it having nice solutions to their problems.
It is more convenient to them to work in an object representation, and
have software work out the impedence matching.
References:
|
|
