System Development Life Cycle Model Research Articles

Web-based smart attendance monitoring system using QR code and GSM module for SMS notificatio

The study was designed and developed to address certain problems and concerns of the school administration and parents of students attending Ciriaco Mariano Elementary School. The system was used to provide the school an innovative way to record attendance of students, provide parents with real time updates regarding the entry and exit of their children in the school premises, and be able to monitor students by generating attendance reports. The Web-based Smart Attendance Monitoring System using QR code and GSM module for SMS notification was developed through the implementation of the Iterative System Development Life Cycle Model. This iterative model ensures that the web-based system conformed to the all of the requirements from the CMES and of the requirements set by the ISO 25010 criteria. To assess the quality of the developed web-based system, the researcher adapted the ISO 25010 Software Quality Standard as evaluation tool. Two sets of questionnaires were developed and were given to respondents who were selected using purposive sampling. The first set of questionnaires were given to IT experts to assess the technical qualities of the system which includes functional suitability, performance efficiency, compatibility, usability, reliability, security, maintainability, and portability. The second set of questionnaires were given to the school principal, teachers, and parents to assess the web-based system quality on selected criteria which includes functional suitability, performance efficiency, and usability. The Web-based Smart Attendance Monitoring System using QR code and GSM module for SMS notification was successfully developed using the iterative SDLC model and found conformed to the ISO 25010 software quality standards as implied by the results from the evaluation of IT experts, school principal, teachers, and parents.

Digitization of Archives at Café Ganesha Mocktail Bandung

This research aims to develop a digital filing system at the Ganesha Mocktail café in Bandung, West Java. This is intended to improve the existing archive storage system at the Ganesha Mocktail café so that the documents that are owned are stored properly. This type of research and development uses a Research and Development (RnD) design developed using the SDLC (System Development Life Cycle) model. The research stages start from system planning, system analysis, system design/development, to system implementation. This research produces a digital archive information system application for Café Ganesha Mocktail based on Microsoft Office Access. Through this application, Café Ganesha Mocktail can store files safely and easily find the documents needed.

“DIA SMART” Android-Based Intelligent Application Expert System for Diagnosis and Mapping of 10 Diseases at Teaching Factory Nutrition Care Center

The Basic Health Research in 2018 showed that the prevalence of non-communicable diseases including cancer, stroke, chronic kidney disease, diabetes mellitus, and hypertension increased in Indonesia. The main risk factors are metabolic factors, behavioral factors, and environmental factors. Based on the existing problems, an Android-based intelligent application for the diagnosis and mapping of 10 diseases was proposed at the Teaching Factory Nutrition Care Center. This application development used the Expert System Development Life Cycle model and Dart Language. The framework used is Flutter. This article only discusses the implementation and testing of applications made based on Android. This application was developed to perform a diagnosis based on some patients’ data. This application is used as a reference for early detection of a disease, allowing patients to take preventive measures. It can map the number of patients who had health consultations in each department. The users of the application were a doctor, nutritionist or health consultant at the Teaching Factory Nutrition Care Center. System functionality tested using Blackbox-testing showed that the application ran well.

Design and Development of Romblon State University Romblon Campus Accreditation Data Warehouse

Accreditation is conducted to assess and upgrade the educational quality of higher education institutions and programs, which requires complete documents for the precise information specification before the expert's review. Therefore, the documents and records of an institution must be effectively preserved to facilitate compliance with accreditation requirements. However, the data generally comes from different sources of various types, unstructured and distributed. This study designed a data warehouse to incorporate all the documents in preparation for college accreditation. The data warehouse was developed in a five-step process, considering the accreditation assessment with an emphasis on academics. Systems Development Life Cycle model was used in the development of the system. The ISO/IEC 25010:2011 standard was used to evaluate the system's acceptability using the eight characteristics. However, only applicable sub-characteristics such as suitability, efficiency, compatibility, usability, reliability, security, and maintainability were applied to evaluate the system. This standard ensures that the system meets the user's preference with the system being satisfied, and the essential features like uploading, viewing, and system maintenance by the administrator, are at their most excellent functional operation. The parameters which were created by the system can be used by other satellite campuses of Romblon State University, as well as other universities applying for accreditation of the Accrediting Agency of Chartered Colleges and Universities in the Philippines (AACCUP).

