bibliography.bib

@misc{AI:2020,
  author        = "Rick Stevens
                   and Valerie Taylor
                   and Jeff Nichols
                   and Arthur Barney Maccabe
                   and Katherine Yelick
                   and David Brown",
  title         = "{AI} for Science Report",
  month         = mar,
  year          = "2020",
  url           = "https://www.anl.gov/ai-for-science-report"
}

@techreport{CF:2020,
  author        = "{Argonne National Laboratory}",
  title         = "{DOE} National Laboratories' Computational Facilities - {R}esearch Workshop Report",
  institution   = "{Argonne National Laboratory}",
  number        = "ANL/MCS-TM-388",
  address       = "Lemont, IL, USA",
  month         = feb,
  year          = "2020",
  url           = "https://publications.anl.gov/anlpubs/2020/02/158604.pdf"
}

@techreport{IRI:2023,
  author        = "William L. Miller
                   and Deborah Bard
                   and Amber Boehnlein
                   and Kjiersten Fagnan
                   and Chin Guok
                   and Eric Lan\c{c}on
                   and Sreeranjani Ramprakash
                   and Mallikarjun Shankar
                   and Nicholas Schwarz
                   and Benjamin L. Brown",
  title         = "Integrated Research Infrastructure Architecture Blueprint Activity (Final Report 2023)",
  institution   = "US Department of Energy, Office of Science",
  number        = "1984466",  year          = "2023",
  url           = "https://doi.org/10.2172/1984466"
}

@misc{DoDAF2:2010,
  author        = "{U.S. Department of Defense}",
  title         = "The {DoDAF} Architecture Framework Version 2.02",
  month         = aug,
  year          = "2010",
  url           = "https://dodcio.defense.gov/Library/DoD-Architecture-Framework"
}

@book{Alexander:1977,
  author        = "Christopher Alexander
                   and Sara Ishikawa
                   and Murray Silverstein",
  title         = "A Pattern Language: Towns, Buildings, Construction",
  publisher     = "Oxford University Press",
  month         = aug,
  year          = "1977",
  isbn          = "978-0195019193"
}

@book{Cole:1991,
  author        = "Murray Cole",
  title         = "Algorithmic Skeletons: Structured Management of Parallel
                   Computation",
  year          = "1991",
  isbn          = "978-0273088073",
  publisher     = "MIT Press",
  address       = "Cambridge, MA, USA"
}

@article{Cole:2004,
  author        = "Murray Cole",
  title         = "Bringing Skeletons out of the Closet: A Pragmatic Manifesto
                   for Skeletal Parallel Programming",
  journal       = "Parallel Computing",
  volume        = "30",
  number        = "3",
  month         = mar,
  year          = "2004",
  issn          = "0167-8191",
  pages         = "389--406",
  doi           = "10.1016/j.parco.2003.12.002",
  url           = "https://dx.doi.org/10.1016/j.parco.2003.12.002",
  publisher     = "Elsevier Science Publishers B. V."
}

@book{Gamma:1995,
  author        = "Erich Gamma
                   and Richard Helm
                   and Ralph Johnson
                   and John Vlissides",
  title         = "Design Patterns: Elements of Reusable Object-oriented
                   Software",
  year          = "1994",
  isbn          = "978-0201633610",
  publisher     = "Addison-Wesley Professional"
}

@book{Buschmann:1996,
  author        = "Frank Buschmann
                   and Regine Meunier
                   and Hans Rohnert
                   and Peter Sommerlad
                   and Michael Stal",
  title         = "Pattern-Oriented Software Architecture - Volume 1: A System
                   of Patterns",
  month         = aug,
  year          = "1996",
  isbn          = "978-0-471-95869-7",
  publisher     = "Wiley Publishing"
}

@book{Schmidt:2000,
  author        = "Douglas C. Schmidt
                   and Michael Stal
                   and Hans Rohnert
                   and Frank Buschmann",
  title         = "Pattern-Oriented Software Architecture Volume 2: Patterns
                   for Concurrent and Networked Objects",
  year          = "2000",
  isbn          = "978-0471606956",
  publisher     = "Wiley Publishing"
}

@book{Kircher:2004,
  author        = "Michael Kircher
                   and Prashant Jain",
  title         = "Pattern-Oriented Software Architecture, Volume 3: Patterns
                   for Resource Management",
  year          = "2004",
  isbn          = "978-0470845257",
  publisher     = "Wiley Publishing"
}

@book{Buschmann:2007,
  author        = "Frank Buschmann
                   and Kevin Henney
                   and Douglas C. Schmidt",
  title         = "Pattern-Oriented Software Architecture - Volume 4: A Pattern
                   Language for Distributed Computing",
  year          = "2007",
  isbn          = "978-0470059029",
  publisher     = "Wiley Publishing"
}

