View Issue Details

IDProjectCategoryView StatusLast Update
0003963CaseTalk ModelerOtherpublic2023-05-21 09:11
ReporterBCP Software Assigned ToBCP Software  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status assignedResolutionopen 
PlatformIntelOSWindowsOS Version11
Target Version13.x 
Summary0003963: Order OTFT by 'Assembly'
DescriptionAfter 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.
TagsNo tags attached.
CaseTalk Editionunknown


BCP Software

BCP Software

2023-05-21 09:11

administrator   ~0004844

OTFTs come with crud indicators for user and timestamps, perhaps it should also contain a copycounter for every copy or update happening.

Issue History

Date Modified Username Field Change
2023-05-21 09:09 BCP Software New Issue
2023-05-21 09:09 BCP Software Status new => assigned
2023-05-21 09:09 BCP Software Assigned To => BCP Software
2023-05-21 09:11 BCP Software Note Added: 0004844