�ݺ�ߣshows by User: JuhaPekkaTolvanen

�ݺ�ߣshows by User: JuhaPekkaTolvanen / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: JuhaPekkaTolvanen / Wed, 25 Sep 2024 10:18:30 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: JuhaPekkaTolvanen Languages for non-developers - invited keynote FedCSIS 2024 /slideshow/languages-for-non-developers-invited-keynote-fedcsis-2024/272011482 languagesfornon-developers-invitedkeynotefedcsis2024-240925101831-1a718ce3
Productivity has improved each time programming languages have raised the level of abstraction. This trend continues today with languages that narrow the scope they address – referred to as domain-specific languages (DSLs). However, many of these DSLs are built by developers for developers and tend to concentrate on the solution domain rather than the problem domain. In this talk, I will advocate for languages to be aligned more closely with the problem domain, addressing the needs of domain experts. Such languages enable non-developers to capture and communicate their knowledge, and together with tools support testing, validation, and feedback. Tools can also transform precise knowledge representations into software code and other artifacts. I will provide examples of non-developer languages used by usability experts, safety engineers, insurance experts, and instrumentation experts. These languages differ from traditional programming languages as they aim to align more closely with the domain, representing knowledge through maps, diagrams, or tables rather than with plain text only. The talk will identify key characteristics of non-developer languages and discuss how creating them differs from programming languages. This leads us to envision the role of non-developers in language creation and identify domains in which non-developer languages are more suitable.]]>
Productivity has improved each time programming languages have raised the level of abstraction. This trend continues today with languages that narrow the scope they address – referred to as domain-specific languages (DSLs). However, many of these DSLs are built by developers for developers and tend to concentrate on the solution domain rather than the problem domain. In this talk, I will advocate for languages to be aligned more closely with the problem domain, addressing the needs of domain experts. Such languages enable non-developers to capture and communicate their knowledge, and together with tools support testing, validation, and feedback. Tools can also transform precise knowledge representations into software code and other artifacts. I will provide examples of non-developer languages used by usability experts, safety engineers, insurance experts, and instrumentation experts. These languages differ from traditional programming languages as they aim to align more closely with the domain, representing knowledge through maps, diagrams, or tables rather than with plain text only. The talk will identify key characteristics of non-developer languages and discuss how creating them differs from programming languages. This leads us to envision the role of non-developers in language creation and identify domains in which non-developer languages are more suitable.]]> Wed, 25 Sep 2024 10:18:30 GMT /slideshow/languages-for-non-developers-invited-keynote-fedcsis-2024/272011482 JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) Languages for non-developers - invited keynote FedCSIS 2024 JuhaPekkaTolvanen Productivity has improved each time programming languages have raised the level of abstraction. This trend continues today with languages that narrow the scope they address – referred to as domain-specific languages (DSLs). However, many of these DSLs are built by developers for developers and tend to concentrate on the solution domain rather than the problem domain. In this talk, I will advocate for languages to be aligned more closely with the problem domain, addressing the needs of domain experts. Such languages enable non-developers to capture and communicate their knowledge, and together with tools support testing, validation, and feedback. Tools can also transform precise knowledge representations into software code and other artifacts. I will provide examples of non-developer languages used by usability experts, safety engineers, insurance experts, and instrumentation experts. These languages differ from traditional programming languages as they aim to align more closely with the domain, representing knowledge through maps, diagrams, or tables rather than with plain text only. The talk will identify key characteristics of non-developer languages and discuss how creating them differs from programming languages. This leads us to envision the role of non-developers in language creation and identify domains in which non-developer languages are more suitable. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/languagesfornon-developers-invitedkeynotefedcsis2024-240925101831-1a718ce3-thumbnail.jpg?width=120&height=120&fit=bounds" /> Productivity has improved each time programming languages have raised the level of abstraction. This trend continues today with languages that narrow the scope they address – referred to as domain-specific languages (DSLs). However, many of these DSLs are built by developers for developers and tend to concentrate on the solution domain rather than the problem domain. In this talk, I will advocate for languages to be aligned more closely with the problem domain, addressing the needs of domain experts. Such languages enable non-developers to capture and communicate their knowledge, and together with tools support testing, validation, and feedback. Tools can also transform precise knowledge representations into software code and other artifacts. I will provide examples of non-developer languages used by usability experts, safety engineers, insurance experts, and instrumentation experts. These languages differ from traditional programming languages as they aim to align more closely with the domain, representing knowledge through maps, diagrams, or tables rather than with plain text only. The talk will identify key characteristics of non-developer languages and discuss how creating them differs from programming languages. This leads us to envision the role of non-developers in language creation and identify domains in which non-developer languages are more suitable.

