Comparative Analysis of Software Development Life Cycle Models (SDLC)

This history column article provides a tour of the main software development life cycle (SDLC) models. (A lifecycle covers all the stages of software from its inception with requirements definition through to fielding and maintenance.) System development lifecycle models have drawn heavily on software and so the two terms can be used interchangeably in terms of SDLC, especially since software development in this respect encompasses software systems development. Because the merits of selecting and using an SDLC vary according to the environment in which software is developed as well as its application, I discuss three broad categories for consideration when analyzing the relative merits of SDLC models. I consider the waterfall model before the other models because it has had a profound effect on software development, and has additionally influenced many SDLC models prevalent today. Thereafter, I consider some of the mainstream models and finish with a discussion of what the future could hold for SDLC models.

Selection of a suitable Software Development Life Cycle (SDLC) model for project implementation is somewhat confusing as there are a lot of SDLC models with similar strengths and weaknesses. Also, the solutions proffered among the researchers so far have been the qualitative comparative analysis of SDLC models. Hence, this paper proposes a comparative analysis of SDLC models using quantitative approach in relation to strengths and weaknesses of SDLC models. The study adapted comparative analysis and Software Development Life Cycle (SDLC) models features’ classification using ten characteristics such as project complexity, project size, project duration, project with risk, implementation/initial cost, error discovery, associated cost, risk analysis, maintenance and cost estimation. A quantitative measure that employs online survey using experts in software design and engineering, project management and system analysis was carried out for the evaluation of SDLC models. Purposeful Stratified Random Sampling (SRS) technique was used to gather the data for analysis using XLSTAT after pre-processing, taking into consideration both benefit and cost criteria. The overall performance evaluation showed that Spiral-Model is the best followed by V-Model and lastly Waterfall Model with comparative values of 38.63%, 35.76% and 25.61% respectively. As regards cost estimation, Waterfall Model is the most efficient with value of 41%, then V-Model with 31% and lastly Spiral Model with 28%. V-Model has great error recovery capability with value of 45% which is closely followed by Spiral Model with 37% and lastly Waterfall Model with 18%. The study revealed that, a model with efficient risk assurance does not guarantee efficient cost management. In the future work, more characteristics regarding SDLC models shall be considered.

In earlier software development all process is completed and implemented but now this is not a scenario. In modern era changes are frequent to any software product or module which is under development phase, due to market competitions priority of requirement changes Due to the fact that the traditional process models are incompatible with these changes, agile methodology is used instead.. Earlier waterfall model was convenient because of less requirement of features and emergency of the application in the short period of time .This Paper Discusses the comparative Analysis of waterfall model and agile methodologies while agile methodologies are taking over, even the waterfall model is older and time consuming it is still use in many sectors The paper will help other software development process models. Agile method plays important role in the areas of software project management, software schedule management etc. The main aim of the agile is Customer satisfaction as well as faster development with low defect rate. This paper reflects the comparison of the agile processes with waterfall model software development life cycle model. Agile processes aren't always beneficial; they have their own set of downsides. Agile method promotes continuous iteration of development and testing throughout the software developed.

The most critical aspect in Software Development Life Cycle (SDLC) model is of Requirement Engineering Phase various kind of complication occurred in software projects, numerous categories of requirements for software projects containing few constraints just like cost, time and a lot of more. Thus it is crucial for choosing such a lot valuable ones for implementation with intention to the delivery of a high-value system. When an instance of lack of cost and time it turns into necessary for prioritizing requirement. The proposed approach prioritize the requirement consistent with higher preference and prioritizing the Non-Functional Requirement w.r.t. Functional Requirement where cost having the principal task for prioritizing and the approach referred to as Artificial Bee Colony (ABC) algorithm based on Population meta-heuristic policy motivated by foraging behavior of bees.

Due to ever‐changing technology and business requirements, the inefficiency and ineffectiveness of traditional plan‐driven software development life cycle models are being questioned. Software engineers have to find ways of improving software development processes by applying more agile principles to the traditional plan‐driven approaches. This paper addresses this issue and suggests how project and technical management can apply principles from the agile group of life cycle models to alleviate some of the problems encountered. Project characteristics that can be used to evaluate individual projects to determine the degree to which the software life cycle can be adapted, are indicated. Practices are also proposed for adapting traditional plan‐driven life cycle processes that can benefit from more agile approaches.

