• Journal of Internet Computing and Services
• /
• v.17 no.5
• /
• pp.161-172
• /
• 2016

Agile software development methodology has been implemented by software industries over a decade ago and well accepted in the practitioner community. However, there is limited understanding on how agile practitioners aware towards implementation of agile practices in software development. Lack of awareness will lead to misunderstandings among agile practitioners and misuse the agile practices. In order to understand the awareness of agile practices, this paper aims to investigate the factors that affect awareness of agile practitioners in implementing agile practices. A systematic literature review (SLR)was conducted in order to classify and define the factors of awareness in agile software development methodology. The review was based on papers between 2002 and December 2014 from seven electronic databases. The relevant papers were included 20 journal articles, 24 conference papers,16 book chapters, 9 workshop papers. Consequently, 69 papers were identified that closely related with awareness in agile software development methodology. From the thematic analysis, 13 factors were classified from 42 elements. Based on the review result, understanding the influential factors on the awareness of agile practices will provide benefit to researchers and agile practitioners.

• Journal of Information Processing Systems
• /
• v.9 no.1
• /
• pp.69-88
• /
• 2013

Agile methods are highly attractive for small projects, but no agile method works well as a standalone system. Therefore, some adaption or customization is always required. In this paper, the Agile Framework for Small Projects (AFSP) was applied to four industry cases. The AFSP provides a structured way for software organizations to adopt agile practices and evaluate the results. The framework includes an extended Scrum process and agile practices, which are based on agility and critical success factors in agile software projects that are selected from Scrum, XP, FDD, DSDM and Crystal Clear. AFSP also helps software managers and developers effectively use agile engineering techniques throughout the software development lifecycle. The case study projects were evaluated on the basis of risk-based agility factors, the agility of the adopted practices, agile adoption levels, and the degree of the agile project success. The analysis of the results showed that the framework used in the aforementioned cases was effective.

• International Journal of Computer Science & Network Security
• /
• v.22 no.3
• /
• pp.229-235
• /
• 2022

The process of correcting, upgrading, and improving software products after they have been handed over to the consumer is known as software maintenance. Offshore software maintenance outsourcing (OSMO) clients benefit from cost savings, time savings, and improved quality software through OSMO. In most circumstances, the OSMO vendor makes a lot of money but not in all the cases. Especially, when the OSMO project offer is not properly assessed. An efficient outsourcing contract might yield successful outcomes for outsourced projects. But before sending a detailed proposal to bid on the OSMO project the vendor must have to assess the client's project (business offer) requirements. The purpose of this study is to find out common trends within the assessment of a OSMO project. A case study approach along with semi-structured interviews from eight companies concluded ten common practices and several roles. Among these practices, four (code structure, requirements, communication barriers and required infrastructure) were consistent amongst the responses .The findings, limitations and future work are discussed.

• Korean Management Science Review
• /
• v.15 no.2
• /
• pp.59-70
• /
• 1998

According to the Gartner Group, the market for ERP software in Korea is growing rapidly. However, the number of successful ERP implementations is quite few. Standard(unmodified) ERP's are built based on best practices. Improvements expected from successful implementation are based on best practices built into the software. Many improvements are lost through modification to "standard" software. Even minor changes in software can significantly reduce benefits. Both implementation time and risk factors are increased with modifications. We introduce a methodology, called package Enable Re-engineering (PER) and the main components of change management program by Ernst & Young. "To-Be" model could be developed through the software capabilities. And change management processes such as continuous education and self-developments are required. The philosophy of the change management processes is to let the software package drive the re-engineering practices and avoid moving the software toward the "As-IS" process. Extensive top management involvement, major focus on speed, extensive communication program, and "clear" picture of the future are essential components of change management. We are sure that the complied experiences and model have implications for practice and for academicians for their endeavors in their fields.

• International Journal of Computer Science & Network Security
• /
• v.24 no.7
• /
• pp.1-10
• /
• 2024