Languages for non-developers - invited keynote FedCSIS 2024 from Juha-Pekka Tolvanen

]]> 59 0 https://cdn.slidesharecdn.com/ss_thumbnails/languagesfornon-developers-invitedkeynotefedcsis2024-240925101831-1a718ce3-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 What Goes Wrong with Language Definitions and How to Improve the Situation /slideshow/what-goes-wrong-with-language-definitions-and-how-to-improve-the-situation/267979386 whatgoeswrongwithlanguagedefinitionsandhowtoimprovethesituation-240510100056-a55337ac
Modeling languages are generally applied for developing systems and software – both internally, with domain-specific languages, and with standardized languages targeting a general purpose and a wide audience. Way too often these languages are weakly created and defined leading to poor quality: Language definitions tend to contain errors and inconsistencies; notations do not recognize the communication and problem-solving needs of humans; standardization organizations push exchange formats that do not fully work and offer certificates that do not measure mastery of the language. We describe common problems in language development and point them out with examples from known cases. To overcome these problems, we suggest several solutions to improve language development, including using modeling languages specifically designed to define modeling languages, continuous testing and prototyping, and keeping language users in the loop.]]>
Modeling languages are generally applied for developing systems and software – both internally, with domain-specific languages, and with standardized languages targeting a general purpose and a wide audience. Way too often these languages are weakly created and defined leading to poor quality: Language definitions tend to contain errors and inconsistencies; notations do not recognize the communication and problem-solving needs of humans; standardization organizations push exchange formats that do not fully work and offer certificates that do not measure mastery of the language. We describe common problems in language development and point them out with examples from known cases. To overcome these problems, we suggest several solutions to improve language development, including using modeling languages specifically designed to define modeling languages, continuous testing and prototyping, and keeping language users in the loop.]]> Fri, 10 May 2024 10:00:56 GMT /slideshow/what-goes-wrong-with-language-definitions-and-how-to-improve-the-situation/267979386 JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) What Goes Wrong with Language Definitions and How to Improve the Situation JuhaPekkaTolvanen Modeling languages are generally applied for developing systems and software – both internally, with domain-specific languages, and with standardized languages targeting a general purpose and a wide audience. Way too often these languages are weakly created and defined leading to poor quality: Language definitions tend to contain errors and inconsistencies; notations do not recognize the communication and problem-solving needs of humans; standardization organizations push exchange formats that do not fully work and offer certificates that do not measure mastery of the language. We describe common problems in language development and point them out with examples from known cases. To overcome these problems, we suggest several solutions to improve language development, including using modeling languages specifically designed to define modeling languages, continuous testing and prototyping, and keeping language users in the loop. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/whatgoeswrongwithlanguagedefinitionsandhowtoimprovethesituation-240510100056-a55337ac-thumbnail.jpg?width=120&height=120&fit=bounds" /> Modeling languages are generally applied for developing systems and software – both internally, with domain-specific languages, and with standardized languages targeting a general purpose and a wide audience. Way too often these languages are weakly created and defined leading to poor quality: Language definitions tend to contain errors and inconsistencies; notations do not recognize the communication and problem-solving needs of humans; standardization organizations push exchange formats that do not fully work and offer certificates that do not measure mastery of the language. We describe common problems in language development and point them out with examples from known cases. To overcome these problems, we suggest several solutions to improve language development, including using modeling languages specifically designed to define modeling languages, continuous testing and prototyping, and keeping language users in the loop.

What Goes Wrong with Language Definitions and How to Improve the Situation from Juha-Pekka Tolvanen

]]> 48 0 https://cdn.slidesharecdn.com/ss_thumbnails/whatgoeswrongwithlanguagedefinitionsandhowtoimprovethesituation-240510100056-a55337ac-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 How to formalize a ubiquitous language into a domain-specific language.pdf /slideshow/how-to-formalize-a-ubiquitous-language-into-a-domainspecific-languagepdf/256209616 howtoformalizeaubiquitouslanguageintoadomain-specificlanguage-230303114047-5c6978bc
Language defines the boundary to our world: it sets what we can describe and what we can’t. This talk describes and demonstrates how to formalize a ubiquitous language into a domain-specific language. If we do this move the language is not used only for communication and collaboration as well as used as a basis for generating code, tests, configs, etc. It means that domain experts/subject matter experts use the language. The talk is based on industry cases from various domains, such as banking and insurance, industry automation and automotive, and been demonstrated during the talk.]]>
Language defines the boundary to our world: it sets what we can describe and what we can’t. This talk describes and demonstrates how to formalize a ubiquitous language into a domain-specific language. If we do this move the language is not used only for communication and collaboration as well as used as a basis for generating code, tests, configs, etc. It means that domain experts/subject matter experts use the language. The talk is based on industry cases from various domains, such as banking and insurance, industry automation and automotive, and been demonstrated during the talk.]]> Fri, 03 Mar 2023 11:40:46 GMT /slideshow/how-to-formalize-a-ubiquitous-language-into-a-domainspecific-languagepdf/256209616 JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) How to formalize a ubiquitous language into a domain-specific language.pdf JuhaPekkaTolvanen Language defines the boundary to our world: it sets what we can describe and what we can’t. This talk describes and demonstrates how to formalize a ubiquitous language into a domain-specific language. If we do this move the language is not used only for communication and collaboration as well as used as a basis for generating code, tests, configs, etc. It means that domain experts/subject matter experts use the language. The talk is based on industry cases from various domains, such as banking and insurance, industry automation and automotive, and been demonstrated during the talk. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/howtoformalizeaubiquitouslanguageintoadomain-specificlanguage-230303114047-5c6978bc-thumbnail.jpg?width=120&height=120&fit=bounds" /> Language defines the boundary to our world: it sets what we can describe and what we can’t. This talk describes and demonstrates how to formalize a ubiquitous language into a domain-specific language. If we do this move the language is not used only for communication and collaboration as well as used as a basis for generating code, tests, configs, etc. It means that domain experts/subject matter experts use the language. The talk is based on industry cases from various domains, such as banking and insurance, industry automation and automotive, and been demonstrated during the talk.

