[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Getting The Pizza (Was Processing 'my' XML (was Re: Why ModelConcepts?))
- From: Rick Jelliffe <firstname.lastname@example.org>
- To: XML DEV <email@example.com>
- Date: Thu, 15 Feb 2001 04:05:09 +0800
From: Bullard, Claude L (Len) <firstname.lastname@example.org>
>Why do we need to model concepts?
Is this just the classic software engineering debate about the value of
closer-to-executable requirements specs? Which comes down to whether we
capture and analyse requirements using a natural tool (conceptual modeling)
or a generic toolkit (UML) or with implementation tools (e.g. DTDs), which
probably makes the choice a function of the complexity and criticality.
Do we make a conceptual modeling language in which pizza concepts can be
expressed (cold, late, don't-let-boy-with-zits-deliver-pepperoni, etc) and
then transform it? Or do we use a generic toolkit which has generic tools?
Or do we try to shoehorn into the low-level implementation system? Why not
have all these options available and well supported?