Search results

Software development life cycle (SDLC) has always been the core methodology for any software engineer that depicts the entire development process which an organization is bound to utilize to achieve successful software. The purpose of this paper is to bring forth a conceptual model after analysing the best practices in SDLC, and extracting the best out of agile methodologies and the open source software, thereby bringing forward an optimised structure.

The OASDLC is hypothesized specifically for “Brihaspati” project and is formulated keeping in mind the gaps and limitations posed by existing SDLC models. OASDLC is further put to test for achieving lower costs and efforts involved. The tests are further substantiated by means of hypothesis validation through execution of a survey based research.

It has been observed that the present conceptual model further optimizes the efforts involved while adopting such a practice.

This paper proposes a novel SDLC model so as to achieve a best practice for a software project. On analysing the issues involved such as tight budget and timelines, it led the authors to formulate a newer concept “Open Agile Software Development Life Cycle model” (OASDLC).

The aim of this paper is to highlight the application of six sigma, software engineering techniques and simulation to software development with a view to improving the software process and product.

This paper attempts to integrate six sigma and simulation to define, analyse, measure and predict various elements of software development (such as cost, schedule, defects) that influence software quality, thereby helping the software personnel take necessary measures early in the development process to improve the software processes and remove defects. Simulation results provide qualitative and quantitative suggestions on the ways to change the software process to achieve six sigma quality. The integration of six sigma and CMM and the role of knowledge management in software organisations have been taken into account.

Most software organisations operate between 2.3 and 3 sigma level. This paper presents a framework for definition, measurement, and analysis of important elements of the software product and process using six sigma tools and exploits the use of simulation in bringing six sigma improvements. Case studies have been presented to demonstrate the findings.

Application of the techniques presented in this paper would definitely improve software organisations' processes and product.

The adoption of methodologies outlined in this paper in software companies would enable them to attain improvements in terms of cost, schedule and quality.

The integration of simulation with six sigma applied to software development is novel in this paper. This paper will be valuable for quality professionals and management personnel in software organisations.

Applying total quality management (TQM) to the software development process can control software quality and productivity. Selecting suitable tools for the TQM process can strengthen the capability of software quality assurance. This article provides a manager’s guide to implementing a total quality process during a systems development life cycle. Also, tools integration can make a complicated TQM‐based software development environment easier.

This study aims to investigate the effects of organizational culture factors on the selection of software process development models and develops a conceptual model for selecting and adopting process development models with an organizational culture approach, using 12 criteria and their sub-criteria defined in Fey and Denison’s model (12 criteria).

The research hypotheses were investigated using statistical analysis, and then the criteria and sub-criteria were selected based on Fey and Denison’s model and the experts’ viewpoints. Afterward, the organizational culture of the selected company was measured using the data from 2016 and 2017, based on Fey and Denison’s questionnaire. Due to the correlation between the criteria, using the decision-making trial and evaluation technique, the correlation between sub-criteria were determined, and by analytical network process method and using Super-Decision software, the process development model was preferred to the 12 common models in information systems development.

Results indicated a significant and positive effect of organizational culture factors (except the core values factor) on the selection of development models. Also, by changing the value of organizational culture, the selected process development model changed either. Sensitivity analysis performed on the sub-criteria implied that by changing and improving some sub-criteria, the organization will be ready and willing to use the agile or risk-based models such as spiral and win-win models. Concerning units where the mentioned indicators were at moderate and low limits, models such as waterfall, V-shaped and incremental worked more appropriately.

While many studies were performed in comparing development models and investigating their strengths and weaknesses, and the impact of organizational culture on the success of information technology projects, literature indicated that the impact of organizational sub-culture prevailing in the selection of development process models has not been investigated. In this study, new factors and indicators were addressed affecting the selection of development models with a focus on organizational culture. Correlation among the factors and indicators was also investigated and, finally, a conceptual model was proposed for proper adoption of the models and methodologies of system development.

This paper is focused at studying the current state of research involving the four dimensions of defect management strategy, i.e. software defect analysis, software quality, software reliability and software development cost/effort.

The methodology developed by Kitchenham (2007) is followed in planning, conducting and reporting of the systematic review. Out of 625 research papers, nearly 100 primary studies related to our research domain are considered. The study attempted to find the various techniques, metrics, data sets and performance validation measures used by researchers.

The study revealed the need for integrating the four dimensions of defect management and studying its effect on software performance. This integrated approach can lead to optimal use of resources in software development process.

There are many dimensions in defect management studies. The authors have considered only vital few based on the practical experiences of software engineers. Most of the research work cited in this review used public data repositories to validate their methodology and there is a need to apply these research methods on real datasets from industry to realize the actual potential of these techniques.

The authors believe that this paper provides a comprehensive insight into the various aspects of state-of-the-art research in software defect management. The authors feel that this is the only research article that delves into the four facets namely software defect analysis, software quality, software reliability and software development cost/effort.

