Posted By:
Angel_vantane
Posted On:
Wednesday, November 3, 2004 10:21 PM
I´ve been dwelling around an idea of marking up a document in such a way that "a set of requirements can be mapped on them". Lets say we have a document that establishes two requirements from a party named "Roger". The content of Roger.rqm is 1.-Parts must be moved with approved equipment 2.-Equipment must be assigned to trained personal. Now, other documents, let´s say "Procedure1.xml" among them, has somewhere (any place within the document) something that was typed by a change like this: When parts are washed, the supervisor John Doe will transport them with an electric
More>>
I´ve been dwelling around an idea
of marking up a document in such a way that "a set of
requirements can be mapped on them". Lets say we have a document
that establishes two requirements from a party named "Roger".
The content of Roger.rqm is
1.-Parts must be moved with approved equipment
2.-Equipment must be assigned to trained personal.
Now, other documents, let´s say
"Procedure1.xml" among them, has somewhere (any place
within the document) something that was typed by a change like this:
When parts are washed, the
supervisor John Doe will transport them with an electric wagon to the
next station (Paul Green is also allowed to do that), then unload
them to the self operated 12" belt.
Pete is in charge of figuring out if
Roger´s requirements are met. So he must open documents,
shadow a text region and double click on the correspondent Roger.rqm
requirement line among the ones in the listing that is conveniently
just beside the editing window. Pete repeat this until he feels
enough info has been marked, no hassle, no DTD, no XML stuff, EASY,
Isn´t it?.
Allow me to elavorate in the idea. Upon
a right click on requirement #1, An output window should report an
extraction of the previously marked sections on different *.xml files
within scope (1 to 4).
Roger.rqm
|
Req
1.- Parts must be moved with approved equipment
|
|
Electric
wagon
|
Roger.rqm
|
Req
1.- Parts must be moved with approved equipment
|
|
Self
operated 12" belt.
|
Roger.rqm
|
Req
1.- Parts must be moved with approved equipment
|
|
Electric
Crane.
|
Roger.rqm
|
Req
1.- Parts must be moved with approved equipment
|
|
Company
car
|
Roger.rqm
|
Req
1.- Parts must be moved with approved equipment
|
|
taxi
cab.
|
Roger.rqm
|
Req 1.- Parts must be moved with approved
equipment
|
|
|
A right click on requirement #2 should
output:
Roger.rqm
|
Req
2.-Equipment must be assigned to trained personal.
|
|
the
supervisor John Doe will transport them with an electric wagon
|
Roger.rqm
|
Req
2.-Equipment must be assigned to trained personal.
|
|
electric
wagon to the next station (Paul Green
|
Roger.rqm
|
Req
2.-Equipment must be assigned to trained personal.
|
|
self
operated 12" belt.
|
Roger.rqm
|
Req
2.-Equipment must be assigned to trained personal.
|
|
Electric
Crane handled by John Doe.
|
Roger.rqm
|
Req
2.-Equipment must be assigned to trained personal.
|
|
Mike
W will use the Company car
|
Roger.rqm
|
Req
2.-Equipment must be assigned to trained personal.
|
|
Bill
B have a choice of using a taxi cab to deliver an urgent PO.
|
By shading and right clicking on John
Doe, an output window should report
Roger.rqm
|
2.- Equipment must be assigned to trained
personal.
|
|
John Doe
will transport them with an
electric wagon
|
Paul.rqm
|
30.- Documents should identify middle to upper
management personnel involved in productive activities.
|
|
The supervisor
John Doe
|
Right clicking on a set of XML files or
RQM files should do the correspondent output but for the set.
Hiperlink to columns 2 and 4 can lead you easely to the section for
edition, or any other ideas. I will stop here with features
description.
NOW THE QUESTIONS
As you see, element tags are
overlapped,
Can the XML specification do that
(overlapped tags)?,
Can an editor do that or has its way
around that?
How a DTD or Schema should be for such
a loose format?,
Can an internet Browser behave such as
depicted or should it be a taylor made app?
Or perhaps , Does this idea is
worthwhile or is there a simpler implementation?
<<Less