How to formalize a ubiquitous language into a domain-specific language.pdf from Juha-Pekka Tolvanen

]]> 241 0 https://cdn.slidesharecdn.com/ss_thumbnails/howtoformalizeaubiquitouslanguageintoadomain-specificlanguage-230303114047-5c6978bc-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Measuring Productivity from Model-Based Development /slideshow/measuring-productivity-from-modelbased-development/255079084 measuringproductivityfrommodel-baseddevelopment-221229121332-8a48a9cb
Model-based development, using models as the primary source when creating systems and software, is claimed to improve productivity but this is often hard to justify in practice. It requires a lot of resources and time to do it in “academic” way by building the same system twice, having parallel teams, many developers and covering large numbers of development tasks. We describe, based on successful cases from practice, how evaluation can be conducted in practical use in a commercial setting. It is based on the same approach that is the basis for daily project business: Inspect how much effort was needed to implement an application that met customer requirements. We give examples of this by describing evaluations done in two different kind of companies: one developing embedded products for consumer electronics and the other web-based enterprise applications for the cloud. The talk shows the evaluation approaches that are realistic but require modest investments both in time and resources. We detail the evaluation procedures so that participants can repeat them in their own teams and companies. This helps to evaluate if a particular model-based development approach is suitable for the company.]]>
Model-based development, using models as the primary source when creating systems and software, is claimed to improve productivity but this is often hard to justify in practice. It requires a lot of resources and time to do it in “academic” way by building the same system twice, having parallel teams, many developers and covering large numbers of development tasks. We describe, based on successful cases from practice, how evaluation can be conducted in practical use in a commercial setting. It is based on the same approach that is the basis for daily project business: Inspect how much effort was needed to implement an application that met customer requirements. We give examples of this by describing evaluations done in two different kind of companies: one developing embedded products for consumer electronics and the other web-based enterprise applications for the cloud. The talk shows the evaluation approaches that are realistic but require modest investments both in time and resources. We detail the evaluation procedures so that participants can repeat them in their own teams and companies. This helps to evaluate if a particular model-based development approach is suitable for the company.]]> Thu, 29 Dec 2022 12:13:32 GMT /slideshow/measuring-productivity-from-modelbased-development/255079084 JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) Measuring Productivity from Model-Based Development JuhaPekkaTolvanen Model-based development, using models as the primary source when creating systems and software, is claimed to improve productivity but this is often hard to justify in practice. It requires a lot of resources and time to do it in “academic” way by building the same system twice, having parallel teams, many developers and covering large numbers of development tasks. We describe, based on successful cases from practice, how evaluation can be conducted in practical use in a commercial setting. It is based on the same approach that is the basis for daily project business: Inspect how much effort was needed to implement an application that met customer requirements. We give examples of this by describing evaluations done in two different kind of companies: one developing embedded products for consumer electronics and the other web-based enterprise applications for the cloud. The talk shows the evaluation approaches that are realistic but require modest investments both in time and resources. We detail the evaluation procedures so that participants can repeat them in their own teams and companies. This helps to evaluate if a particular model-based development approach is suitable for the company. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/measuringproductivityfrommodel-baseddevelopment-221229121332-8a48a9cb-thumbnail.jpg?width=120&height=120&fit=bounds" /> Model-based development, using models as the primary source when creating systems and software, is claimed to improve productivity but this is often hard to justify in practice. It requires a lot of resources and time to do it in “academic” way by building the same system twice, having parallel teams, many developers and covering large numbers of development tasks. We describe, based on successful cases from practice, how evaluation can be conducted in practical use in a commercial setting. It is based on the same approach that is the basis for daily project business: Inspect how much effort was needed to implement an application that met customer requirements. We give examples of this by describing evaluations done in two different kind of companies: one developing embedded products for consumer electronics and the other web-based enterprise applications for the cloud. The talk shows the evaluation approaches that are realistic but require modest investments both in time and resources. We detail the evaluation procedures so that participants can repeat them in their own teams and companies. This helps to evaluate if a particular model-based development approach is suitable for the company.

Measuring Productivity from Model-Based Development from Juha-Pekka Tolvanen

]]> 17 0 https://cdn.slidesharecdn.com/ss_thumbnails/measuringproductivityfrommodel-baseddevelopment-221229121332-8a48a9cb-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 How domain specific modeling languages address variability: investigation of 23 cases /slideshow/how-domain-specific-modeling-languages-address-variability-investigation-of-23-cases/170821270 howdomain-specificmodelinglanguagesaddressvariability-190911080001
Domain-Specific Modeling raises the level of abstraction beyond programming by specifying the solution directly with domain concepts. Within product lines domain-specific approaches are applied to specify variability and then generate final products together with commonality. Such automated product derivation is possible because both the modeling language and generator are made for a particular product line — often inside a single company. We examine which kinds of reuse and product line approaches are applied in industry with domain-specific modeling. Our work is based on empirical analysis of 23 cases and the languages and models created there. The analysis reveals a wide variety and some commonalities in the size of languages and in the ways they apply reuse and product line approaches.]]>
Domain-Specific Modeling raises the level of abstraction beyond programming by specifying the solution directly with domain concepts. Within product lines domain-specific approaches are applied to specify variability and then generate final products together with commonality. Such automated product derivation is possible because both the modeling language and generator are made for a particular product line — often inside a single company. We examine which kinds of reuse and product line approaches are applied in industry with domain-specific modeling. Our work is based on empirical analysis of 23 cases and the languages and models created there. The analysis reveals a wide variety and some commonalities in the size of languages and in the ways they apply reuse and product line approaches.]]> Wed, 11 Sep 2019 08:00:01 GMT /slideshow/how-domain-specific-modeling-languages-address-variability-investigation-of-23-cases/170821270 JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) How domain specific modeling languages address variability: investigation of 23 cases JuhaPekkaTolvanen Domain-Specific Modeling raises the level of abstraction beyond programming by specifying the solution directly with domain concepts. Within product lines domain-specific approaches are applied to specify variability and then generate final products together with commonality. Such automated product derivation is possible because both the modeling language and generator are made for a particular product line — often inside a single company. We examine which kinds of reuse and product line approaches are applied in industry with domain-specific modeling. Our work is based on empirical analysis of 23 cases and the languages and models created there. The analysis reveals a wide variety and some commonalities in the size of languages and in the ways they apply reuse and product line approaches. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/howdomain-specificmodelinglanguagesaddressvariability-190911080001-thumbnail.jpg?width=120&height=120&fit=bounds" /> Domain-Specific Modeling raises the level of abstraction beyond programming by specifying the solution directly with domain concepts. Within product lines domain-specific approaches are applied to specify variability and then generate final products together with commonality. Such automated product derivation is possible because both the modeling language and generator are made for a particular product line — often inside a single company. We examine which kinds of reuse and product line approaches are applied in industry with domain-specific modeling. Our work is based on empirical analysis of 23 cases and the languages and models created there. The analysis reveals a wide variety and some commonalities in the size of languages and in the ways they apply reuse and product line approaches.