Comparison Of Waterfall And Prototyping Models In Research And Development (R&D) Methods For Android-Based Learning Application Design

<p><strong>Design of learning applications that use Development Methods (Research and Development/R&D) using a commonly used system development methodology, namely SDLC (System Development Life Cycle). Several stages of SDLC consist of planning, analysis, design, implementation to system maintenance. The SDLC concept is the basis of various types of software development models to form a framework in planning and controlling information systems. The SDLC model that is often used in research and development (R&D) research for the development of Android -based learning applications is a waterfall and prototyping model. The comparison of the two models states that the waterfall model is more suitable for a system or software that is generic or in the form of software that can provide services to the buyer. While prototyping is more suitable for customize systems or software, meaning software made based on demand and needs (even certain situations and conditions). In accordance with the analysis obtained, the two methods have the advantages and disadvantages of each, so that the developer can choose which method is more suitable for the development of the software.</strong></p>

Systematic development of a data model for the blockchain-based embodied carbon (BEC) Estimator for construction

PurposeBlockchain as an emerging technology has increased the interests within various industries because of its salient features. A potential application of blockchain for embodied carbon (EC) estimating is being explored. Though there are several databases/tools to estimate EC, the accuracy of estimates prepared using them is affected due to several limitations. As a solution, a prototype blockchain-based EC (BEC) Estimator for distributed supply chain-based EC estimating has been introduced. The data models and user flow diagram that lead to development of a BEC Estimator are developed and evaluated in this study.Design/methodology/approachA case study approach assisted in developing the data models and user flow diagram for the BEC Estimator. A Delphi-based expert forum was used to evaluate and produce the refined data models and user flow diagram.FindingsThe BEC Estimator adopts a waterfall model, a system development lifecycle model, in developing the application. The phases, system analysis and system design, consisting the development of the data models and user flow diagram for the BEC Estimator are discussed.Originality/valueEstimating EC accurately plays an important role in construction. The BEC Estimator uses the supply chain based embodied carbon estimating method to estimate EC accurately. This paper demonstrates the data models and user flow diagram developed for the BEC Estimator.

The system development life cycle model implementation on information system of performance reporting IT asset case study: PT Kereta Api Indonesia (Persero)

The asset performance monitoring should be done to find out and review the reported data whether it has been in line with the reality or not. It is important to identify the occurring problems to be immediately handled. The information system development aimed to build the existing system. Thus, it will be more effective and efficient to produce information. This research applied the System Development Life Cycle (SDLC) with Waterfall Model to design, create, maintain the information and process the system. During the creation of this information system, the authors applied the PHP language program, Framework Codeigniter, MySQL, database, and Visual Studio Code as the editorial codes. The implementation of the SIPERITA application, could be used excellently were proven effective and efficient because the application facilitated the monitoring activities by providing single application access in promoting a checking process of the condition asset then the user administrator can see a diagram of the monitoring results on the home page so that if there is a problem with the asset, direct action can be taken and with this application, users can print the reports based on daily, monthly, and annually.

New Model-Based Systems Engineering Methodology Based on Transdisciplinary Quality System Development Lifecycle Model

New Model-Based Systems Engineering Methodology Based on Transdisciplinary Quality System Development Lifecycle Model

ER2C SDMLC: enterprise release risk-centric systems development and maintenance life cycle

