![]() |
![]() ![]()
Experimental Physics and
| ||||||||||||||||
|
Hi Stéphane, Thanks a lot for your detailed explanations! I know some of the tools (we're even using a few of them), but there were a lot of new ideas and pointers. Cool! My interest in this case, however, is really focused on obsolescence management. Completely off-line, no running system needed. We will have 170 separate EPICS applications and need to decide where to start our maintenance: updating OS version, updating EPICS Base, updating Device Supports, re-writing user-supplied code. What I'm searching for is between simple record counts and static code analysis, for an EPICS application. Intermediate metrics could be things like
And then some magic formulas that spit out some size, complexity and quality indices for each of the applications and - obviously - the number of man-months needed to bring them up to the "current" standard (whatever that is). There will always be a lot of manually collected data, factors based on experience, and additional personal judgment necessary in such a planning process, that's very clear. But I would like to get as much data as possible out of the applications themselves. To help the judgment and allow better comparison between applications. Base things on data. Cheers, ~Ralph
| ||||||||||||||||
ANJ, 04 Mar 2024 |
![]() · Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |