Lightweight and lean are necessary but not sufficient attributes for agile practices (Qumer and Henderson-Sellers, 2008 Conboy 2009), and thus lightweight and lean practices can be considered in the middle point between agile and plan-driven methods (Wang et al., 2012). To alleviate software architecture design omissions in agile practices, lightweight and lean approaches have been suggested. This omission is considered a weakness of current agile approaches, given the introduction of the technical debt problem (Behutiye et al., 2017) and because it is widely recognized that software architecture design practices help to avoid costly errors to be corrected in the subsequent software process development phases (Boehm, 2002). However, whereas a well-documented software architecture design activity is mandatory in plan-driven methodologies (Reyes-Delgado et al., 2016), this is not promoted by agile practices (Kruchten, 2010 Abrahamsson et al., 2010).
Therefore, Agile development has gained large acceptance in Industry as a methodology to increase adaptability to changes as opposed to the rigidity of rigor-oriented methodologies (Hoda et al., 2018). Agile processes are very dynamic and flexible and eliminate much of the bureaucratic documentation procedures of rigor-oriented methodologies.
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 kommentar(er)
