Skip to content

Commit

Permalink
Add explanatory content
Browse files Browse the repository at this point in the history
Also table of contents
  • Loading branch information
bernhold committed Apr 30, 2024
1 parent b516ec6 commit 59013f9
Showing 1 changed file with 18 additions and 3 deletions.
21 changes: 18 additions & 3 deletions index.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,26 @@
---
title: Mapping of Terms Between Software Engineering Research (SER) and Research Software Engineering (RSE)
layout: single
toc: true
toc_sticky: true
---
{% assign first = site.terms | sort | first %}
[Browse by term]({{ first.url | relative_url }})

---
## Goals

Many in the research software engineering (RSE) community have picked up their understanding of software engineering (SE) terminology, concepts, practices, and tools (which we call "SE fundamentals") via informal means, and often not from software engineering researchers (SERs). We want to get a better handle on what RSEs know about and use from the SE community and where there might be gaps. Gaps may stem largely from lack of awareness, or it may be that RSEs have tried the fundamental and found it less useful in the context of research software. In the former case, there are opportunities for education and training as well as other outreach to increase awareness and adoption. In the latter case, there may be opportunities for the SER community to work with RSEs to understand why not, and if there might be adaptations that would make it more amenable to use in the research software (RS) community.

## Approach

We're developing a mapping between terminology used in the two communities. For each term, we're trying to gauge the extent to which the RSE community is aware of these fundamentals of software engineering and uses them, along with the perceived potential for software engineering research to improve usage in RS.

In an attempt to be systematic, we're starting with the [Software Engineering Body of Knowledge](https://www.computer.org/education/bodies-of-knowledge/software-engineering) (SWEBOK) as the primary source of terms and their meanings from the SE community. Once we've covered the terms from SWEBOK, we'll open it to other sources, though we'll always prefer sources that will help us be systematic.

## How to contribute

*to be added*

{% assign first = site.terms | sort | first %}
## Summary list of terms ([browse by term]({{ first.url | relative_url }}))

{% for term in site.terms sort %}
<section style="margin-top:1em;width:100%">
Expand Down

0 comments on commit 59013f9

Please sign in to comment.