How domain specific modeling languages address variability: investigation of 23 cases from Juha-Pekka Tolvanen

]]> 206 0 https://cdn.slidesharecdn.com/ss_thumbnails/howdomain-specificmodelinglanguagesaddressvariability-190911080001-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Effort Used to Create Domain-Specific Modeling Languages /slideshow/effort-used-to-create-domainspecific-modeling-languages/120284452 efforttocreatemodelingsolutions-181022103109
Domain-specific modeling languages and generators have been shown to significantly improve the productivity and quality of system and software development. These benefits are typically reported without explaining the size of the initial investment in creating the languages, generators and related tooling. We compare the investment needed across ten cases, in two different ways, focusing on the effort to develop a complete modeling solution for a particular domain with the MetaEdit+ tool. Firstly, we use a case study research method to obtain detailed data on the development effort of implementing two realistically-sized domain-specific modeling solutions. Secondly, we review eight publicly available cases from various companies to obtain data from industry experiences with the same tool, and compare them with the results from our case studies. Both the case studies and the industry reports indicate that, for this tool, the investment required to create domain-specific modeling support is modest: ranging from 3 to 15 man-days with an average of 10 days]]>
Domain-specific modeling languages and generators have been shown to significantly improve the productivity and quality of system and software development. These benefits are typically reported without explaining the size of the initial investment in creating the languages, generators and related tooling. We compare the investment needed across ten cases, in two different ways, focusing on the effort to develop a complete modeling solution for a particular domain with the MetaEdit+ tool. Firstly, we use a case study research method to obtain detailed data on the development effort of implementing two realistically-sized domain-specific modeling solutions. Secondly, we review eight publicly available cases from various companies to obtain data from industry experiences with the same tool, and compare them with the results from our case studies. Both the case studies and the industry reports indicate that, for this tool, the investment required to create domain-specific modeling support is modest: ranging from 3 to 15 man-days with an average of 10 days]]> Mon, 22 Oct 2018 10:31:09 GMT /slideshow/effort-used-to-create-domainspecific-modeling-languages/120284452 JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) Effort Used to Create Domain-Specific Modeling Languages JuhaPekkaTolvanen Domain-specific modeling languages and generators have been shown to significantly improve the productivity and quality of system and software development. These benefits are typically reported without explaining the size of the initial investment in creating the languages, generators and related tooling. We compare the investment needed across ten cases, in two different ways, focusing on the effort to develop a complete modeling solution for a particular domain with the MetaEdit+ tool. Firstly, we use a case study research method to obtain detailed data on the development effort of implementing two realistically-sized domain-specific modeling solutions. Secondly, we review eight publicly available cases from various companies to obtain data from industry experiences with the same tool, and compare them with the results from our case studies. Both the case studies and the industry reports indicate that, for this tool, the investment required to create domain-specific modeling support is modest: ranging from 3 to 15 man-days with an average of 10 days <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/efforttocreatemodelingsolutions-181022103109-thumbnail.jpg?width=120&height=120&fit=bounds" /> Domain-specific modeling languages and generators have been shown to significantly improve the productivity and quality of system and software development. These benefits are typically reported without explaining the size of the initial investment in creating the languages, generators and related tooling. We compare the investment needed across ten cases, in two different ways, focusing on the effort to develop a complete modeling solution for a particular domain with the MetaEdit+ tool. Firstly, we use a case study research method to obtain detailed data on the development effort of implementing two realistically-sized domain-specific modeling solutions. Secondly, we review eight publicly available cases from various companies to obtain data from industry experiences with the same tool, and compare them with the results from our case studies. Both the case studies and the industry reports indicate that, for this tool, the investment required to create domain-specific modeling support is modest: ranging from 3 to 15 man-days with an average of 10 days

Effort Used to Create Domain-Specific Modeling Languages from Juha-Pekka Tolvanen

]]> 169 0 https://cdn.slidesharecdn.com/ss_thumbnails/efforttocreatemodelingsolutions-181022103109-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Automating safety engineering with model based techniques /slideshow/automating-safety-engineering-with-model-based-techniques/73405208 automatingsafetyengineeringwithmodel-basedtechniques-170321100038
Fault Trees and Failure Models and Effects Analyses are well known methods in safety and reliability engineering. Their use, however, requires a considerable amount of work, in particular when the system evolves and grows. We describe an approach that automates parts of safety design flow. First, existing architecture models can be translated to dependability and error models. Safety engineers can then adapt the models for various safety cases and finally run analysis calling a suitable tool. We demonstrate the approach within automotive domain: System is specified with domain-specific languages and the created models are translated to analysis tools. This approach provides several benefits. It helps to ensure that safety analysis is done for the intended/designed architecture. It also makes safety analysis faster as it is partly automated, reduces error-prone routine work and makes safety analysis easier to use and accessible.]]>
Fault Trees and Failure Models and Effects Analyses are well known methods in safety and reliability engineering. Their use, however, requires a considerable amount of work, in particular when the system evolves and grows. We describe an approach that automates parts of safety design flow. First, existing architecture models can be translated to dependability and error models. Safety engineers can then adapt the models for various safety cases and finally run analysis calling a suitable tool. We demonstrate the approach within automotive domain: System is specified with domain-specific languages and the created models are translated to analysis tools. This approach provides several benefits. It helps to ensure that safety analysis is done for the intended/designed architecture. It also makes safety analysis faster as it is partly automated, reduces error-prone routine work and makes safety analysis easier to use and accessible.]]> Tue, 21 Mar 2017 10:00:38 GMT /slideshow/automating-safety-engineering-with-model-based-techniques/73405208 JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) Automating safety engineering with model based techniques JuhaPekkaTolvanen Fault Trees and Failure Models and Effects Analyses are well known methods in safety and reliability engineering. Their use, however, requires a considerable amount of work, in particular when the system evolves and grows. We describe an approach that automates parts of safety design flow. First, existing architecture models can be translated to dependability and error models. Safety engineers can then adapt the models for various safety cases and finally run analysis calling a suitable tool. We demonstrate the approach within automotive domain: System is specified with domain-specific languages and the created models are translated to analysis tools. This approach provides several benefits. It helps to ensure that safety analysis is done for the intended/designed architecture. It also makes safety analysis faster as it is partly automated, reduces error-prone routine work and makes safety analysis easier to use and accessible. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/automatingsafetyengineeringwithmodel-basedtechniques-170321100038-thumbnail.jpg?width=120&height=120&fit=bounds" /> Fault Trees and Failure Models and Effects Analyses are well known methods in safety and reliability engineering. Their use, however, requires a considerable amount of work, in particular when the system evolves and grows. We describe an approach that automates parts of safety design flow. First, existing architecture models can be translated to dependability and error models. Safety engineers can then adapt the models for various safety cases and finally run analysis calling a suitable tool. We demonstrate the approach within automotive domain: System is specified with domain-specific languages and the created models are translated to analysis tools. This approach provides several benefits. It helps to ensure that safety analysis is done for the intended/designed architecture. It also makes safety analysis faster as it is partly automated, reduces error-prone routine work and makes safety analysis easier to use and accessible.

