In contrast, in the Agile software development approach (Hoda et al., 2018), Software Architecture design and evaluation methods, as well as Software Architecture artifacts, are still under academic and practitioner debate (Kruchten, 2010 Abrahamsson et al., 2010 Yang et al., 2016).Īgile approaches have also succeeded in having a more predictable product delivery, schedule, and costs. A vast body of knowledge on Software Architecture (SA) design and evaluation methods exists in the SA literature from a classic and plan-driven approach (Hofmeister et al., 2007 Shahin et al., 2014 Hohpe et al., 2016). A first-class artifact implies that the artifact is considered mandatory to be elaborated in a high-quality system development methodology, because its omission or partial, or low-quality elaboration leads to a flawed software design and lately to a wrong software product. Software Architecture artifacts are considered as the first-class type in the classic and plan-driven software development methodologies (Clemens et al., 2011). Manuel Mora, Autonomous University of Aguascalientes, MexicoĪlok Mishra, Molde University College-Specialized University in Logistics, Norway and Atilim University, Turkey Laporte, École de te chnologie supérieure, Canada Hector Duran-Limon, University of Guadalajara, MexicoĬlaude Y. CfP: Special Issue on Agile, Lightweight and Lean Practices for Designing Software Architectures
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |