Skip to main content
 
Models for Action: Developing Practical Approaches to Electronic Records Management and Preservation

Abstract

Introduction

Theoretical Foundations

Functional Requirements for Electronic Records Management

The Records Requirement Elicitation Component

Next Steps

Appendix
print html versionPrint Chapter (html)
print pdf versionPrint Chapter (pdf)
Appendix

Models for Action First Draft of Functional Requirements

  1. Compliant - Legal and administrative requirements as well as best practices for record keeping related to a specific business process including those requirements specific to the field or discipline that the system will support, are addressed.
  2. System Reliability - System should be administered in line with best practices in the information resource management (IRM) field to ensure the reliability of the records it produces.
  3. Records Capture - Records are created or captured and identified to support the business process and meet all record keeping requirements.
  4. Records Maintained - Electronic records are maintained so that they are accessible and retain their integrity for as long as they are needed.
  5. Records Are Usable - Electronic records are usable for the purposes they were created and can be exported into an integral, accessible, usable format from the creating system to other systems. This includes the ability to transfer the records to an archival repository if necessary.

Models for Action Functional Requirements

  1. System Reliability - System should be administered in line with best practices in the information resource management (IRM) field to ensure the reliability of the records it produces.
  2. Records Capture - Records are created or captured and identified to support the business process and meet all record keeping requirements.
  3. Records Maintenance and Accessibility - Electronic records are maintained so that they are accessible and retain their integrity for as long as they are needed.