@book{Mattson:2004,
  author        = "Timothy Mattson
                   and Beverly Sanders
                   and Berna Massingill",
  title         = "Patterns for Parallel Programming",
  year          = "2004",
  isbn          = "978-0321228116",
  edition       = "First",
  publisher     = "Addison-Wesley Professional"
}

@misc{Mattson:OPL:2009,
  author        = "Kurt Keutzer and Timothy Mattson", 
  title         = "Our Pattern Language ({OPL}): A design pattern language for
                   engineering (parallel) software", 
  year          = "2009",
  url           = "https://patterns.eecs.berkeley.edu/?page_id=98"
}

@inproceedings{McCool:2010,
  author        = "Michael D. McCool",
  title         = "Structured Parallel Programming with Deterministic Patterns",
  booktitle     = "Proceedings of the 2nd USENIX Conference on Hot Topics in
                   Parallelism (HotPar) 2010",
  month         = jun,
  year          = "2010",
  location      = "Berkeley, CA, USA",
  publisher     = "USENIX Association",
  url           = "https://www.usenix.org/legacy/event/hotpar10/tech/full_papers/McCool.pdf"
}

@book{McCool:2012,
  author        = "Michael McCool
                   and James Reinders
                   and Arch Robison",
  title         = "Structured Parallel Programming: Patterns for Efficient
                   Computation",
  year          = "2012",
  isbn          = "978-0-12-415993-8",
  publisher     = "Elsevier"
}

@inproceedings{Talton:2012,
  author        = "Jerry Talton
                   and Lingfeng Yang
                   and Ranjitha Kumar
                   and Maxine Lim
                   and Noah Goodman
                   and Radom\'{\i}r M\v{e}ch",
  title         = "Learning Design Patterns with Bayesian Grammar Induction",
  booktitle     = "Proceedings of the 25th Annual ACM Symposium on User
                   Interface Software and Technology (UIST) 2012",
  year          = "2012",
  isbn          = "978-1-4503-1580-7",
  location      = "Cambridge, Massachusetts, USA",
  pages         = "63--74",
  publisher     = "ACM",
  address       = "New York, NY, USA",
  doi           = "10.1145/2380116.2380127",
  url           = "https://dx.doi.org/10.1145/2380116.2380127"
}

@book{Borchers:2001,
 author         = "Jan Borchers",
 title          = "A Pattern Approach to Interaction Design",
 year           = "2001",
 isbn           = "978-0471498285",
 publisher      = "John Wiley \& Sons, Inc.",
 address        = "New York, NY, USA"
}

@book{Duyne:2002,
  author        = "Douglas K. Van Duyne
                   and James Landay
                   and Jason I. Hong",
  title         = "The  Design of Sites: Patterns, Principles, and Processes for
                   Crafting a Customer-Centered Web Experience",
  year          = "2002",
  isbn          = "978-0201721492",
  publisher     = "Addison-Wesley Longman Publishing Co., Inc.",
  address       = "Boston, MA, USA"
}

@article{Heer:2006,
  author        = "Jeffrey Heer and
                   Maneesh Agrawala",
  title         = "Software Design Patterns for Information Visualization",
  journal       = "IEEE Transactions on Visualization and Computer Graphics",
  issue_date    = "September 2006",
  volume        = "12",
  number        = "5",
  month         = sep,
  year          = "2006",
  issn          = "1077-2626",
  pages         = "853--860",
  doi           = "10.1109/TVCG.2006.178",
  url           = "https://dx.doi.org/10.1109/TVCG.2006.178"
}

@techreport{Dougherty:2009,
  author        = "Chad Dougherty
                   and Kirk Sayre
                   and Robert Seacord
                   and David Svoboda
                   and Kazuya Togashi",
  title         = "Secure Design Patterns",
  year          = "2009",
  number        = "CMU/SEI-2009-TR-010",
  institution   = "Software Engineering Institute, Carnegie Mellon University",
  address       = "Pittsburgh, PA",
  doi           = "10.1184/R1/6583640.v1",
  url           = "https://dx.doi.org/10.1184/R1/6583640.v1"
}

@article{hukerikar17resilience,
  author        = "Saurabh Hukerikar
                   and Christian Engelmann",
  title         = "Resilience Design Patterns: {A} Structured Approach to
                   Resilience at Extreme Scale",
  journal       = "{http://superfri.org/superfri}{Journal of
                   Supercomputing Frontiers and Innovations (JSFI)}",
  volume        = "4",
  number        = "3",
  pages         = "4--42",
  month         = oct,
  year          = "2017",
  publisher     = "{http://www.susu.ru/en}{South Ural State University
                   Chelyabinsk, Russia}",
  issn          = "2409-6008",
  doi           = "10.14529/jsfi170301",
  url           = "https://dx.doi.org/10.14529/jsfi170301"
}