Automating safety engineering with model based techniques from Juha-Pekka Tolvanen

]]> 738 0 https://cdn.slidesharecdn.com/ss_thumbnails/automatingsafetyengineeringwithmodel-basedtechniques-170321100038-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Collaborative language engineering and language use: demo with MetaEdit+ /slideshow/collaborative-language-engineering-and-language-use-demo-with-metaedit/68050035 collaborativelanguageengineeringandlanguageuse-demowithmetaedit-161102101400
Video part of the demonstration: http://www.metacase.com/webcasts/Multi-user.html. Almost all software development activities require collaboration and language engineering is no exception. First, there is a need for collaboration among language engineers as it is not realistic to expect one man to master all. Second, there is a natural need for collaboration among language users. Finally, there is a need for collaboration among language engineers and language users: Not only when languages are originally designed but more importantly when they are maintained along with the work already created with them. Unfortunately too often tools ignore collaboration by unnecessarily splitting the work into separate formats, tools and roles. We describe and demonstrate collaborative tool capabilities implemented into MetaEdit+ tool and describe experiences on their use in practice. ]]>
Video part of the demonstration: http://www.metacase.com/webcasts/Multi-user.html. Almost all software development activities require collaboration and language engineering is no exception. First, there is a need for collaboration among language engineers as it is not realistic to expect one man to master all. Second, there is a natural need for collaboration among language users. Finally, there is a need for collaboration among language engineers and language users: Not only when languages are originally designed but more importantly when they are maintained along with the work already created with them. Unfortunately too often tools ignore collaboration by unnecessarily splitting the work into separate formats, tools and roles. We describe and demonstrate collaborative tool capabilities implemented into MetaEdit+ tool and describe experiences on their use in practice. ]]> Wed, 02 Nov 2016 10:13:59 GMT /slideshow/collaborative-language-engineering-and-language-use-demo-with-metaedit/68050035 JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) Collaborative language engineering and language use: demo with MetaEdit+ JuhaPekkaTolvanen Video part of the demonstration: http://www.metacase.com/webcasts/Multi-user.html. Almost all software development activities require collaboration and language engineering is no exception. First, there is a need for collaboration among language engineers as it is not realistic to expect one man to master all. Second, there is a natural need for collaboration among language users. Finally, there is a need for collaboration among language engineers and language users: Not only when languages are originally designed but more importantly when they are maintained along with the work already created with them. Unfortunately too often tools ignore collaboration by unnecessarily splitting the work into separate formats, tools and roles. We describe and demonstrate collaborative tool capabilities implemented into MetaEdit+ tool and describe experiences on their use in practice. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/collaborativelanguageengineeringandlanguageuse-demowithmetaedit-161102101400-thumbnail.jpg?width=120&height=120&fit=bounds" /> Video part of the demonstration: http://www.metacase.com/webcasts/Multi-user.html. Almost all software development activities require collaboration and language engineering is no exception. First, there is a need for collaboration among language engineers as it is not realistic to expect one man to master all. Second, there is a natural need for collaboration among language users. Finally, there is a need for collaboration among language engineers and language users: Not only when languages are originally designed but more importantly when they are maintained along with the work already created with them. Unfortunately too often tools ignore collaboration by unnecessarily splitting the work into separate formats, tools and roles. We describe and demonstrate collaborative tool capabilities implemented into MetaEdit+ tool and describe experiences on their use in practice.

Collaborative language engineering and language use: demo with MetaEdit+ from Juha-Pekka Tolvanen

]]> 329 0 https://cdn.slidesharecdn.com/ss_thumbnails/collaborativelanguageengineeringandlanguageuse-demowithmetaedit-161102101400-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Automotive architecture examples with EAST-ADL models /JuhaPekkaTolvanen/automotive-architecture-examples-with-eastadl-models automotivearchitectureexamplewitheast-adlmodels-151123130548-lva1-app6891
The slides presents end-to-end example of architecture modeling with EAST-ADL using a PowerWindow example following the V-model. MetaEdit+ tool provides EAST-ADL support for safety analysis, code generation and integration with external tools.]]>
The slides presents end-to-end example of architecture modeling with EAST-ADL using a PowerWindow example following the V-model. MetaEdit+ tool provides EAST-ADL support for safety analysis, code generation and integration with external tools.]]> Mon, 23 Nov 2015 13:05:48 GMT /JuhaPekkaTolvanen/automotive-architecture-examples-with-eastadl-models JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) Automotive architecture examples with EAST-ADL models JuhaPekkaTolvanen The slides presents end-to-end example of architecture modeling with EAST-ADL using a PowerWindow example following the V-model. MetaEdit+ tool provides EAST-ADL support for safety analysis, code generation and integration with external tools. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/automotivearchitectureexamplewitheast-adlmodels-151123130548-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds" /> The slides presents end-to-end example of architecture modeling with EAST-ADL using a PowerWindow example following the V-model. MetaEdit+ tool provides EAST-ADL support for safety analysis, code generation and integration with external tools.