Software architecture are High-level design decisions shaping a software system's components, structure, and interactions. It can be a blueprint for development, evolution, and ongoing maintenance. This research investigates the communication practices employed by software architects and developers to ensure adherence to the designed software architecture. It explores the factors influencing the selection of follow-up methods and the impact of follow-up frequency on successful implementation. Findings reveal that formalized follow-up procedures are not yet a ubiquitous element within the software development lifecycle. While electronic communication, particularly email, appears to be the preferred method for both architects and developers, physical and online meetings are utilized less frequently. Interestingly, the study suggests a potential confidence gap, with architects expressing concerns about developers' ability to faithfully implement the architecture. This may lead to architects providing additional clarification. Conversely, while most developers reported confidence in their software knowledge, overly detailed architecture documentation may pose challenges, highlighting the need for architects to consider alternative communication strategies. A key limitation of this study is the sample size, restricting the generalizability of the conclusions. However, the research offers valuable preliminary insights into the communication practices employed for architecture implementation, paving the way for further investigation with a larger and more diverse participant pool.

• Journal of Information Technology Services
• /
• v.20 no.2
• /
• pp.33-55
• /
• 2021

Many agile practices have been suggested for software development flexible enough to adapt to a rapidly changing environment. However, too many agile practices hinder computer engineers from deciding which agile practices are suitable for a given project. They need guidelines of the benefits an agile practice provides for a project, and how many of its benefits are effective. Therefore, this study investigates IT experts' perspectives on each agile practice's effectiveness in their projects using a repertory grid technique. Based on an analysis of data collected from 23 Korean IT experts about 33 agile projects, we elicit 361 cognitive effects categorized into 30 benefits using content analysis. Next, we identify agile practices that are primarily used and recognized as positive and further examine what benefits many agile practices usually bring. Finally, we evaluate the level of benefits overall that each agile practice provides.

• Proceedings of the Safety Management and Science Conference
• /
• 2005.05a
• /
• pp.129-135
• /
• 2005

This paper proposes the interated and balanced project management system for software and IT by considering BSC, MBNQA, ISO 9001, Six Sigma, CMM and SPICE. This system can be extended to assess the various project management practices.

• The Journal of Society for e-Business Studies
• /
• v.22 no.2
• /
• pp.39-60
• /
• 2017

Software product line engineering is widely recognized as an effective way for systematic software reuse, and many studies have been conducted to convert existing software development practices and processes into software product line. In order to convert existing software development into product line, a lot of investments are required such as dedicated development units, appropriate process selection and adaptation, and tool support. In particular, small businesses need business cases and specific practices for applying software product line engineering before its full-scale adoption. In this paper, we present a practical case of applying software product line engineering to the development of web system families and a process of systematically building and reusing software assets. To do this, we analyzed a number of web development projects and presented the experiences and various considerations of small software companies adopting software product line.

• Journal of the Korean Society for information Management
• /
• v.38 no.4
• /
• pp.65-82
• /
• 2021

The purpose of this research is to explore the phenomenon of the sharing, reuse, and citation of research software. These practices are playing an increasingly important role in scholarly communication. The researchers found that the citation and reuse of research software are currently uncommon or at least not reflected in the Data Citation Index (DCI). Such citation was observed, however, for the newer software in a number of prominent repositories. The repositories Comprehensive R Archive Network (CRAN) and Zenodo received the most formal software citations. The researchers observed both formal and informal forms of citation when researchers reused software. The latter form involves mentioning research software in passing in the main text of articles, while formal citations appear in the references section. In addition, our comparative analysis helps to explain the phenomenon of self-citation of research software.

• The Journal of Asian Finance, Economics and Business
• /
• v.8 no.3
• /
• pp.943-952
• /
• 2021

The Covid-19 pandemic situation has changed all medical priorities. This has put pressure on the World's health sector, which also affects the economy of the whole world. This study aims to study how Islamic work ethics affects the relationship between spiritual leadership and organizational inclusion practices in the health care sector of Pakistan in the COVID-19 situation. This is a mix-method study. Data collected of 158 practicing doctors through survey-based questionnaire and interview was conducted from 30 doctors dealing with direct coronavirus. The organizational inclusion practices variable is used for the first time in a quantitative approach in this study. The reliability and validity of organizational inclusion practices are checked by Adanco, SPSS, and SmartPLS software. For this purpose, data on inclusion practices was also collected from the banking and education sector. Results show that spiritual leadership significantly relates to Islamic work ethics also has a positive connection between spiritual leadership and organizational inclusion practices. Still, Islamic work ethics as a moderator has an insignificant impact on the relationship between spiritual and organizational inclusion practices. Also, from the result, it is verified that the organizational inclusion practices variable is valid and reliable for further studies.