slide1
Download
Skip this Video
Download Presentation
Model Requirements for the Management of Electronic Records

Loading in 2 Seconds...

play fullscreen
1 / 25

Model Requirements for the Management of Electronic Records - PowerPoint PPT Presentation


  • 124 Views
  • Uploaded on

Model Requirements for the Management of Electronic Records A new evolutionary structure for defining ERMS for simple and complex systems and industry sector requirements. 15 th September 2010, ICA CITRA Oslo Jon Garde, Journal IT. DLM Forum. 1996 - present.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Model Requirements for the Management of Electronic Records' - lawrencia


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide1
Model Requirements for the Management of Electronic Records

A new evolutionary structure for defining ERMS for simple and complex systems and industry sector requirements.

15th September 2010, ICA CITRA Oslo

Jon Garde, Journal IT

dlm forum

DLM Forum

1996 - present

slide3
Model Requirements for the Management of Electronic Records

BUT…

  • MoReq2 is…
  • DLM Forum’s most successful “product”
  • Expanded set of records management requirements
  • 12+ translation projects
  • Testing and certification programme
moreq2 issues
MoReq2 Issues
  • Many requirements = high cost of implementation
  • Suitable for “traditional” EDRMS but NOT suitable for dedicated or hybrid products
  • Many dependencies = harder to maintain
  • How do we know that what is tested is the same as what is delivered?
  • Many implementations = poor interoperability
roadmap
HEALTH

FINANCE

DEFENCE

LEGAL

Roadmap

scope

MoReq

MoReq2

MoReq2010

Future

time

2001

2005-8

2010

2012+

mo req 2010 aims
MoReq2010 Aims
  • Evolution of MoReq2
  • Scalability
  • Flexibility
  • Decoupling of requirements
  • Small core with more options
  • Groundwork for interoperability
  • Appeal to a wide variety of software
  • Supplier assurance
slide8
MoReq2010 – Project Plan

Project Setup

Completed

Public Consult

Completed

Prepare Draft

September – October

Public Review

October – November

Prepare Final

November – December

Expert Review

Approve & Publish

slide9
MoReq2010 – Project Plan

Public Consult

Completed

6th September

Report to Expert Review Group

Expert Review Group Opinion

Prepare Draft

slide10
MoReq2010 – Project Plan

Project Setup

Completed

Public Consult

Completed

Prepare Draft

September – October

Public Review

October – November

Prepare Final

November – December

Expert Review

Approve & Publish

slide11
MoReq2010 – Project Plan

Project Setup

Completed

Public Consult

Prepare Draft

Public Review

Prepare Final

Expert Review

Approve & Publish

mo req 2010 concept outcomes
MoReq2010 Concept Outcomes
  • Held over summer period
  • Original completion in August
  • Extended to September
  • > 100 people signed up
  • ~ 500 comments on proposals
slide17
Functional Requirement - Example

reference

functional requirement

function

entity

metadata

test

R3.4.20

The ERMS must allow an electronic file to be closed by user roles.

U3.9

E3.12

M3.34

M3.35

T3.4p

T3.17

more

Functions (for access and audit)

U3.9 = reference to a function available to user roles – “Close”

Entities

E3.12 = reference to an entity – “File”

Metadata

M3.34 = reference to an metadata element – “Closed by user”

M3.35 = reference to an metadata element – “Closed at datetime”

Tests

T3.4p = reference to a certification test – “p” indicates a partial test

T3.17 = reference to a certification test

slide20
Tension

Functional

Technical

slide21
Theoretical

Tension

Functional

Technical

Practical

slide22
Standards

Domain Specific

Interoperable

Best Practice

slide23
Standards

Domain Specific

Interoperable

Best Practice

slide24
MoReq2010 – Project Plan

Project Setup

Public Consult

Prepare Draft

Your opportunity to CONTRIBUTE!

Public Review

Prepare Final

Expert Review

Approve & Publish

ad