Automotive architecture examples with EAST-ADL models from Juha-Pekka Tolvanen

]]> 1747 0 https://cdn.slidesharecdn.com/ss_thumbnails/automotivearchitectureexamplewitheast-adlmodels-151123130548-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Collaborative modeling and metamodeling /slideshow/collaborative-modeling-and-metamodeling/55243132 collaborativemodelingandmetamodeling-151118092721-lva1-app6892
Almost all software development activities require collaboration, and model-based software development is no exception. In modern model-based development collaboration comes in two levels. We start from collaborative language creation (aka metamodeling) and describe the benefits it can provide and then do the same for collaborative language use (aka modeling). We conclude by inspecting how the collaboration enables scalability in terms of multiple engineers, multiple languages, large models, and transformations.]]>
Almost all software development activities require collaboration, and model-based software development is no exception. In modern model-based development collaboration comes in two levels. We start from collaborative language creation (aka metamodeling) and describe the benefits it can provide and then do the same for collaborative language use (aka modeling). We conclude by inspecting how the collaboration enables scalability in terms of multiple engineers, multiple languages, large models, and transformations.]]> Wed, 18 Nov 2015 09:27:21 GMT /slideshow/collaborative-modeling-and-metamodeling/55243132 JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) Collaborative modeling and metamodeling JuhaPekkaTolvanen Almost all software development activities require collaboration, and model-based software development is no exception. In modern model-based development collaboration comes in two levels. We start from collaborative language creation (aka metamodeling) and describe the benefits it can provide and then do the same for collaborative language use (aka modeling). We conclude by inspecting how the collaboration enables scalability in terms of multiple engineers, multiple languages, large models, and transformations. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/collaborativemodelingandmetamodeling-151118092721-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds" /> Almost all software development activities require collaboration, and model-based software development is no exception. In modern model-based development collaboration comes in two levels. We start from collaborative language creation (aka metamodeling) and describe the benefits it can provide and then do the same for collaborative language use (aka modeling). We conclude by inspecting how the collaboration enables scalability in terms of multiple engineers, multiple languages, large models, and transformations.

Collaborative modeling and metamodeling from Juha-Pekka Tolvanen

]]> 557 0 https://cdn.slidesharecdn.com/ss_thumbnails/collaborativemodelingandmetamodeling-151118092721-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds document Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Collaborative modeling and metamodeling in MetaEdit+ /slideshow/collaborative-modeling-and-metamodeling-in-metaedit/55242854 collaborativemodelingandmetamodelinginmetaedit-151118091907-lva1-app6892
In modern model-based development collaboration comes in two levels. First, developers want to create, edit and check the same shared specifications and avoid handling conflicts, run diff and merge activities etc. all taking time from the actual development work. Second, also language developers defining modeling languages, generators, notations, checks etc. want to collaborate similarly too. �ݺ�ߣs describe how to work collaboratively in MetaEdit+ tool with models and metamodelsand as well as describe the benefits it provides.]]>
In modern model-based development collaboration comes in two levels. First, developers want to create, edit and check the same shared specifications and avoid handling conflicts, run diff and merge activities etc. all taking time from the actual development work. Second, also language developers defining modeling languages, generators, notations, checks etc. want to collaborate similarly too. �ݺ�ߣs describe how to work collaboratively in MetaEdit+ tool with models and metamodelsand as well as describe the benefits it provides.]]> Wed, 18 Nov 2015 09:19:07 GMT /slideshow/collaborative-modeling-and-metamodeling-in-metaedit/55242854 JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) Collaborative modeling and metamodeling in MetaEdit+ JuhaPekkaTolvanen In modern model-based development collaboration comes in two levels. First, developers want to create, edit and check the same shared specifications and avoid handling conflicts, run diff and merge activities etc. all taking time from the actual development work. Second, also language developers defining modeling languages, generators, notations, checks etc. want to collaborate similarly too. �ݺ�ߣs describe how to work collaboratively in MetaEdit+ tool with models and metamodelsand as well as describe the benefits it provides. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/collaborativemodelingandmetamodelinginmetaedit-151118091907-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds" /> In modern model-based development collaboration comes in two levels. First, developers want to create, edit and check the same shared specifications and avoid handling conflicts, run diff and merge activities etc. all taking time from the actual development work. Second, also language developers defining modeling languages, generators, notations, checks etc. want to collaborate similarly too. �ݺ�ߣs describe how to work collaboratively in MetaEdit+ tool with models and metamodelsand as well as describe the benefits it provides.

Collaborative modeling and metamodeling in MetaEdit+ from Juha-Pekka Tolvanen

]]> 3197 0 https://cdn.slidesharecdn.com/ss_thumbnails/collaborativemodelingandmetamodelinginmetaedit-151118091907-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 20 examples on Domain-Specific Modeling Languages /slideshow/20-examples-on-domain-specific-modeling/34281214 20examplesondomain-specificmodeling-140505032702-phpapp02
These slides illustrate 20 different examples on using Domain-Specific Modeling: Models are expressed using directly the concepts of the problem domain and generate the code for a given target/programming language. ]]>
These slides illustrate 20 different examples on using Domain-Specific Modeling: Models are expressed using directly the concepts of the problem domain and generate the code for a given target/programming language. ]]> Mon, 05 May 2014 03:27:02 GMT /slideshow/20-examples-on-domain-specific-modeling/34281214 JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) 20 examples on Domain-Specific Modeling Languages JuhaPekkaTolvanen These slides illustrate 20 different examples on using Domain-Specific Modeling: Models are expressed using directly the concepts of the problem domain and generate the code for a given target/programming language. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/20examplesondomain-specificmodeling-140505032702-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> These slides illustrate 20 different examples on using Domain-Specific Modeling: Models are expressed using directly the concepts of the problem domain and generate the code for a given target/programming language.

