FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2469033296> ?p ?o ?g. }

• W2469033296 abstract "ion is built on the idea to remove irrelevant details in order to focus on the essential from the actual context. Conceptual abstraction means [28] “to replace low level concepts representing technical detail by more abstract concepts that are better suited to describe and study some aspects”. The essential part of a service, like most software applications, is the ability to perform logically and to handle information related to the service. For instance it is better to describe a “depositing cash” service using the UML language than the C programming language. The reference model for Open Distributed Processing (RM-ODP), has defined a different set of viewpoints: Enterprise, Information, Computation, Engineering, and Technology, where the three first viewpoints cover the functionality aspects, and Computational and Engineering cover Realization. The choice of concepts for the description of the functionality is dependent on the characteristic of the system to be described. Applications to be deployed in Service Network as described in chapter 1.1, which are characterized by communication between concurrently operating and physically distributed objects, are best described in terms of communicating state machines that encapsulate data. As shown in chapter 2, UML2.0 has those concepts needed to describe this type of functionality. There are different approaches [28] to the process of transforming the description of the functionality to a realization: • The elaboration approach where the functionality is described with informal or semi informal languages, and therefore the models are incomplete and not precise. Additional details have to be added by elaboration, during deployment and during realization. This is the most common approach in software engineering today also among those that use UML to describe the functionality. • The translation approach where the functionality is described completely and formally. The deployment description is kept orthogonally to the functional description to obtain transparency. There is also a trend against leaving out the deployment information for the deployment of a component. These two descriptions define the input to the realization, as such can the functionality Agder University College Conceptual approach to mapping of models Geir Melby Thesis modified 27.05.2003 43 survive technology and platform changes. The translation can be both automatic or manually. Model Driven Architecture (MDA) defined by OMG supports the translation approach. The PIM model is the functional description and the PSM describes both the implementation and the functionality aspects of the system. 5.2 Translation of models A common way to specify the deployment is to tag the different elements of a model. These tags are used by the translator to select the mapping rules that should be applied for each model element. There are two principle types of tags. • Platform specific tags where the different tags represent concepts in the realization platform. For instance if a J2EE platform is used, the tags can identify the different types of Enterprise java beans. This approach can be used with MDA. The PIM is defined with UML and it should be independent of the realization. If a J2EE platform shall be used in the realization, the different elements of an UML model should be tagged by stereotypes defined in a UML profile for this platform. The PIM model is then tailored with deployment information, which transforms the PIM model to PSM model. • Concepts specific tags where the tags represent concepts in the domain of interest. They normally do not tell anything about the realization, only which phenomenon it represents. How to realize these concepts, is part of the definition of the translator. So the translator has to be changed if the realization platform is changed. This approach is often called concept modeling. These concepts can also be defined as stereotypes. The stereotypes are used in the platform independent model as modeling elements. This is different from the use of realization-oriented concepts that are added to the PIM model. The differences between these two approaches are significant as shown in Figure 5-2. The figure describes the different approaches to transforming of platform independent UML models to an EJB platform using the Java programming language. When platform specific tags are used there are two complete models that each describe the functionality. The PIM is transformed to a PSM model by adding platform specific information to the PIM model. The PSM model is then transformed to an implementation using corresponding classes from the EJB java package. Conceptual approach to mapping of models Agder University College 44 Geir Melby Thesis modified 27.05.2003 UML model EJB java package EJB stereotyped model Implementation using EJB classes M od el in g" @default.
• W2469033296 created "2016-07-22" @default.
• W2469033296 creator A5065682764 @default.
• W2469033296 date "2003-01-01" @default.
• W2469033296 modified "2023-09-27" @default.
• W2469033296 title "Using J2EE technologies for implementation of ActorFrame based UML 2.0 models" @default.
• W2469033296 cites W185975986 @default.
• W2469033296 hasPublicationYear "2003" @default.
• W2469033296 type Work @default.
• W2469033296 sameAs 2469033296 @default.
• W2469033296 citedByCount "1" @default.
• W2469033296 crossrefType "dissertation" @default.
• W2469033296 hasAuthorship W2469033296A5065682764 @default.
• W2469033296 hasConcept C115903868 @default.
• W2469033296 hasConcept C136264566 @default.
• W2469033296 hasConcept C142362112 @default.
• W2469033296 hasConcept C145644426 @default.
• W2469033296 hasConcept C153349607 @default.
• W2469033296 hasConcept C162324750 @default.
• W2469033296 hasConcept C199360897 @default.
• W2469033296 hasConcept C2776035091 @default.
• W2469033296 hasConcept C2777904410 @default.
• W2469033296 hasConcept C2780378061 @default.
• W2469033296 hasConcept C41008148 @default.
• W2469033296 hasConceptScore W2469033296C115903868 @default.
• W2469033296 hasConceptScore W2469033296C136264566 @default.
• W2469033296 hasConceptScore W2469033296C142362112 @default.
• W2469033296 hasConceptScore W2469033296C145644426 @default.
• W2469033296 hasConceptScore W2469033296C153349607 @default.
• W2469033296 hasConceptScore W2469033296C162324750 @default.
• W2469033296 hasConceptScore W2469033296C199360897 @default.
• W2469033296 hasConceptScore W2469033296C2776035091 @default.
• W2469033296 hasConceptScore W2469033296C2777904410 @default.
• W2469033296 hasConceptScore W2469033296C2780378061 @default.
• W2469033296 hasConceptScore W2469033296C41008148 @default.
• W2469033296 hasLocation W24690332961 @default.
• W2469033296 hasOpenAccess W2469033296 @default.
• W2469033296 hasPrimaryLocation W24690332961 @default.
• W2469033296 hasRelatedWork W1041851187 @default.
• W2469033296 hasRelatedWork W1495524151 @default.
• W2469033296 hasRelatedWork W1527048478 @default.
• W2469033296 hasRelatedWork W1545796665 @default.
• W2469033296 hasRelatedWork W1550925250 @default.
• W2469033296 hasRelatedWork W1805562699 @default.
• W2469033296 hasRelatedWork W2004795023 @default.
• W2469033296 hasRelatedWork W2010173096 @default.
• W2469033296 hasRelatedWork W2069600217 @default.
• W2469033296 hasRelatedWork W2117600166 @default.
• W2469033296 hasRelatedWork W2150888487 @default.
• W2469033296 hasRelatedWork W2167363782 @default.
• W2469033296 hasRelatedWork W222707479 @default.
• W2469033296 hasRelatedWork W2293654010 @default.
• W2469033296 hasRelatedWork W2314596900 @default.
• W2469033296 hasRelatedWork W2331914920 @default.
• W2469033296 hasRelatedWork W2529802478 @default.
• W2469033296 hasRelatedWork W2968352956 @default.
• W2469033296 hasRelatedWork W3021671904 @default.
• W2469033296 hasRelatedWork W201855355 @default.
• W2469033296 isParatext "false" @default.
• W2469033296 isRetracted "false" @default.
• W2469033296 magId "2469033296" @default.
• W2469033296 workType "dissertation" @default.