mod/techproject/view/concepts/entitiesandunits: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[mod/techproject/view|Index]] | |||
== Project Entities == | |||
The Technical Project Manager module uses a unique representation to store descriptions of what makes a project : the ''autonumbering tree_shaped entity representation''. | |||
A description entity is a treeset of entries, each one able to be indefinitely divided into sub-entites. Thus requirements might be divided into sub-requirements, specifications into sub-specifications, tasks into sub-tasks and deliverable description into sub-deliverables down to a single ressource. | |||
The "Milestone" is the only one which is list-shaped. | |||
Entities are autonumbering i.e. it will renumber automatically entries using a hierarchical numeric numbering starting from 1 within each level. Numbering is uniform : | |||
* The sub-entry just following a level N entry WILL be at level N+1, and will be locally numbered starting from 1. | |||
* Numberings of successive entries within the same sub-branch will be in following order. | |||
Thus the tree : | |||
1, 1.1, 1.2, 1.2.1, 1.2.2, 1.3 | |||
is legal, conversely to such illegal tree : | |||
1, 1.1, 1.2, 1.2.1.1, 1.2.1.2 | |||
in which the subnode 1.2.1 is missing. | |||
[[fr:mod/techproject/view/concepts/entitiesandunits]] | [[fr:mod/techproject/view/concepts/entitiesandunits]] | ||
Revision as of 20:59, 10 May 2007
Project Entities
The Technical Project Manager module uses a unique representation to store descriptions of what makes a project : the autonumbering tree_shaped entity representation.
A description entity is a treeset of entries, each one able to be indefinitely divided into sub-entites. Thus requirements might be divided into sub-requirements, specifications into sub-specifications, tasks into sub-tasks and deliverable description into sub-deliverables down to a single ressource.
The "Milestone" is the only one which is list-shaped.
Entities are autonumbering i.e. it will renumber automatically entries using a hierarchical numeric numbering starting from 1 within each level. Numbering is uniform :
- The sub-entry just following a level N entry WILL be at level N+1, and will be locally numbered starting from 1.
- Numberings of successive entries within the same sub-branch will be in following order.
Thus the tree :
1, 1.1, 1.2, 1.2.1, 1.2.2, 1.3
is legal, conversely to such illegal tree :
1, 1.1, 1.2, 1.2.1.1, 1.2.1.2
in which the subnode 1.2.1 is missing.
