Versioning of Topic Map Templates Structuring Versioning and - PowerPoint PPT Presentation

Versioning of TM Templates and Scalability M. Ueberall, O. Drobnik Introduction Versioning of Topic Map Templates Structuring Versioning and Scalability Scalability Proc. Model Ongoing Work M. Ueberall, O. Drobnik Telematics Group, Institute of Computer Science J. W. Goethe-University, Frankfurt/Main, Germany 2007 / 10 / 12

Versioning of TM Templates Motivation and Objective and Scalability M. Ueberall, O. Drobnik Introduction • Problems in the context of software development Structuring processes: Versioning • participants use concepts from different knowledge Scalability domains → information overflow Proc. Model • insufficient communications → traceability deficits Ongoing Work • Our approach is based on • Templates consisting of Topic Map Objects → lightweight representation • version management → traceability • meta process model → communications support • role-based filtering → scalability

Versioning of TM Templates (Nested) Templates and Scalability M. Ueberall, Example O. Drobnik Introduction Structuring Versioning Semi-formal Representation Use Case Scalability (Template containing Topic Map Objects) <<actor>> BookingSystem Proc. Model Name ... Ongoing Work UseCase FlightBooking Actor ... Book flight Precondition ... Action ... Postcondition ... Customer Name: Customer Type: Person Description: ...

Versioning of TM Templates (Nested) Templates and Scalability M. Ueberall, Nesting Example O. Drobnik Introduction Structuring Versioning Semi-formal Representation Use Case Scalability (Template containing Topic Map Objects) <<actor>> BookingSystem Proc. Model Name ... Ongoing Work UseCase FlightBooking Name: Customer Book flight Type: Person Actor ... Description: ... Precondition ... Customer Action ... Postcondition ... Name: Customer Type: Person Description: ...

Versioning of TM Templates Usage Restrictions for Templates and Scalability M. Ueberall, Constraints in LTM notation O. Drobnik Introduction Structuring Versioning [person : topic-type = "Person"] Scalability [age : occurrence-type = "Age" = "Person’s Age" /person ~toc1] Proc. Model Ongoing Work [toc1 : topic-occurrence-constraint = "Topic Occurrence Constraint Label for Occurrence ’Age’"] {toc1, max-cardinality, [[1]]} • embedded constraints as opposed to linked/embedded schemas allow for unified handling of versioning

Versioning of TM Templates Faceted Classification and Scalability M. Ueberall, Browser Example O. Drobnik Introduction Structuring Versioning Scalability Proc. Model Ongoing Work

Versioning of TM Templates Faceted classification and Scalability M. Ueberall, LTM notation (1) O. Drobnik Introduction Structuring // cf. [Ahmed2003] (Proc. Extreme Markup Languages) Versioning #PREFIX tmhd @"http://www.techquila.com/psi/hierarchy/#" Scalability #PREFIX tmtd @"http://www.techquila.com/psi/thesaurus/#" Proc. Model #PREFIX tmfd @"http://www.techquila.com/psi/ faceted-classification /#" Ongoing Work [all-templates : tmfd:facet = "Set of all Templates"] [template-facet : tmfd:facet = "Template Facet"] tmfd:facet-has-hierarchy-type(template-facet : tmfd:facet, tmfd:subcategory-supercategory : tmfd:facet-hierarchy-type) tmfd:facet-has-root(template-facet : tmfd:facet, all-templates : tmfd:facet-root)

Versioning of TM Templates Faceted classification and Scalability M. Ueberall, LTM notation (2) O. Drobnik Introduction Structuring // taken from the UML Superstructure specification, cf. [UD06] Versioning [actor : template-class = "Actor"] Scalability Proc. Model tmfd:subcategory-supercategory(actor : tmhd:subcategory, Ongoing Work all-templates : tmhd:supercategory) tmfd:subcategory-supercategory(person : tmhd:subcategory, actor : tmhd:supercategory) tmfd:subcategory-supercategory(legal-entity : tmhd:subcategory, actor : tmhd:supercategory) tmtd:part-whole(actor : tmtd:whole, role : tmtd:part) tmtd:part-whole(person : tmtd:whole, age : tmtd:part)

