How do we make a long life existing legacy application mobile? We define an applica-tion as legacy if it has one or more of the following characteristics: 1. The application has moved into the sustenance phase in the software develop-ment lifecycle. 2. An application, which cannot be modified. This could be due to unavailability of the original development platforms, unavailability of original source code or unavailability of expertise to make necessary changes. 3. Products and packaged software where enterprise does not have any control. This could be due to high cost of ownership for new upgrade or the vendor does not have any plan to support the new requirement. Let us assume that an enterprise has licensed an ERP system from an external vendor. The enterprise wants to offer a notification of yesterday's sales figures to some select executives at 9:30 AM everyday morning through SMS. The ERP vendor plans to offer similar function in their next release six months down the line. The license fee for the next upgrade will be very expensive. Another example is that a wireless network opera-tor wants to offer enterprise mails through its network. In all such cases the adaptation will be done without changing the base product. This requires a framework that attempts to perform most of the adaptation dynamically. Content and behavior management will be managed real-time through a behavior management middleware.
No comments:
Post a Comment