@book{Fowler:2002,
  author        = "Martin Fowler",
  title         = "Patterns of Enterprise Application Architecture",
  year          = "2002",
  isbn          = "978-0321127426",
  publisher     = "Addison-Wesley Longman Publishing Co., Inc.",
  address       = "Boston, MA, USA"
}

@article{aalst02workflow,
  author        = "W.M.P. van der Aalst
                   and A.H.M. ter Hofstede
                   and B. Kiepuszewski
                   and A.P. Barros",
  title         = "Workflow Patterns",
  journal       = "{https://www.springer.com/journal/10619}
                   {Distributed and Parallel Databases}",
  volume        = "14",
  number        = "1",
  pages         = "5--51",
  year          = "2003",
  publisher     = "{https://www.springer.com/}{Springer}",
  issn          = "1573-7578",
  doi           = "10.1023/A:1022883727209",
  abstract      = "Differences in features supported by the various contemporary
                   commercial workflow management systems point to different
                   insights of suitability and different levels of expressive
                   power. The challenge, which we undertake in this paper, is to
                   systematically address workflow requirements, from basic to
                   complex. Many of the more complex requirements identified,
                   recur quite frequently in the analysis phases of workflow
                   projects, however their implementation is uncertain in
                   current products. Requirements for workflow languages are
                   indicated through workflow patterns. In this context,
                   patterns address business requirements in an imperative
                   workflow style expression, but are removed from specific
                   workflow languages. The paper describes a number of workflow
                   patterns addressing what we believe identify comprehensive
                   workflow functionality. These patterns provide the basis for
                   an in-depth comparison of a number of commercially available
                   work flow management systems. As such, this paper can be
                   seen as the academic response to evaluations made by
                   prestigious consulting companies. Typically, these
                   evaluations hardly consider the workflow modeling language
                   and routing capabilities, and focus more on the purely
                   technical and commercial aspects."
}