Versioning of TM Templates Versioning and Scalability M. Ueberall, Example: Proxy Design Pattern O. Drobnik uses Introduction Service Client action() Structuring V1 V1 Versioning Service- Scalability Annotation V1 Proc. Model Ongoing Work

Versioning of TM Templates Versioning and Scalability M. Ueberall, Example: Proxy Design Pattern O. Drobnik uses Introduction Service Client action() Structuring V1 V1 Versioning Service- Scalability decoupling Annotation V1 Proc. Model Ongoing Work «interface» uses ServiceIF Client action() ... V1 V1 Client- Annotation V1 V1 V2 ServiceProxy Service action() action() Service- Annotation V1

Versioning of TM Templates Versioning and Scalability M. Ueberall, Granularity of Objects O. Drobnik Introduction Structuring Name ... Name ... Versioning UseCase FlightBooking UseCase FlightBooking Scalability Description Description Statement A Statement B Description1 Statement A Proc. Model Statement C Description2 Statement B Ongoing Work Precondition ... Description3 Statement C Action ... Precondition ... Postcondition ... Action ... Postcondition ... • rule-of-thumb: any statement which is explicitly referenced has to be reified • ordering accomplishable by means of “sortkey” concept, cf. [Grønmo93]

Versioning of TM Templates Versioning and Scalability M. Ueberall, Metadata for Units of Information, LTM notation O. Drobnik Introduction // <occurrence | association> ~object-ref Structuring Versioning Scalability // dc: cf. http://dublincore.org/documents/dces (Dublin Core) Proc. Model { object-ref , dc:creation-date, [[2007-06-04T2359:59+01:00]]} Ongoing Work { object-ref , dc:version, [[ version-id ]]} { object-ref , dc:author, [[ user-id ]]} // skos: cf. http://w3.org/2004/02/skos (SKOS) { object-ref , skos:changeNote, [[ description ]]} ... is-replaced-by( object-ref 1 :old-obj, object-ref 2 :new-obj) is-deprecated( object-ref 3 :obj) is-deleted( object-ref 4 :obj)

Versioning of TM Templates Versioning and Scalability and Scalability M. Ueberall, Software Development Scenario O. Drobnik Introduction Phases / Artefacts Information Flow Visualisations Structuring domain specific forms-based Versioning Requirements Analysis Phase Annotation Flight UseCase FlightBooking Scalability Precond. ... Status: . . . - Use Cases extends Postcond. ... FlightBooking Depend. ... - Business Cases Proc. Model Conflicts ... Actors ... PrintTicket Requirem. High-availability Ongoing Work Design Phase DesignPatt. Proxy «interface» Purpose Comm. Decoupling - Architectural Patterns uses Client ServiceIF Status: . . . Synonyms ... action() - Design Patterns Uses ... ... Structure ... Depend. ... Annot ation Conflicts ... Implementation Phase Annotation Implement. TicketingService - Packages Precond. ... Postcond. ... - Classes Depend. ... Conflicts ... - Code Status: . . . DesignPatt. Proxy , ... Package 1 Package 2 Uses ...

Versioning of TM Templates Versioning and Scalability and Scalability M. Ueberall, Software Development Scenario O. Drobnik Introduction Phases / Artefacts Information Flow Visualisations Structuring domain specific forms-based Versioning Requirements Analysis Phase Annotation Flight UseCase FlightBooking Scalability Precond. ... Status: . . . - Use Cases extends Postcond. ... FlightBooking Depend. ... - Business Cases Proc. Model Conflicts ... Actors ... PrintTicket Requirem. High-availability Ongoing Work Design Phase «interface» uses Client ServiceIF action() DesignPatt. Proxy ... Decision: Use of Purpose Comm. Decoupling - Architectural Patterns Synonyms ... proxy pattern for - Design Patterns Annot Uses ... ation client-server comm. Structure ... Depend. ... ServiceProxy Service Conflicts ... action() action() Implementation Phase Annotation Implement. TicketingService - Packages Precond. ... Postcond. ... - Classes Depend. ... Conflicts ... - Code Status: . . . DesignPatt. Proxy , ... Package 1 Package 2 Uses ...