• International Journal of Quality Innovation
• /
• v.7 no.1
• /
• pp.90-97
• /
• 2006

The process of producing software differs in many aspects from that of traditional manufacturing. Software is not manufactured in the classical sense. Development of software more closely resembles the development effort that goes into design new product [1-3]. In this article, we first describe the foundations of process improvement, which all processes can share. The process improvement differences between software and manufacturing process are then discussed, and a defect driven process inspection and improvement is introduced. Based on the discussion, two experiments were designed and the results of the results were collected. Through the comparison, we found that some efficient quality improvement approaches can be easily adapted in the software improvement and that the inspection efficiency is also significant.

• Journal of the Korea Society of Computer and Information
• /
• v.17 no.8
• /
• pp.123-133
• /
• 2012

Recently, as IT convergence has seen rapid growth the role and scope of software has been extended. many software companies are trying to improve the software quality and project outcome using software process improvement approach to cope with increasing software demands and software quality. Although software process improvement is difficult task which requires a lot of cost and time, there is still insufficient objective evidence on business benefits by its deployment. The purpose of this study is to analyze the relationship between software process improvement and software project productivity. That is, we investigated whether there is difference in software development productivity depends on software engineering level using statistical methods. We found that the software development productivity is different across the software engineering levels and the higher software engineering level can lead to improved software development productivity.

• Soft Computing and Machine Intelligence
• /
• v.1 no.1
• /
• pp.36-52
• /
• 2021

Software development organizations are globalizing their development activities increasingly due to strategic and economic gains. Global software development (GSD) is an intricate concept, and various challenges are associated with it, specifically related to the software requirement change management Process (RCM). This research aims to identify humans' related success factors (HSFs) and human-related challenges (HCHs) that could influence the RCM process in GSD organizations and propose a theoretical framework of the identified factors concerning RCM process implementation. The Systematic Literature Review (SLR) method was adopted to investigate the HSFs and HCHs. Using the SLR approach, a total of 10 SFs and 10 CHs were identified. The study also reported the critical success factors (HCSFs) and critical challenges (HCCHs) for RCM process implementation following the factors having a frequency 50% as critical. Our results reveal that five out of ten HSFs and 4 out of ten HCHs are critical for RCM process implementation in GSD. Finally, we have developed a theoretical framework based on the identified factors that indicated a relationship among the identified factors and the implementation of the RCM process in the context of GSD. We believe that the results of this research can help tackle the complications associated with the RCM in GSD environment, which is vigorous to the success and progression of GSD organizations.

• Journal of Korean Society for Quality Management
• /
• v.13 no.2
• /
• pp.61-65
• /
• 1985

The quality of a final SOFTWARE PACKAGE depends on many complicated factors in the software development process. This paper describes ststistical methods for establishing relationships between final quality and development process factors. The final software quality is represented by the number of errors through the system test phase. The data presented here were gathered during the course of a real IS-month development project. Regression theory is used for data analysis. Some of the interesting results include the observation that specification changes during the development process have an adverse effect on final software quality.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.11 no.2
• /
• pp.1217-1233
• /
• 2017

Effective monitoring and testing during each step are essential for document verification in research and development (R&D) projects. In software development, proper testing is required to verify it carefully and constantly because of the invisibility features of software. However, not enough studies on test processes for R&D projects have been done. Thus, in this paper, we introduce a Test Maturity Model integration (TMMi)-based software field R&D test process that offers five integrity levels and makes the process compatible for different types of projects. The Software & Systems Process Engineering Metamodel (SPEM) is used widely in the software process-modeling context, but it lacks built-in enactment capabilities, so there is no tool or process engine that enables one to execute the process models described in SPEM. Business Process Model and Notation (BPMN)-based workflow engines can be a solution for process execution, but process models described in SPEM need to be converted to BPMN models. Thus, we propose an approach to support enactment of SPEM-based process models by converting them into business processes. We show the effectiveness of our approach through converting software R&D test processes specified in SPEM in a case study.

• The Journal of Society for e-Business Studies
• /
• v.9 no.1
• /
• pp.255-268
• /
• 2004

