a method for the development of dublin core application profiles (me4dcap v0.2): detailed...

Agenda Introduction Me4DCAP V0.2 Future Work The End

Me4DCAP V0.2: A method for the development of DublinCore Application Profiles

Mariana Curado Malta & Ana Alice BaptistaAlgoritmi Center, University of Minho

[email protected]@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 – Fundacao para a Ciencia 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

I DCMI created new instruments with a goal: to speak acommon language

I Dublin Core Abstract Model (DCAM): a model developed forDCMI syntax specifications

I presents the components and constructs used in DCMIdatabases

I one of them is the Dublin Core Application Profiles (DCAP)

I A DCAP is a generic construct for designing metadatarecords

Research Problem

I A DCAP development is a complex taskI it needs an adequate support

I A study we have performed (Curado Malta & Baptista,2013b) shows that:

I (to the best of our knowledge)

there is no method for the development of DCAP onlydocuments with some thoughts on how the process should be

I It is imperative to have such a method

Research Problem

I A DCAP development is a complex taskI it needs an adequate support

I A study we have performed (Curado Malta & Baptista,2013b) shows that:

I (to the best of our knowledge)

there is no method for the development of DCAP onlydocuments with some thoughts on how the process should be

I It is imperative to have such a method

Research Methodology

I Design Science Research (DSR)

I DSR aims at the development of innovative artifacts thatsolve real-world problems (Simon, 1996)

I Our artifact is a method: A method for the developmentof DCAP (Me4DCAP)

I 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 CoreApplication Profiles” - Baker et al. (2008)

I Functional Requirements (Mandatory)

I Domain Model (Mandatory)

I Description Set Profile (Mandatory)

I Usage guidelines (optional)

I Encoding Syntax guidelines (optional)

The development of a DCAP is a process by stages

Introduction

I Me4DCAP defines:

I The composition of the work-team and

I ... the type of work each work-team-member should do

I The process workflow

I The deliverables at every stage

I The techniques used to develop those deliverables

Deliverables Workflow

Work-Team

The work-team should have at least one person of each of thefolowing profiles:

I Project Manager: has a scope vision of the organisations andof the goals they want to achieve with the DCAP

I System Analyst: has technical skills in data modeling and inrequirements elicitation

I Integrator: understands the Semantic Web concepts

I Final User: works with the Web System that will be using theDCAP in development

Glossary

A Glossary should be developed during the whole processdevelopment

I It is a very important deliverable because of themultidisciplinarity of the work-team

I A Glossary is a text document with the keywords (and itsdescription) used in the process

I All work-team members should contribute to the Glossary

Functional Requirements

To build the Functional Requirements Me4DCAP obliges thedevelopment of the following deliverables:

I Work-Plan: time planning of the project activities (e.g aGantt Chart) (all team; Project Manager leads)

I Vision Statement: shows what developers want to reachwith the DCAP development; it defines the scope of theDCAP(all team; Project Manager leads)

I Expression of Functional Requirements: a list of theFunctional Requirements Expressed by the work-team - veryshort description per Functional Requirement (all team; System analyst

leads)

(continues...)

leads)

(continues...)

leads)

(continues...)

(Continued from last page...)

I Use-Cases Model. It is composed by:I the UML Use-Cases diagrams with the actors that interact in

the Use-CasesI the set of all detailed Use-Cases: the sequence of actions.

(all team; System analyst leads)

To finally build the Functional Requirements (FR) (SingaporeStage 1) (all team; System Analyst leads):

I FR deliverable is a text document with general goals andspecific tasks (Baker and Coyle, 2009)

I Use the Expression of Functional Requirements and Use-CaseModel to identify the FR these deliverables explicit;

(Continued from last page...)

I Use-Cases Model. It is composed by:I the UML Use-Cases diagrams with the actors that interact in

the Use-CasesI the set of all detailed Use-Cases: the sequence of actions.

(all team; System analyst leads)

To finally build the Functional Requirements (FR) (SingaporeStage 1) (all team; System Analyst leads):

