[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: DOCBOOK-APPS: Manage project documents with docbook
Hello, That reminds me I had written a Project Management DTD inspired from projectManageSchema. It was intended to be used as a file format for MrProject (http://mrproject.codefactory.se/) but has not been used so far. Here it is if it can be of any use to someone. Camille. Eric.Belpaire@equant.com a écrit : > > Nancy, > > this makes sense. Your answer triggered a search that produced the > following. > http://xml.coverpages.org/projectManageSchema.html > I'll have to look into it. > > Eric > ________________________________________________________________________________________ > > >From "Nancy (Paisner) Harrison" <nancyh@rational.com> on 22 March 2002 > 18'21'03 > To : Eric.Belpaire@equant.com, docbook-apps@lists.oasis-open.org > Subject : Re: DOCBOOK-APPS: Manage project documents with docbook > > Hi, > > I can think of a number of information types (e.g. 'effort' defined in > hours/days/weeks to do a task) that would be needed in a project mgmt or > requirements mgmt DTD, which would be out of place in the kind of technical > document that DocBook was designed for. I can also think of lots of > elements they would have in common, and lots of DocBook that (IMHO) would > be completely irrelevant to project management > > The first step would be to analyze the subject area and come up with the > information types you'd need. If your goal is easy tranferral of data > between the project management space and the technical document space, you > need to know what you need for each, and then see where the overlaps and > uniqueness lie. The analysis for 'what you need' has already been done in > the tech doc space, and the result is DocBook. It sounds from your > question that the analysis hasn't been done in the project mgmt space, but > since I've heard from various sources the idea that project mgmt data needs > to be stored in XML, it presumably needs to be done. Only once it's been > done can you start looking at where information can be reused across > spaces. > > A thought, are any of the OASIS TCs working on this area? [There are so > many of them that anything seems possible...] > > Nancy > > "It is up to us to journey forth in search of new practices and new ideas > that will enable us to create lives and organizations worthy of human > habitation." Margaret Wheatley
<!-- ...................................................................... --> <!-- ProjectXChange XML DTD V0.0.2 ........................................ --> <!-- File projectxchange.dtd .............................................. --> <!-- ...................................................................... --> <!-- Copyright 2001 Camille Bégnis This DTD is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA --> <!-- ...................................................................... --> <!-- This is the driver file for V0.01 of the ProjectXChange DTD. Please use the following formal public identifier to identify it: "-//CodeFactory//DTD ProjectXChange XML V0.0.2//EN" --> <!-- ...................................................................... --> <!-- This DTD is designed to store the data used by project management software. It is expecially structured in the hope that it will be useful to various open-source project management tools. If you have any comment or suggestion, please contact the current maintainer of the DTD at camille<at>mandrakesoft.com In its current state the XML structre can hold basic information about three different entities: budgets, tasks, and ressources (human, material and equipment). It also allow basic relationships between those three entities allowing the processor to manage money, time, human and physical ressources. --> <!-- ...................................................................... --> <!-- The root element, project --> <!ELEMENT project (name,description?,owners,budgets,tasks,resourcepools)> <!ATTLIST project projectid CDATA #REQUIRED> <!ELEMENT owners (owner*)> <!ELEMENT owner EMPTY> <!ATTLIST owner resourceid CDATA #REQUIRED> <!ELEMENT budgets (budget*)> <!ELEMENT budget (name?,(budgetlabor|budgetmaterial|budgetequipment|budgetother)+)> <!ATTLIST budget budgetid CDATA #REQUIRED> <!ELEMENT budgetlabor (costs)> <!ATTLIST budgetlabor budgetlaborid CDATA #REQUIRED> <!ATTLIST budgetlabor resourcename CDATA #IMPLIED> <!ELEMENT budgetmaterial (costs)> <!ATTLIST budgetmaterial budgetmaterialid CDATA #REQUIRED> <!ATTLIST budgetmaterial description CDATA #IMPLIED> <!-- One can fix the budget for a material either by fixing a quantity and cost per unit or total cost --> <!ELEMENT budgetequipment (costs)> <!ATTLIST budgetequipment budgetequipmentid CDATA #REQUIRED> <!ATTLIST budgetequipment description CDATA #IMPLIED> <!-- One can fix the budget for equipment either by fixing a quantity and cost per time unit (rate) or total cost --> <!-- The budgetother element holds information about other fixed cost expenses --> <!ELEMENT budgetother (costs)> <!ATTLIST budgetother budgetotherid CDATA #REQUIRED> <!ATTLIST budgetother description CDATA #IMPLIED> <!ELEMENT tasks (task*)> <!ELEMENT task (name?,period,relation*,(tasklabor|taskmaterial|taskequipment|taskother)*,task*)> <!ATTLIST task taskid CDATA #REQUIRED> <!ATTLIST task priority CDATA #IMPLIED> <!ATTLIST task percentcomplete CDATA #IMPLIED> <!ATTLIST task milestone CDATA #IMPLIED> <!ELEMENT period (start,finish)> <!ELEMENT start (#PCDATA)> <!ELEMENT finish (#PCDATA)> <!ELEMENT relation EMPTY> <!ATTLIST relation taskid CDATA #REQUIRED> <!ATTLIST relation type (finish2start | finish2finish | start2start) "finish2start"> <!-- A same task can consume different resources of different types: --> <!-- Human resources first: --> <!ELEMENT tasklabor (costs?)> <!ATTLIST tasklabor tasklaborid CDATA #IMPLIED> <!ATTLIST tasklabor resourceid IDREF #REQUIRED> <!ATTLIST tasklabor budgetlaborid CDATA #IMPLIED> <!-- and material: --> <!ELEMENT taskmaterial (costs?)> <!ATTLIST taskmaterial taskmaterialid CDATA #IMPLIED> <!ATTLIST taskmaterial resourceid CDATA #REQUIRED> <!ATTLIST taskmaterial budgetmaterialid IDREF #IMPLIED> <!-- and also equipment: --> <!ELEMENT taskequipment (costs?)> <!ATTLIST taskequipment taskequipmentid CDATA #IMPLIED> <!ATTLIST taskequipment resourceid CDATA #REQUIRED> <!ATTLIST taskequipment budgetequipmentid IDREF #IMPLIED> <!-- and finally other fixed cost resources: --> <!ELEMENT taskother (name?,description?,costs?)> <!ATTLIST taskother taskotherid CDATA #IMPLIED> <!ATTLIST taskother completed CDATA #IMPLIED> <!ATTLIST taskother budgeotherid CDATA #IMPLIED> <!ELEMENT resourcepools ((peoplepool|materialpool|equipmentpool)*)> <!ELEMENT peoplepool (name,description?,person+)> <!ATTLIST peoplepool peoplepoolid CDATA #IMPLIED> <!ELEMENT person (firstname?,lastname?,emailaddress?,costs?)> <!ATTLIST person resourceid ID #REQUIRED> <!ELEMENT firstname (#PCDATA)> <!ELEMENT lastname (#PCDATA)> <!ELEMENT emailaddress (#PCDATA)> <!ELEMENT materialpool (name,material+)> <!ATTLIST materialpool materialpoolid CDATA #IMPLIED> <!ELEMENT material (name,description?,costs?)> <!ATTLIST material resourceid ID #REQUIRED> <!ATTLIST material quantity CDATA #IMPLIED> <!ELEMENT equipmentpool (name,equipment+)> <!ATTLIST equipmentpool equipmentpoolid CDATA #IMPLIED> <!ELEMENT equipment (name,description?,costs?)> <!ATTLIST equipment resourceid ID #REQUIRED> <!-- General elements --> <!ELEMENT name (#PCDATA)> <!ELEMENT description (#PCDATA)> <!ELEMENT costs (work?,rate?,unitcost?,quantity?,cost?)> <!ELEMENT work (#PCDATA)> <!ATTLIST work unit CDATA #IMPLIED> <!ELEMENT rate (#PCDATA)> <!ATTLIST rate unit CDATA #IMPLIED> <!ELEMENT unitcost (#PCDATA)> <!ATTLIST unitcost unit CDATA #IMPLIED> <!ELEMENT cost (#PCDATA)> <!ATTLIST cost unit CDATA #IMPLIED> <!ELEMENT quantity (#PCDATA)> <!ATTLIST quantity unit CDATA #IMPLIED>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC