Modification free extension of standard software

A. Selmeci, T. Orosz
{"title":"Modification free extension of standard software","authors":"A. Selmeci, T. Orosz","doi":"10.1109/SAMI.2014.6822403","DOIUrl":null,"url":null,"abstract":"In software development the companies create new versions to enhance the solution according to the market requirements and own ideas. On the other hand the ready to use products are not always stable and offer the promised features, so the software should corrected generating new builds and sub versions. These repaired features are delivered as patches or bundles (packages) to the customers. In case of office or home applications the patching or versioning not considers the customers' requirements, just apply the patches and keep or not the configuration. The integrated software, like an ERP solution has generally client/server architecture and is very complex not to consider the configurations. These solutions many times need customer side, project based extensions on different levels like database structure, data-model, functional model, programming, user interface, etc. These extensions should be kept and in some cases redesigned after applying patches or upgrading to new versions. Our paper gives direction how we can build into a software such capability to handle the sustainability and long-term maintenance.","PeriodicalId":441172,"journal":{"name":"2014 IEEE 12th International Symposium on Applied Machine Intelligence and Informatics (SAMI)","volume":"28 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2014-05-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2014 IEEE 12th International Symposium on Applied Machine Intelligence and Informatics (SAMI)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SAMI.2014.6822403","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 2

Abstract

In software development the companies create new versions to enhance the solution according to the market requirements and own ideas. On the other hand the ready to use products are not always stable and offer the promised features, so the software should corrected generating new builds and sub versions. These repaired features are delivered as patches or bundles (packages) to the customers. In case of office or home applications the patching or versioning not considers the customers' requirements, just apply the patches and keep or not the configuration. The integrated software, like an ERP solution has generally client/server architecture and is very complex not to consider the configurations. These solutions many times need customer side, project based extensions on different levels like database structure, data-model, functional model, programming, user interface, etc. These extensions should be kept and in some cases redesigned after applying patches or upgrading to new versions. Our paper gives direction how we can build into a software such capability to handle the sustainability and long-term maintenance.
修改和扩展标准软件
在软件开发中,公司根据市场需求和自己的想法创建新版本来增强解决方案。另一方面,准备使用的产品并不总是稳定的,并提供承诺的功能,因此软件应该纠正生成新的构建和子版本。这些修复的特性以补丁或包的形式交付给客户。在办公室或家庭应用程序的情况下,补丁或版本控制不考虑客户的需求,只是应用补丁和保持或不配置。集成软件,如ERP解决方案一般具有客户机/服务器架构,如果不考虑配置,则非常复杂。这些解决方案很多时候需要客户端、基于项目的不同层次的扩展,如数据库结构、数据模型、功能模型、编程、用户界面等。这些扩展应该保留,在某些情况下,在应用补丁或升级到新版本后应该重新设计。我们的论文给出了如何构建这样的软件来处理可持续性和长期维护的方向。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:604180095
Book学术官方微信