A method for the development of Dublin Core Application Profiles (Me4DCAP V0.2): detailed description

Agenda Introduction Me4DCAP V0.2 Future Work The End
Me4DCAP V0.2: A method for the development of Dublin
Core Application Profiles
Mariana Curado Malta & Ana Alice Baptista
Algoritmi Center, University of Minho
mariana.malta@algoritmi.uminho.pt
analice@dsi.uminho.pt
DC-2013, Lisbon - Portugal - Sep 2013
This project is financed with FEDER funds by the Programa Operacional Fatores de Competitividade – COMPETE
and by Portuguese National Funds through FCT – Funda¸cão para a Ciência e Tecnologia for the project:
FCOMP-01-0124-FEDER-022674
Mariana Malta & Ana Alice Baptista
Me4DCAP V0.2: A method for the development of Dublin Core Application Profiles

Introduction
Me4DCAP V0.2
Future Work

DCAP
DCMI created new instruments with a goal: to speak a
common language
Dublin Core Abstract Model (DCAM): a model developed for
DCMI syntax speciﬁcations
presents the components and constructs used in DCMI
databases
one of them is the Dublin Core Application Proﬁles (DCAP)
A DCAP is a generic construct for designing metadata
records

Research Problem
A DCAP development is a complex task
it needs an adequate support
A study we have performed (Curado Malta & Baptista,
2013b) shows that:
(to the best of our knowledge)
there is no method for the development of DCAP only
documents with some thoughts on how the process should be

Research Problem
A DCAP development is a complex task
it needs an adequate support
A study we have performed (Curado Malta & Baptista,
2013b) shows that:
(to the best of our knowledge)
there is no method for the development of DCAP only
documents with some thoughts on how the process should be
It is imperative to have such a method

Research Methodology
Design Science Research (DSR)
DSR aims at the development of innovative artifacts that
solve real-world problems (Simon, 1996)
Our artifact is a method: A method for the development
of DCAP (Me4DCAP)
Our project uses Hevner’s (2007) DSR framework

Take a deep breath....
... here we go!

Starting point
A DCAP is defined in the “Singapore Framework for Dublin Core
Application Profiles” - Baker et al. (2008)
Functional Requirements (Mandatory)
Domain Model (Mandatory)
Description Set Profile (Mandatory)
Usage guidelines (optional)
Encoding Syntax guidelines (optional)
The development of a DCAP is a process by stages

Introduction
Me4DCAP deﬁnes:
The composition of the work-team and
... the type of work each work-team-member should do
The process workﬂow
The deliverables at every stage
The techniques used to develop those deliverables

Deliverables Workﬂow

Work-Team
The work-team should have at least one person of each of the
folowing proﬁles:
Project Manager: has a scope vision of the organisations and
of the goals they want to achieve with the DCAP
System Analyst: has technical skills in data modeling and in
requirements elicitation
Integrator: understands the Semantic Web concepts
Final User: works with the Web System that will be using the
DCAP in development

Glossary
A Glossary should be developed during the whole process
development
It is a very important deliverable because of the
multidisciplinarity of the work-team
A Glossary is a text document with the keywords (and its
description) used in the process
All work-team members should contribute to the Glossary

Functional Requirements
To build the Functional Requirements Me4DCAP obliges the
development of the following deliverables:
Work-Plan: time planning of the project activities (e.g a
Gantt Chart) (all team; Project Manager leads)

Vision Statement: shows what developers want to reach
with the DCAP development; it deﬁnes the scope of the
DCAP(all team; Project Manager leads)

Vision Statement: shows what developers want to reach
with the DCAP development; it deﬁnes the scope of the
DCAP(all team; Project Manager leads)
Expression of Functional Requirements: a list of the
Functional Requirements Expressed by the work-team - very
short description per Functional Requirement (all team; System analyst
leads)
(continues...)

(Continued from last page...)
Use-Cases Model. It is composed by:
the UML Use-Cases diagrams with the actors that interact in
the Use-Cases
the set of all detailed Use-Cases: the sequence of actions.
(all team; System analyst leads)

(Continued from last page...)
Use-Cases Model. It is composed by:
the UML Use-Cases diagrams with the actors that interact in
the Use-Cases
the set of all detailed Use-Cases: the sequence of actions.
(all team; System analyst leads)
To ﬁnally build the Functional Requirements (FR) (Singapore
Stage 1) (all team; System Analyst leads):
FR deliverable is a text document with general goals and
speciﬁc tasks (Baker and Coyle, 2009)
Use the Expression of Functional Requirements and Use-Case
Model to identify the FR these deliverables explicit;

