View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003963 | CaseTalk Modeler | Other | public | 2023-05-21 09:09 | 2023-10-25 10:05 |
| Reporter | Marco Wobben | Assigned To | Marco Wobben | ||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Platform | Intel | OS | Windows | OS Version | 11 |
| Target Version | Future | ||||
| Summary | 0003963: Order OTFT by 'Assembly' | ||||
| Description | After reading the article about how time is an object, perhaps a ordering of OTFT's according to their 'Assembly' (complexity+copycount) as an indication of organizational memory, is a good thing. It can serve as a measurement how well integrated it might be, and how hard to change in the organization. A copycount is an indicator of how much it evolved (count the number of version increments of it in the server). A complexity count indicates whether it is a low tech (single label) or a high tech (part of a complex expression, and many used-by). The overall assembly measure is an indicator of how far back it goes in time, and how well the 'memory' of it exists in an organization. The assembly (or memory) could therefor be a measure of impact, and risk to change. | ||||
| Tags | No tags attached. | ||||
| CaseTalk Edition | unknown | ||||
 |
OTFTs come with crud indicators for user and timestamps, perhaps it should also contain a copycounter for every copy or update happening. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-05-21 09:09 | Marco Wobben | New Issue | |
| 2023-05-21 09:09 | Marco Wobben | Status | new => assigned |
| 2023-05-21 09:09 | Marco Wobben | Assigned To | => Marco Wobben |
| 2023-05-21 09:11 | Marco Wobben | Note Added: 0004844 | |
| 2023-10-25 10:05 | Marco Wobben | Target Version | 13.0.1 => Future |
