<efrbr:recordSet xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:efrbr="http://vfrbr.info/efrbr/1.1" xmlns:efrbr-work="http://vfrbr.info/efrbr/1.1/work" xmlns:efrbr-expression="http://vfrbr.info/efrbr/1.1/expression" xmlns:efrbr-manifestation="http://vfrbr.info/efrbr/1.1/manifestation" xmlns:efrbr-person="http://vfrbr.info/efrbr/1.1/person" xmlns:efrbr-corporateBody="http://vfrbr.info/efrbr/1.1/corporateBody" xmlns:efrbr-concept="http://vfrbr.info/efrbr/1.1/concept" xmlns:efrbr-structure="http://vfrbr.info/efrbr/1.1/structure" xmlns:efrbr-responsible="http://vfrbr.info/efrbr/1.1/responsible" xmlns:efrbr-subject="http://vfrbr.info/efrbr/1.1/subject" xmlns:efrbr-other="http://vfrbr.info/efrbr/1.1/other" xsi:schemaLocation="http://vfrbr.info/efrbr/1.1 http://vfrbr.info/schemas/1.1/efrbr.xsd"><efrbr:entities><efrbr-work:work identifier="http://purl.tuc.gr/dl/dias/A5868D55-820A-4195-A6A0-EB4A15E67490"><efrbr-work:titleOfTheWork>UTML: Unified Transaction Modeling Language</efrbr-work:titleOfTheWork></efrbr-work:work><efrbr-expression:expression identifier="http://purl.tuc.gr/dl/dias/A5868D55-820A-4195-A6A0-EB4A15E67490"><efrbr-expression:titleOfTheExpression>UTML: Unified Transaction Modeling Language</efrbr-expression:titleOfTheExpression><efrbr-expression:formOfExpression vocabulary="DIAS:TYPES">
            Πλήρης Δημοσίευση σε Συνέδριο
            Conference Full Paper
         </efrbr-expression:formOfExpression><efrbr-expression:dateOfExpression type="issued">2015-10-05</efrbr-expression:dateOfExpression><efrbr-expression:dateOfExpression type="published">2002</efrbr-expression:dateOfExpression><efrbr-expression:languageOfExpression vocabulary="iso639-1">en</efrbr-expression:languageOfExpression><efrbr-expression:summarizationOfContent>We propose UTML as a high level transaction modeling
language to facilitate the complex web transaction design
process. Web transactions may be complex, composed of
several sub-transactions and they may access resources
with diverse behavior and interfaces like legacy systems
and databases. They may also have complex semantics.
Thus, transaction design methodologies and tools need to
be very flexible allowing for designing web applications
from scratch (top-down design), as well as using existing
systems or services to compose new applications which
offer added-value services (bottom-up design) to the user.
UTML is based on a transaction meta-model, which can
describe, in a flexible and extensible manner, most of the
known transaction models as well as new ones according
to the application’s requirements. It provides modeling for
transactions that incorporate different behavioral
patterns, and it is capable to describe activities with
weaker transactional semantics that they do not have all
the ACID properties. Unlike other models, it can be used
to synthesize new transactions from pre-existing
transaction systems (like legacy systems), with diverse
transactional semantics. UTML provides a rich notation to
visualize the transaction design process. This notation has
been built on top of UML using its extension mechanisms</efrbr-expression:summarizationOfContent><efrbr-expression:useRestrictionsOnTheExpression type="creative-commons">http://creativecommons.org/licenses/by/4.0/</efrbr-expression:useRestrictionsOnTheExpression><efrbr-expression:note type="page range">115-126</efrbr-expression:note><efrbr-expression:note type="conference name">3rd International Conference on Web Information Systems Engineering</efrbr-expression:note><efrbr-expression:note type="proceedings title">Proceedings Of The Third International Conference On Web Information Systems Engineering</efrbr-expression:note></efrbr-expression:expression><efrbr-person:person identifier="http://users.isc.tuc.gr/~schristodoulakis"><efrbr-person:nameOfPerson vocabulary="TUC:LDAP">
            Christodoulakis Stavros
            Χριστοδουλακης Σταυρος
         </efrbr-person:nameOfPerson></efrbr-person:person><efrbr-person:person identifier="http://users.isc.tuc.gr/~ngioldasis"><efrbr-person:nameOfPerson vocabulary="TUC:LDAP">
            Gioldasis Nektarios
            Γιολδασης Νεκταριος
         </efrbr-person:nameOfPerson></efrbr-person:person><efrbr-corporateBody:corporateBody identifier="http://www.ieee.org/index.html"><efrbr-corporateBody:nameOfTheCorporateBody vocabulary="S/R:PUBLISHERS">
            Institute of Electrical and Electronics Engineers
         </efrbr-corporateBody:nameOfTheCorporateBody></efrbr-corporateBody:corporateBody><efrbr-concept:concept identifier="D28D316E-CCC9-4FF2-8616-54C47B894A31"><efrbr-concept:termForTheConcept>
            Unified modeling language
         </efrbr-concept:termForTheConcept></efrbr-concept:concept></efrbr:entities><efrbr:relationships><efrbr-structure:structureRelations><efrbr-structure:realizedThrough sourceEntity="work" sourceURI="http://purl.tuc.gr/dl/dias/A5868D55-820A-4195-A6A0-EB4A15E67490" targetEntity="expression" targetURI="http://purl.tuc.gr/dl/dias/A5868D55-820A-4195-A6A0-EB4A15E67490"/></efrbr-structure:structureRelations><efrbr-responsible:responsibleRelations><efrbr-responsible:createdBy sourceEntity="work" sourceURI="http://purl.tuc.gr/dl/dias/A5868D55-820A-4195-A6A0-EB4A15E67490" targetEntity="person" targetURI="http://users.isc.tuc.gr/~schristodoulakis"/><efrbr-responsible:realizedBy sourceEntity="expression" sourceURI="http://purl.tuc.gr/dl/dias/A5868D55-820A-4195-A6A0-EB4A15E67490" targetEntity="person" targetURI="http://users.isc.tuc.gr/~schristodoulakis" role="author"/><efrbr-responsible:realizedBy sourceEntity="expression" sourceURI="http://purl.tuc.gr/dl/dias/A5868D55-820A-4195-A6A0-EB4A15E67490" targetEntity="person" targetURI="http://users.isc.tuc.gr/~ngioldasis" role="author"/><efrbr-responsible:realizedBy sourceEntity="expression" sourceURI="http://purl.tuc.gr/dl/dias/A5868D55-820A-4195-A6A0-EB4A15E67490" targetEntity="person" targetURI="http://www.ieee.org/index.html" role="publisher"/></efrbr-responsible:responsibleRelations><efrbr-subject:subjectRelations><efrbr-subject:hasSubject sourceEntity="work" sourceURI="http://purl.tuc.gr/dl/dias/A5868D55-820A-4195-A6A0-EB4A15E67490" targetEntity="concept" targetURI="D28D316E-CCC9-4FF2-8616-54C47B894A31"/></efrbr-subject:subjectRelations><efrbr-other:otherRelations/></efrbr:relationships></efrbr:recordSet>