Merge pull request #1 from Samatgator/main

Integration of BibTex references rendering to Jekyll GitHub Actions

.github/workflows/jekyll.yml

@@ -0,0 +1,63 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+# Sample workflow for building and deploying a Jekyll site to GitHub Pages
+name: Deploy Jekyll site to Pages
+
+on:
+  # Runs on pushes targeting the default branch
+  push:
+    branches: ["main"]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  # Build job
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      - name: Setup Ruby
+        uses: ruby/setup-ruby@8575951200e472d5f2d95c625da0c7bec8217c42 # v1.161.0
+        with:
+          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
+          cache-version: 0 # Increment this number if you need to re-download cached gems
+      - name: Setup Pages
+        id: pages
+        uses: actions/configure-pages@v5
+      - name: Build with Jekyll
+        # Outputs to the './_site' directory by default
+        run: bundle exec jekyll build --baseurl "${{ steps.pages.outputs.base_path }}"
+        env:
+          JEKYLL_ENV: production
+      - name: Upload artifact
+        # Automatically uploads an artifact from the './_site' directory by default
+        uses: actions/upload-pages-artifact@v3
+
+  # Deployment job
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.gitignore

@@ -0,0 +1 @@
+Gemfile.lock

.ruby-version

@@ -0,0 +1 @@
+3.0

Gemfile

@@ -0,0 +1,11 @@
+source 'https://rubygems.org'
+
+group :jekyll_plugins do
+  gem "jekyll"
+  gem "jekyll-remote-theme"
+  gem 'jekyll-theme-minimal'
+  gem 'jekyll-github-metadata'
+  gem 'jekyll-figure'
+  gem 'jekyll-scholar'
+  gem 'faraday-retry'
+end

_bibliography/references.bib

