Access and Feeds

Resilient Software Design: Where Will Your App be in Ten Years?

By Dick Weisinger

Technology changes.  Very quickly.  Can your software keep up?

Will that modern streamlined app you created today still be as cool next year?  Probably not.  Technology is continually changing in a way that in turn causes you to see things  from a different perspective.

Peter Schroer, CEO of Open Source PLM software vendor Aras, asked “what does it mean to have a resilient design for a software system that will be running 40 years from now?…  You can’t have a short timeframe. You’ve got to be thinking about phases all the way to the end.”   In the context of Product Lifecycle Management (PLM) software, Schroer said “You need to have a resilient PLM system. A truly resilient PLM that will last 20 years or more. In fact, it should last indefinitely.”

“Resilient PLM” is a term introduced by Aras software in 2013.  But the concept of resiliency can be extended to any software application, framework, platform or project.

Schroer outlined three characteristics that need to be designed into software that’s intended to endure for years:

  • Transparency – the meaning of data should be clear and understandable
  • Evolvable – avoid being platform-specific because Microsoft, Google, Oracle and other tool vendors today may not be around then
  • Adaptable – company processes are sure to change over the next decade

 

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

Leave a Reply

Your email address will not be published. Required fields are marked *

*