ArchCaMO - A Maturity Model for Software Architecture Description Based on ISO/IEC/IEEE 42010:2011

Costa, Ademir Almeida da; Misra, Sanjay; Soares, Michel S.

doi:10.1007/978-3-030-24308-1_3

Cited by 5 publications

(2 citation statements)

References 30 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Test TD -Implementing the TDD (Test-Driven Development) approach [11] -automation testing [11], [39] -Applying Continuous Integration and Continuous Testing (CI/CT) [11] -Collaboration between developers and testers [11] 6 Documentation TD -Documenting important and relevant information [40] -Updating documentation when there are changes [22] -Involving the team in testing and verifying documentation [11] 7…”

Section: A) Technical Debt Classificationmentioning

confidence: 99%

Lean and Agile Software Development for Managing Technical Debt on A Large-scale Software: A Systematic Literature Review

Simangunsong,

Raharjo,

Anita Nur Fitriani

2024

ijcs

View full text Add to dashboard Cite

Agile methodologies are employed by software development teams for collaboration and adapting to changing requirements. However, this flexibility may lead to technical debt (TD), causing potential bugs in the long term. Lean principles, focusing on waste elimination and continuous process improvement, can be applied to manage TD in agile software development. This research conducts a systematic literature review on using lean and agile methodologies for TD management. The review identifies 34 papers, categorizing TD types, pinpointing lean and agile principles, and aligning technical debt categories with suitable lean and agile principles. Additionally, three existing technical debt management frameworks are identified: the TAP framework, the LTD framework, and the CoDVA framework. The study concludes that integrating lean principles into agile software development assists organizations in effectively managing technical debt. Furthermore, the research offers insights into selecting the most suitable TD management framework based on an organization's needs and available resources.

show abstract

Section: A) Technical Debt Classificationmentioning

confidence: 99%

Lean and Agile Software Development for Managing Technical Debt on A Large-scale Software: A Systematic Literature Review

Simangunsong,

Raharjo,

Anita Nur Fitriani

2024

ijcs

View full text Add to dashboard Cite

show abstract

“…Activities related to each one of these software engineering elements have been proposed in the past decades. However, processes related to software architecture are often neglected [ 2 , 9 , 10 , 16 ], even though it is well-known in industry and academia that software architecture processes are considered a critical success factor [ 5 ], and even for agile software development, software architecture processes and activities have been considered important [ 1 ].…”

Section: Introductionmentioning

confidence: 99%

Architecture Conceptualization for Health Information Systems Using ISO/IEC/IEEE 42020

Santos

Misra

Soares

2020

Computational Science and Its Applications – ICCSA 2020

Self Cite

View full text Add to dashboard Cite

Health Information Systems (HIS) are complex systems which present many difficulties in their development. From the software engineering point of view, among the difficulties for HIS development are the necessity of managing and controlling data that must be held for decades, even considering the evolution of technology in the following years, as well as the necessity of cooperating with legacy systems and describing the needs and concerns of a variety of stakeholders. Considering the domain, HIS deal with human life, and errors during software development, management and operation can be catastrophic. These concerns are relevant from the software architecture point of view. Therefore, developing HIS based on a solid software architecture is a success factor that cannot be neglected. However, the processes related to the software architecture of HIS are often considered only from low level of abstraction, even for software architecture description. The ISO/IEC/IEEE 42020 defines 6 clauses for architecture process, among them the Architecture Conceptualization process is the subject of this paper. Given the importance of establishing a well-defined software architecture, and considering the difficulties of understanding an architectural standard, and also considering that ISO/IEC/IEEE 42020 has only recently been published, we propose a framework for using the Architecture Conceptualization clause, which leverages high level concepts and elements of software architecture. A case study on a HIS is described.

show abstract

eHealth: A Focus on Software Architectures for Brazilian Public Health

Gonçalves

Pereira

Akkari

2022

Proceedings of the 7th Brazilian Technology Symposium (BTSym’21)

View full text Add to dashboard Cite

ArchCaMO - A Maturity Model for Software Architecture Description Based on ISO/IEC/IEEE 42010:2011

Cited by 5 publications

References 30 publications

Lean and Agile Software Development for Managing Technical Debt on A Large-scale Software: A Systematic Literature Review

Lean and Agile Software Development for Managing Technical Debt on A Large-scale Software: A Systematic Literature Review

Architecture Conceptualization for Health Information Systems Using ISO/IEC/IEEE 42020

eHealth: A Focus on Software Architectures for Brazilian Public Health

Contact Info

Product

Resources

About