@@ -0,0 +1,194 @@
+@incollection{abrahamsson_leanagile_2010,
+	address = {Berlin, Heidelberg},
+	title = {Lean/{Agile} {Software} {Development} {Methodologies} in {Regulated} {Environments} – {State} of the {Art}},
+	volume = {65},
+	copyright = {http://www.springer.com/tdm},
+	isbn = {978-3-642-16415-6 978-3-642-16416-3},
+	url = {http://link.springer.com/10.1007/978-3-642-16416-3_4},
+	language = {en},
+	urldate = {2024-11-30},
+	booktitle = {Lean {Enterprise} {Software} and {Systems}},
+	publisher = {Springer Berlin Heidelberg},
+	author = {Cawley, Oisín and Wang, Xiaofeng and Richardson, Ita},
+	editor = {Abrahamsson, Pekka and Oza, Nilay},
+	year = {2010},
+	doi = {10.1007/978-3-642-16416-3_4},
+	note = {Series Title: Lecture Notes in Business Information Processing},
+	pages = {31--36},
+	file = {PDF:/home/sam/snap/zotero-snap/common/Zotero/storage/CLZPPGL5/Cawley et al. - 2010 - LeanAgile Software Development Methodologies in Regulated Environments – State of the Art.pdf:application/pdf},
+}
+
+@article{noauthor_creation_2024,
+	title = {Creation of an {IEC} 62304 compliant software development plan},
+	url = {https://www.researchgate.net/publication/309231377_Creation_of_an_IEC_62304_compliant_software_development_plan},
+	doi = {10.1002/smr.1826},
+	abstract = {PDF {\textbar} Organizations engaged in medical device software development are required to demonstrate compliance with a set of medical device standards and... {\textbar} Find, read and cite all the research you need on ResearchGate},
+	language = {en},
+	urldate = {2024-11-30},
+	journal = {ResearchGate},
+	month = oct,
+	year = {2024},
+	file = {Snapshot:/home/sam/snap/zotero-snap/common/Zotero/storage/DYH9PZVL/309231377_Creation_of_an_IEC_62304_compliant_software_development_plan.html:text/html},
+}
+
+@article{hamou-lhadj_regulatory_nodate,
+	title = {Regulatory {Compliance} and its {Impact} on {Software} {Development}},
+	abstract = {Abstract. Since the outset of our research, we have been looking for ways to help software companies develop software systems for which regulatory compliance is a key quality attribute. This is because many regulations, laws, standards, and other authoritative rules have a direct impact on the way software systems, used by regulated organizations, are developed, tested, and maintained. In this paper, we particularly discuss the impact of regulatory compliance on software development practices. We achieve this by discussing how regulations and laws impact three main aspects of software which are: product, process, and project. We argue that there is a need for a new field of study that we refer to as software compliance engineering and which aims to investigate techniques and tools for the development and maintenance of auditable software systems.},
+	language = {en},
+	author = {Hamou-Lhadj, Abdelwahab},
+	file = {PDF:/home/sam/snap/zotero-snap/common/Zotero/storage/75U37ZVM/Hamou-Lhadj - Regulatory Compliance and its Impact on Software Development.pdf:application/pdf},
+}
+
+@book{juuso_medical-grade_2024,
+	title = {Medical-{Grade} {Software} {Development}. {How} to {Build} {Medical}-{Device} {Products} {That} {Meet} the {Requirements} of {IEC} 62304 and {ISO} 13485},
+	isbn = {978-1-03-259318-0},
+	url = {http://gen.lib.rus.ec/book/index.php?md5=FDD262939E1B96853349A4C0A9F360BE},
+	urldate = {2024-11-30},
+	publisher = {Routledge. Taylor \& Francis Group},
+	author = {Juuso, Ilkka and Pöyhönen, Ilpo},
+	year = {2024},
+	file = {PDF:/home/sam/snap/zotero-snap/common/Zotero/storage/XKFXVFKV/Juuso and Pöyhönen - 2024 - Medical-Grade Software Development. How to Build Medical-Device Products That Meet the Requirements.pdf:application/pdf},
+}
+
+@article{steck_iss_nodate,
+	title = {{ISS} {Integrated} {Scientific} {Services} {AG}},
+	language = {en},
+	author = {Steck, Matthias},
+	file = {PDF:/home/sam/snap/zotero-snap/common/Zotero/storage/BQ5U42H7/Steck - ISS Integrated Scientific Services AG.pdf:application/pdf},
+}
+
+@article{ohm_regulating_nodate,
+	title = {Regulating {Software} {When} {Everything} {Has} {Software}},
+	abstract = {This Article identifies a profound, ongoing shift in the modern administrative state: from the regulation of things to the regulation of code. This shift has and will continue to place previously isolated agencies in an increasing state of overlap, raising the likelihood of inconsistent regulations and putting seemingly disparate policy goals, like privacy, safety, environmental protection, and copyright enforcement, in tension. This Article explores this problem through a series of case studies and articulates a taxonomy of code regulations to help place hardware-turned-code rules in context. The Article considers the likely turf wars, regulatory thickets, and related dynamics that are likely to arise, and closes by considering the benefits of creating a new agency with some degree of centralized authority over software regulation issues.},
+	language = {en},
+	author = {Ohm, Paul and Reid, Blake},
+	file = {PDF:/home/sam/snap/zotero-snap/common/Zotero/storage/DFBUXRAG/Ohm and Reid - Regulating Software When Everything Has Software.pdf:application/pdf},
+}
+
+@inproceedings{lie_devops_2020,
+	address = {Bari Italy},
+	title = {{DevOps} in an {ISO} 13485 {Regulated} {Environment}: {A} {Multivocal} {Literature} {Review}},
+	isbn = {978-1-4503-7580-1},
+	shorttitle = {{DevOps} in an {ISO} 13485 {Regulated} {Environment}},
+	url = {https://dl.acm.org/doi/10.1145/3382494.3410679},
+	doi = {10.1145/3382494.3410679},
+	language = {en},
+	urldate = {2024-11-30},
+	booktitle = {Proceedings of the 14th {ACM} / {IEEE} {International} {Symposium} on {Empirical} {Software} {Engineering} and {Measurement} ({ESEM})},
+	publisher = {ACM},
+	author = {Lie, Martin Forsberg and Sánchez-Gordón, Mary and Colomo-Palacios, Ricardo},
+	month = oct,
+	year = {2020},
+	pages = {1--11},
+	file = {Submitted Version:/home/sam/snap/zotero-snap/common/Zotero/storage/HFUTI64T/Lie et al. - 2020 - DevOps in an ISO 13485 Regulated Environment A Multivocal Literature Review.pdf:application/pdf},
+}
+
+@article{laukkarinen_regulated_2018,
+	title = {Regulated software meets {DevOps}},
+	volume = {97},
+	issn = {09505849},
+	url = {https://linkinghub.elsevier.com/retrieve/pii/S0950584918300144},
+	doi = {10.1016/j.infsof.2018.01.011},
+	language = {en},
+	urldate = {2024-11-30},
+	journal = {Information and Software Technology},
+	author = {Laukkarinen, Teemu and Kuusinen, Kati and Mikkonen, Tommi},
+	month = may,
+	year = {2018},
+	pages = {176--178},
+	file = {Submitted Version:/home/sam/snap/zotero-snap/common/Zotero/storage/L8WTYYEL/Laukkarinen et al. - 2018 - Regulated software meets DevOps.pdf:application/pdf},
+}
+
+@inproceedings{laukkarinen_devops_2017,
+	address = {Buenos Aires, Argentina},
+	title = {{DevOps} in {Regulated} {Software} {Development}: {Case} {Medical} {Devices}},
+	isbn = {978-1-5386-2675-7},
+	shorttitle = {{DevOps} in {Regulated} {Software} {Development}},
+	url = {http://ieeexplore.ieee.org/document/7966870/},
+	doi = {10.1109/ICSE-NIER.2017.20},
+	urldate = {2024-11-30},
+	booktitle = {2017 {IEEE}/{ACM} 39th {International} {Conference} on {Software} {Engineering}: {New} {Ideas} and {Emerging} {Technologies} {Results} {Track} ({ICSE}-{NIER})},
+	publisher = {IEEE},
+	author = {Laukkarinen, Teemu and Kuusinen, Kati and Mikkonen, Tommi},
+	month = may,
+	year = {2017},
+	pages = {15--18},
+	file = {PDF:/home/sam/snap/zotero-snap/common/Zotero/storage/84NVEC8D/Laukkarinen et al. - 2017 - DevOps in Regulated Software Development Case Medical Devices.pdf:application/pdf},
+}
+
+@article{williams_cybersecurity_2015,
+	title = {Cybersecurity vulnerabilities in medical devices: a complex environment and multifaceted problem},
+	copyright = {http://creativecommons.org/licenses/by-nc/3.0/},
+	issn = {1179-1470},
+	shorttitle = {Cybersecurity vulnerabilities in medical devices},
+	url = {http://www.dovepress.com/cybersecurity-vulnerabilities-in-medical-devices-a-complex-environment-peer-reviewed-article-MDER},
+	doi = {10.2147/MDER.S50048},
+	language = {en},
+	urldate = {2024-11-20},
+	journal = {Medical Devices: Evidence and Research},
+	author = {Williams, Patricia and Woodward, Andrew},
+	month = jul,
+	year = {2015},
+	pages = {305},
+	file = {Full Text:/home/sam/snap/zotero-snap/common/Zotero/storage/YJYS9FJF/Williams and Woodward - 2015 - Cybersecurity vulnerabilities in medical devices a complex environment and multifaceted problem.pdf:application/pdf},
+}
+
+@article{lechner_overview_2017,
+	title = {An {Overview} of {Cybersecurity} {Regulations} and {Standards} for {Medical} {Device} {Software}},
+	abstract = {This paper discusses current cybersecurity regulations and standards for medical device software set by government agencies and agencies developing industry and international standards such as the FDA (Food and Drug Administration), CFDA (China Food and Drug Administration), ISO (International Organization for Standardization), IEC (International Electrotechnical Commission), UL (Underwriters Laboratories), and others. The concepts described within this paper can be utilized by medical device manufacturers in order to establish a cybersecurity program as part of their quality management systems. In general, there are three complementary ways based on the NIST (National Institute of Standards and Technology) cybersecurity framework that can be used to remove gaps in the organization’s cybersecurity. The first way focuses on designing software products that take cybersecurity into account (i.e., prevention). The second way is to perform security and penetration testing and to apply other cybersecurity controls to reduce attacks and vulnerabilities that could be exploited (i.e., detection). The third way emphasizes maintenance plan in case of a cyberattack (i.e., response and recovery).},
+	language = {en},
+	author = {Lechner, Nadica Hrgarek},
+	year = {2017},
+	file = {PDF:/home/sam/snap/zotero-snap/common/Zotero/storage/K62USUWS/Lechner - 2017 - An Overview of Cybersecurity Regulations and Standards for Medical Device Software.pdf:application/pdf},
+}
+
+@article{boda_fintech_2020,
+	title = {From {FinTech} to {Healthcare}: {A} {DevOps} {Journey} {Across} {Industries}},
+	volume = {3},
+	copyright = {Copyright (c) 2020},
+	shorttitle = {From {FinTech} to {Healthcare}},
+	url = {https://academicpinnacle.com/index.php/acs/article/view/384},
+	abstract = {In today's rapidly evolving tech landscape, the principles of DevOps have transcended industry boundaries, bringing transformative changes from FinTech to healthcare. This journey across industries showcases how DevOps practices, originally honed in the fast-paced world of financial technology, are now being adapted to meet the rigorous demands of the healthcare sector. The shift is not just about technology; it's about culture, collaboration, and continuous improvement. In FinTech, where speed, security, and compliance are paramount, DevOps has enabled organizations to innovate quickly while maintaining stringent regulatory standards. As these practices migrate into healthcare, they are reshaping the way hospitals, clinics, and health-tech companies operate, emphasizing patient safety, data privacy, and system reliability. The journey is marked by challenges unique to each field—from the financial sector’s need for rapid deployment and resilience under pressure to healthcare’s focus on compliance with healthcare regulations and ensuring uninterrupted patient care. However, the core principles of DevOps—automation, continuous delivery, and a culture of collaboration—remain consistent, proving that these methodologies can be as effective in improving patient outcomes as they are in driving financial performance. This cross-industry exploration not only highlights the versatility of DevOps but also illustrates the broader impact of this approach, showing how it can drive innovation, improve efficiencies, and foster a culture of continuous improvement across diverse fields. Ultimately, the DevOps journey from FinTech to healthcare is a testament to the adaptability and power of these practices, offering valuable insights for organizations looking to harness the full potential of DevOps, regardless of their industry.},
+	language = {en},
+	number = {1},
+	urldate = {2024-11-20},
+	journal = {Advances in Computer Sciences},
+	author = {Boda, Vishnu Vardhan Reddy},
+	month = jun,
+	year = {2020},
+	note = {Number: 1},
+	file = {Full Text PDF:/home/sam/snap/zotero-snap/common/Zotero/storage/3EX47KYB/Boda - 2020 - From FinTech to Healthcare A DevOps Journey Across Industries.pdf:application/pdf},
+}
+
+@inproceedings{shahin_beyond_2017,
+	address = {Toronto, ON},
+	title = {Beyond {Continuous} {Delivery}: {An} {Empirical} {Investigation} of {Continuous} {Deployment} {Challenges}},
+	isbn = {978-1-5090-4039-1},
+	shorttitle = {Beyond {Continuous} {Delivery}},
+	url = {http://ieeexplore.ieee.org/document/8170091/},
+	doi = {10.1109/ESEM.2017.18},
+	urldate = {2024-11-20},
+	booktitle = {2017 {ACM}/{IEEE} {International} {Symposium} on {Empirical} {Software} {Engineering} and {Measurement} ({ESEM})},
+	publisher = {IEEE},
+	author = {Shahin, Mojtaba and Babar, Muhammad Ali and Zahedi, Mansooreh and Zhu, Liming},
+	month = nov,
+	year = {2017},
+	pages = {111--120},
+	file = {PDF:/home/sam/snap/zotero-snap/common/Zotero/storage/DNQYSJAQ/Shahin et al. - 2017 - Beyond Continuous Delivery An Empirical Investigation of Continuous Deployment Challenges.pdf:application/pdf},
+}
+
+@article{shahin_continuous_2017,
+	title = {Continuous {Integration}, {Delivery} and {Deployment}: {A} {Systematic} {Review} on {Approaches}, {Tools}, {Challenges} and {Practices}},
+	volume = {5},
+	copyright = {https://ieeexplore.ieee.org/Xplorehelp/downloads/license-information/OAPA.html},
+	issn = {2169-3536},
+	shorttitle = {Continuous {Integration}, {Delivery} and {Deployment}},
+	url = {http://ieeexplore.ieee.org/document/7884954/},
+	doi = {10.1109/ACCESS.2017.2685629},
+	urldate = {2024-11-20},
+	journal = {IEEE Access},
+	author = {Shahin, Mojtaba and Ali Babar, Muhammad and Zhu, Liming},
+	year = {2017},
+	pages = {3909--3943},
+	file = {Full Text PDF:/home/sam/snap/zotero-snap/common/Zotero/storage/9QCYCSYY/Shahin et al. - 2017 - Continuous Integration, Delivery and Deployment A Systematic Review on Approaches, Tools, Challenge.pdf:application/pdf},
+}

_config.yml

@@ -4,6 +4,9 @@
 remote_theme:  mmistakes/[email protected]
 plugins:
   - jekyll-remote-theme
+  - jekyll-scholar
+
+repository: Samatgator/msdbok.github.io
 title: Managing Software Development Body of Knowledge
 description: Review of the research in software development management
 
@@ -16,4 +19,8 @@ collections:
   scope:
     output: true
   planning:
-    output: true
+    output: true
+
+
+scholar:
+  style: ieee