20 examples on Domain-Specific Modeling Languages from Juha-Pekka Tolvanen

]]> 13732 0 https://cdn.slidesharecdn.com/ss_thumbnails/20examplesondomain-specificmodeling-140505032702-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Model level debugging and profiling, Code Generation Conference 2014 /slideshow/model-level-debugging-and-profiling-code-generation-conference-2014/33536464 tolvanencodegen2014modelleveldebuggingandprofiling-140415013705-phpapp02
Most Model-Driven Development today drops right back down to the code level as soon as developers have to debug, profile or otherwise analyse the running application. Debugging code you have never seen is a major productivity killer – just as it was when early 3GLs lacked support for source-level debugging. In this session we will show how true model-level debugging, profiling and runtime analysis can realise the full value of MDD. We will show how models can be used as first class citizens not only for code generation but also during debugging and profiling: animating application execution, showing data on the current state, highlighting the paths executed, adding performance and trace information into the models. Breakpoints can be set in the model, just as you would in an IDE. All this can be added to any modelling language with minimal effort, integrating with your existing code IDE back-end, as we shall show with practical examples in tools like MetaEdit+, Visual Studio and Eclipse.]]>
Most Model-Driven Development today drops right back down to the code level as soon as developers have to debug, profile or otherwise analyse the running application. Debugging code you have never seen is a major productivity killer – just as it was when early 3GLs lacked support for source-level debugging. In this session we will show how true model-level debugging, profiling and runtime analysis can realise the full value of MDD. We will show how models can be used as first class citizens not only for code generation but also during debugging and profiling: animating application execution, showing data on the current state, highlighting the paths executed, adding performance and trace information into the models. Breakpoints can be set in the model, just as you would in an IDE. All this can be added to any modelling language with minimal effort, integrating with your existing code IDE back-end, as we shall show with practical examples in tools like MetaEdit+, Visual Studio and Eclipse.]]> Tue, 15 Apr 2014 01:37:05 GMT /slideshow/model-level-debugging-and-profiling-code-generation-conference-2014/33536464 JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) Model level debugging and profiling, Code Generation Conference 2014 JuhaPekkaTolvanen Most Model-Driven Development today drops right back down to the code level as soon as developers have to debug, profile or otherwise analyse the running application. Debugging code you have never seen is a major productivity killer – just as it was when early 3GLs lacked support for source-level debugging. In this session we will show how true model-level debugging, profiling and runtime analysis can realise the full value of MDD. We will show how models can be used as first class citizens not only for code generation but also during debugging and profiling: animating application execution, showing data on the current state, highlighting the paths executed, adding performance and trace information into the models. Breakpoints can be set in the model, just as you would in an IDE. All this can be added to any modelling language with minimal effort, integrating with your existing code IDE back-end, as we shall show with practical examples in tools like MetaEdit+, Visual Studio and Eclipse. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/tolvanencodegen2014modelleveldebuggingandprofiling-140415013705-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> Most Model-Driven Development today drops right back down to the code level as soon as developers have to debug, profile or otherwise analyse the running application. Debugging code you have never seen is a major productivity killer – just as it was when early 3GLs lacked support for source-level debugging. In this session we will show how true model-level debugging, profiling and runtime analysis can realise the full value of MDD. We will show how models can be used as first class citizens not only for code generation but also during debugging and profiling: animating application execution, showing data on the current state, highlighting the paths executed, adding performance and trace information into the models. Breakpoints can be set in the model, just as you would in an IDE. All this can be added to any modelling language with minimal effort, integrating with your existing code IDE back-end, as we shall show with practical examples in tools like MetaEdit+, Visual Studio and Eclipse.

