Research Papers

Towards a Reference Architecture for Archival Systems: Use Case With Product Data

[+] Author and Article Information
Raphael Barbau

Le2i, Université de Bourgogne,
BP 47870, 21078 Dijon, France;
Systems Integration Division,
National Institute of Standards and Technology,
Gaithersburg, MD 20899

Joshua Lubell, Sudarsan Rachuri

Systems Integration Division,
National Institute of Standards and Technology,
Gaithersburg, MD 20899

Sebti Foufou

CSE Department,
CENG, Qatar University,
Doha, Qatar;
Le2i, Université de Bourgogne,
BP 47870, 21078 Dijon, France

1Corresponding author.

This material is declared a work of the U.S. government and is not subject to copyright protection in the United States. Approved for public release; distribution is unlimited.Contributed by the Computers and Information Division of ASME for publication in the JOURNAL OF COMPUTING AND INFORMATION SCIENCE IN ENGINEERING. Manuscript received February 10, 2014; final manuscript received February 25, 2014; published online April 28, 2014. Editor: Bahram Ravani.

J. Comput. Inf. Sci. Eng 14(3), 031005 (Apr 28, 2014) (12 pages) Paper No: JCISE-14-1046; doi: 10.1115/1.4027150 History: Received February 10, 2014; Revised February 25, 2014

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 product data archive has to support and the systems that interact with the archive. Enterprise architecture provides a means to describe systems in their potentially complex environments. This paper proposes a holistic approach to formally describe the architecture and the environment of archival systems. This approach relies on the formal representation of the preservation terminology, including OAIS concepts, using the Department of Defense Architecture Framework (DoDAF). The approach covers the various interactions of other business functions with the archive and the information models necessary to ensure preservation and accessibility of product data. This approach is a step towards a reference architecture for the formal description of archival systems. To demonstrate the approach, we formally describe the ingest of product data related to a ship. The resulting description uses the preservation terminology defined in the OAIS Reference Model. It facilitates the understanding of how the preservation solution is actually implemented and provides evidence that the solution is able to preserve product data and make it accessible.

U.S. Government
Topics: Preservation
Your Session has timed out. Please sign back in to continue.



Grahic Jump Location
Fig. 1

OAIS functional model

Grahic Jump Location
Fig. 2

Presentation of the approach

Grahic Jump Location
Fig. 3

Notation used for stereotypes

Grahic Jump Location
Fig. 4

Extension of ExchangeElement

Grahic Jump Location
Fig. 5

Extension of EntityItem

Grahic Jump Location
Fig. 6

Extension of nodes

Grahic Jump Location
Fig. 7

Extension of operational activities

Grahic Jump Location
Fig. 8

Extension of services

Grahic Jump Location
Fig. 9

Extension of function

Grahic Jump Location
Fig. 10

Extension of constraints

Grahic Jump Location
Fig. 11

Extension of standards

Grahic Jump Location
Fig. 12

3D representation of a fuel oil system

Grahic Jump Location
Fig. 13

OV-2 view for ingest and access of product data

Grahic Jump Location
Fig. 14

DIV-1 view of the LEAPS SIP

Grahic Jump Location
Fig. 15

DIV-1 view of generic product metadata

Grahic Jump Location
Fig. 16

Generic product metadata for a particular CAD file

Grahic Jump Location
Fig. 17

DIV-1 view of conceptual metadata for LEAPS information

Grahic Jump Location
Fig. 18

LEAPS information related to a part

Grahic Jump Location
Fig. 19

DIV-1 view of conceptual metadata for CAD files

Grahic Jump Location
Fig. 20

CAD metadata related to a part

Grahic Jump Location
Fig. 21

StdV-1 view of formats used in the SIP

Grahic Jump Location
Fig. 22

Ingest activity (OV-5b)

Grahic Jump Location
Fig. 23

Ingest and access rules (OV-6a)

Grahic Jump Location
Fig. 24

Sequence diagram of the ingest scenario (OV-6c)




Some tools below are only available to our subscribers or users with an online account.

Related Content

Customize your page view by dragging and repositioning the boxes below.

Related Journal Articles
Related eBook Content
Topic Collections

Sorry! You do not have access to this content. For assistance or to subscribe, please contact us:

  • TELEPHONE: 1-800-843-2763 (Toll-free in the USA)
  • EMAIL: asmedigitalcollection@asme.org
Sign In