Explores the issue of software development process improvement. Total quality management (TQM) tools have been studied as possible means to improve the quality of the software that is becoming an important part of organizational processes. The TQM philosophy that has been so successfully applied in manufacturing holds that quality must be built into the production process and not inspected into the product. Given the complexity of modern software applications, the ability to move away from using testing and inspection as quality control methods is very attractive. Examines the current literature on software development process improvement. Particular attention is paid to how customer requirements are gathered and translated into system requirements. Finds that current methods for requirements definition do not provide a formal means to deploy the “voice of the customer” into system specifications. Further, finds after a review, that current software quality function deployment (QFD) methods suffer from a number of shortcomings. Proposes a four‐stage model for performing software‐oriented QFD to address these significant problems.

Connected Health is an emerging and rapidly developing field never before witnessed across the healthcare sector. It has the potential to transform healthcare service systems by increasing its safety, quality and overall efficiency. However, as healthcare technologies or medical devices continuously rely more on software development, one of the core challenges is examining how Connected Health is regulated – often impacting Connected Health innovation. The purpose of this paper is to present an understanding of how Connected Health is regulated. Many of these regulatory developments fall under “medical devices”, giving rise to Software-as-a-Medical Device (SaaMD).

Through an extensive literature review, this paper demystifies Connected Health regulation. It presents the outcome of expert discussions which explore the key regulatory developments in the context of Connected Health to provide a practical guide to understanding how regulation can potentially shape healthcare innovation.

Several key issues are identified, and the authors present a comprehensive overview of regulatory developments relating to Connected Health with a view to support the continued growth of IT-enabled healthcare service models. The authors also identify the key challenges in Connected Health and identify areas for future research.

A key outcome of this research is a clearer understanding of the opportunities and challenges that regulation and standards present to Connected Health. Furthermore, this research is of critical importance in a first attempt towards recognising the impact of regulation and standards compliance in Connected Health.

The purpose of this paper is to improve the understanding of the role of the bottlenecks in the dynamic software development supply chains. The paper examines the effects of the task priorities in the software development and investigates the possible strategies to manage them effectively.

In this paper, a software development supply chain has been simulated. This includes modeling of the various sizes of software requirement, different priorities, variations in development times, quality defects, etc. The model assumes a fixed set of resources of various skills. The model is studied for the bottlenecks, throughput, work in progress (WIP), etc. under various work preemption scenarios.

The results indicate that job priorities impact the bottleneck formulation, throughput and WIP of the software development. The work interruption policies to accommodate priority jobs adversely impact the throughput. Selective introduction of interruptions by leaving the bottlenecks from interruptions helps balancing the throughput and priorities.

The impact of the learning curve and knowledge acquisition time needed by the resources to restart the interrupted work has not been considered in this paper, which can be a future area of research.

The paper helps the practicing managers evaluate the dynamics of the bottlenecks with various task management approaches and comprehend the possible tradeoffs between priority and throughout.

The paper looks at software development from a perspective of workflow dynamics. This is a pioneer effort, as it utilizes simulation and modeling approach in understanding the software supply chains better.

This paper reviews existing business process (BP) modeling languages that are widely used in the industry as well as recent research work on modeling and analysis of BPs in the service-oriented environment and Internetware-based software paradigm. BPs in such environment are different from traditional BPs due to loose coupling of partner services, dynamic and on-the-fly selection of partners and run-time process adaptability. The unique characteristics of these BPs require formal modeling of the requirements and constraints in each phase of their life cycle, including design phase, implementation and deployment phase and execution phase.

The paper first provides a categorization of typical user requirements in each phase of the BP life cycle. Then a detailed comparison of the selected languages with respect to their requirement modeling and analysis capabilities in each of the identified categories is provided. The paper also discusses new requirements engineering research challenges arising from future software needs and emerging trends in software engineering in the context of Web-services-based BPs and Internetware.

There is a need to have a framework that provides support for user requirements modeling and analysis for all the phases of BP life cycle in an integrated manner. Such a framework would be useful not only in resolving the inconsistencies between requirements across phases but also in addressing the issues related to BP evolution due to changes in user requirements over time. Moreover, with the Internet of things (IoT) adoption in BPM, there is a need to have an integrated environment that provides support for capturing the resilience requirements of enterprise BPs as well as the mobility constraints of the underlying IoT devices.

This paper reviews existing BP modeling languages and frameworks and discusses the new requirements engineering research challenges arising from future software needs and the emerging trends in BP management in the service-oriented environment and Internetware-based software paradigm.

This paper aims to examine the process for estimation of efforts for software development and suggests a framework for estimating software development costs and ensuring quality of code in e-Government projects from the Indian state of Andhra Pradesh. With no established processes for estimation of efforts, the Government relied on open bids from the market to develop these e-Government applications.

The paper adopts an exploratory case study approach to analyze the e-Government applications in Andhra Pradesh. Using data from the information technology department of the Government of Andhra Pradesh, the paper evolves a framework to compute costs of software development, based on the software development life cycle.

The framework helps in arriving at a hurdle price before the tender process. The study has shown that an e-Government application in AP state would cost Rs. 224,000, or US$2,969.25, for a simple application, and Rs. 33,60,000, or US$44,538.71, for a complex application over a five-year period, depending on the complexity and size of the application. This information would be useful to the Government decision-makers for expanding e-Government.

Further research may assess the utility of this framework for e-Government support activities like automation of data centers, video conferencing facilities and ushering in financial technologies for encouraging cashless payments.

The paper provides information that could be of value at a national level (for India) and at the same time providing a guide for other countries that would like to adopt this framework.