Model level debugging and profiling, Code Generation Conference 2014 from Juha-Pekka Tolvanen

]]> 2230 0 https://cdn.slidesharecdn.com/ss_thumbnails/tolvanencodegen2014modelleveldebuggingandprofiling-140415013705-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Keynote at Code Generation 2014: The business cases of modeling and generators /slideshow/keynote-at-code-generation-2014-the-business-case-of-modeling-and-generators/33446033 tolvanencodegen2014thebusinesscaseofmodelingandgenerators-140412105636-phpapp01
There is no business case for modelling and generators – only for a specific language and generator in a specific situation. The right language in the right situation can improve productivity by an order of magnitude; the wrong language will reduce it. So what makes a language “right”? In this talk we look what kinds of modelling languages and generators tend to be more beneficial than others –from the early days of modelling right up to the latest research. Getting more out of the models than their original creation required, raising the level of abstraction and addressing a specific need seem to be common characteristics of successful modelling and code generation approaches. To evaluate the full business case we also need to look at the costs and benefits of creating languages, generators and tools. By applying the above principles to language creation itself, we can improve the quality of the resulting modelling language, whilst lowering the time and effort needed to create and maintain it. Other features important to the language developer include enabling tools to support language evolution, and improving tool scalability to tackle larger systems and teams.]]>
There is no business case for modelling and generators – only for a specific language and generator in a specific situation. The right language in the right situation can improve productivity by an order of magnitude; the wrong language will reduce it. So what makes a language “right”? In this talk we look what kinds of modelling languages and generators tend to be more beneficial than others –from the early days of modelling right up to the latest research. Getting more out of the models than their original creation required, raising the level of abstraction and addressing a specific need seem to be common characteristics of successful modelling and code generation approaches. To evaluate the full business case we also need to look at the costs and benefits of creating languages, generators and tools. By applying the above principles to language creation itself, we can improve the quality of the resulting modelling language, whilst lowering the time and effort needed to create and maintain it. Other features important to the language developer include enabling tools to support language evolution, and improving tool scalability to tackle larger systems and teams.]]> Sat, 12 Apr 2014 10:56:36 GMT /slideshow/keynote-at-code-generation-2014-the-business-case-of-modeling-and-generators/33446033 JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) Keynote at Code Generation 2014: The business cases of modeling and generators JuhaPekkaTolvanen There is no business case for modelling and generators – only for a specific language and generator in a specific situation. The right language in the right situation can improve productivity by an order of magnitude; the wrong language will reduce it. So what makes a language “right”? In this talk we look what kinds of modelling languages and generators tend to be more beneficial than others –from the early days of modelling right up to the latest research. Getting more out of the models than their original creation required, raising the level of abstraction and addressing a specific need seem to be common characteristics of successful modelling and code generation approaches. To evaluate the full business case we also need to look at the costs and benefits of creating languages, generators and tools. By applying the above principles to language creation itself, we can improve the quality of the resulting modelling language, whilst lowering the time and effort needed to create and maintain it. Other features important to the language developer include enabling tools to support language evolution, and improving tool scalability to tackle larger systems and teams. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/tolvanencodegen2014thebusinesscaseofmodelingandgenerators-140412105636-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> There is no business case for modelling and generators – only for a specific language and generator in a specific situation. The right language in the right situation can improve productivity by an order of magnitude; the wrong language will reduce it. So what makes a language “right”? In this talk we look what kinds of modelling languages and generators tend to be more beneficial than others –from the early days of modelling right up to the latest research. Getting more out of the models than their original creation required, raising the level of abstraction and addressing a specific need seem to be common characteristics of successful modelling and code generation approaches. To evaluate the full business case we also need to look at the costs and benefits of creating languages, generators and tools. By applying the above principles to language creation itself, we can improve the quality of the resulting modelling language, whilst lowering the time and effort needed to create and maintain it. Other features important to the language developer include enabling tools to support language evolution, and improving tool scalability to tackle larger systems and teams.

Keynote at Code Generation 2014: The business cases of modeling and generators from Juha-Pekka Tolvanen

]]> 5652 5 https://cdn.slidesharecdn.com/ss_thumbnails/tolvanencodegen2014thebusinesscaseofmodelingandgenerators-140412105636-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Industrial experiences on Domain-Specific Modeling /slideshow/industrial-experiencesondomain-specificmodeling/33445802 industrialexperiencesondomain-specificmodeling-140412104317-phpapp02
Domain-Specific Modeling (DSM) enables raising the level of abstraction close to the problem domain yet generating production code from the models. These slides describe industrial experiences on DSM in four different domains: home automation, military radio, touch screen device and sports computer applications. ]]>
Domain-Specific Modeling (DSM) enables raising the level of abstraction close to the problem domain yet generating production code from the models. These slides describe industrial experiences on DSM in four different domains: home automation, military radio, touch screen device and sports computer applications. ]]> Sat, 12 Apr 2014 10:43:16 GMT /slideshow/industrial-experiencesondomain-specificmodeling/33445802 JuhaPekkaTolvanen@slideshare.net(JuhaPekkaTolvanen) Industrial experiences on Domain-Specific Modeling JuhaPekkaTolvanen Domain-Specific Modeling (DSM) enables raising the level of abstraction close to the problem domain yet generating production code from the models. These slides describe industrial experiences on DSM in four different domains: home automation, military radio, touch screen device and sports computer applications. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/industrialexperiencesondomain-specificmodeling-140412104317-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> Domain-Specific Modeling (DSM) enables raising the level of abstraction close to the problem domain yet generating production code from the models. These slides describe industrial experiences on DSM in four different domains: home automation, military radio, touch screen device and sports computer applications.

Industrial experiences on Domain-Specific Modeling from Juha-Pekka Tolvanen

]]> 1624 0 https://cdn.slidesharecdn.com/ss_thumbnails/industrialexperiencesondomain-specificmodeling-140412104317-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://cdn.slidesharecdn.com/profile-photo-JuhaPekkaTolvanen-48x48.jpg?cb=1728413217 CEO of MetaCase and co-founder of the DSM Forum. Focused on model-driven approaches and tools, notably method engineering and metamodeling since 1991. Acted as a consultant world-wide for method development. Author of a book (www.dsmbook.com) and over 60 articles on model-based software development, recently in journals such as IEEE Software, ObjektSpektrum and Embedded Computing Design. Organizes the series of the OOPSLA workshops on Domain-Specific Modeling, Ph.D. in computer science from the University of Jyväskylä, Finland. Specialties: Model-based code generation, domain-specific modeling (DSM) languages, metamodeling, method engineering www.metacase.com/blogs/jpt/blogView https://cdn.slidesharecdn.com/ss_thumbnails/languagesfornon-developers-invitedkeynotefedcsis2024-240925101831-1a718ce3-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/languages-for-non-developers-invited-keynote-fedcsis-2024/272011482 Languages for non-deve... https://cdn.slidesharecdn.com/ss_thumbnails/whatgoeswrongwithlanguagedefinitionsandhowtoimprovethesituation-240510100056-a55337ac-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/what-goes-wrong-with-language-definitions-and-how-to-improve-the-situation/267979386 What Goes Wrong with L... https://cdn.slidesharecdn.com/ss_thumbnails/howtoformalizeaubiquitouslanguageintoadomain-specificlanguage-230303114047-5c6978bc-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/how-to-formalize-a-ubiquitous-language-into-a-domainspecific-languagepdf/256209616 How to formalize a ubi...