0000000000178377
AUTHOR
Joshua Lubell
DEXML: A First Step Toward a UML Based Implementation Framework for PLCS
Data exchange specifications not only must be broad and general to achieve acceptance, but also must be customizable in a controlled and interoperable manner to be useful. The Product Life Cycle Support (PLCS) suite of data exchange specifications (known as DEXs) uses templates to enable controlled customizability without sacrificing breadth or interoperability. DEXs are business context-specific subsets of ISO 10303 Application Protocol (AP) 239, subject to additional constraints imposed by the templates. A PLCS template defines how AP239 entities and their attributes will be instantiated using an externally-defined controlled vocabulary defined in a Reference Data Library. Template instan…
Toward a Reference Architecture for Archival Systems
Long-term preservation of product data is imperative for many organizations. A product data archive should be designed to ensure information accessibility and understanding over time. Approaches such as the Open Archival Information System (OAIS) Reference Model and the Audit and Certification of Trustworthy Digital Repositories (ACTDR) provide a framework for conceptually describing and evaluating archives. These approaches are generic and do not focus on particular contexts or content types. Enterprise architecture provides a way to describe systems in their potentially complex environments.
Towards a Reference Architecture for Archival Systems: Use Case With Product Data
Long-term preservation of product data is imperative for many organizations. A product data archive should be designed to ensure information accessibility and understanding over time. Approaches, such as the Open Archival Information System Reference Model (OAIS RM) and the Audit and Certification of Trustworthy Digital Repositories (ACTDR), provide a framework for conceptually describing and evaluating archives. These approaches are generic and do not focus on particular contexts or content types such as product data. Moreover, these approaches offer no guidance on how to formally and comprehensively describe archival systems. Such descriptions should include the business activities that a…