Domain Model
The Domain Model “captures the most important types of objects
in the context of the system.” (Booch et al., 1999, p. 119)
based on the Functional Requirements and on the Use-Cases
Model, Expression of Functional Requirements deliverables
and on other information or documents, if available

Domain Model
The Domain Model “captures the most important types of objects
in the context of the system.” (Booch et al., 1999, p. 119)
based on the Functional Requirements and on the Use-Cases
Model, Expression of Functional Requirements deliverables
and on other information or documents, if available
Me4DCAP sugests the use of the ORM technique:
The diagram identiﬁes the classes of objects and the
relationships among them
attributes are omitted at this phase of the process
other techniques can be used (e.g. ER technique)
(all team; System Analyst leads)

Description Set Proﬁle
To build the Description Set Proﬁle Me4DCAP obliges the
The Integration Dossier
The Validation Dossier (in laboratory)

Description Set Proﬁle - Integration Dossier
The Integration Dossier is composed by 3 mandatory deliberables:
A Detailed Data Model Diagram (System Analyst: all team checks):
classes of objects (deﬁned in the Domain Model);
attributes of the classes of objects;
attributes’ constraints, such as their repeatability and range

A State Of The Art report: A State of the art to existing
metadata schemes that are described in RDF (Integrator)
If the metadata schemes of the State of The Art report does
not fullﬁll the needs of properties descriptions the work-team
will have to coin new RDF properties

A State Of The Art report: A State of the art to existing
metadata schemes that are described in RDF (Integrator)
If the metadata schemes of the State of The Art report does
not fullﬁll the needs of properties descriptions the work-team
will have to coin new RDF properties
A Document of Integration: shows, in a matrix, per line,
every property or class and its constraints, described by the
properties of the metadata schemes and encoding schemes
chosen (Integrator)

Description Set Proﬁle - Validation Dossier (in laboratory)
The Validation Dossier (in laboratory) is composed by 3
mandatory deliberables:
A Validation Report (all team): to check the DCAP adequacy to
what has been deﬁned in the “Vision Statement”

A Document of Validation (all team - Integrator leads):
To check the DCAP adequacy to the resources that are going
to be described by it
To apply the DCAP descriptors to a resource sample

A Questionnaire: Answer to a set of questions to assess the
diﬃculties of the validation process (all team; Project Manager leads)

A Questionnaire: Answer to a set of questions to assess the
diﬃculties of the validation process (all team; Project Manager leads)
According to the results of the Validation Dossier, the process
iterates or follows to the Description Set Proﬁle development

Description Set Profile
Once both, the Integration Dossier and the Validation Dossier
are done, it is possible to pass on into the development of the
Description Set Profile (DSP)
DSP is defined in the Nilsson’s (2008) document
The Document of Integration is the basis for the DSP
development

Guidelines
The Usage Guidelines and Syntax Guidelines are not
mandatory in the Singapore Framework
Me4DCAP recommends that they should be developed
the developing of the Usage Guidelines can start at the same
time as the Domain Model development (Project Manager and Integrator)
The development of the Syntax Guidelines (Integrator)needs that
the Integration Dossier has been already developed in a
certain stage in order to have already some maturity

Validation in Production
Use of log registration technique
observing ﬁnal-users working with a system that implemented
the DCAP (integrator)
the results of this validation in production are reported to the
whole team in order to review and access the DCAP
deﬁnitions
If there is any new information to add, the process starts again
DCAP users are not standalone machines; in such an
environment, the whole system will be impacted with changes!

Next steps:
The validation of Me4DCAP V0.2 will be executed
Me4DCAP V0.3
Future Work:
Me4DCAP V0.3 ﬁeld testing - call for testing
Work in another Me4DCAP Version ??

Thank you
Look for references in the paper

Questions
Mariana Curado Malta & Ana Alice Baptista
Algoritmi Center, University of Minho
QUESTIONS?
CALL FOR Me4DCAP TESTING
=⇒ mariana.malta@algoritmi.uminho.pt

A method for the development of Dublin Core Application Profiles (Me4DCAP V0.2): detailed description

Recommended

Recommended

More Related Content

Similar to A method for the development of Dublin Core Application Profiles (Me4DCAP V0.2): detailed description

Similar to A method for the development of Dublin Core Application Profiles (Me4DCAP V0.2): detailed description (20)

Recently uploaded

Recently uploaded (20)

A method for the development of Dublin Core Application Profiles (Me4DCAP V0.2): detailed description