Domain-specific multimodeling (original) (raw)
Domain-specific multimodeling is a software development paradigm where each view is made explicit as a separate domain-specific language (DSL). Successful development of a modern enterprise system requires the convergence of multiple views. Business analysts, domain experts, interaction designers, database experts, and developers with different kinds of expertise all take part in the process of building such a system. Their different work products must be managed, aligned, and integrated to produce a running system. Every participant of the development process has a particular language tailored to solve problems specific to its view on the system. The challenge of integrating these different views and avoiding the potential cacophony of multiple different languages is the coordination prob
| Property | Value |
|---|---|
| dbo:abstract | Domain-specific multimodeling is a software development paradigm where each view is made explicit as a separate domain-specific language (DSL). Successful development of a modern enterprise system requires the convergence of multiple views. Business analysts, domain experts, interaction designers, database experts, and developers with different kinds of expertise all take part in the process of building such a system. Their different work products must be managed, aligned, and integrated to produce a running system. Every participant of the development process has a particular language tailored to solve problems specific to its view on the system. The challenge of integrating these different views and avoiding the potential cacophony of multiple different languages is the coordination problem. Domain-specific multimodeling is promising when compared to more traditional development paradigms such as single-language programming and general-purpose modeling. To reap the benefits of this new paradigm, we must solve the coordination problem. This problem is also known as the fragmentation problem in the context of Global Model Management. One proposal to solve this problem is the coordination method. This is a three-step method to overcome the obstacles of integrating different views and coordinating multiple languages. The method prescribes how to (1) identify and (2) specify the references across language boundaries, that is the overlaps between different languages. Finally, the method offers concrete proposals on how to (3) apply this knowledge in actual development in the form of consistency, navigation, and guidance. (en) |
| dbo:thumbnail | wiki-commons:Special:FilePath/CreateSurvey-screen.png?width=300 |
| dbo:wikiPageExternalLink | http://ofbiz.apache.org/ https://web.archive.org/web/20100902033523/http:/ralyx.inria.fr/2006/Raweb/atlas/uid26.html |
| dbo:wikiPageID | 21468960 (xsd:integer) |
| dbo:wikiPageLength | 30912 (xsd:nonNegativeInteger) |
| dbo:wikiPageRevisionID | 1050035751 (xsd:integer) |
| dbo:wikiPageWikiLink | dbr:Enterprise_resource_planning dbr:Primary_key dbr:User_interface dbr:General-purpose_modeling dbr:Electronic_commerce dbr:Enterprise_system dbr:Content_management dbc:Software_development_process dbr:Top-down_and_bottom-up_design dbr:Domain-specific_language dbr:Domain-specific_modeling dbr:DHIS dbr:Extensible_Markup_Language dbr:Legacy_system dbr:Referential_integrity dbr:Java_Database_Connectivity dbr:Portable_Document_Format dbr:Abstract_syntax_tree dbc:Programming_language_topics dbr:Well-formed_element dbr:Business_object dbr:Business_rules_engine dbr:Empirical_studies dbr:Integrated_development_environment dbr:Health_care_system dbr:Model-driven_engineering dbr:Scripting_language dbr:Enterprise_JavaBean dbr:Model_(abstract) dbr:File:CreateSurvey-screen.png dbr:File:Method.png dbr:File:SurveyDatabase-visio.png |
| dbp:wikiPageUsesTemplate | dbt:Short_description |
| dct:subject | dbc:Software_development_process dbc:Programming_language_topics |
| rdf:type | yago:Abstraction100002137 yago:Communication100033020 yago:Message106598915 yago:Subject106599788 yago:WikicatProgrammingLanguageTopics |
| rdfs:comment | Domain-specific multimodeling is a software development paradigm where each view is made explicit as a separate domain-specific language (DSL). Successful development of a modern enterprise system requires the convergence of multiple views. Business analysts, domain experts, interaction designers, database experts, and developers with different kinds of expertise all take part in the process of building such a system. Their different work products must be managed, aligned, and integrated to produce a running system. Every participant of the development process has a particular language tailored to solve problems specific to its view on the system. The challenge of integrating these different views and avoiding the potential cacophony of multiple different languages is the coordination prob (en) |
| rdfs:label | Domain-specific multimodeling (en) |
| owl:sameAs | freebase:Domain-specific multimodeling yago-res:Domain-specific multimodeling wikidata:Domain-specific multimodeling dbpedia-sr:Domain-specific multimodeling https://global.dbpedia.org/id/4iv4p |
| prov:wasDerivedFrom | wikipedia-en:Domain-specific_multimodeling?oldid=1050035751&ns=0 |
| foaf:depiction | wiki-commons:Special:FilePath/Method.png wiki-commons:Special:FilePath/CreateSurvey-screen.png wiki-commons:Special:FilePath/SurveyDatabase-visio.png |
| foaf:isPrimaryTopicOf | wikipedia-en:Domain-specific_multimodeling |
| is dbo:wikiPageRedirects of | dbr:Domain-Specific_Multimodeling |
| is dbo:wikiPageWikiLink of | dbr:Metalinguistic_abstraction dbr:Comparison_of_multi-paradigm_programming_languages dbr:Domain-Specific_Multimodeling dbr:Domain-specific_modeling dbr:Domain-driven_design dbr:Model-driven_engineering |
| is foaf:primaryTopic of | wikipedia-en:Domain-specific_multimodeling |
