{"title":"基于云的ERP解决方案中的代码可重用性","authors":"I. Orosz, T. Orosz","doi":"10.1109/INES.2017.8118554","DOIUrl":null,"url":null,"abstract":"Cloud based technology created a new software abstraction layer above the implementation layers in and therefore changed the way how Enterprise Resource Planning (ERP) systems are developed and implemented over the hardware abstraction layers. The traditional release-by-release update methodology governed by main version change (from pre-alpha to gold release) was changed to a continuous release management. Within the cloud based Software as a Service (SaaS) model, the core business logic is implied above the physical implementation layer. This scenario can predict that the software product can have a longer lifetime, because it is segregated from the always changing physical implementation layer. As the sudden change of technology is present in nowadays IT architecture, the presence of this new abstraction layer seems logical, because the basic business processes are not changing this rapidly. The SaaS type life cycle management means that the heavily technology independent part are not describing the business processes anymore. Previous lifecycle implementations from the assessment phase to the post go-live and support phase dealt the business logic as one entity with its implementation. That means, that the question of code reusability has a different role as in the standard on premise model. This paper introduces a new method of encapsulating and identifying the software parts, which can be later reused in a cloud SaaS environment.","PeriodicalId":344933,"journal":{"name":"2017 IEEE 21st International Conference on Intelligent Engineering Systems (INES)","volume":"87 ","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2017-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":"{\"title\":\"Code reusability in cloud based ERP solutions\",\"authors\":\"I. Orosz, T. Orosz\",\"doi\":\"10.1109/INES.2017.8118554\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Cloud based technology created a new software abstraction layer above the implementation layers in and therefore changed the way how Enterprise Resource Planning (ERP) systems are developed and implemented over the hardware abstraction layers. The traditional release-by-release update methodology governed by main version change (from pre-alpha to gold release) was changed to a continuous release management. Within the cloud based Software as a Service (SaaS) model, the core business logic is implied above the physical implementation layer. This scenario can predict that the software product can have a longer lifetime, because it is segregated from the always changing physical implementation layer. As the sudden change of technology is present in nowadays IT architecture, the presence of this new abstraction layer seems logical, because the basic business processes are not changing this rapidly. The SaaS type life cycle management means that the heavily technology independent part are not describing the business processes anymore. Previous lifecycle implementations from the assessment phase to the post go-live and support phase dealt the business logic as one entity with its implementation. That means, that the question of code reusability has a different role as in the standard on premise model. This paper introduces a new method of encapsulating and identifying the software parts, which can be later reused in a cloud SaaS environment.\",\"PeriodicalId\":344933,\"journal\":{\"name\":\"2017 IEEE 21st International Conference on Intelligent Engineering Systems (INES)\",\"volume\":\"87 \",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2017-10-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"2\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2017 IEEE 21st International Conference on Intelligent Engineering Systems (INES)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/INES.2017.8118554\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2017 IEEE 21st International Conference on Intelligent Engineering Systems (INES)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/INES.2017.8118554","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Cloud based technology created a new software abstraction layer above the implementation layers in and therefore changed the way how Enterprise Resource Planning (ERP) systems are developed and implemented over the hardware abstraction layers. The traditional release-by-release update methodology governed by main version change (from pre-alpha to gold release) was changed to a continuous release management. Within the cloud based Software as a Service (SaaS) model, the core business logic is implied above the physical implementation layer. This scenario can predict that the software product can have a longer lifetime, because it is segregated from the always changing physical implementation layer. As the sudden change of technology is present in nowadays IT architecture, the presence of this new abstraction layer seems logical, because the basic business processes are not changing this rapidly. The SaaS type life cycle management means that the heavily technology independent part are not describing the business processes anymore. Previous lifecycle implementations from the assessment phase to the post go-live and support phase dealt the business logic as one entity with its implementation. That means, that the question of code reusability has a different role as in the standard on premise model. This paper introduces a new method of encapsulating and identifying the software parts, which can be later reused in a cloud SaaS environment.