Traditional systems development life cycle models can be viewed as technical life cycle models in systems development projects. These life cycle models mostly focus on the initial delivery of systems as part of projects. However, many systems end up in a perpetual development mode and can be viewed as a continuum of releases rather than the deliverables of temporary projects. Newer versions of such systems are usually released as part of support/maintenance processes rather than through rigorous projects. In environments with quick-fix maintenance or loose release management regimes, lack of rigor may result in the compromise of quality, especially quality-in-use. This may cause end users’ exposure to risks as a result of using potentially faulty releases and products. Minimizing product risks should be an inherent inclusion in product life cycle, regardless of whether the product is released as part of a project or as part of support/maintenance work. A novel systems development and maintenance life cycle model is proposed that models the life of a system as a sequence of releases. It covers non-project maintenance-related releases as well as major projectized releases under a unified consistent governance model. It proposes applying different levels of rigor depending on analyzed release risks via the enforcement of different thresholds to a set of metrics that are extracted from release artifacts. The proposed life cycle model supports iterative development and is conformant to ISO 15288:2015. Evaluations performed by a community of practice in a large government agency in Queensland, Australia, has demonstrated the success of the proposed model in a number of areas, especially in how risk is managed when changes are introduced to systems after their initial release.

A Software System Development Life Cycle Model for Improved Students Communication and Collaboration

A Software System Development Life Cycle Model for Improved Students Communication and Collaboration

Casey's Collections: A Strategic Decision-Making Case Using the Systems Development Lifecycle—Planning and Analysis Phases

ABSTRACTThe Systems Development Life Cycle (SDLC) model, developed in the 1980s, remains the foundational model for strategic decision making regarding the development or acquisition of new information systems (IS). The SDLC model proposes five system development phases—planning, analysis, design, implementation, and maintenance—using a waterfall theory. These early phases of the SDLC require strategic decisions to be made regarding information systems. Strategic decision making is a model of multi-attribute utility theory, which helps promote decisions that maximize utility among multiple alternatives. This case provides students with experience in making reasoned strategic IT decisions by executing the planning and analysis phases in a new system acquisition life cycle. This educational case is structured to be the first of several cases covering the SDLC involving the same small fictitious public corporation, Casey's Collections. Upon completion of the case, students should have a deeper understanding and appreciation for the process of IS strategic decision making. In addition, students should better understand how to identify an information system's needs and prepare system proposals based on the generation and analysis of alternative solutions. This case is suitable for students in an introductory or graduate accounting systems course; it is also appropriate for use in a IS course on systems analysis and design.

Development of Adaptive Mobile Learning (AML) on Information System Courses

In general, the learning process is done conventionally, where the learning process is done face to face between teachers with learners in the classroom. Teachers have a very important role in determining the quantity and quality of the implementation study. Therefore, teachers must think and plan carefully to improve learning opportunities for learners and improve the quality of teaching. Along with the development of mobile technology and communication is rapidly increasing, enabling the learning process is not only done in the classroom, but can be done anywhere and anytime. Based on the analysis of the results of observations in the class conducted by a researcher and as a teacher in the learning courses of Information Systems, found some obstacles encountered during the learning process This research is to develop an Adaptive Mobile Learning on Information Systems courses. The method used in this research is the development of research methods (research and development), which selected the design development using System Development Life Cycle model. Adaptive Mobile Learning will be validated and tested through three phases of testing are: (1) Product technical test as a software. (2) Testing of the product as a medium of learning, through expert review by a media expert, (3) Field test to evaluate the response of the students that learned Adaptive Mobile Learning. The results show that Adaptive Mobile Learning software is can present the material in the course of Information Systems. Media Adaptive Mobile Learning can be used as an alternative medium (supplement) of learning Information Systems courses. The response of students to the development and use of software for Adaptive Mobile Learning Information Systems courses is likely to very positive, which is at 67.7% very positive and 32.3% is positive.

Ubiquitous Healthcare Information System: Toward Crossing the Security Chasm

Ubiquitous healthcare information system is increasingly seen as a viable option for reducing the inherent time lag and inaccuracies in the traditional model of healthcare and promoting the delivery and practice of evidence-based healthcare―as and when needed―without any location and time constraints. Although promising, the realization of ubiquitous healthcare information system brings several threats and risks rooted in real-time collection, analysis, storage, transmission, and access of critical medical data. In this research, we address information security concerns pertaining to the paradigm of ubiquitous healthcare information system. To accomplish this we use National Institute for Standards and Technology’s (NIST’s) system development lifecycle model (SDLC) as the underlying framework to explore the current state of ubiquitous healthcare from the perspective of security. We then leverage the model to propose future research directions in this area. By implementing the NIST’s SDLC model in such a manner, we offer a different dynamic of healthcare security that has not been addressed in literature before.

