Best-Practices-for-software-development.md

@@ -7,4 +7,12 @@ The document summarised the collection of best practices for
 
 | Best Practice | Steps in SDLC | Current Status | Examples and links | Gaps | Priorities |
 | ------------- | ------------- | -------------- | ------------------ | ---- | ---------- | 
-| Provide guidelines to researches and developers  | development    |Several guidelines available | DLR |  Development and deployment in the community, harmonisation | adoption
+| Provide guidelines to researches and developers  | development    |Several guidelines available | [DLR](https://rse.dlr.de/),[Netherlands eScience center](https://guide.esciencecenter.nl/#/best_practices/checklist) |  Development and deployment in the community, harmonisation | adoption |
+| Management of Software Projects | general/planning | different solutions (from open source to commercial in use | | experiment specific   | none |
+| Choice of Development Platform | development | internal and external platforms, both open source and commercial | github and gitlab | harmonisation needed? | none |
+| Continuous Integration/Deployment | deployment | automated platform for CI/CD including software tests | gitlab/github CI/CD | harmonisation | harmonisation |
+| Containerisation | development, deployment, archiving, maintenance | containers as overarching solution for flexible software distribution and handling | including Kubernetes | research (overview gathering) | development |
+| Avoiding Vendor Lock-In | general | 
+| Prepare software for archiving, choose archive | Archiving | Archives available, OSSR will help | Zenodo, Software Heritage | automation in OSSR | harmonisation |
+| Maintenance takes more resources than development | Maintenance | Most projects focused on development, maintenance took into consideration by the platform, resources only partly available | funding for long-term maintenance not securable | raise awareness | harmonisation |
+