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

Center for Technology in Government
NYS Archives and Records Administration
Models for Action Project
Records Requirements Elicitation Component

Business Process Level

1. What is the transaction to be automated (from the perspective of the customer)?

2. What are the sub-tasks associated with the transaction?*

3. For each of the subtasks gather the following information:

  • Legal
  • Regulatory
  • Best Practices
  • Agency Policies and Practices

  • A. What is the purpose of the sub-task? Is it intended to fulfill a legal, regulatory or operational purpose?
  •  
    • 1. Are there any when or how requirements for the transaction (i.e., time clocks or professional techniques)?
    •  
  • B. What other documents or information need to be accessed during the sub-task? Are copies of these records included in the record of the transaction?
  •  
  • C. Does the record of the transaction get created or modified?
  •  
    • 1. If yes, (add to table) at what point in the transaction does the record get created or modified?
    •  
    • 2. Who is authorized to change or modify the record?
    •  
    • 3. What is the content of the record or the component of the record created during the sub-task?
    •  
      • a. Are there records created by other systems that need to be integrated into the record?
      •  
      • b. Are there any proofs of authenticity associated with the content created or modified during the sub-task?
      •  

*Sub-task starts a process and ends with a decision point or completes the transaction.