I FR deliverable is a text document with general goals andspecific tasks (Baker and Coyle, 2009)

I Use the Expression of Functional Requirements and Use-CaseModel to identify the FR these deliverables explicit;

Domain Model

The Domain Model “captures the most important types of objectsin the context of the system.” (Booch et al., 1999, p. 119)

I based on the Functional Requirements and on the Use-CasesModel, Expression of Functional Requirements deliverables

I and on other information or documents, if available

I Me4DCAP sugests the use of the ORM technique:I The diagram identifies the classes of objects and the

relationships among them

I attributes are omitted at this phase of the process

I other techniques can be used (e.g. ER technique)

(all team; System Analyst leads)

Domain Model

The Domain Model “captures the most important types of objectsin the context of the system.” (Booch et al., 1999, p. 119)

I based on the Functional Requirements and on the Use-CasesModel, Expression of Functional Requirements deliverables

I and on other information or documents, if available

I Me4DCAP sugests the use of the ORM technique:I The diagram identifies the classes of objects and the

relationships among them

I attributes are omitted at this phase of the process

I other techniques can be used (e.g. ER technique)

(all team; System Analyst leads)

Description Set Profile

To build the Description Set Profile Me4DCAP obliges thedevelopment of the following deliverables:

I The Integration Dossier

I The Validation Dossier (in laboratory)

Description Set Profile - Integration Dossier

The Integration Dossier is composed by 3 mandatory deliberables:I A Detailed Data Model Diagram (System Analyst: all team checks):

I classes of objects (defined in the Domain Model);I attributes of the classes of objects;I attributes’ constraints, such as their repeatability and range

I A State Of The Art report: A State of the art to existingmetadata schemes that are described in RDF (Integrator)

I If the metadata schemes of the State of The Art report doesnot fullfill the needs of properties descriptions the work-teamwill have to coin new RDF properties

I A Document of Integration: shows, in a matrix, per line,every property or class and its constraints, described by theproperties of the metadata schemes and encoding schemeschosen (Integrator)

Description Set Profile - Validation Dossier (in laboratory)

The Validation Dossier (in laboratory) is composed by 3mandatory deliberables:

I A Validation Report (all team): to check the DCAP adequacy towhat has been defined in the “Vision Statement”

I A Document of Validation (all team - Integrator leads):I To check the DCAP adequacy to the resources that are going

to be described by itI To apply the DCAP descriptors to a resource sample

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

I According to the results of the Validation Dossier, the processiterates or follows to the Description Set Profile development

Description Set Profile

I Once both, the Integration Dossier and the Validation Dossierare done, it is possible to pass on into the development of theDescription Set Profile (DSP)

I DSP is defined in the Nilsson’s (2008) document

I The Document of Integration is the basis for the DSPdevelopment

Guidelines

I The Usage Guidelines and Syntax Guidelines are notmandatory in the Singapore Framework

I Me4DCAP recommends that they should be developed

I the developing of the Usage Guidelines can start at the sametime as the Domain Model development (Project Manager and Integrator)

I The development of the Syntax Guidelines (Integrator)needs thatthe Integration Dossier has been already developed in acertain stage in order to have already some maturity

Validation in Production

I Use of log registration technique

I observing final-users working with a system that implementedthe DCAP (integrator)

I the results of this validation in production are reported to thewhole team in order to review and access the DCAPdefinitions

I If there is any new information to add, the process starts again

I DCAP users are not standalone machines; in such anenvironment, the whole system will be impacted with changes!

Next steps:

I The validation of Me4DCAP V0.2 will be executed

I Me4DCAP V0.3

Future Work:

I Me4DCAP V0.3 field testing - call for testing

I 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

=⇒ [email protected]

a method for the development of dublin core application profiles (me4dcap v0.2): detailed...

Science

end me4dcap v0

end introduction me4dcap

agenda introduction

development of dcap

dcap development

end introduction me4dcap

process development

end workteam