Pub Date : 1900-01-01DOI: 10.4018/978-1-61692-874-2.ch005
S. Rose, M. Lauder, M. Schlereth, Andy Schürr
Mechatronic engineering is about integration of different engineering disciplines, mainly mechanical engineering, electrical engineering, and software engineering. Within the machine and plant engineering process, software engineering is part of automation engineering, which deals with configuration and programming of devices like programmable logic controllers (PLC), motion controllers, and human machine interface (HMI) ABstrAct
{"title":"A Multidimensional Approach for Concurrent Model-Driven Automation Engineering","authors":"S. Rose, M. Lauder, M. Schlereth, Andy Schürr","doi":"10.4018/978-1-61692-874-2.ch005","DOIUrl":"https://doi.org/10.4018/978-1-61692-874-2.ch005","url":null,"abstract":"Mechatronic engineering is about integration of different engineering disciplines, mainly mechanical engineering, electrical engineering, and software engineering. Within the machine and plant engineering process, software engineering is part of automation engineering, which deals with configuration and programming of devices like programmable logic controllers (PLC), motion controllers, and human machine interface (HMI) ABstrAct","PeriodicalId":158461,"journal":{"name":"Model-Driven Domain Analysis and Software Development","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134580567","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 : 1900-01-01DOI: 10.4018/978-1-61692-874-2.ch001
J. Osis, Erika Asnina
Experts’ opinions exist that the way software is built is primitive. The role of modeling as a treatment for Software Engineering (SE) became more important after the appearance of Model-Driven Architecture (MDA). The main advantage of MDA is architectural separation of concerns that showed the necessity of modeling and opened the way for Software Development (SD) to become engineering. However, this principle does not demonstrate its whole potential power in practice, because of a lack of mathematical accuracy in the initial steps of SD. The question about the sufficiency of modeling in SD is still open. The authors believe that SD, in general, and modeling, in particular, based on mathematical formalism in all its stages together with the implemented principle of architectural separation of concerns can become an important part of SE in its real sense. They introduce such mathematical formalism by means of topological modeling of system functioning.
{"title":"Is Modeling a Treatment for the Weakness of Software Engineering?","authors":"J. Osis, Erika Asnina","doi":"10.4018/978-1-61692-874-2.ch001","DOIUrl":"https://doi.org/10.4018/978-1-61692-874-2.ch001","url":null,"abstract":"Experts’ opinions exist that the way software is built is primitive. The role of modeling as a treatment for Software Engineering (SE) became more important after the appearance of Model-Driven Architecture (MDA). The main advantage of MDA is architectural separation of concerns that showed the necessity of modeling and opened the way for Software Development (SD) to become engineering. However, this principle does not demonstrate its whole potential power in practice, because of a lack of mathematical accuracy in the initial steps of SD. The question about the sufficiency of modeling in SD is still open. The authors believe that SD, in general, and modeling, in particular, based on mathematical formalism in all its stages together with the implemented principle of architectural separation of concerns can become an important part of SE in its real sense. They introduce such mathematical formalism by means of topological modeling of system functioning.","PeriodicalId":158461,"journal":{"name":"Model-Driven Domain Analysis and Software Development","volume":"105 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123301900","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 : 1900-01-01DOI: 10.4018/978-1-61692-874-2.ch017
Mauricio Alférez, A. Moreira, Vasco Amaral, J. Araújo
Model-driven methods for requirements specification in Software Product Lines (SPLs) support the construction of different models to provide a better understanding of each SPL feature and intended use scenarios. However, the different models must be composed to show the requirements of the target applications and, therefore, help to understand how features will be integrated in a new product of a software product line. Although well-established standards for creating metamodels and model transformations exist, there is currently no established foundation that allows practitioners to distinguish between the different modeling and composition approaches for requirements models. This chapter provides an overview of different approaches for specifying requirements models and composing models for specific products of an SPL. In particular, it emphasizes one of the most recurring specification techniques: model-driven and use case scenario-based specification. This technique, in combination with feature models and the Variability Modeling Language for Requirements (VML4RE), integrates our approach for model-driven requirements specification for SPLs.
{"title":"Model-Driven Requirements Specification for Software Product Lines","authors":"Mauricio Alférez, A. Moreira, Vasco Amaral, J. Araújo","doi":"10.4018/978-1-61692-874-2.ch017","DOIUrl":"https://doi.org/10.4018/978-1-61692-874-2.ch017","url":null,"abstract":"Model-driven methods for requirements specification in Software Product Lines (SPLs) support the construction of different models to provide a better understanding of each SPL feature and intended use scenarios. However, the different models must be composed to show the requirements of the target applications and, therefore, help to understand how features will be integrated in a new product of a software product line. Although well-established standards for creating metamodels and model transformations exist, there is currently no established foundation that allows practitioners to distinguish between the different modeling and composition approaches for requirements models. This chapter provides an overview of different approaches for specifying requirements models and composing models for specific products of an SPL. In particular, it emphasizes one of the most recurring specification techniques: model-driven and use case scenario-based specification. This technique, in combination with feature models and the Variability Modeling Language for Requirements (VML4RE), integrates our approach for model-driven requirements specification for SPLs.","PeriodicalId":158461,"journal":{"name":"Model-Driven Domain Analysis and Software Development","volume":"45 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125689191","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 : 1900-01-01DOI: 10.4018/978-1-61692-874-2.ch009
A. Kalnins, M. Smialek, E. Kalniņa, E. Celms, W. Nowakowski, Tomasz Straszak
{"title":"Domain-Driven Reuse of Software Design Models","authors":"A. Kalnins, M. Smialek, E. Kalniņa, E. Celms, W. Nowakowski, Tomasz Straszak","doi":"10.4018/978-1-61692-874-2.ch009","DOIUrl":"https://doi.org/10.4018/978-1-61692-874-2.ch009","url":null,"abstract":"","PeriodicalId":158461,"journal":{"name":"Model-Driven Domain Analysis and Software Development","volume":"22 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127445887","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 : 1900-01-01DOI: 10.4018/978-1-61692-874-2.ch010
I. Dubielewicz, B. Hnatkowska, Z. Huzar, Lech Tuzinkiewicz
{"title":"Quality-Driven Database System Development","authors":"I. Dubielewicz, B. Hnatkowska, Z. Huzar, Lech Tuzinkiewicz","doi":"10.4018/978-1-61692-874-2.ch010","DOIUrl":"https://doi.org/10.4018/978-1-61692-874-2.ch010","url":null,"abstract":"","PeriodicalId":158461,"journal":{"name":"Model-Driven Domain Analysis and Software Development","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130718057","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 : 1900-01-01DOI: 10.4018/978-1-61692-874-2.ch014
Sofia Azevedo, R. J. Machado, A. Bragança, Hugo Ribeiro
Software patterns are reusable solutions to problems that occur often throughout the software development process. This chapter formally states which sort of software patterns shall be used in which particular moment of the software development process and in the context of which Software Engineering professionals, technologies and methodologies. The way to do that is to classify those patterns according to the proposed multilevel and multistage pattern classification based on the software development process. The classification is based on the OMG modeling infrastructure or Four-Layer Architecture and also on the RUP (Rational Unified Process). It considers that patterns can be represented at different levels of the OMG modeling infrastructure and that representing patterns as metamodels is a way of turning the decisions on their application more objective. Classifying patterns according to the proposed pattern classification allows for the preservation of the original advantages of those patterns and avoids that the patterns from a specific category are handled by the inadequate professionals, technologies and methodologies. The chapter illustrates the proposed approach with the classification of some patterns.
{"title":"Systematic Use of Software Development Patterns through a Multilevel and Multistage Classification","authors":"Sofia Azevedo, R. J. Machado, A. Bragança, Hugo Ribeiro","doi":"10.4018/978-1-61692-874-2.ch014","DOIUrl":"https://doi.org/10.4018/978-1-61692-874-2.ch014","url":null,"abstract":"Software patterns are reusable solutions to problems that occur often throughout the software development process. This chapter formally states which sort of software patterns shall be used in which particular moment of the software development process and in the context of which Software Engineering professionals, technologies and methodologies. The way to do that is to classify those patterns according to the proposed multilevel and multistage pattern classification based on the software development process. The classification is based on the OMG modeling infrastructure or Four-Layer Architecture and also on the RUP (Rational Unified Process). It considers that patterns can be represented at different levels of the OMG modeling infrastructure and that representing patterns as metamodels is a way of turning the decisions on their application more objective. Classifying patterns according to the proposed pattern classification allows for the preservation of the original advantages of those patterns and avoids that the patterns from a specific category are handled by the inadequate professionals, technologies and methodologies. The chapter illustrates the proposed approach with the classification of some patterns.","PeriodicalId":158461,"journal":{"name":"Model-Driven Domain Analysis and Software Development","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127852914","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 : 1900-01-01DOI: 10.4018/978-1-61692-874-2.ch002
J. Osis, Erika Asnina
There are many ways how to describe semantics. In software development during the so called problem domain analysis mostly informal approaches and languages are used. There are several causes, and one of more important is that the problem domain itself is not well determined. Thus, developers explore the problem domain by parts, at the beginning trying to understand each fragment of the problem domain and only after that trying to join those fragments together in the holistic and more formal representation. Indeed, the question about possibility of formal description of semantics still exists. The important property of diagrams used in software development is that they must provide very precise or even formal sense. In (Diskin, Kadish, Piessens, & ABstrAct
{"title":"Topological Modeling for Model-Driven Domain Analysis and Software Development: Functions and Architectures","authors":"J. Osis, Erika Asnina","doi":"10.4018/978-1-61692-874-2.ch002","DOIUrl":"https://doi.org/10.4018/978-1-61692-874-2.ch002","url":null,"abstract":"There are many ways how to describe semantics. In software development during the so called problem domain analysis mostly informal approaches and languages are used. There are several causes, and one of more important is that the problem domain itself is not well determined. Thus, developers explore the problem domain by parts, at the beginning trying to understand each fragment of the problem domain and only after that trying to join those fragments together in the holistic and more formal representation. Indeed, the question about possibility of formal description of semantics still exists. The important property of diagrams used in software development is that they must provide very precise or even formal sense. In (Diskin, Kadish, Piessens, & ABstrAct","PeriodicalId":158461,"journal":{"name":"Model-Driven Domain Analysis and Software Development","volume":"189 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131372241","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 : 1900-01-01DOI: 10.4018/978-1-61692-874-2.ch006
B. Dougherty, Jules White, D. Schmidt
{"title":"Model-Driven Configuration of Distributed Real-time and Embedded Systems","authors":"B. Dougherty, Jules White, D. Schmidt","doi":"10.4018/978-1-61692-874-2.ch006","DOIUrl":"https://doi.org/10.4018/978-1-61692-874-2.ch006","url":null,"abstract":"","PeriodicalId":158461,"journal":{"name":"Model-Driven Domain Analysis and Software Development","volume":"3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116915043","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 : 1900-01-01DOI: 10.4018/978-1-61692-874-2.ch011
J. Zdravkovic, T. Ilayperuma
Contemporary enterprises face strong pressures to increase competitiveness by engaging in alliances of several kinds. In a rapidly increasing degree, traditional organizational structures evolve towards online business using modern ICT - such as the Internet, semantic standards, process- and service-oriented architectures. For efficient applications of inter-organizational information systems, the alignment between business and ICT is a key factor. At the ICT level, Web services are used as the cornerstones for modeling the interaction points of Web applications. So far, development of Web services has focused on a technical perspective, such as the development of standards for message exchanges and service coordination. Thereby, business concepts, such as economic values exchanged among the cooperating actors, cannot be traced in Web service specifications. As a consequence, business and ICT models become difficult to keep aligned. To address this issue, the authors propose a MDA-based approach for design of software services which may be implemented using Web services and Web service coordinations. The proposal focuses on a value-explorative analysis and modeling of business services at the CIM level, and model transformations using UML 2 to the PIM level, by utilizing well-defined mappings.
{"title":"Exploring Business Value Models for E-Service Design","authors":"J. Zdravkovic, T. Ilayperuma","doi":"10.4018/978-1-61692-874-2.ch011","DOIUrl":"https://doi.org/10.4018/978-1-61692-874-2.ch011","url":null,"abstract":"Contemporary enterprises face strong pressures to increase competitiveness by engaging in alliances of several kinds. In a rapidly increasing degree, traditional organizational structures evolve towards online business using modern ICT - such as the Internet, semantic standards, process- and service-oriented architectures. For efficient applications of inter-organizational information systems, the alignment between business and ICT is a key factor. At the ICT level, Web services are used as the cornerstones for modeling the interaction points of Web applications. So far, development of Web services has focused on a technical perspective, such as the development of standards for message exchanges and service coordination. Thereby, business concepts, such as economic values exchanged among the cooperating actors, cannot be traced in Web service specifications. As a consequence, business and ICT models become difficult to keep aligned. To address this issue, the authors propose a MDA-based approach for design of software services which may be implemented using Web services and Web service coordinations. The proposal focuses on a value-explorative analysis and modeling of business services at the CIM level, and model transformations using UML 2 to the PIM level, by utilizing well-defined mappings.","PeriodicalId":158461,"journal":{"name":"Model-Driven Domain Analysis and Software Development","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128738781","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
扫码关注我们
求助内容：
应助结果提醒方式：