@article{GARIJO2014338,
title = {Common motifs in scientific workflows: An empirical analysis},
journal = {Future Generation Computer Systems},
volume = {36},
pages = {338-351},
year = {2014},
note = {Special Section: Intelligent Big Data Processing Special Section: Behavior Data Security Issues in Network Information Propagation Special Section: Energy-efficiency in Large Distributed Computing Architectures Special Section: eScience Infrastructure and Applications},
issn = {0167-739X},
doi = {https://doi.org/10.1016/j.future.2013.09.018},
url = {https://www.sciencedirect.com/science/article/pii/S0167739X13001970},
author = {Daniel Garijo and Pinar Alper and Khalid Belhajjame and Oscar Corcho and Yolanda Gil and Carole Goble},
keywords = {Scientific workflows, Workflow motif, Workflow pattern, Taverna, Wings, Galaxy, Vistrails},
abstract = {Workflow technology continues to play an important role as a means for specifying and enacting computational experiments in modern science. Reusing and re-purposing workflows allow scientists to do new experiments faster, since the workflows capture useful expertise from others. As workflow libraries grow, scientists face the challenge of finding workflows appropriate for their task, understanding what each workflow does, and reusing relevant portions of a given workflow. We believe that workflows would be easier to understand and reuse if high-level views (abstractions) of their activities were available in workflow libraries. As a first step towards obtaining these abstractions, we report in this paper on the results of a manual analysis performed over a set of real-world scientific workflows from Taverna, Wings, Galaxy and Vistrails. Our analysis has resulted in a set of scientific workflow motifs that outline (i) the kinds of data-intensive activities that are observed in workflows (Data-Operation motifs), and (ii) the different manners in which activities are implemented within workflows (Workflow-Oriented motifs). These motifs are helpful to identify the functionality of the steps in a given workflow, to develop best practices for workflow design, and to develop approaches for automated generation of workflow abstractions.}
}

@article{VESCOVI2022100606,
title = {Linking scientific instruments and computation: Patterns, technologies, and experiences},
journal = {Patterns},
volume = {3},
number = {10},
pages = {100606},
year = {2022},
issn = {2666-3899},
doi = {https://doi.org/10.1016/j.patter.2022.100606},
url = {https://www.sciencedirect.com/science/article/pii/S2666389922002318},
author = {Rafael Vescovi and Ryan Chard and Nickolaus D. Saint and Ben Blaiszik and Jim Pruyne and Tekin Bicer and Alex Lavens and Zhengchun Liu and Michael E. Papka and Suresh Narayanan and Nicholas Schwarz and Kyle Chard and Ian T. Foster},
keywords = {Experiment automation, workflow, Globus, synchrotron light source, big data, machine learning, data fabric, computing fabric, trust fabric, scientific facility},
abstract = {Summary
Powerful detectors at modern experimental facilities routinely collect data at multiple GB/s. Online analysis methods are needed to enable the collection of only interesting subsets of such massive data streams, such as by explicitly discarding some data elements or by directing instruments to relevant areas of experimental space. Thus, methods are required for configuring and running distributed computing pipelines—what we call flows—that link instruments, computers (e.g., for analysis, simulation, artificial intelligence [AI] model training), edge computing (e.g., for analysis), data stores, metadata catalogs, and high-speed networks. We review common patterns associated with such flows and describe methods for instantiating these patterns. We present experiences with the application of these methods to the processing of data from five different scientific instruments, each of which engages powerful computers for data inversion,model training, or other purposes. We also discuss implications of such methods for operators and users of scientific facilities.}
}

@article{doi:10.1021/acsnano.1c02104,
author = {Kalinin, Sergei V. and Ziatdinov, Maxim and Hinkle, Jacob and Jesse, Stephen and Ghosh, Ayana and Kelley, Kyle P. and Lupini, Andrew R. and Sumpter, Bobby G. and Vasudevan, Rama K.},
title = {Automated and Autonomous Experiments in Electron and Scanning Probe Microscopy},
journal = {ACS Nano},
volume = {15},
number = {8},
pages = {12604-12627},
year = {2021},
doi = {10.1021/acsnano.1c02104},
URL = {https://doi.org/10.1021/acsnano.1c02104},
eprint = {https://doi.org/10.1021/acsnano.1c02104}
}

@INPROCEEDINGS{9812673,
  author={Torkjazi, Mohammadreza and Raz, Ali K.},
  booktitle={2022 17th Annual System of Systems Engineering Conference (SOSE)}, 
  title={A Taxonomy for System of Autonomous Systems}, 
  year={2022},
  volume={},
  number={},
  pages={198-203},
  doi={10.1109/SOSE55472.2022.9812673}}

@article{hanchen23scientific,
  author        = "Wang, Hanchen
                   and Fu, Tianfan
                   and Du, Yuanqi
                   and Gao, Wenhao
                   and Huang, Kexin
                   and Liu, Ziming
                   and Chandak, Payal
                   and Liu, Shengchao
                   and Van Katwyk, Peter
                   and Deac, Andreea
                   and Anandkumar, Anima
                   and Bergen, Karianne
                   and Gomes, Carla P.
                   and Ho, Shirley
                   and Kohli, Pushmeet
                   and Lasenby, Joan
                   and Leskovec, Jure
                   and Liu, Tie-Yan
                   and Manrai, Arjun
                   and Marks, Debora
                   and Ramsundar, Bharath
                   and Song, Le
                   and Sun, Jimeng
                   and Tang, Jian
                   and Veličković, Petar
                   and Welling, Max
                   and Zhang, Linfeng
                   and Coley, Connor W.
                   and Bengio, Yoshua
                   and Zitnik, Marinka",
  title         = "Scientific Discovery in the Age of Artificial Intelligence",
  journal       = "Nature",
  volume        = "620",
  month         = aug,
  year          = "2023",
  pages         = "47--60",
  doi           = "10.1038/s41586-023-06221-2",
  url           = "https://doi.org/10.1038/s41586-023-06221-2"
}

@misc{OpenAPI-spec:v3,
  author        = "SmartBear Software",
  title         = "{OpenAPI} Specification - Version 3.0.3",
  year          = "2021",
  url           = "https://swagger.io/specification/"
}

@misc{AsyncAPI-spec:v2,
  author        = "AsyncAPI Project",
  title         = "{AsyncAPI Specification - Version 2.3.0}",
  year          = "2022",
  url           = "https://www.asyncapi.com/docs/specifications/v2.3.0"
}

@misc{IETF:JSON-schema,
  author        = "Internet Engineering Task Force",
  title         = "{JSON Schema: A Media Type for Describing JSON Documents}",
  year          = "2022",
  url           = "https://json-schema.org/draft/2020-12/json-schema-core.html"
}

@misc{OGF:GridFTP,
  author        = "W. Allcock",
  title         = "{GridFTP: Protocol Extensions to FTP for the Grid}",
  year          = "2003",
  url           = "http://www.ogf.org/documents/GFD.20.pdf"
}

@misc{RFC:4122,
  author        = "P. Leach and M. Mealling and R. Salz",
  title         = "{A Universally Unique IDentifier (UUID) URN Namespace}",
  year          = "2005",
  url           = "https://www.rfc-editor.org/rfc/rfc4122.html"
}

@misc{SemanticVersioning:v2,
  title         = "{Semantic Versioning 2.0.0 | Semantic Versioning}",
  year          = "2023",
  url           = "https://semver.org/spec/v2.0.0.html"
}

@misc{Wikipedia:application,
  author        = "Wikipedia",
  title         = "Application software",
  year          = "2022",
  url           = "https://en.wikipedia.org/wiki/Application_software"
}
@misc{W3C:XML-Schema-Definition,
  author        = "World Wide Web Consortium (W3C)",
  title         = "{W3C XML Schema Definition Language (XSD) 1.1 Part 1: Structures}",
  year          = "2012",
  url           = "https://www.w3.org/TR/xmlschema11-1/"
}

@misc{dropbox,
  author        = "DropBox",
  title         = "{Dropbox.com}",
  year          = "2023",
  url           = "https://www.dropbox.com"
}

@misc{globus,
  author        = "{University of Chicago}, and {Argonne National Laboratory}",
  title         = "{Research data management simplified - globus}",
  year          = "2023",
  url           = "https://www.globus.org/"
}


@misc{memcached,
  author        = "Dormando",
  title         = "{memcached - a distributed memory object caching system}",
  year          = "2023",
  url           = "https://memcached.org/"
}

@misc{minio,
  author        = "MinIO",
  title         = "{MinIO | High Performance, Kubernetes Native Object Storage}",
  year          = "2023",
  url           = "https://min.io/"
}

@misc{mongodb,
  author        = "MongoDB",
  title         = "{MongoDB: The Developer Data Platform | MongoDB}",
  year          = "2023",
  url           = "https://www.mongodb.com"
}

@misc{mysql,
  author        = "Oracle",
  title         = "{MySQL}",
  year          = "2023",
  url           = "https://www.mysql.com"
}

@misc{neo4j,
  author        = "Neo4j",
  title         = "{Neo4j Graph Data Platform | Graph Database Management System}",
  year          = "2023",
  url           = "https://neo4j.com"
}

@misc{postgresql,
  author        = "The PostgreSQL Global Development Group",
  title         = "{PostgreSQL: The world's most advanced open source database}",
  year          = "2023",
  url           = "https://www.postgresql.org"
}

@misc{redis,
  author        = "Redis Ltd.",
  title         = "{Redis | The Real-time Data Platform}",
  year          = "2023",
  url           = "https://redis.com/"
}

@misc{sqlite,
  author        = "SQLite Consortium",
  title         = "{SQLite Home Page}",
  year          = "2023",
  url           = "https://www.sqlite.org/"
}

@misc{Amazon:DynamoDB,
  author        = "Amazon Web Services (AWS)",
  title         = "{Fast NoSQL Key-Value Database - Amazon DynamoDB - Amazon Web Services}",
  year          = "2023",
  url           = "https://aws.amazon.com/dynamodb/"
}

@misc{Amazon:Kinesis,
  author        = "Amazon Web Services (AWS)",
  title         = "{Amazon Kinesis - Process \& Analyze Streaming Data - Amazon Web Services}",
  year          = "2023",
  url           = "https://aws.amazon.com/kinesis/"
}

@misc{Amazon:Neptune,
  author        = "Amazon Web Services (AWS)",
  title         = "{Fully Managed Graph Database - Amazon Neptune - Amazon Web Services}",
  year          = "2023",
  url           = "https://aws.amazon.com/neptune/"
}

@misc{Amazon:S3,
  author        = "Amazon Web Services (AWS)",
  title         = "{Cloud Object Storage - Amazon S3 - Amazon Web Services}",
  year          = "2023",
  url           = "https://aws.amazon.com/s3/"
}

@misc{Apache:Avro,
  author        = "The Apache Software Foundation",
  title         = "{Apache Avro 1.11.0 Documentation}",
  year          = "2021",
  url           = "https://avro.apache.org/docs/current/"
}

@misc{Apache:Cassandra,
  author        = "The Apache Software Foundation",
  title         = "{Apache Cassandra | Apache Cassandra Documentation}",
  year          = "2023",
  url           = "https://cassandra.apache.org/"
}

@misc{Apache:Kafka,
  author        = "The Apache Software Foundation",
  title         = "{Apache Kafka}",
  year          = "2023",
  url           = "https://kafka.apache.org"
}

@misc{Google:BigTable,
  author        = "Google",
  title         = "{Cloud Bigtable: HBase-compatible, NoSQL database | Google Cloud}",
  year          = "2023",
  url           = "https://cloud.google.com/bigtable"
}

@misc{Google:CloudStorage,
  author        = "Google",
  title         = "{Cloud Storage | Google Cloud}",
  year          = "2023",
  url           = "https://cloud.google.com/storage"
}

@misc{Google:Drive,
  author        = "Google",
  title         = "{Personal Cloud Storage \& File Sharing Platform - Google}",
  year          = "2023",
  url           = "https://www.google.com/drive/"
}

@misc{Microsoft:AzureBlob,
  author        = "Microsoft",
  title         = "{Azure Blob Storage | Microsoft Azure}",
  year          = "2023",
  url           = "https://azure.microsoft.com/en-us/products/storage/blobs/"
}

@misc{Microsoft:OneDrive,
  author        = "Microsoft",
  title         = "{Microsoft OneDrive Cloud Storage and File Sharing | Microsoft 365}",
  year          = "2023",
  url           = "https://www.microsoft.com/en-us/microsoft-365/onedrive/onedrive-for-business"
}

@misc{EPICS-software,
  author        = "EPICS Controls",
  title         = "{EPICS - Experimental Physics and Industrial Control System}",
  year          = "2023",
  url           = "https://epics-controls.org/"
}
@misc{NionSwift-software,
  author        = "Nion Software",
  title         = "{Welcome to Nion Swift Instrumentation documentation!}",
  year          = "2018",
  url           = "https://nionswift-instrumentation.readthedocs.io/en/latest/index.html"
}

@misc{ROS-software,
  author = "Open Robotics",
  title  = "{ROS: Home}",
  year   = "2021",
  url    = "https://www.ros.org/"
}

@misc{adamantine-software,
  author = "Oak Ridge National Laboratory",
  title  = "{Software to simulate heat transfer for additive manufacturing}",
  year   = "2024",
  url    = "https://github.com/adamantine-sim/adamantine"
}

@misc{Slurm,
  author = "SchedMD",
  title  = "{Slurm Workload Manager - Documentation}",
  year   = "2024",
  url    = "https://slurm.schedmd.com/documentation.html"
}

@misc{Wikipedia:PBS,
  author = "Wikipedia",
  title  = "{Portable Batch System}",
  year   = "2024",
  url    = "https://en.wikipedia.org/wiki/Portable_Batch_System"
}

@misc{IBM:LSF,
  author = "IBM Corporation",
  title  = "{Introduction to IBM Spectrum LSF - IBM Documentation}",
  year   = "2024",
  url    = "https://www.ibm.com/docs/en/spectrum-lsf/10.1.0?topic=overview-lsf-introduction"
}

@misc{IBM:GPFS,
  author = "IBM Corporation",
  title  = "{IBM Storage Scale documentation}",
  year   = "2024",
  url    = "https://www.ibm.com/docs/en/storage-scale"
}

@article{manthorpe96emerging,
  author        = "William H. J. {Manthorpe Jr.}",
  title         = "The Emerging Joint System of Systems: A Systems Engineering Challenge and Opportunity for APL",
  journal       = "John Hopkins APL Technical Digest",
  volume        = "17",
  number        = "3",
  pages         = "305--313",
  month         = jul,
  year          = "1996",
  publisher     = "Johns Hopkins University Applied Physics Laboratory",
  issn          = "0270-5214"
}

@inproceedings{pei00system,
  author        = "Richard S. Pei",
  title         = "System of Systems Integration (SoSI) - A Smart Way of Acquiring Army C4I2WS Systems",
  booktitle     = "Proceedings of the Summer Computer Simulation Conference 2000",
  year          = "2000",
  pages         = "574--579"
}

@misc{iso21839,
  author        = "{ISO/IEC JTC 1/SC 7 Software and systems engineering}",
  title         = "{ISO/IEC/IEEE 21839:2019}",
  month         = jul,
  year          = "2019",
  url           = "https://www.iso.org/standard/71955.html"
}

@article{maier98architecting,
  author        = "Mark. W. Maier",
  title         = "Architecting Principles for System-of-Systems",
  journal       = "Systems Engineering",
  volume        = "1",
  number        = "4",
  pages         = "267--284",
  month         = nov,
  year          = "1998",
  publisher     = "Wiley Subscription Services, Inc., A Wiley Company",
  address       = "New York, NY, USA",
  issn          = "1098-1241",
}

@book{rechtin90systems,
  author        = "Eberhardt Rechtin",
  title         = "Systems Architecting: Creating \& Building Complex Systems",
  year          = "1990",
  isbn          = "978-0138803452",
  publisher     = "Prentice Hall"
}

@book{maier09art,
  author        = "Mark. W. Maier
                   and Eberhardt Rechtin",
  title         = "The Art of Systems Architecting (Systems Engineering)",
  year          = "2009",
  isbn          = "978-1420079135",
  publisher     = "CRC Press",
  address       = "Boca Raton, FL, USA"
}

@misc{darpa22sosite,
  author        = "{Defense Advanced Research Projects Agency, U.S. Department of Defense}",
  title         = "System of Systems Integration Technology and Experimentation (SoSITE)",
  month         = jun,
  year          = "2022",
  url           = "https://www.darpa.mil/program/system-of-systems-integration-technology-and-experimentation"
}

@misc{fortunato22stitches,
  author        = "Evan Fortunato",
  title         = "{STITCHES} - {SoS} Technology Integration Tool Chain for Heterogeneous Electronic Systems",
  month         = sep,
  year          = "2016",
  url           = "https://ndiastorage.blob.core.usgovcloudapi. net/ndia/2016/systems/18869\_Fortunato\_SoSITE\_STITCHES\_Overview\_Long\_ 9Sep2016\_.pdf"
}

@misc{darpa22creating,
  author        = "{Defense Advanced Research Projects Agency, U.S. Department of Defense}",
  title         = "Creating Cross-Domain Kill Webs in Real Time",
  month         = jun,
  year          = "2022",
  url           = "https://www.darpa.mil/news-events/2020-09-18a"
}

@misc{MoDAF:2010,
  author        = "{U.K. Ministry of Defense}",
  title         = "The {MOD} Architecture Framework",
  month         = sep # "~14, ",
  year          = "2011",
  url           = "http://www.modaf.org.uk/"
}

@misc{Kruchten:1995,
  author        = "{Kruchten, P.}",
  title         = "{Architectural Blueprints -- The ``4+1'' View Model of
                    Software Architecture}",
  year          = "1995",
  url           = "http://www.cs.ubc.ca/~gregor/teaching/papers/4+1view-architecture.pdf"
}

@article{ieee:iso42010,
  author = {ISO/IEC/IEEE},
  title = "{Systems and software engineering -- Architecture description}",
  doi = {10.1109/IEEESTD.2011.6129467},
  journal = {ISO/IEC/IEEE 42010:2011(E) (Revision of ISO/IEC 42010:2007 and IEEE Std 1471-2000)},
  month = {1},
  pages = {1 -46},
  timestamp = {2012-07-23T10:06:24.000+0200},
  year = 2011,
  keywords = {architecture iec ieee iso software standard},
  abstract = "{ISO/IEC/IEEE 42010:2011 addresses the creation, analysis and
          sustainment of architectures of systems through the use of
          architecture descriptions. A conceptual model of architecture
          description is established. The required contents of an
          architecture description are specified. Architecture viewpoints,
          architecture frameworks and architecture description languages are
          introduced for codifying conventions and common practices of
          architecture description. The required content of architecture
          viewpoints, architecture frameworks and architecture description
          languages is specified. Annexes provide the motivation and
          background for key concepts and terminology and examples of
          applying ISO/IEC/IEEE 42010:2011.}",
}

@misc{SNS:VULCAN,
  author = "{Oak Ridge National Laboratory}",
  title  = "{Engineering Materials Diffractometer | Neutron Science at ORNL}",
  year   = "2024",
  url    = "https://neutrons.ornl.gov/vulcan"
}

@techreport{engelmann22rdp-20,
  author        = "Christian Engelmann
                   and Rizwan Ashraf
                   and Saurabh Hukerikar
                   and Mohit Kumar
                   and Piyush Sao",
  title         = "Resilience Design Patterns: {A} Structured Approach to
                   Resilience at Extreme Scale (Version 2.0)",
  institution   = "Oak Ridge National Laboratory",
  number        = "ORNL/TM-2022/2809",
  address       = "Oak Ridge, TN, USA",
  month         = aug,
  year          = "2022",
  doi           = "10.2172/1922296",
  url           = "http://www.christian-engelmann.info/publications/engelmann22rdp-20.pdf",
  abstract      = "Reliability is a serious concern for future extreme-scale
                   high-performance computing (HPC) systems. Projections based
                   on the current generation of HPC systems and technology
                   roadmaps suggest the prevalence of very high fault rates in
                   future systems. The errors resulting from these faults will
                   propagate and generate various kinds of failures, which may
                   result in outcomes ranging from result corruptions to
                   catastrophic application crashes. Therefore, the resilience
                   challenge for extreme-scale HPC systems requires coordination
                   between various hardware and software technologies that are
                   capable of handling a broad set of fault models at
                   accelerated fault rates. Also, due to practical limits on
                   power consumption in future HPC systems, they are likely to
                   embrace innovative architectures, increasing the levels of
                   hardware and software complexities. Therefore, the
                   techniques that seek to improve resilience must navigate the
                   complex trade-off space between resilience and the overheads
                   to power consumption and performance. While the HPC community
                   has developed various resilience solutions, application-level
                   techniques as well as system-based solutions, the solution
                   space of HPC resilience techniques remains fragmented. There
                   are no formal methods to integrate the various HPC resilience
                   techniques into composite solutions, nor are there methods to
                   holistically evaluate the adequacy and efficacy of such
                   solutions in terms of their protection coverage, and their
                   performance & power efficiency characteristics. Additionally,
                   few implementations of current resilience solutions are
                   portable to newer architectures and software environments that
                   will be deployed on future systems.
                   We developed a new structured approach to the management of
                   HPC resilience using the concept of resilience-based design
                   patterns. In general, a design pattern is a repeatable
                   solution to a commonly occurring problem. We identified the
                   well-known solutions that are commonly used to deal with
                   faults, errors and failures in HPC systems. In the initial
                   design patterns specification (version 1.0), we described
                   the various solutions, which address specific problems in
                   the design of resilient HPC environments, in the form of
                   patterns. Each pattern describes a problem caused by a fault,
                   error or failure event in an HPC environment, and then
                   describes the core of the solution of the problem in such a
                   way that this solution may be adapted to different systems
                   and implemented at different layers of the system stack. The
                   catalog of these resilience design patterns provides
                   designers with a collection of design elements. To construct
                   complete resilience solutions using combinations of various
                   patterns, we defined a framework that enhances HPC designers'
                   understanding of the important constraints and the
                   opportunities for the design patterns to be implemented and
                   deployed at various layers of the system stack. The design
                   framework is also useful for establishing interfaces and
                   mechanisms to coordinate flexible fault management across
                   hardware and software components, as well as to consider the
                   trade-off between performance, resilience, and power
                   consumption when constructing a solution. The resilience
                   design patterns specification version 1.1 included more
                   detailed explanations of the pattern solutions, the context
                   in which the patterns are applicable, and the implications
                   for hardware or software design. It also provided several
                   additional examples and detailed case studies to demonstrate
                   the use of patterns to build realistic solutions.
                   In this version 1.2 of the specification document, we have
                   improved the pattern descriptions, including graphical
                   representations of the pattern components. These
                   improvements are largely based on critical comments,
                   feedback and suggestions received from pattern experts and
                   readers of the previous versions of the specification. The
                   pattern classification has been modified to further clarify
                   the relationships between pattern categories. This version
                   of the specification also introduces a pattern language for
                   resilience design patterns. The pattern language presents
                   the patterns in the catalog as a network, revealing the
                   relations among the resilience patterns. The language
                   provides designers with the means to explore alternative
                   techniques for handling a specific fault model that may have
                   different efficiency and complexity characteristics. Using
                   the pattern language also enables the design and
                   implementation of comprehensive resilience solutions as a
                   set of interconnected resilience patterns that can be
                   instantiated across layers of the system stack. The overall
                   goal of this work is to provide hardware and software
                   designers, as well as the users and operators of HPC systems,
                   a systematic methodology for the design and evaluation of
                   resilience technologies in HPC systems that keep scientific
                   applications running to a correct solution in a timely and
                   cost-efficient manner despite frequent faults, errors, and
                   failures of various types.
                   Version 2.0 expands the resilience design pattern
                   classification and catalog to include self-stabilization
                   patterns and reliability, availability and performance models
                   for each structural pattern."
}

@misc{Microsoft:Azure:Patterns:Ambassador,
  author        = "Microsoft",
  title         = "{Ambassador pattern - Azure Architecture Center | Microsoft Learn}",
  year          = "2024",
  url           = "https://learn.microsoft.com/en-us/azure/architecture/patterns/retry"
}

@misc{Microsoft:Azure:Patterns:Retry,
  author        = "Microsoft",
  title         = "{Retry pattern - Azure Architecture Center | Microsoft Learn}",
  year          = "2024",
  url           = "https://learn.microsoft.com/en-us/azure/architecture/patterns/retry"
}

@misc{Microsoft:Azure:Patterns:Sidecar,
  author        = "Microsoft",
  title         = "{Sidecar pattern - Azure Architecture Center | Microsoft Learn}",
  year          = "2024",
  url           = "https://learn.microsoft.com/en-us/azure/architecture/patterns/sidecar"
}

@misc{Microsoft:Azure:Patterns:SAS,
  author        = "Microsoft",
  title         = "{Scheduler Agent Supervisor pattern - Azure Architecture Center | Microsoft Learn}",
  year          = "2024",
  url           = "https://learn.microsoft.com/en-us/azure/architecture/patterns/scheduler-agent-supervisor"
}

@misc{olcf:ace,
  author        = "Oak Ridge Leadership Computing Facility (OLCF)",
  title         = "{Advanced Computing Ecosystem (ACE) Testbed}",
  year          = "2024",
  url           = "https://docs.olcf.ornl.gov/ace_testbed/"
}