Mostrar el registro sencillo del ítem
Improving hardware/software interface management in systems of systems through documentation as code
dc.contributor.author | Cadavid, Héctor | |
dc.contributor.author | Andrikopoulos, Vasilios | |
dc.contributor.author | Avgeriou, Paris | |
dc.date.accessioned | 2024-07-12T20:10:57Z | |
dc.date.available | 2024-07-12T20:10:57Z | |
dc.date.issued | 2023 | |
dc.identifier.issn | 1573-7616 | spa |
dc.identifier.uri | https://repositorio.escuelaing.edu.co/handle/001/3165 | |
dc.description.abstract | Context: The management of Interface Control Documents (ICDs) has shown to be a major pain point in the architecting processes of Systems of Systems (SoS). Objective ThisworkaimstoimproveonpreviouslyidentifiedICDmanagementissuesusing the documentation-as-code philosophy as a potential basis for a treatment, and in collaboration with practitioners. Method: Weconducted a Technical Action Research (TAR) study with a group of engineers at the Netherlands Radio Astronomy Institute (ASTRON), in the context of the LOFAR radio telescope. An additional research instrument, in the form of an expert panel, was used to evaluate the transferability of the proposed treatment to alternative domains. Results: In-depth insights on previously identified interface management issues were gained. Based on these insights a functional proof-of-concept was developed aimed at addressing these issues following the documentation-as-code principles. In addition to receiving overall positive reviews from practitioners and experts, further areas of improvement and transferability considerations for future work were identified. Conclusions: The proposed approach, which to our knowledge has not been explored before in this context, is promising to address some of the recurring interfacing-related issues with directed SoS in multiple engineering domains. This could be done mainly by enforcing consistency and completeness on both text-based and formal elements of the ICDs, and turning ICDs into single sources of truth for the architecting processes of large scale SoS. | eng |
dc.description.abstract | Contexto: La gestión de documentos de control de interfaz (ICD) ha demostrado ser un punto importante en los procesos de arquitectura de sistemas de sistemas (SoS). Objetivo Este trabajo tiene como objetivo mejorar los problemas de gestión de ICD previamente identificados utilizando la filosofía de documentación como código como base potencial para un tratamiento y en colaboración con los profesionales. Método: Llevamos a cabo un estudio de Investigación de Acción Técnica (TAR) con un grupo de ingenieros del Instituto de Radioastronomía de los Países Bajos (ASTRON), en el contexto del radiotelescopio LOFAR. Se utilizó un instrumento de investigación adicional, en forma de un panel de expertos, para evaluar la transferibilidad del tratamiento propuesto a dominios alternativos. Resultados: Se obtuvieron conocimientos profundos sobre problemas de gestión de interfaces previamente identificados. Sobre la base de estos conocimientos, se desarrolló una prueba de concepto funcional destinada a abordar estos problemas siguiendo los principios de documentación como código. Además de recibir críticas positivas en general de profesionales y expertos, se identificaron otras áreas de mejora y consideraciones de transferibilidad para trabajos futuros. Conclusiones: El enfoque propuesto, que hasta donde sabemos no se ha explorado antes en este contexto, promete abordar algunos de los problemas recurrentes relacionados con la interfaz con SoS dirigido en múltiples dominios de ingeniería. Esto podría lograrse principalmente imponiendo coherencia e integridad a los elementos formales y basados en texto de los ICD, y convirtiendo los ICD en fuentes únicas de verdad para los procesos de arquitectura de SoS a gran escala. | spa |
dc.format.extent | 35 páginas | spa |
dc.format.mimetype | application/pdf | spa |
dc.language.iso | eng | spa |
dc.publisher | Springer | spa |
dc.source | https://link.springer.com/journal/10664 | spa |
dc.title | Improving hardware/software interface management in systems of systems through documentation as code | eng |
dc.type | Artículo de revista | spa |
dc.type.version | info:eu-repo/semantics/publishedVersion | spa |
oaire.accessrights | http://purl.org/coar/access_right/c_abf2 | spa |
oaire.version | http://purl.org/coar/version/c_970fb48d4fbd8a85 | spa |
dc.contributor.researchgroup | CTG - Informática | spa |
dc.identifier.eissn | 1573-7616 | spa |
dc.identifier.instname | Universidad Escuela Colombiana de Ingeniería Julio Garavito | spa |
dc.identifier.reponame | Repositorio Digital | spa |
dc.identifier.repourl | https://repositorio.escuelaing.edu.co/ | spa |
dc.publisher.place | Estados Unidos | spa |
dc.relation.citationedition | Vol. 28 No. 4 2023 | spa |
dc.relation.citationendpage | 35 | spa |
dc.relation.citationissue | 4 | spa |
dc.relation.citationstartpage | 1 | spa |
dc.relation.citationvolume | 28 | spa |
dc.relation.ispartofjournal | Empirical Software Engineering | eng |
dc.relation.references | Maier MW (1998) Architecting principles for systems-of-systems. Syst Eng J Int Council Syst Eng 1(4): 267–284 | spa |
dc.relation.references | ISO, IEC, (2019) 21839 information technology- systems and software engineering- system of systems (sos) considerations in life cycle stages of a system. Standard, International Organization for Standardization, Geneva, CH | spa |
dc.relation.references | Cadavid H, Andrikopoulos V, Avgeriou P (2020) Architecting systems of systems: A tertiary study. Inf Softw Technol 118:106202 | spa |
dc.relation.references | CadavidH,AndrikopoulosV,AvgeriouP,KleinJ(2020)Asurveyontheinterplaybetweensoftwareengineeringandsystemsengineeringduringsosarchitecting.InProceedingsofthe14thACM/IEEEInternational Symposium on Empirical Software Engineering and Measurement (ESEM). ESEM ’20. Association for Computing Machinery, New York, NY USA | spa |
dc.relation.references | Cadavid H, Andrikopoulos V, Avgeriou P, Broekema PC (2021) System- and software-level architecting harmonizationpracticesforsystems-of-systems:Anexploratorycasestudyonalong-runninglarge-scale scientific instrument. In 2021 IEEE 18th International Conference on Software Architecture (ICSA), pp 13–24 | spa |
dc.relation.references | Cadavid H, Andrikopoulos V, Avgeriou P, Broekema PC (2022) System and software architecting harmonization practices in ultra-large-scale systems of systems: A confirmatory case study. Inf Softw Technol 150:106984 | spa |
dc.relation.references | Sheard S, Creel R, Cadigan J, Marvin J, Chim L, Pafford ME (2018) Incose working group addresses system and software interfaces. INSIGHT 21(3):62–71 | spa |
dc.relation.references | Cadavid H, Andrikopoulos V, Avgeriou P (2022) Documentation-as-code for interface control document management in systems of systems: A technical action research study. In European Conference on Software Architecture, pp 19–37 Springer | spa |
dc.relation.references | Gentle A (2017) Docs Like Code. Lulu Press, Inc Morrisville, North Carolina | spa |
dc.relation.references | Beck R (2015) In Lazarian A, de Gouveia Dal Pino EM. In: Melioli C (ed) Future Observations of Cosmic Magnetic Fields with LOFAR, SKA and Its Precursors. Springer, Berlin, Heidelberg, pp 3–17 | spa |
dc.relation.references | Firesmith D (2010) Profiling systems using the defining characteristics of systems of systems (sos) | spa |
dc.relation.references | Thomchick R (2018) Improving access to api documentation for developers with docs-as-code-as-a-service. Proceedings of the association for information science and technology 55(1):908–910 | spa |
dc.relation.references | Lambourne J (2017) Why we use a ’docs as code’ approach for technical documentation. https://technology. blog.gov.uk/2017/08/25/why-we-use-a-docs-as-code-approach-for-technical-documentation/ | spa |
dc.relation.references | Rong G, Jin Z, Zhang H, Zhang Y, Ye W, Shao D (2020) Devdocops: Enabling continuous documentation in alignment with devops. Softw Practice Exp 50(3):210–226 | spa |
dc.relation.references | Rahmani K, Thomson V (2011) Managing subsystem interfaces of complex products. Int J Product Lifecycle Management 5(1):73 | spa |
dc.relation.references | Louadah H, Champagne R (2014) Labiche Y. Towards automating interface control documents elaboration and management 1250:26–33 | spa |
dc.relation.references | Harvey D, Waite M, Logan P, Liddy T (2012) Document the model, don’t model the document. In Proc Syst Eng/Test Eval Conf 6th Asia Pac Conf Syst Eng | spa |
dc.relation.references | Karban R, Troy M, Brack GL, Dekens FG, Michaels SB, Herzig S (2018) Verifying Interfaces and generating interface control documents for the alignment and phasing subsystem of the Thirty Meter Telescope from a system model in SysML. In: Angeli GZ, Dierickx P (eds) Modeling, systems engineering, and project management for astronomy VIII, pp 29 SPIE. Austin United States | spa |
dc.relation.references | Chiozzi G, Andolfato L, Kiekebusch MJ, Kornweibel N, Schilling M, Zamparelli M (2018) Designing and managingsoftwareinterfaces for the ELT.In:GuzmanJC,IbsenJ(eds)SoftwareandCyberinfrastructure for Astronomy V, pp 78 SPIE. Austin United States | spa |
dc.relation.references | Di Maio M, Atorf L, Dahmen U, Schluse M, Rossmann J, Hoppe M, Kapos G-D (2018) Interface management with closed-loop systems engineering (CLOSE). In 2018 IEEE international systems engineering symposium (ISSE), pp 1–8 | spa |
dc.relation.references | Vipavetz K, Shull TA, Infeld S, Price J (2016) Interface management for a NASA flight project using modelbased systems engineering (MBSE). INCOSE Int Symposium 26(1):1129–1144 | spa |
dc.relation.references | Tsui R, Davis D, Sahlin J (2018) Digital engineering models of complex systems using model-based systems engineering (mbse) from enterprise architecture (ea) to systems of systems (sos) architectures & systems development life cycle (sdlc). In INCOSE international symposium, vol 28, pp 760–776 Wiley Online Library | spa |
dc.relation.references | Japs S, Anacker H, Dumitrescu R (2021) Save: Security & safety by model-based systems engineering on the example of automotive industry. Procedia CIRP 100:187–192 | spa |
dc.relation.references | WheatcraftLS(2010)9.2.2everythingyouwantedtoknowaboutinterfaces,butwereafraidtoask.InINCOSE international symposium, vol 20, pp 1132–1149 Wiley Online Library | spa |
dc.relation.references | BroyM,BöhmW,RumpeB(2021)Advancedsystemsengineering.Model-BasedEngineeringofCollaborative Embedded Systems. Springer, New York, NY, pp 353–364 | spa |
dc.relation.references | Guo D, Zhang X, Zhang J, Li H (2020) An interface management approach for civil aircraft design. In International Conference on Aerospace System Science and Engineering, pp 435–446 Springer | spa |
dc.relation.references | van Haarlem MP, Wise MW, Gunst A, Heald G, McKean JP, Hessels JW, de Bruyn AG, Nijboer R, Swinbank J, Fallows R et al (2013) Lofar: The low-frequency array. Astronomy & Astrophysics 556:2 | spa |
dc.relation.references | Yasseri SF, Bahai H (2019) Interface and integration management for FPSOs. Ocean Eng 191:106441 | spa |
dc.relation.references | Borrowman AJ, Taylor P (2016) Can your software engineer program your PLC? In: Chiozzi G, Guzman JC (eds) Software and Cyberinfrastructure for Astronomy IV, vol 9913, pp 99131. WA International Society for Optics and Photonics, SPIE, Bellingham | spa |
dc.relation.references | Wieringa RJ (2014) Design science methodology for information systems and software engineering. Springer, New York, NY | spa |
dc.relation.references | Kontio J, Bragge J, Lehtola L (2008) In Shull F. In: Singer J, Sjøberg DIK (eds) The Focus group method as an Empirical tool in software engineering. Springer, London, pp 93–116 | spa |
dc.relation.references | Petersen K, Gencel C, Asghari N, Baca D, Betz S (2014) Action research as a model for industry-academia collaboration in the software engineering context. In Proceedings of the 2014 international workshop on long-term industrial collaboration on software engineering, pp 55–62 | spa |
dc.relation.references | Fairley RE (2019) Systems engineering of software-enabled systems. Wiley Online Library, River Street Hoboken, NJ | spa |
dc.relation.references | Ralph P, Tempero E (2018) Construct validity in software engineering research and software metrics. In Proceedingsofthe22ndInternationalConferenceonEvaluationandAssessmentinSoftwareEngineering 2018, pp 13–23 | spa |
dc.rights.accessrights | info:eu-repo/semantics/openAccess | spa |
dc.subject.armarc | Análisis de sistemas | |
dc.subject.armarc | System analysis | |
dc.subject.armarc | Procesamiento electrónico de datos - Técnicas estructuradas | |
dc.subject.armarc | Electronic data processing - Structured techniques | |
dc.subject.armarc | Ingeniería de sistemas - Investigaciones | |
dc.subject.armarc | Systems engineering - Research | |
dc.subject.proposal | System of systems | eng |
dc.subject.proposal | Sistema de sistemas | spa |
dc.subject.proposal | Interface control document | eng |
dc.subject.proposal | Documento de control de interfaz | spa |
dc.subject.proposal | Documentation as code | eng |
dc.subject.proposal | Documentación como código | spa |
dc.subject.proposal | Technical action research | eng |
dc.subject.proposal | Investigación acción técnica | spa |
dc.type.coar | http://purl.org/coar/resource_type/c_6501 | spa |
dc.type.content | Text | spa |
dc.type.driver | info:eu-repo/semantics/article | spa |
Ficheros en el ítem
Este ítem aparece en la(s) siguiente(s) colección(ones)
-
AD - CTG – Informática [83]
Clasificación B- Convocatoria 2018