Big Data Analytics Systems (BDAS) are software systems developed with descriptive, predictive, or prescriptive decision-making purposes, and currently are implemented in diverse domains – i.e. Healthcare, Finance, and Manufacturing, among others -. BDAS emerged by the joint availability of Analytics techniques and affordable sources of massive internal and external datasets. However, despite the advanced technological progress – i.e. on BDAS algorithms, languages and platforms-, their development has been mainly through uncomplete ad-hoc or old rigorous heavyweight system development life cycles (SDLC). Nowadays, the business competitive environment demands lightweight and agile SDLC, and initial ones have emerged for BDAS. However, studies comparing heavyweight vs lightweight BDAS SDLC are still scarce in the literature. This research, thus, addresses this knowledge gap, and report a comparative review between the main heavyweight (KDD, SEMMA, CRISP-DM, BDPL) and emergent lightweight (ASUM, TDSP, DDSL) SDLC for BDAS, selected through a Selective Systematic Literature Review (SSLR) research method for the 2000-2023 period. For this aim, a Pro Forma of the ISO/IEC 29110 standard – Basic Profile –is used to examine their conceptual structure – i.e. roles, phases-activities, products -. This comparative review provides theoretical and practical insights for discriminating both approaches for BDAS development and calls for further conceptual and empirical research.

Business Process Management Systems (BPMS) are critical for enabling organizations to automate, monitor, and optimize their core processes. While agile software development approaches have transformed traditional systems engineering, their systematic application to BPMS development remains limited and underexplored. Existing agile SDLCs for BPMS are often incomplete, lack standardization, and provide insufficient documentation, hindering their adoption in both academic and professional contexts. This study addresses this gap by designing and validating AgileBPM SDLC, a novel, fine-grained Agile Software Development Life Cycle tailored specifically for BPMS. Grounded in Design Science Research Methodology (DSRM), the proposed model integrates best practices from the Scrum-XP framework and insights from four existing agile BPMS methodologies. The resulting AgileBPM SDLC includes three agile roles, four phases, fifteen activities, and twelve structured artifacts, all comprehensively documented through an open-access Electronic Process Guide (EPG). Validation involved expert review by senior evaluators and comparative assessment using a Rigor-Agility Framework. Results demonstrate the SDLC’s theoretical soundness, alignment with agile principles, and practical applicability. By providing a detailed, reusable framework for agile BPMS development, this study makes a significant contribution to researchers, developers, and organizations seeking faster, more flexible, and well-documented approaches to process-aware information systems.

Education in Software Engineering traditionally focuses on techniques used in the classroom that generate stress and disinterest in the topics taught; therefore, a significant challenge to the use of more effective and motivating teaching methods to achieve student learning. Moreover, the lack of motivating teaching methods results in a lack of perception regarding the importance of artifacts that come together with software, such as documentation. Consequently, students prefer to focus only on development without paying attention to the necessary artifacts, so the maintenance and update of software in later stages are negatively affected. In response to this problem, the need arises to incorporate more dynamic and effective teaching approaches that encourage student participation and commitment. In this sense, Gamification is presented as an innovative solution that has gained increasing interest in Software Engineering and other fields of education. This research aims to provide the results of a case study in which Gamification has been used in teaching Software Engineering for the topic of software requirements within a master's software engineering course.