Short answer

Integrate archival considerations and documentation strategies into the software development process from its inception, especially for projects intended for long-term scholarly use.

Field: Innovation & Design
Source: eScholarship (California Digital Library) (2014)
Method: Case Study and Literature Review
Evidence: Moderate effect

Preserving culturally significant software, especially from academic and research settings, necessitates a comprehensive strategy that captures not only the final product but also its entire development lifecycle. This innovation & design research insight is drawn from a 2014 study published in eScholarship (California Digital Library). Using Case study and literature review, researchers explored how this design variable affects real-world outcomes. The key design takeaway: Integrate archival considerations and documentation strategies into the software development process from its inception, especially for projects intended for long-term scholarly use.

Study

Innovation & DesignHigh ImpactModerate effect

Archiving academic software requires a unified approach to preserve development histories.

eScholarship (California Digital Library) · 2014

Key Findings

01Academic software, particularly game software, presents unique challenges for preservation due to its complex development histories and specific institutional contexts.
02A unified approach is needed to capture not just the final software artifact but also its associated development data, code, documentation, and the intellectual context of its creation.
03Existing archival practices are often insufficient for preserving the full value and research potential of academic software.

Application

Design takeaway

Integrate archival considerations and documentation strategies into the software development process from its inception, especially for projects intended for long-term scholarly use.

How to apply

When developing software for research or cultural heritage purposes, establish a clear protocol for version control, documentation, and metadata creation that supports future archival access and understanding.

Project actions

01When starting a design project, think about how it might be studied or archived in the future.
02Keep detailed records of your design process, including sketches, prototypes, user feedback, and code versions.

Method & Evidence

AimHow can culturally significant software produced in non-commercial research institutions, such as universities, be archived to ensure its availability for future scholarly research?

MethodCase Study and Literature Review

ProcedureThe research involved a case study of the academic game 'Prom Week' developed at UC Santa Cruz, analyzing its unique characteristics and the challenges in its documentation and preservation. This was supplemented by a review of existing practices and challenges in archiving academic software.

ContextDigital Humanities, Computing, Archival Preservation, Academic Software Development, Game Studies

Variables

IVArchival approach (unified vs. traditional)

DVAvailability and research potential of archived software

CVType of software (academic game), institutional context

Strengths & Limitations

Strengths

+Addresses a critical gap in digital preservation practices.
+Provides a concrete case study to illustrate challenges and potential solutions.

Limitations

The specific tools and methods for archiving may vary depending on the type of software and the available resources.

Reliability & validity

The study's validity is supported by its focus on a specific case and its contribution to a recognized problem area. Reliability would depend on the consistency of archival practices described.

Think critically

What are the ethical considerations involved in archiving software that may contain sensitive data or intellectual property?

Design Principles

"Document and preserve the entire lifecycle of significant digital artifacts, not just the final output."

This insight is crucial for designers and researchers working on projects with long-term scholarly or historical value. Understanding how to document and archive the evolution of software ensures that future generations can study its creation, understand its context, and learn from its design decisions.

What This Means for Your Design

To save important computer programs from universities for future study, we need a special plan that saves not just the program itself, but also all the steps and information from when it was being made.

How to use in your project

1.Reference this research when discussing the importance of documenting and preserving design processes, especially for projects with potential long-term impact or scholarly value.

Add to My Project

Quick Cite

Paragraph starter

The preservation of culturally significant software, particularly within academic and research contexts, necessitates a unified approach that extends beyond the final product to encompass its entire development history. This involves meticulously documenting code, design decisions, and the intellectual context of creation to ensure future scholarly access and understanding.

Source

eScholarship (California Digital Library)

A Unified Approach to Preserving Cultural Software Objects and their Development Histories

journal · 2014

View source

Questions About This Research

What does the research say about archiving academic software requires a unified approach to preserve development histories?: Integrate archival considerations and documentation strategies into the software development process from its inception, especially for projects intended for long-term scholarly use. Evidence: eScholarship (California Digital Library) (2014).
Why does "Archiving academic software requires a unified approach to preserve development histories." matter for design?: This insight is crucial for designers and researchers working on projects with long-term scholarly or historical value. Understanding how to document and archive the evolution of software ensures that future generations can study its creation, understand its context, and learn from its design decisions.
How can designers apply this research?: Integrate archival considerations and documentation strategies into the software development process from its inception, especially for projects intended for long-term scholarly use.
What were the main findings?: Academic software, particularly game software, presents unique challenges for preservation due to its complex development histories and specific institutional contexts.. A unified approach is needed to capture not just the final software artifact but also its associated development data, code, documentation, and the intellectual context of its creation.. Existing archival practices are often insufficient for preserving the full value and research potential of academic software.
What research method was used?: Case Study and Literature Review.
How strong is the evidence?: Evidence strength is rated Moderate effect, based on a 2014 journal from eScholarship (California Digital Library).
What should I do differently in my next project?: When developing software for research or cultural heritage purposes, establish a clear protocol for version control, documentation, and metadata creation that supports future archival access and understanding.
What are the limitations?: The study primarily focused on academic game software, and the findings may not be directly generalizable to all types of software or all institutional contexts.