|
On 2/15/14 5:25 PM, David Eddy wrote:
Kingsley -
On Feb 15, 2014, at 5:06 PM, Kingsley Idehen wrote:
Keeping the utility of the legacy system alive without
going down the futile "rip and replace" path.
That's most reasonable.
I'm in strong agreement that "rip & replace"—which
comes in many guises—while inherently appealing (of course I
want a new Ferrari) & is often disastrous.
All I've been trying to get out of you is the admission
you're interested in the data from systems, but not the
systems themselves.
An application (which you refer to as system) is comprised of data.
An application orchestrates data state transitions. The data that
drives the application is what I am interested in, not the
programming language runtime constrained (and confined) code.
I was hoping that as a long shot what you do might be
useful for coping with legacy systems.
What we do enable the continued use of legacy without making them
victims of futile "rip and replace" adventures.
I think we as an industry have proven beyond the shadow of
a doubt we can produce plenty of data. How we maintain legacy
systems going forward is a different challenge.
The systems (what I call applications) can be useful for much longer
if new generations of tools are provided with access to their data.
Remember, SOA (Service Oriented Architecture) and Web Services (SOAP
or those offering RESTful interaction patterns) all provide
mechanisms for exposing application (or system) functions,
procedures, and modules to external tools. That's how you plug
legacy software in lego-like fashion into new systems and
infrastructure.
For me a major issue is the looming departure of the SMEs
(subject matter experts).
They aren't going anywhere. The issue is that that need forums and
platforms that enable them participate in the broader discourse. As
I said in my prior post: today, the discourse is overly dominated by
the views of programmers and marketeers.
I was hoping there might be some useful tricks in your kit
bag, but I think we agree your focus & my focus are in
different ends of the spectrum.
I don't know that they are as misaligned as you assume. We work with
open standards based interfaces for enabling the incorporation of
new and emerging technologies with minimum disruption (if any) to
what exists. That's our fundamental reason for existence, at
OpenLink Software.
Kingsley
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
--
Regards,
Kingsley Idehen
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter Profile: https://twitter.com/kidehen
Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen
|
smime.p7s
Description: S/MIME Cryptographic Signature
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J (01)
|