Penelitian ini bertujuan untuk mengembangkan sistem informasi berbasis aplikasi mobile E-Pasraman Hindu sebagai solusi digital untuk optimalisasi pengelolaan data akademik di Pasraman Hindu. Pasraman, sebagai lembaga pendidikan non-formal yang berfokus pada nilai-nilai spiritual dan budaya Hindu, menghadapi tantangan dalam pengelolaan administrasi. Dengan metode Software Development Life Cycle (SDLC) model Waterfall, aplikasi ini dirancang untuk memenuhi kebutuhan spesifik Pasraman, seperti pengelolaan data Acarya (guru), Brahmacari (siswa), kelas, kegiatan, absensi, ujian, dan kuis. Pengujian aplikasi mobile e-Pasraman juga telah diuji menggunakan metode BlackBox Testing. Hasil implementasi dan testing menunjukan seluruh fitur berhasil diimplementasikan dengan baik sesuai harapan dan menunjukkan bahwa aplikasi ini memberikan kemudahan dalam pengelolaan data akademik, meningkatkan efisiensi operasional, transparansi, dan kualitas layanan pendidikan. Fitur-fitur seperti profil pengguna, jadwal, kehadiran, ujian, berita, pembayaran, hingga e-book, mendukung pengelolaan Pasraman secara terintegrasi. Penelitian ini memberikan kontribusi signifikan terhadap modernisasi pendidikan keagamaan Hindu melalui teknologi digital.

Burung walet merupakan salah satu jenis burung yang memiliki nilai ekonomi tinggi karena air liurnya yang dapat dimanfaatkan sebagai bahan dasar produk kesehatan dan kecantikan. Dalam proses budi daya burung walet, kondisi lingkungan yang sesuai sangat penting, terutama suhu antara 26–29°C dan kelembapan 80–90%. Namun, terdapat dua permasalahan utama yang sering dihadapi oleh pemilik rumah burung walet, yaitu sulitnya memantau kondisi suhu dan kelembapan secara real-time serta meningkatnya risiko pencurian sarang walet. Penelitian ini bertujuan untuk membangun sistem monitoring suhu, kelembapan, dan keamanan rumah walet berbasis Internet of Things (IoT) menggunakan MQTT Broker. Sistem ini menggunakan sensor DHT11 untuk mengukur suhu dan kelembapan, sensor LDR untuk deteksi intensitas cahaya, serta magnetic switch untuk mendeteksi akses pintu. Metode penelitian yang digunakan adalah Software Development Life Cycle (SDLC) model Waterfall dengan teknik pengumpulan data berupa studi pustaka, observasi, dan wawancara. Tahapan perancangan meliputi perancangan arsitektur sistem, perangkat keras, alur data, antarmuka, dan pengujian sistem. Hasil dari penelitian ini adalah sistem monitoring berbasis IoT yang mampu memberikan data suhu, kelembapan, serta notifikasi keamanan secara real-time melalui Telegram dan tampilan antarmuka pada Node-RED. Pengujian menggunakan metode black box menunjukkan bahwa seluruh sensor dan sistem notifikasi bekerja dengan baik sesuai fungsinya.

The management of borrowing and returning goods in government institutions is still largely carried out manually, which often gives rise to various problems, such as difficulties in tracking borrowing histories, the high risk of recording errors, and the lack of transparency regarding the availability of goods. This condition indicates the need for support from an information system that is capable of assisting the recording process and inventory management in a more structured, systematic, and easily monitored manner. This research aims to design a prototype of a goods borrowing and returning application as an initial solution to these problems as well as a preliminary representation of a system that can be further developed by the institution. The research method used is a Research and Development (R&D) approach with a prototype Software Development Life Cycle (SDLC) model, which allows system development to be carried out gradually and flexibly in accordance with user needs. Data collection was conducted through observation and interviews to obtain an overview of the ongoing work processes and to identify the required system needs. The collected data were then analyzed as the basis for designing the system workflow, data structure, and user interface design. The results of this research are in the form of an application prototype that represents the main system features, including goods borrowing, goods returning, availability checking, goods data management, and report generation.

10 - Project Wizardry 101

Patient falls and fall-related injuries are serious problems in hospitals. The Fall TIPS application aims to prevent patient falls by translating routine nursing fall risk assessment into a decision support intervention that communicates fall risk status and creates a tailored evidence-based plan of care that is accessible to the care team, patients, and family members. In our design and implementation of the Fall TIPS toolkit, we used the Spiral Software Development Life Cycle model. Three output tools available to be generated from the toolkit are bed poster, plan of care, and patient education handout. A preliminary design of the application was based on initial requirements defined by project leaders and informed by focus groups with end users. Preliminary design partially simulated the paper version of the Morse Fall Scale currently used in hospitals involved in the research study. Strengths and weaknesses of the first prototype were identified by heuristic evaluation. Usability testing was performed at sites where research study is implemented. Suggestions mentioned by end users participating in usability studies were either directly incorporated into the toolkit and output tools, were slightly modified, or will be addressed during training. The next step is implementation of the fall prevention toolkit on the pilot testing units.

