Search

Human decomposition studies aim to understand the various factors influencing human decay to assess the deceased and develop postmortem interval (PMI) estimation methods. These types of studies are typically conducted through physical experiments examining the deceased; however, big data systems have the potential to transform how large‐scale forensic anthropology research questions can be addressed with curated images of donors with known demographic, climatic, and postmortem historical data. This study introduces ICPUTRD (Image Cloud Platform for Use in Tagging and Research on Decomposition), a web‐based software system, which enables forensic scientists to easily access, enhance (or curate), and analyze very large photographic collections documenting the longitudinal process of human decomposition. ICPUTRD, a JavaScript‐based application, was designed and built through a combination of the Waterfall and Agile software development life‐cycle methods and provides an image search and tagging features with a predefined nomenclature of forensic‐related keywords. To evaluate the system, a user study was conducted, involving 27 participants who completed pre‐ and post‐study surveys and three research tasks. Analysis of the study results confirmed the feasibility and practicality of ICPUTRD to facilitate aspects of forensic research and casework involving large collections of digital photographs of human decomposition. It was observed that the nomenclature lacked certain law enforcement keywords, so future work will focus on expanding it to ensure ICPUTRD is suited for all its intended users. [ABSTRACT FROM AUTHOR]

Agile methods have emerged to overcome the obstacles of structured methodologies, such as the waterfall, prototype, spiral, and so on. There are studies showing the usefulness of agile approaches in software development. However, studies on Agile maintenance are very limited in number. Regardless of the chosen methodology, software maintenance can be carried out in either a local (on‐the‐premise) or global (distributed) environment. In a local environment, the software maintenance team is co‐located on the same premises, while in a global environment, the team is geographically dispersed from the customer. The main objective of this Systematic Mapping (SM) study is to identify the practices useful for software maintenance using the Agile approaches in the Cloud environment. We have conducted a comprehensive search in well‐known digital databases and examined the articles that map to the pre‐defined inclusion criteria. The study selected and analyzed 48 articles out of 320 published between 2000 and 2022. The findings of the mapping study reveal that Agile can resolve the major issues faced in traditional software maintenance, making the role of this approach significant in global/distributed software maintenance. Cloud computing plays a vital role in software maintenance. Most of the studies highlight the application of XP‐ and Scrum‐based Agile maintenance models. The study found a need for more Agile maintenance solutions in the cloud, highlighting the importance of agile in software maintenance, both locally and globally. Irrespective of the environment, Cloud computing provides a centralized platform for collaboration and communication, while also offering scalability and flexibility to adapt to diverse infrastructure needs. This allows agile maintenance practices to be implemented across both local and global environments, leveraging the cloud's capabilities to overcome geographical and infrastructural challenges. [ABSTRACT FROM AUTHOR]

Agile software development has reached wide adoption in various countries including Turkey, even though from which its original cultural backgrounds differ. In Turkey, many organizations have started to adopt Agile approaches more and more in their software development processes. This interest in the country's software development is parallel to what the academic literature on Agile in the country exhibits. However, despite the prevalence of Agile in Turkey, there is a lack of sufficient secondary research and comprehensive review on Agile in Turkey, which poses a significant necessity for further investigation. Considering this gap, we performed a quantitative bibliometric analysis of Agile software development publications produced by Turkish organizations in a holistic and broad approach both for scholars and practitioners. We provide a summary of relevant academic studies that emerged in Agile research in Turkey by focusing on many aspects including bibliometric properties of papers, researchers, affiliations, venues, and thematic contents that are separated into 15 sub‐research questions. After delivering results based on the questions, we discuss the results and findings of our study and present implications regarding the findings. The main contributions of our work are twofold. First, the paper may help the readers to have a quick idea, understand the subject, and gain insight from a large volume of scientific data. Second, the paper can help readers to use these analyses to form future research. [ABSTRACT FROM AUTHOR]

There have been success stories reported regarding the adoption of agile software development methods in the industry. There also exist observations on their limitations. One of these limitations is scalability since agile methods like Scrum were originally designed for small software teams. Scalable agile frameworks were introduced to address this limitation. We conducted an industrial case study on the adoption of such a framework, called Nexus. Our study involves quantitative and qualitative evaluation based on observations within a product development organization over a period of 12 months. Scrum is used for the development of a product during the first 6 months of this period. Nexus is used in the remaining 6 months. Data are collected throughout the whole period for measuring productivity, quality, and team member motivation. Results suggest a significant increase in productivity and product quality after switching to Nexus. Team motivation was slightly improved as well. [ABSTRACT FROM AUTHOR]

