[huhtenberg]

It's a solution in a search of the problem, I think.

If it's a poorly designed system, then the view will be a muddy web of connections. On the other hand, if it's a well designed system, it will be highly modular, with each module being small enough to be readily comprehensible in one go and with very few connections between the modules. So I basically don't see a use for the system that you are describing.

[xauronx]

Well, I think the muddy pool of connections is what this is a solution for. While I see it as practically impossible to implement, it would be great for huge legacy systems that grew rather than were designed. For instance, all of a sudden my patient certification table is getting weird records appearing in it. I would be able to find that table in this cloud, filter to connections to objects that have changed recently and individually inspect each one to see if it was the source of the problem.

The big problem is automating this to a degree that it's not a full time job to maintain.

[akkartik]

A weighing scale is a solution in search of a problem. Most people will do nothing, and the few that truly care will do so whether they have one or not. So I basically don't see a use for it.

---

If you believe that we improve what we measure then this can be useful.

[davidfm]

I deleted a line from my original post before submitting it which said it was a problem I wanted a solution for so that might make it worth persuing!

I like your suggestion that it should be highly modular, not sure what makes that mean its not useful though?

[tgrass]

I disagree.

If the objects are generalized enough, this could be applicable to any industry with complex, integrated procedures.