Meeting Minutes & Group Communication, Daren Welsh, SMWCon Fall 2014
SMWCon Fall 2015: SmartConnect (a SmartSuite extension)
19
SmartConnect Dr. Remco de Boer CTO @ XL&Knowledge [email protected] Consultant @ ArchiXL [email protected] SMWCon Fall 2015 Thursday, October 29 th 2015 Barcelona
-
Upload
remco-de-boer -
Category
Data & Analytics
-
view
283 -
download
0
Transcript of SMWCon Fall 2015: SmartConnect (a SmartSuite extension)
SmartConnect
Dr. Remco de Boer
CTO @ XL&Knowledge [email protected]
Consultant @ ArchiXL [email protected]
SMWCon Fall 2015
Thursday, October 29th 2015
Barcelona
2 2
Semantic MediaWiki in a modeling environment
• SmartConnect™ – Import content from other
environments
• SmartBooks™ – Export content to ODF, Microsoft
Word, PDF, ePub, text
• SmartCore™ – Maintain content structure
• SmartPublish™ – Publish selected content from closed
(development) environment to open (publication) environment
Interaction and integration: SmartSuite ™
Semantic wiki
Smar
tCon
nect
SmartBooks
SmartCore
SmartPublish
Semantic wiki
4 4
Example connectors
• SmartConnect for ARIS
• SmartConnect for Archi
• SmartConnect for ArchiMate
• SmartConnect for BiZZdesign Architect
• SmartConnect for BiZZdesigner
• SmartConnect for Sparx Enterprise Architect
5 5
Showcase SmartConnect™ for ARIS
SmartConnect pipeline
6 6
7 7
Some details
• Data export:
– Report in ARIS creates XML file and accompanying diagrams and metadata
– Special page in WikiXL platform import these files
• Pipeline architecture
– SmartConnect provides a pipeline architecture for transforming an export from another environment to a SmartCore structure
– Tasks performed by the pipeline:
• Reading in the export
• Filtering out unnecessary and/or unwanted elements
• Mapping and tranforming the source (ARIS) structure to the target (SmartCore) structure
• Importing the elements as wiki pages
– Each step in the pipeline can be tailored towards customer requirements
8 8
Pipeline architecture
• Why a pipeline?
– Started off as monolithic extensions
– Maintainability issues
– Customizability issues
– Modularization!
• Added benefits
– Chain of Responsibility (decoupled sender and receiver)
– Adaptable behavior (through interfaces and inheritance)
9 9
ARIS Model
10 10
ARIS Model
11 11
SmartCore object model, the basis for pipeline operations
12 12
The pipeline components explained: Step 1: Reader
13 13
The pipeline components explained: Step 2: Mapper
14 14
The pipeline components explained: Step 3: Postprocessor
15 15
The pipeline components explained: Step 4: Postfilter
16 16
The pipeline components explained: Step 5: Writer (wiki serialization)
{{#element: |Type=Process |Name=Determine communication method used for service request |GUID=8df946756… |Leads to=Telephone used for service request (Event) – ac55090a… }}
{{#element: |Type=Event |Name=Telephone used for service request |GUID= ac55090a… }}
17 17
Interesting challenges
• Technical:
– Page renames
– Deletions
– Partial exports / imports
– Bespoke model processing rules
• Procedural:
– Compliance with modeling guidelines
18 18
In conclusion
• SMW often does not run in isolation
• Most imports follow a similar set of operations
• Modularization takes advantage of these similarities
– Modular operations: pipeline
– Modular data: object model
• Future work:
– From import to export
– From model to metamodel (OWL ontology definitions to prime SMW?)
– From manual uploads to scheduled and real-time readers
– From SmartCore/SMW-writers to ‘any’ writer (not necessarily wiki)
– Semantic model validation?
19 19