Enterprise architecture is a growing trend that aims to help deal with the complexity of socio‐technical systems such as human organizations, as well as their information technology and systems areas. Nevertheless, the contribution of enterprise architecture to the field of software engineering remains unclear. The purpose of this systematic literature review is to see how enterprise architecture is used in software development and maintenance practice. To this end, we first carried out a search in the SCOPUS database and then organized the papers according to the Software Engineering Body of Knowledge to determine what areas of software engineering are covered by each research study. To understand how enterprise architecture is used, we established a classification based on ISO 42010 and TOGAF. From the systematic literature review, we noticed that the early stages of development are the most impacted by the enterprise architecture. On the other hand, we observed that enterprise architecture is of assistance in the areas of engineering management, engineering processes, and engineering models and methods; these tasks are carried out by teams or managers using different, often agile, development methods or standards. In turn, we found that the most common categories are architecture descriptions; these are often used to facilitate communication and information‐sharing between different stakeholders, in addition to frameworks, which will help to establish common practices in the organization related to the joint use of enterprise architecture and software development. [ABSTRACT FROM AUTHOR]

The practices of lean and agile methods are important to manage and guide projects development in different situations. However, selecting the appropriate practices of lean and agile methods is a daunting task, owing to the availability of hundreds of practices. This wide variety of available practices bewilders potential users, in terms of the best practices that may yield satisfactory solution when applied to the project development. Lean and agile practices selection model is necessary to guide both academic and industrial experts to choose the appropriate practices for a specific project development. Thus, this study aimed to develop lean and agile practices selection (LAPS) model that presents a clear picture of how developers can use LAPS model to select and adopt different practices from various lean and agile methods. Qualitative research method (e.g., grounded theory) was used to interview 18 software developers across 13 countries. The validated qualitative analysis results showed that the proposed LAPS model consists of two main components, which are (1) lean and agile practices that include 41 best practices related to lean and agile methods and (2) factors that affect the process of lean and agile practices selection including five main factors and 17 subfactors associated with the five main factors. The two case studies conducted assured the validity and applicability of the lean and agile practices selection model. [ABSTRACT FROM AUTHOR]

Scrum is an important and essential technique for developing software. Scrum framework is a project management technique that can emphasize software development teamwork. If you are starting, consider scrum as a method for accomplishing tasks as a team in manageable chunks simultaneously, with ongoing experimentation and feedback loops to learn and improve as you go. Scrum enables individuals and groups to collaboratively and gradually generate value. Being an agile framework, scrum gives people and teams the perfect structure to fit into their workflows while still including the best practices to cater to their requirements. There are some important considerations for security in the agile software development process such as threat modeling, secure coding practices, continuous security testing, authentication, and authorization. In this work, we reviewed various scrum developing techniques to find out the research gaps. This article consider the scrum technique with blockchain technologies for review because it is preferred by most of the software industries. [ABSTRACT FROM AUTHOR]

The Data Mine at Purdue University is a pioneering experiential learning community for undergraduate and graduate students of any background to learn data science. The first data‐intensive experience embedded in a large learning community, The Data Mine had nearly 1300 students in academic year (AY) 2022–2023 and nearly 1700 students for AY 2023–2024. The Data Mine embodies data‐infused education, research, and collaboration. Students learn Python, R, SQL, and shell‐scripting, while working on weekly projects within a high‐performance computing (HPC) cluster. In the Corporate Partners cohort, students work on teams of 5–15 students, led by a paid student team leader. Each cohort follows an Agile approach, working on data‐intensive projects provided by industry partners and mentored by company employees. Students develop professional and data skills throughout the academic year, from August through April. Many students return in subsequent years to the program, increasing their tenure with a Corporate Partner. Student teams are inherently interdisciplinary; students from 133 different majors are involved in the program, ranging from new incoming students through PhD level students. These interdisciplinary teams of students bring new perspectives to challenging problems in which data science is a key part of the solution. The interdisciplinary teams foster an environment of synthesis with ideas and solutions. Students come together with different life experiences, different levels of technical skill, but also varying ways they navigate paths to solutions because of the variety of majors represented, resulting in a more creative and robust solution than a traditional data science program. This article is categorized under:Applications of Computational Statistics > Education in Computational Statistics [ABSTRACT FROM AUTHOR]

The letter to the editor discusses the article titled "Agile 3+ and Agile 4 scores predict chronic kidney disease development in metabolic dysfunction-associated steatotic liver disease." The authors of the letter express their interest in the study's findings but note biases in the use of the Cox proportional hazards (CoxPH) model that the authors did not address. They suggest that the authors should consider the potential impact of censoring events and the proportional hazards assumption in their evaluation. The authors also provide recommendations for alternative models that can handle different types of censored data. They conclude by emphasizing the need for further research in this field. [Extracted from the article]