christoph becker gon alo antunes vienna university of jos
play

Christoph Becker Gonalo Antunes, Vienna University of Jos - PowerPoint PPT Presentation

A Capability Model for Digital Preservation Analyzing Concerns, Drivers, Constraints, Capabilities and Maturities Christoph Becker Gonalo Antunes, Vienna University of Jos Barateiro, Technology Ricardo Vieira Vienna, Austria INESC-ID


  1. A Capability Model for Digital Preservation Analyzing Concerns, Drivers, Constraints, Capabilities and Maturities Christoph Becker Gonçalo Antunes, Vienna University of José Barateiro, Technology Ricardo Vieira Vienna, Austria INESC-ID Information Systems www.ifs.tuwien.ac.at/˜becker Group, Lisbon, Portugal

  2. Digital Longevity • Numerous reference models, frameworks and concepts – OAIS and trust: TRAC, RAC (ISO 16363), NESTOR… – Records Management: MoReq, ISO 15489… – Risk: DRAMBORA… – Planning: PLATO, PLATTER – Economics: BRTF, LIFE…. • Yet, we still lack a holistic view – Maturity of the field is unclear and evolving – Integration into Information Systems and Information Technology fields is unclear – How does Digital Preservation relate to, e.g., IT Governance? – How can we assess and improve organizational capabilities? – How can we deal with non-repository scenarios?

  3. About systems, requirements and preservation Scenarios of systems and their perceived relevance of digital preservation requirements The Digital Preservation System (DPS): Digital DP as functional requirements Preservation System The Systems of Systems (SoS): Business system Business Digital delegates DP responsibility to a DPS Support Preservation System System Business The “Digital Preservation Ready” System (DPR): Support Longevity as a non-functional requirement ! System

  4. Background • Enterprise Architecture (EA) – Holistic system architecture approach to information systems and technology in organizations • IT Governance – decision making and communication within IT-supported organizations – leadership, organisational structures and processes – ensure that the IT sustains the organisation’s objectives – COBIT: Control Objectives for IT • The goals of Reference Architectures – Process – Stakeholder concerns – Independent of business domain and organization

  5. Make DP ubiquitous in systems • Consider clearly defined Goals… – Business process – Stakeholder concerns • Align business and technology according to the best references in Enterprise Architecture (EA)… – TOGAF Architecture Development Method • Follow IT Governance best practices… – COBIT (goal-oriented, process-oriented, control-based) – Maturity Model based on CMM • Define a Reference Architecture for reuse in the EA processes where DP is a relevant concern

  6. Consolidation of DP Reference Models Contextualization of a DP Architecture SHAMAN-RA Modeling of DP Capabilities Creation of a DP Architecture Vision CONCRETE ARCHITECTURES

  7. A Capability-based Reference Architecture Domain Knowledge Standards and Best- • SHAMAN-RA v1.0 Practices • OAIS • OMG UML • TRAC/RAC • OMG BMM • OMG SBVR • TDR 2002 • OMG OSM • NESTOR • ISO 27000: Security • Planets Planning method • Planets Functional Model • ISO 31000: Risk Manag. • PREMIS • IEEE Std. 1471-2000 • Zachman Framework • BRTF Sustainability Report • COBIT • DRAMBORA • DoDAF • PARSE.Insight • … • … Stakeholders Concerns Influencers Goals Capabilities

  8. Metamodel of key elements Stakeholder Concern Key Question has expressed by relates to Influencer Constraint Driver can be motivates quantified by limits deployment of Goal is a Key Performance Capability Indicator Desired Result delivers assessed by channels effort towards a Maturity Course of Action

  9. Digital Preservation Capabilities A capability is an “ ability that an organization, person, or system possesses. Capabilities are typically expressed in general and high-level terms and typically require a combination of organization, people, processes, and technology to achieve” A capability can control, inform, include, or depend on another capability

  10. Digital Preservation Capabilities A capability is an “ ability that an organization, person, or system possesses. Capabilities are typically expressed in general and high-level terms and typically require a combination of organization, people, processes, and technology to achieve” Preserve Contents is the ability to maintain content authentic and understandable to the defined user community over time and assure its provenance.

  11. Core Preservation Capabilities Preservation Planning Preservation Operation Monitor, steer and control the preservation Control the deployment and execution of operation of content preservation plans.

  12. Core Preservation Capabilities Preservation Planning Preservation Operation Monitor, steer and control the preservation Control the deployment and execution of operation of content preservation plans. • Influencers and Decision making • Options diagnosis • Specification and delivery • Monitoring

  13. Core Preservation Capabilities Preservation Planning Preservation Operation Monitor, steer and control the preservation Control the deployment and execution of operation of content preservation plans. • Influencers and Decision making • Analyze content • Options diagnosis • Execute preservation actions • Specification and delivery • Ensure adequate provenance trail • Monitoring • Handle preservation metadata • Conduct Quality Assurance • Provide reports and statistics

  14. Core Preservation Capabilities Preservation Planning Preservation Operation Monitor, steer and control the preservation Control the deployment and execution of operation of content preservation plans. • Influencers and Decision making • Analyze content • Options diagnosis • Execute preservation actions • Specification and delivery • Ensure adequate provenance trail • Monitoring • Handle preservation metadata • Conduct Quality Assurance • Provide reports and statistics “Migrate this set of images (in TIFF-5) to JP2 • Analyze original using ImageMagick 6.3 with parameters • Migrate, analyze output a,b,c” • Conduct quality assurance • Provenance, metadata, Reporting

  15. Preservation Planning Capabilities • Planning Operational Preservation: – make drivers and goals operational and assess options against these criteria to deliver efficient decisions and operational plans 1. Influencers and Decision Making 2. Options Diagnosis 3. Specification and Delivery • Monitoring 1. Internal Monitoring 2. External Monitoring

  16. Preservation Operation Capabilities • Analysis • Action • Quality Assurance • Preservation Metadata • Plan Deployment • Reporting and Statistics

  17. Example: Measuring Reporting and Statistics • Timeliness • Currentness • Completeness • Relevance • Correctness • Understandability

  18. Analysing drivers and constraints Stakeholders concerned Concerns addressed Goals impacted Capabilities affected Metrics applicable

  19. A Capability Maturity Model for Preservation Operation The CMM has been shown to be a powerful instrument for assessment and improvement in Software Engineering Awareness and Policies, Plans Tools and Skills and Responsibility Goal Setting Communication and Procedures Automation Expertise and and Accountability Measurement 1 Initial / ad-hoc 2 Repeatable, but Intuitive 3 Defined 4 Managed and Measurable 5 Optimized

  20. Awareness and Policies, Plans and Tools and Skills and Responsibility Goal Setting Communication Procedures Automation Expertise and and Accountability Measurement 1 Need for Some uncontrol- Some tools No aware- None assigned Operations operations led , undocumen- employed ness of skills react to recognized ted operations ad-hoc / expertise incidents, not tracked 2 Awareness of Operational Automated Hands-on Responsibility Individual role of opera- procedures tools used experience, emerges, awareness of tions, no formal emerge, informal, incoherently informal undocumented, short-term reporting, intuitive. Indivi- based on peer no accountability goals, no individual dual procedures, need and training consistent communication ad-hoc QA availability definition 3 Understanding Defined process, Plans Formal Responsibility Operational of role of driven by deployed training assigned, goals specified, operations, components and according to plan, but accountability no formal reporting services. spec, but training still not always metrics or guidelines not mostly individual provided alignment to enforced manual initiative goals 4 … … automated skills and Responsibility and Metrics aligned system expertise accountability with goals, controls defined for defined for all compliance automated all roles roles enforced operations 5 … … … … RACI plan fully … traceable to ops

Recommend


More recommend