31st EUROMICRO Conference on Software Engineering and Advanced Applications
DOI: 10.1109/euromicro.2005.21
|View full text |Cite
|
Sign up to set email alerts
|

Developing Content-Intensive Applications with XML Documents, Document Transformations and Software Components

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(3 citation statements)
references
References 4 publications
0
3
0
Order By: Relevance
“…There are two kinds of game components: core rules, which roughly correspond to the small-step rules of the <e-Game> operational semantics, and GUI components, which implement interaction and presentation services for supporting the final presentation layer of the videogame. These components follow a common component model, which is an evolution of the model described in [37].…”
Section: Implementation Detailsmentioning
confidence: 99%
“…There are two kinds of game components: core rules, which roughly correspond to the small-step rules of the <e-Game> operational semantics, and GUI components, which implement interaction and presentation services for supporting the final presentation layer of the videogame. These components follow a common component model, which is an evolution of the model described in [37].…”
Section: Implementation Detailsmentioning
confidence: 99%
“…ADDS has been formulated and refined for several years [25] [43]. In [39][40] the approach was called DTC: structured Documents, document Transformations and software Components (see also [44] for an updated revision of DTC). It is important to notice that ADDS is not a development environment, but it is better thought of as a process model in the sense used in Software Engineering [45] (see [1] for the role of ADDS as a process model in the context of software comprehension).…”
Section: 1mentioning
confidence: 99%
“…In this way, OADDS is comparable to a transformation language like XSLT, which specifies the transformation mechanism, but does not specify the nature of the target document types. In our opinion this is not a disadvantage but a feature, because it allows many application models to be accommodated although we have not explicitly defined any of these models, outside of our earlier works on component-oriented DTC applications [44]. Therefore, in our experiments we have adopted ad hoc mechanisms to manage the evolution of the generated applications when the processor generating them evolves.…”
Section: Drawbacksmentioning
confidence: 99%