A Software System Development Life Cycle Model for Improved Stakeholders’ Communication and Collaboration

<p>Software vendors and entrepreneurs, who try to introduce an innovative software product to a specific organization or an entire market, enter a long and tedious process. During this process, the market and various organizations evaluate the product from different perspectives, such as software robustness, manufacturer reliability, and corporate need for the product. The vendors and entrepreneurs engaged in this process encounter decision crossroads for which no relevant guidance exists in the literature.<br /> The research closely monitored the processes associated with the introduction and assimilation of an innovative off-the-shelf (OTS) software product into five different organizations in different vertical market segments. Observations were carried out to assess organizational and marketing processes and to document and analyze what the software product undergoes before it is accepted for acquisition or full implementation within the organization.<br /> The research outcomes offer a unified, collaborative multi-tier System Development Life Cycle (SDLC) framework and methodology for packaged OTS software products that greatly improves communication and collaboration among the stakeholders. Each tier addresses a different force or stakeholder involved in the software market: vendor, customer, consultants and integrators. All stakeholders refer to the same time-line thus; tasks of various stakeholders are streamlined. Adherence to the unified time-line brings about an increased amount of stakeholder interaction, communication and collaboration.<br /> Newly found tasks that improve communication and collaboration among stakeholders include (1) offering of the OTS software product together with personnel as a bundle, (2) an improvisation-intensive iterative task of weaving potential customers’ requirements into the prototype, and (3) a third sale milestone, representing the successful diffusion of the product. The significance of this interdisciplinary research stems from its unique position at a crossroad between software engineering, marketing, and business administration, which has not yet been sufficiently explored or cultivated.</p>

The Phases of ERP Software Implementation and Maintenance: A Model for Predicting Preferred ERP Use

Nearly all information technology educators and practitioners are familiar with the concept of a systems development life cycle (SDLC). The SDLC model is mainly based on new software development. The stages vary based on methodology, but mostly include planning and requirements definition, analysis, design of the new system, implementation, and post-implementation support such as maintenance and security. Less explored and known are the stages involved in commercial off the shelf installation. The actual implementation of commercial off the shelf software ERP (enterprise resource planning) systems is an area that is suggested to have a life cycle of its own. The importance of specific phases of this ERP implementation life cycle is the subject of this study. By surveying SAP enterprise resource planning implementations at two divisions of a major manufacturing company, a confirmatory factor analysis confirms the existence of four distinct phases of ERP implementation — preparation and training, transition, performance and usefulness, and maintenance. In addition, the overall preferred ERP use is studied and compared with these factors. It was found that the two significant phases which directly influenced preferred ERP use were preparation and training phase, and performance and usefulness phase. Neither transition nor maintenance was found to significantly affect preferred ERP use. This suggests to practitioners that more focus needs to be placed on the key determinants of preferred ERP use — preparation and training phase, and performance and usefulness phase.

Requirements engineering changes for COTS-intensive systems

COTS products (hardware, software, components, subsystems, and so on) are becoming part of the solution for evermore-complex systems. This means you must make changes in any overall system development lifecycle model as well as in the processes and methods you use to define, design, construct, and validate these systems. In particular, requirements engineering and management must undergo process changes.

Iterative design and testing within the software development life cycle

The activity of testing begins during system development and spans all subsequent phases. Some system development lifecycles describe testing which is performed after the coding phase, but this may cause the software to be delivered without sufficient testing. In this paper, we present a software system development lifecycle model, called the Test design Stages Processed model (TSP model), in which we emphasize that iterative test design stages should be incorporated at each phase of the software development lifecycle. When a phase is completed, testing of the phase should also be completed at that time. Within this paper we have added unit, integration and system testing processes into BoochOs micro–design process to generate a new designs and test model. This shows the process of iterative and incremental software development. Comparing this with our model, we explain how the TSP model can be used for developing and testing an object-oriented software system.