Message-ID: <24972743.13898.1411439544599.JavaMail.confluence@ece-vmapps> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_13897_265897450.1411439544598" ------=_Part_13897_265897450.1411439544598 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Content Capture is Drupal; this is the source of truth until all= content modelling is complete. UML Class Model is EA, which becomes the so= urce of truth once the content modelling is finished and been OK'd by the f= irst review with the modelling team. Drupal must always be kept in synch wi= th EA - this means we need to update packages for each object in library, a= nd any other changes.
1. Achim to take issues 5 and 6, and get XSLTs, mapping docs, and issues= list(s) up on Wiki
2. Exploration of XMI and EA documentation flows in and out - can EA/XMI= handle inline DocBook?
3. Table issues 1, 2, 7, 9, 10, and 11 for now.
4. Based on outcome of step 2, address the documentation-related issues = (3, 4, and 8): h= ttp://www.eadocx.com/
5. XMI export from Drupal seems dodgy - investigate!
Goal for this week is to do a prototype production run on some p= art of the model, to test the process!=20
Note that we should use not Drupal IDs, but UUIDs. We can round-trip non= -EA IDs using a custom attribute in the XMI, and EA will not eat them. The = idea is to have Drupal generate a UUID on export, embed it into the XMI slu= rped up by EA. This can be safely exported from EA for a later merge with D= ocBook coming straight out of Drupal.
Olof is fixing this according to the solution Achim identified. Get docu= mentation from Achim, and explore UUID approach with Olof.=20
Given the process decision to do all modelling in Drupal, modelers will = clean up package locations and object dupliucations before export to EA for= the immediate term - issue closed=20
Issue 3, Disscussion:
We need diagrams for documenting the model deliverables. We have several= deliverables here:
(1) The model of the entire library
a. Show the packages in the library and their relations
b. Show the objects in each package
c. Show each object and its directly related objects (like clickable GSI= M)
(2) For each view
a. A diagram of all the objects in the view
b. A diagram for each object (same as 1. c)
The library contains a package for each view (in UML terms, views are ju= st packages). There are also non-view packages in the library. Different ty= pes of packages should be given different colors=20
We need the Drupal XMI export to be modified, to include: Diagrams (as X= MI Extensions) and documentation (as XMI Extensions). Also, we should embed= the Drupal IDs into the XMI as per Achim's earlier test. This documentatio= n will - tken from the EA export - be used to populate the XSD Documentatio= n elements (two forms: one with forma tags stripped out, one with format ta= gs still in, for use in the XSD HTML documentation tool used for DDI Lifecy= cle). Set up form for high-level documentation for authoring in Drupa= l. See the Roadmap for Production Process document - issue closed=20
We think this is already on Drupal - check with Olof=20
Closed - to be tested as part of prototype=20
Drupal: Johanna Vompras, Jannik Jensen. Olof - to be followed up n= ext week at IASSIST=20
Drupal updated to include formal mappings of equivalent objects to exter= nal namespaces - issue closed=20
DDI4 is the Model
The Model is divided into:
The Library is made of UML Packages
Primitives and Extende= d Primitives are Objects
Extended Primitives ar= e based (specify) on Primitives
Functional Views are also UML Packages and are made of references to Obj= ects of the Library or constraints applied to Objects of the Library. A Fun= ctional View cannot be included in another.
This is a revised list of what products will be released:
Note that this is a list of technical deliverables - #1 is the most comp= rehensive and authoritative document from a standards perspective. From a c= ommunications perspective, the views will likely be more important, since t= he deliverables around the whole model are intended for those making their = own views.