Pub Date : 1999-03-07DOI: 10.1109/ECBS.1999.755865
G. Karsai
Model interpreters play an essential role in model integrated systems: they transform domain-specific models into executable models. The state-of-the-art of model interpreter writing needs to be advanced to enhance the reusability and maintainability of this software. This paper presents an approach which makes this possible through the use of structured specifications. These specifications let the programmer express traversal strategies and visitation actions in very high-level terms. From these specifications efficient traversal code can be automatically generated.
{"title":"Structured specification of model interpreters","authors":"G. Karsai","doi":"10.1109/ECBS.1999.755865","DOIUrl":"https://doi.org/10.1109/ECBS.1999.755865","url":null,"abstract":"Model interpreters play an essential role in model integrated systems: they transform domain-specific models into executable models. The state-of-the-art of model interpreter writing needs to be advanced to enhance the reusability and maintainability of this software. This paper presents an approach which makes this possible through the use of structured specifications. These specifications let the programmer express traversal strategies and visitation actions in very high-level terms. From these specifications efficient traversal code can be automatically generated.","PeriodicalId":229109,"journal":{"name":"Proceedings ECBS'99. IEEE Conference and Workshop on Engineering of Computer-Based Systems","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-03-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132509963","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1999-03-07DOI: 10.1109/ECBS.1999.755868
N. Bogunovic
Distributed systems are essential for many real world applications. The paper presents an experimental programming model that enables visual configuration, deployment and control of data flow based collaborative systems, a class of distributed applications (DA). The programming model solves the problem of interoperability among DA functional components through the introduction of a fast middleware network software layer and by implementing a transparent message based communication between processes executing on machines connected by a local area network. At the next higher level, the programming model allows deployment and interconnection of encapsulated modules by logical composition of the entire collaborative application. The project differs widely from the existing systems in the network communication overhead, and the user interface design.
{"title":"A programming model for composing data-flow collaborative applications","authors":"N. Bogunovic","doi":"10.1109/ECBS.1999.755868","DOIUrl":"https://doi.org/10.1109/ECBS.1999.755868","url":null,"abstract":"Distributed systems are essential for many real world applications. The paper presents an experimental programming model that enables visual configuration, deployment and control of data flow based collaborative systems, a class of distributed applications (DA). The programming model solves the problem of interoperability among DA functional components through the introduction of a fast middleware network software layer and by implementing a transparent message based communication between processes executing on machines connected by a local area network. At the next higher level, the programming model allows deployment and interconnection of encapsulated modules by logical composition of the entire collaborative application. The project differs widely from the existing systems in the network communication overhead, and the user interface design.","PeriodicalId":229109,"journal":{"name":"Proceedings ECBS'99. IEEE Conference and Workshop on Engineering of Computer-Based Systems","volume":"79 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-03-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134361663","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1999-03-07DOI: 10.1109/ECBS.1999.755893
D. Dalcher
This paper investigates the underlying flaws in the development of the LAS despatch system and compares it with similar attempts from across the globe. The common themes that seem to plague ambulance despatch systems are investigated and put into context and a set of recommendations and lessons is proposed. The question of professionalism and ethics stands out and leads to the recognition of the value of failure analysis in the context of information systems development. Failure it is argued provides a great learning opportunity that may lead, when recognised, to enhanced professionalism and future success.
{"title":"Lessons for the future: safety critical systems","authors":"D. Dalcher","doi":"10.1109/ECBS.1999.755893","DOIUrl":"https://doi.org/10.1109/ECBS.1999.755893","url":null,"abstract":"This paper investigates the underlying flaws in the development of the LAS despatch system and compares it with similar attempts from across the globe. The common themes that seem to plague ambulance despatch systems are investigated and put into context and a set of recommendations and lessons is proposed. The question of professionalism and ethics stands out and leads to the recognition of the value of failure analysis in the context of information systems development. Failure it is argued provides a great learning opportunity that may lead, when recognised, to enhanced professionalism and future success.","PeriodicalId":229109,"journal":{"name":"Proceedings ECBS'99. IEEE Conference and Workshop on Engineering of Computer-Based Systems","volume":"23 3","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-03-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120912876","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1999-03-07DOI: 10.1109/ECBS.1999.755861
E. Long, A. Misra, J. Sztipanovits
Manufacturing Execution Systems (MESs) are those systems that exist between the plant floor and the business systems of the front office. There is work in progress to support this application space but tends to become impeded by the complexity of the dynamics of the plant. Model-Integrated Computing (MIC) is a software/system integration technology that provides the ability to build IS solutions to complex problems at low cost. The MIC approach and the MGA tools have been applied to the domain of constraint management in Saturn Manufacturing via the research, development, and deployment of Saturn Site Production Flow (SSPF). Constraint management involves identifying bottlenecks in the manufacturing process and then focusing plant resources on removing that bottleneck (constraint) which in turn provides an improved throughput for the plant. Through the use of SSPF in conjunction with strong business processes, 10% throughput improvement in Saturn plants has been achieved. General Motors (GM) is under going a globalization process that involves the use of common processes and systems throughout the whole corporation. To achieve globalization will involve rapid consistent deployment along with business process understanding and attendant training. To understand the magnitude of this problem one must understand that all these 400 plants have, to some degree, different processes, systems, and plant cultures. There is some degree of common (which is strategic) and some degree of difference (which represents the degree of local practice). These differences must be taken into account in achieving a common set of processes, practices, and systems although the focus is to support and deploy the common strategic business practices. In this paper we will discuss how MIC could be used to address these issues.
制造执行系统(MESs)是存在于工厂车间和前台业务系统之间的系统。支持这一应用空间的工作正在进行中，但往往受到植物动态复杂性的阻碍。模型集成计算(MIC)是一种软件/系统集成技术，它提供了以低成本构建复杂问题的is解决方案的能力。MIC方法和MGA工具已经通过研究、开发和部署Saturn Site Production Flow (SSPF)应用于Saturn Manufacturing的约束管理领域。约束管理包括识别制造过程中的瓶颈，然后将工厂资源集中在消除该瓶颈(约束)上，从而提高工厂的吞吐量。通过将SSPF与强大的业务流程结合使用，土星工厂的吞吐量提高了10%。通用汽车公司(GM)正在进行全球化进程，这涉及到在整个公司使用共同的流程和系统。实现全球化将涉及快速一致的部署，以及业务流程理解和随之而来的培训。要了解这个问题的严重性，就必须了解这400种植物在某种程度上都有不同的生长过程、系统和植物文化。有一定程度的共同点(这是战略性的)和一定程度的差异(这代表了当地实践的程度)。在实现一组通用的过程、实践和系统时，必须考虑到这些差异，尽管重点是支持和部署通用的战略业务实践。在本文中，我们将讨论如何使用MIC来解决这些问题。
{"title":"Application of model-integrated computing in manufacturing execution systems","authors":"E. Long, A. Misra, J. Sztipanovits","doi":"10.1109/ECBS.1999.755861","DOIUrl":"https://doi.org/10.1109/ECBS.1999.755861","url":null,"abstract":"Manufacturing Execution Systems (MESs) are those systems that exist between the plant floor and the business systems of the front office. There is work in progress to support this application space but tends to become impeded by the complexity of the dynamics of the plant. Model-Integrated Computing (MIC) is a software/system integration technology that provides the ability to build IS solutions to complex problems at low cost. The MIC approach and the MGA tools have been applied to the domain of constraint management in Saturn Manufacturing via the research, development, and deployment of Saturn Site Production Flow (SSPF). Constraint management involves identifying bottlenecks in the manufacturing process and then focusing plant resources on removing that bottleneck (constraint) which in turn provides an improved throughput for the plant. Through the use of SSPF in conjunction with strong business processes, 10% throughput improvement in Saturn plants has been achieved. General Motors (GM) is under going a globalization process that involves the use of common processes and systems throughout the whole corporation. To achieve globalization will involve rapid consistent deployment along with business process understanding and attendant training. To understand the magnitude of this problem one must understand that all these 400 plants have, to some degree, different processes, systems, and plant cultures. There is some degree of common (which is strategic) and some degree of difference (which represents the degree of local practice). These differences must be taken into account in achieving a common set of processes, practices, and systems although the focus is to support and deploy the common strategic business practices. In this paper we will discuss how MIC could be used to address these issues.","PeriodicalId":229109,"journal":{"name":"Proceedings ECBS'99. IEEE Conference and Workshop on Engineering of Computer-Based Systems","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-03-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114696241","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1999-03-07DOI: 10.1109/ECBS.1999.755859
J. Conrad, Mark Baldwin, Sean Curran, Larry Martin
This paper contains a case study of a code reuse project completed at Ericsson Inc. The product developed was a variation of three digital cordless telephone (DCT) products previously developed by Ericsson's Holland and Research Triangle Park laboratories. The new DCT product used designs and code from all three existing products. Engineers used the Ericsson software development process for this reuse project. This paper describes the product, processes, and experiences of team members.
{"title":"Using a new software product development process for a code reuse project","authors":"J. Conrad, Mark Baldwin, Sean Curran, Larry Martin","doi":"10.1109/ECBS.1999.755859","DOIUrl":"https://doi.org/10.1109/ECBS.1999.755859","url":null,"abstract":"This paper contains a case study of a code reuse project completed at Ericsson Inc. The product developed was a variation of three digital cordless telephone (DCT) products previously developed by Ericsson's Holland and Research Triangle Park laboratories. The new DCT product used designs and code from all three existing products. Engineers used the Ericsson software development process for this reuse project. This paper describes the product, processes, and experiences of team members.","PeriodicalId":229109,"journal":{"name":"Proceedings ECBS'99. IEEE Conference and Workshop on Engineering of Computer-Based Systems","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-03-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127246437","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1999-03-07DOI: 10.1109/ECBS.1999.755900
J. Z. Lavi, R. Gonzales, M. Mannion, M. Svéda
Many modern systems are controlled by Computer-Based Systems (CBS). Examples include commercial management information systems such as airline reservations, payroll information, stock central, and electronic banking systems, real-time embedded computer systems such as process control and computer integrated manufacturing systems, space systems, telephone and communications systems, transportation systems (automotive control, train control, ship control, traffic control), medical instruments, avionics systems, missile control systems, microcomputer controlled domestic appliances and point of sale systems. The CBS controlling these systems, typically consist of many networked geographically distributed subsystems. Each subsystem may be or may contain a multi-computer system. They are intensively dependent on software, and frequently depend on data communication networks, human-computer interaction, and special hardware. Engineers developing such systems have to work with CBS engineers responsible for the development of the supporting CBS. To be able to work with them they have to have a basic knowledge in the Engineering of CBS (ECBS). The paper describes the ECBS tasks to be undertaken by systems engineers during the development of systems they build, the CBS subjects they should understand and comprehend and the structure of the courses they should take to augment their knowledge. The proposed courses can be given as part of regular engineering undergraduate or graduate programs, or as training courses in industry. The proposed ECBS courses are being developed by the Education and Training Working Group of the IEEE Computer Society ECBS Technical Committee. The current version of the suggested courses is based on the results of the discussions of the working group during the ECBS98 conference in Jerusalem, and on work done during the past year by the group following ECBS98.
{"title":"Engineering of computer based-systems enhancement courses-proposed course outlines","authors":"J. Z. Lavi, R. Gonzales, M. Mannion, M. Svéda","doi":"10.1109/ECBS.1999.755900","DOIUrl":"https://doi.org/10.1109/ECBS.1999.755900","url":null,"abstract":"Many modern systems are controlled by Computer-Based Systems (CBS). Examples include commercial management information systems such as airline reservations, payroll information, stock central, and electronic banking systems, real-time embedded computer systems such as process control and computer integrated manufacturing systems, space systems, telephone and communications systems, transportation systems (automotive control, train control, ship control, traffic control), medical instruments, avionics systems, missile control systems, microcomputer controlled domestic appliances and point of sale systems. The CBS controlling these systems, typically consist of many networked geographically distributed subsystems. Each subsystem may be or may contain a multi-computer system. They are intensively dependent on software, and frequently depend on data communication networks, human-computer interaction, and special hardware. Engineers developing such systems have to work with CBS engineers responsible for the development of the supporting CBS. To be able to work with them they have to have a basic knowledge in the Engineering of CBS (ECBS). The paper describes the ECBS tasks to be undertaken by systems engineers during the development of systems they build, the CBS subjects they should understand and comprehend and the structure of the courses they should take to augment their knowledge. The proposed courses can be given as part of regular engineering undergraduate or graduate programs, or as training courses in industry. The proposed ECBS courses are being developed by the Education and Training Working Group of the IEEE Computer Society ECBS Technical Committee. The current version of the suggested courses is based on the results of the discussions of the working group during the ECBS98 conference in Jerusalem, and on work done during the past year by the group following ECBS98.","PeriodicalId":229109,"journal":{"name":"Proceedings ECBS'99. IEEE Conference and Workshop on Engineering of Computer-Based Systems","volume":"21 2","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-03-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"113976642","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1999-03-07DOI: 10.1109/ECBS.1999.755873
S. Deniziak, K. Sapiecha
A new technique for automatic generation of VHDL testbenches is presented. Testbenches are generated using stimuli description in the WEGA language (K. Sapiecha and S. Deniziak, 1996) and VHDL entity declaration of the model under test. This technique makes it possible to reduce the length and complexity of testbenches by the factor of 10, on average. Moreover, describing testbenches in WEGA is much easier and flexible than describing them directly in VHDL. The source WEGA code is also more readable.
{"title":"High level testbench generation for VHDL models","authors":"S. Deniziak, K. Sapiecha","doi":"10.1109/ECBS.1999.755873","DOIUrl":"https://doi.org/10.1109/ECBS.1999.755873","url":null,"abstract":"A new technique for automatic generation of VHDL testbenches is presented. Testbenches are generated using stimuli description in the WEGA language (K. Sapiecha and S. Deniziak, 1996) and VHDL entity declaration of the model under test. This technique makes it possible to reduce the length and complexity of testbenches by the factor of 10, on average. Moreover, describing testbenches in WEGA is much easier and flexible than describing them directly in VHDL. The source WEGA code is also more readable.","PeriodicalId":229109,"journal":{"name":"Proceedings ECBS'99. IEEE Conference and Workshop on Engineering of Computer-Based Systems","volume":"17 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-03-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122554406","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1999-03-07DOI: 10.1109/ECBS.1999.755864
R. Kampfner
Information is essential to the performance, control, and coordination of an organization's functions. Yet, although an increasingly broad variety of models is used for the analysis and evaluation of organizational processes and functions, their information-processing aspects are only rarely considered in these models. In this paper I present an approach to the abstraction and description of information-processing aspects of organizational functions. The descriptions so obtained can then be translated into simulation models that, interfaced with suitable models of the organizational functions they support; can be used for the design and analysis of organizational functions as well as for the development of their supporting information systems.
{"title":"Modeling the information-processing aspect of organizational functions","authors":"R. Kampfner","doi":"10.1109/ECBS.1999.755864","DOIUrl":"https://doi.org/10.1109/ECBS.1999.755864","url":null,"abstract":"Information is essential to the performance, control, and coordination of an organization's functions. Yet, although an increasingly broad variety of models is used for the analysis and evaluation of organizational processes and functions, their information-processing aspects are only rarely considered in these models. In this paper I present an approach to the abstraction and description of information-processing aspects of organizational functions. The descriptions so obtained can then be translated into simulation models that, interfaced with suitable models of the organizational functions they support; can be used for the design and analysis of organizational functions as well as for the development of their supporting information systems.","PeriodicalId":229109,"journal":{"name":"Proceedings ECBS'99. IEEE Conference and Workshop on Engineering of Computer-Based Systems","volume":"43 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-03-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128486624","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1999-03-07DOI: 10.1109/ECBS.1999.755879
B. Kanchanam, V. Sarma
This paper presents a methodology for selection of optimal software design parameters using the experimental design. When an organization is at the point of taking up a new project with an objective of improving the software quality, Taguchi method is applied for the software design process with an objective that not more than one error is found per software module. The strategy in robust design is to conduct off-line experiments using orthogonal arrays (OA) and to optimize the design by maximizing performance measures with respect to design parameters. Towards this a cause and effect diagram for design errors was drawn with opinions from customer, production, quality personnel and engineers. This diagram gave three most likely parameters as candidate for software design error, they are coupling, number of requirements per module and McCabe's cyclomatic complexity. It was planned to consider coupling parameter at two levels as low coupling at level 1 and high coupling at level 2, in case of number of requirements per module parameter three levels were considered they are one requirement per module at level 1, two requirements per module at level 2 and greater than two requirements per module as the level 3. In case of McCabe's complexity value<5 is set at level 1, value 5 to 10 is set at level 2 and value >10 is set at level 3. The possible number of factorial experiment required be conducted for levels selected for the three parameters is 18. The appropriate orthogonal array based on the guidelines of Taguchi is L/sub 9/ that is nine experiments need to be conducted to find the optimal software design parameters.
{"title":"Software quality enhancement through software process optimization using Taguchi methods","authors":"B. Kanchanam, V. Sarma","doi":"10.1109/ECBS.1999.755879","DOIUrl":"https://doi.org/10.1109/ECBS.1999.755879","url":null,"abstract":"This paper presents a methodology for selection of optimal software design parameters using the experimental design. When an organization is at the point of taking up a new project with an objective of improving the software quality, Taguchi method is applied for the software design process with an objective that not more than one error is found per software module. The strategy in robust design is to conduct off-line experiments using orthogonal arrays (OA) and to optimize the design by maximizing performance measures with respect to design parameters. Towards this a cause and effect diagram for design errors was drawn with opinions from customer, production, quality personnel and engineers. This diagram gave three most likely parameters as candidate for software design error, they are coupling, number of requirements per module and McCabe's cyclomatic complexity. It was planned to consider coupling parameter at two levels as low coupling at level 1 and high coupling at level 2, in case of number of requirements per module parameter three levels were considered they are one requirement per module at level 1, two requirements per module at level 2 and greater than two requirements per module as the level 3. In case of McCabe's complexity value<5 is set at level 1, value 5 to 10 is set at level 2 and value >10 is set at level 3. The possible number of factorial experiment required be conducted for levels selected for the three parameters is 18. The appropriate orthogonal array based on the guidelines of Taguchi is L/sub 9/ that is nine experiments need to be conducted to find the optimal software design parameters.","PeriodicalId":229109,"journal":{"name":"Proceedings ECBS'99. IEEE Conference and Workshop on Engineering of Computer-Based Systems","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-03-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116034497","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1999-03-07DOI: 10.1109/ECBS.1999.755863
G. Nordstrom, J. Sztipanovits, G. Karsai, Á. Lédeczi
Model integrated computing (MIC) is gaining increased attention as an effective and efficient method for developing, maintaining, and evolving large-scale, domain-specific software applications for computer-based systems. MIC is a model-based approach to software development, allowing the synthesis of application programs from models created using customized, domain-specific model integrated program synthesis (MIPS) environments. Until now, these MIPS environments have been handcrafted. Analysis has shown that it is possible to "model the modeling environment" by creating a metamodel that specifies both the syntactic and semantic behavior of the desired domain-specific MIPS environment (DSME). Such a metamodel could then be used to synthesize the DSME itself allowing the entire design environment to safely and efficiently evolve in the face of changing domain requirements. This paper discusses the use of the Unified Modeling Language and the Object Constraint Language to specify, such metamodels, and describes a method for incorporating these metamodels into the MultiGraph Architecture, a MIPS creation toolset.
{"title":"Metamodeling-rapid design and evolution of domain-specific modeling environments","authors":"G. Nordstrom, J. Sztipanovits, G. Karsai, Á. Lédeczi","doi":"10.1109/ECBS.1999.755863","DOIUrl":"https://doi.org/10.1109/ECBS.1999.755863","url":null,"abstract":"Model integrated computing (MIC) is gaining increased attention as an effective and efficient method for developing, maintaining, and evolving large-scale, domain-specific software applications for computer-based systems. MIC is a model-based approach to software development, allowing the synthesis of application programs from models created using customized, domain-specific model integrated program synthesis (MIPS) environments. Until now, these MIPS environments have been handcrafted. Analysis has shown that it is possible to \"model the modeling environment\" by creating a metamodel that specifies both the syntactic and semantic behavior of the desired domain-specific MIPS environment (DSME). Such a metamodel could then be used to synthesize the DSME itself allowing the entire design environment to safely and efficiently evolve in the face of changing domain requirements. This paper discusses the use of the Unified Modeling Language and the Object Constraint Language to specify, such metamodels, and describes a method for incorporating these metamodels into the MultiGraph Architecture, a MIPS creation toolset.","PeriodicalId":229109,"journal":{"name":"Proceedings ECBS'99. IEEE Conference and Workshop on Engineering of Computer-Based Systems","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-03-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127334126","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：