1 / 14

Conceptual XML for Systems Analysis

Conceptual XML for Systems Analysis. Reema Al-Kamha Spring Research Conference. Supported by NSF. Motivation. Since: XML becoming standard for data representation XML Schema to specify and validate XML documents Thus,

masseyj
Download Presentation

Conceptual XML for Systems Analysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Conceptual XML for Systems Analysis Reema Al-Kamha Spring Research Conference Supported by NSF

  2. Motivation Since: • XML becoming standard for data representation • XML Schema to specify and validate XML documents Thus, Systems analysts who store their models using XML need a simple conceptual model that works with XML-based development

  3. Motivation • XML Schema • Low-level implementation details • Hierarchical structure • Textual implementation • Conceptual models

  4. Conceptual XML (C-XML) • We have an answer to the new need of XML system analysts! • Conceptual XML (C-XML) is a conceptual model: • “Model-equivalent” with XML Schema • Represents the model at a high level of abstraction • Example of usefulness: integration of XML repositories

  5. C-XML

  6. Transformations between C-XML and XML Schema • We need information- and constraint-preserving transformations in both directions • Transformations need not be inverses

  7. Transformation from C-XML to XML Schema 8: <xs:element name="Item"> 9: <xs:complexType> ... 28: <xs:attribute name="ItemNr" type="xs:positiveInteger" use="required"/> 29: <xs:attribute name="Description" type="xs:string" use="required"/> 30: <xs:attribute name="Price" type="xs:decimal" use="required"/> 31: </xs:complexType> 32: </xs:element> (Customer,CustomerName,CustomerAddr,Discount, (Order, OrderID, OrderDate, (Item, SalePrice, Qty)* )* )* (Item, ItemNr, Description,Price, (PreviousItem)*,(Manufacturer,RequestDateTime,Qty)* )*

  8. Transformation from XML Schema to C-XML Algorithm overview: • Generate object sets for each element, attribute • Connected by relationship sets • Nested according to XML hierarchy • Re-code all constraints in C-XML 56: <xs:group name=“CusomerDetails”> 57: <xs:sequence> ... 60: <xs:element name="Order" minOccurs="0" maxOccurs="unbounded"> ... 77: </xs:seuence> 78: </xs:group>

  9. Artifact of XML Schema Artifact of XML nesting n-ary relationship decomposition Transformation from XML Schema to C-XML

  10. Integrated C-XML model instance Transform C-XML1 instance C-XML2 instance Transform Transform XML Schema1 XML Schema2 Integrated XML Schema Integration Integrated XML Schema

  11. Integration

  12. Customer Consumer CustomerDetails ConsumerDetails CustomerName ID CustomerAddr Name Order Addr OrderID Order OrderDate ID-Nr Month Day Year Integration

  13. Integration

  14. Contributions • A vision for applying conceptual modeling to support the need of XML systems analysts • A framework to support the vision • Information- and constraint-preserving mappings between C-XML and XML Schema • Conceptual-level integration indeed properly provides for XML schema integration

More Related