Capability (C088):— representing_task_structure Date: 2007/06/22 12:22:11
Revision: 1.6
CoverContentsIntro.Overview Info. modelIssues

Issue raised against: representing_task_structure

OTHER issues

Open issue Issue: TJT-1 by Tim Turner (05-11-19) major_technical issue
Resolution: Accept. Status: open

This capability refers to entities and attributes of the DIS model and not the current (IS) model. It needs to be brought upto IS level asap. For example, Task_state_relationship, task result etc.. are no longer in the model.

Open issue Issue: NN-1 by Nigel Newling (05-11-17) editorial issue
Resolution: Accept. Status: open

Figures 7-9 missing.

Open issue Issue: NN-2 by Nigel Newling (05-11-17) minor_technical issue
Resolution: Accept. Status: open

Capability referencing_product_breakdown_element should be a link.

Open issue Issue: NN-3 by Nigel Newling (05-11-17) minor_technical issue
Resolution: Accept. Status: open

Reference data classes should be links where possible to standard reference data.

Open issue Issue: NN-4 by Nigel Newling (05-11-17) minor_technical issue
Resolution: Accept. Status: open

Require a reference data section.

Open issue Issue: NN-5 by Nigel Newling (05-11-17) minor_technical issue
Resolution: Accept. Status: open

Make entity names mixed case to be consistent with other capabilities e.g. Task_method not TASK_METHOD and links.

Open issue Issue: NN-6 by Nigel Newling (05-11-17) minor_technical issue
Resolution: Accept. Status: open

Empty entity list.

OTHER issues

Closed issue Issue: TJT-2 by Tim Turner (05-11-19) minor_technical issue
Resolution: Accept. Status: closed

The relationship between this (C088) and Task_Structure (C015) should be clarified urgently - should one be removed?
Comment: (Sean Barker 2007-03-19)
C015 was renames as Representing Task, and covers the basic capability for describing a task. This capability describes an exension to that capability.

Closed issue Issue: TJT-3 by Tim Turner (05-11-19) minor_technical issue
Resolution: Accept. Status: closed

The complexity of this capability would suggest that it would benefit from a number of templates to be defined. However, it might also be worth subdividing the capability.
Comment: (Sean Barker 2007-03-19)
No useful templates have been identified. Breaking the capability into capabilities for different types of structure would not be helpful,