In the rapidly evolving field of project management, the need for a universal, adaptable, and user-friendly system is more critical than ever. This paper introduces "Autonome: The Universal Project Management System", a groundbreaking solution designed to address these needs. The main aim of this project is to create an automated system for managing all the activities of projects. The system includes the project application and review module, project opening management module, project progress management module, project completion management module, and project research results display module, which realizes the distributed submission of project declaration, opening report, progress report, and conclusion report. Autonome integrates key quality attributes of software usability into every phase of the Software Development Life Cycle (SDLC)[10], thereby reducing latent and patent flaws and enhancing user satisfaction. By comparing various SDLC models, Autonome has been designed to fulfill diverse customer requirements, thereby addressing the industry-wide issue of underutilized software. Furthermore, Autonome facilitates effective stakeholder engagement through governance-based, value-based, and dynamism-based solutions, ensuring value delivery to all stakeholders. The system also acknowledges and addresses the inherent complexity of projects, incorporating a procedure for the quantitative assessment of structural complexity. Preliminary results indicate that Autonome significantly enhances project efficiency, stakeholder satisfaction, and team productivity. This paper delves into the design, implementation, and potential impact of Autonome, heralding a new era in project management.

Cloud-based computing services trend has significantly increased the building of new cloud data centres in the recent times. These data centres consume a large amount of electrical energy to run the Information Communication Technology (ICT) devices and for its cooling, as a result of that emission of \(CO_2\) and Greenhouse Gas (GHG) has increased largely. This paper proposes a Sustainable Software Development Life Cycle (SDLC) Model. This model would contribute towards making the cloud computing systems more energy efficient and the ICT a green and sustainable development ecosystem. The Green Cloud Computing will be considered as an implementation platform for the proposed Sustainable SDLC. It is proposed that reusable, modular and cloud-shared development approach be used to make the software development and the software more energy efficient. The SDLC will use a cloud repository which will be accessible as per software development organizations cloud deployment model.

Developing the right products the right way is challenging, not least in software product development. It requires sound business decisions as well as good engineering practices. Various software development life-cycle models can be mapped to business decision models by mapping business decision gates and major development milestones. Two well-known life-cycle models have been mapped to the ABB Gate Model, a business decision model for product development projects that was developed to ensure that released products could be successfully deployed into the marketplace.

The government of India has launched a web portal to register and schedule appointments for COVID-19 vaccination. This paper illustrates an android app model through which people can get notified about available slots according to their filters (age-group, dose type, vaccine name, centers). The proposed app checks for available slots for every given time in the background. Users can schedule their appointment and also enable/disable notifications at any time in the app. The project is developed in android studio. The data source is API Setu, and for client side, Java, XML, and SQLite are used. Software Development Life Cycle model and testing methods are used during the development process. ER diagram, message sequence chart, and flow chart have been shown for database, some important functions, and development process, respectively. The project developed is highly efficient, lightweight, and user-friendly.

Active learning methods are needed to promote student motivation and facilitate the development of technical and soft skills. Previous research in software engineering education shows that LEGO® Serious Play (LSP) fully aligns with these needs. However, prior works are usually based on insufficiently robust research methods that do not include a large sample, a variety of evaluation instruments, and/or rigorous comparative methods such as randomized controlled trials, which makes it difficult to obtain reliable and solid conclusions. This article presents an original LSP activity to teach software development life cycle models and core software engineering activities, tackling learning objectives different from those addressed by the LSP activities reported in prior works. The LSP activity was validated through a cluster-randomized controlled trial involving 217 computer science students. These students were divided into a control group that received a traditional lecture and an experimental group that performed the LSP activity. The research was supported by pre and post-tests that allowed the study of the knowledge attained by the students, as well as a questionnaire to gather students’ perceptions. The results indicate that the students in the experimental group learned significantly more and were more motivated than their counterparts in the control group. This leads to the conclusion that LSP-based activities such as the one reported in this article are highly effective in terms of knowledge acquisition and motivation to teach some software engineering topics compared to traditional lectures.