{"id":5089,"date":"2015-01-08T07:00:53","date_gmt":"2015-01-08T15:00:53","guid":{"rendered":"http:\/\/formtek.com\/blog\/?p=5089"},"modified":"2014-12-02T15:51:07","modified_gmt":"2014-12-02T23:51:07","slug":"resilient-programming-where-will-your-app-be-in-ten-years","status":"publish","type":"post","link":"https:\/\/formtek.com\/blog\/resilient-programming-where-will-your-app-be-in-ten-years\/","title":{"rendered":"Resilient Software Design: Where Will Your App be in Ten Years?"},"content":{"rendered":"

Technology changes. \u00a0Very quickly. \u00a0Can your software keep up?<\/p>\n

Will that modern streamlined app you created today still be as cool next year? \u00a0Probably not. \u00a0Technology is continually changing in a way that in turn causes you to see things \u00a0from a different perspective.<\/p>\n

Peter Schroer<\/a>,\u00a0CEO of Open Source PLM software vendor Aras, asked <\/a>“what does it mean to have a resilient design for a software system that will be running 40 years from now?… \u00a0You can’t have a short timeframe. You’ve got to be thinking about phases all the way to the end.” \u00a0 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.”<\/p>\n

“Resilient PLM” is a term introduced by Aras software in 2013. \u00a0But the concept of resiliency can be extended to any software application, framework, platform or project.<\/p>\n

Schroer outlined three characteristics that need to be designed into software\u00a0that’s intended to endure for\u00a0years:<\/p>\n