Automatic Identification of Software System Differences
IEEE Transactions on Software Engineering
Software engineering (6th ed.)
Software engineering (6th ed.)
Software Engineering: A Practitioner's Approach
Software Engineering: A Practitioner's Approach
Oops! Coping with Human Error in IT Systems
Queue - System Failures
Benchmarking the Customer Configuration Updating Practices of Product Software Vendors
ICCBSS '08 Proceedings of the Seventh International Conference on Composition-Based Software Systems (ICCBSS 2008)
ICIW '08 Proceedings of the 2008 Third International Conference on Internet and Web Applications and Services
ACM SIGSOFT Software Engineering Notes
Why are software projects moving from centralized to decentralized version control systems?
CHASE '09 Proceedings of the 2009 ICSE Workshop on Cooperative and Human Aspects on Software Engineering
Hi-index | 0.00 |
Large scale Enterprise Information Systems and Enterprise Resource Planning style applications present significant costs and issues during upgrades and as a consequence can lead user organisations to defer potential upgrades. An objective of our meta-data EIS application framework is to significantly reduce these concerns to make new EIS features more redaily available. Our meta-data EIS applications model framework seeks to minimise the majority of these upgrade issues by standardising all update procedures to become an updated stream of sequential meta-data changes, rather than compiled code modules. A key attribute of this update process is the embedded support for Variant Logic, any non code-based changes to the core application logic that may have been added by third parties, analogous to customisations. Logic collision detection is greatly simplified as any potential conflict can be fully identified in advance, reducing any compatibility effort for the Variant Logic. This automated update process also removes the need from vendors to produce version specific update programs, and fully automates the end user's meta-data EIS application update processes. We show that this process combined with the metadata model methodology can support close to an order of magnitude of lifecycle cost savings through successive software generations.