User authentication is indispensable in computer login and internet banking. Usability as well as security is needed in user authentication software. To develop the software systematically, development process must be defined, and it can result in the improvement of software maturity. In this paper, a process needed to develop user authentication software systematically is proposed from experience of developing visual password input software. This process is composed of 6 phases and 15 activities. It is able to improve usability with its requirement analysis, planning, integration testing, and acceptance testing activity.

• Nuclear Engineering and Technology
• /
• v.27 no.1
• /
• pp.84-95
• /
• 1995

Application of computer software to safety-critical systems is on the increase. To be successful, the software must be designed and constructed to meet the functional and performance requirements of the system. For safety reason, the software must be demonstrated not only to meet these requirements, but also to operate safely as a component within the system. For longer-term cost consideration, the software must be designed and structured to ease future maintenance and modifications. This paper present a software engineering process for the production of safety-critical software for a nuclear power plant The presentation is expository in nature of a viable high quality safety-critical software development. It is based on the ideas of a rational design process and on the experience of the adaptation of such process in the production of the safety-critical software for the Shutdown System Number Two of Wolsong 2, 3 & 4 nuclear power generation plants. This process is significantly different from a conventional process in terms of rigorous software development phases and software design techniques. The process covers documentation, design, verification and testing using mathematically precise notations and highly reviewable tabular format to specify software requirements and software design. These specifications allow rigorous, stepwise verification of software design against software requirements, and code against software design using static analysis. The software engineering process described in this paper applies the principle of information-hiding decomposition in software design using a modular design technique so that when a change is' required or an error is detected, the affected scope can be readily and confidently located. It also facilitates a sense of high degree of confidence in the ‘correctness’ of the software production, and provides a relatively simple and straightforward code implementation effort.

• International Journal of Computer Science & Network Security
• /
• v.23 no.8
• /
• pp.199-203
• /
• 2023

Influential trend that widely reflected the software engineering industry is service oriented architecture. Vendors are migrating towards cloud environment to benefit their organization. Companies usually offer products and services with a goal to solve problems at customer end. Because customers are more interested in solution of their problem rather than focusing on products or services. In software industry the approach in which customers' problems are solved by providing services is known as software as a service. However, software development life cycle encounters enormous changes when migrating software from product model to service model. Enough research has been done on the overall development process but a limited work has been done on the factors that influence requirements elicitation process. This paper focuses on those changes that influence requirement elicitation process and proposes a systematic methodology for transformation of software from product to service model in a successful manner. The paper then elaborates the benefits that inherently come along with elicitation process in cloud environment. The paper also describes the problems during transformation. The paper concludes that requirement engineering process turn out to be more profitable after transformation of traditional software from product to service model.

• Proceedings of the KSR Conference
• /
• 2007.05a
• /
• pp.968-973
• /
• 2007

The systems such as the railway control system, satellite control system and nuclear power plant control system are the safety critical systems because the failure of them could lead to risk significant events. These softwares of digital systems must follow the life cycle process from the beginning of software development to guarantee their safety and reliability. The NRC(Nuclear Regulatory Commission) Reg Guide of nuclear fields, the RTCA/DO-178B standard which is used to acquire the certification for software in industrial aero field in European Union and United State, the DEF STAN 00-55 standard for the safety of electronic weapon in England, the IEC 601-1-4 for medical equipment and the IEC 62279 for railway system recommended the development life cycle. This paper introduces the development process and compares each other. Also it indicates applicable development criteria for the software of systems related to railway fields and describes the detailed procedure of development criteria. We describe the procedure to make the software development criteria in nuclear filed. For the software development related to railways, the process from plan phase to maintenance phase must be satisfied. The safety and reliability is guaranteed through these standards.

• KIPS Transactions on Software and Data Engineering
• /
• v.2 no.10
• /
• pp.691-696
• /
• 2013

To develop of a new software, software development methodology is offering the most efficient development methods and management methods. But, it require a lot of time, cost and software engineering specialist. For this reason, we are awaking to the need of it, but it has its problem that is only applied to large-scale software. In this paper, we suggest optimized software development methodology that you can apply to a lot well-used small software development methodology in present, and we prove it through AHP(Analytic Hierarchy Process). This helps small and business not to introduce specialist can efficiently develop and manage software.