• International journal of advanced smart convergence
• /
• v.9 no.4
• /
• pp.149-155
• /
• 2020

In the software industry of Korean Small and Medium-sized Enterprise(SME)s, the development process is often not mature. This may lead to failures in quality control and output management. As a result, the quality of the software can be degraded. To solve the problem, the software visualization technique, which is from the National IT Industry Promotion Agency Software Engineering Center can be applied. We have experienced with mentoring not only the visualization of software development process, but also various visualization process of SMEs. However, the existing software visualization method was difficult to install environment and its time cost was high. This paper proposes a software visualization environment through a cloud service along with a case of building a software visualization environment. We expect that this method will make it easier to build a visualization environment and improve the quality of SME software.

• Journal of Information Technology Services
• /
• v.10 no.4
• /
• pp.191-204
• /
• 2011

Recently, many software companies are trying to improve the software quality and project outcome with more costs and efforts in development time. In the software convergence and integration environments, it is required efforts to gain high quality of software. In other words, it is required to utilize software engineering knowledge and technology for higher software quality and better software project productivity. The Software development productivity can be varied by software process capability according to building a framework for software development, selection and use of appropriate technology, human resource management. Software process capability will influence software project outcome which is the general opinion. This study provides empirical evidence about software engineering efforts and investment approach to lead software project performance. We measured the software engineering efforts by SW engineering level and analyzed the corelation between software engineering level and schedule deviation. And, we verified that this performance is affected by the size of software company. As a result, software process capability is important to build a infrastructure and develop systematically software project. The higher software engineering level can lead to improved software project performance.

• Journal of KIISE
• /
• v.44 no.5
• /
• pp.510-521
• /
• 2017

The software development process (SDP) plays an important basic role in software engineering education. Every software is developed in accordance with a specific SDP which contains all phases of software development. SDP education helps students to understand the overall techniques and the process of software engineering. This paper introduces a software development methodology (i.e., process) - 'OOPT (Object Oriented Process with Traceability),' which was proposed for use in university software engineering classes. The OOPT is based on object-oriented software development, and it defines concrete requirements as well as outputs of each process/phases. It also contains the unit/system testing and a traceability analysis. We have used the OOPT in software engineering classes at Konkuk university for eight years. This paper conveys our experience as well as future extension and improvement plans.

• 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.

• International Journal of Advanced Culture Technology
• /
• v.9 no.4
• /
• pp.417-423
• /
• 2021

Recently, in the Game industries, they are increasing to use of game engines to reduce the development cost of 3D content and software. In particular, Unreal Engine provides a blueprint visual scripting function that enables software production without programming (coding). Although High-end video content can be produced, the problem is that content development is complicated and requires advanced manpower. To solve this problem, we propose an optimized VR game context process. This is because 1) a Blueprint visual script is used, 2) VR games with various interactions can be produced, 3) Non-majors in the software field (or groups) can develop advanced content. In various related industries such as defense, medical care, manufacturing, and construction, we may easily develop any game content without programming with our refined VR rhythm action game development process. We expect to reduce the development cost with the process advantages in the game industries.

• Nuclear Engineering and Technology
• /
• v.41 no.1
• /
• pp.91-98
• /
• 2009

The "3+3 Process" for safety critical software for nuclear power plants' I&C (Instrumentation and Control system) has been developed in this work. The main idea of the "3+3 Process" is both to simplify the software development and safety analysis in three steps to fulfill the requirements of a software safety plan [1]. The "3-Step" software development process consists of formal modeling and simulation, automated code generation and coverage analysis between the model and the generated source codes. The "3-Step" safety analysis consists of HAZOP (hazard and operability analysis), FTA (fault tree analysis), and DV (design validation). Put together, these steps are called the "3+3 Process". This scheme of development and safety analysis minimizes the V&V work while increasing the safety and reliability of the software product. For assessment of this process, validation has been done through prototyping of the SDS (safety shut-down system) #1 for PHWR (Pressurized Heavy Water Reactor).

• Communications of the Korean Institute of Information Scientists and Engineers
• /
• v.21 no.4
• /
• pp.4-12
• /
• 2003

Software process improvement has been one of the most important ways to improve the quality of software and the effectiveness and efficiency of software development organization. During the past 10 years, more than 5,000 organizations have adopted the SW-CMM and many other organizations have adopted similar process models. IEEE and international standards are evolving to encourage and support continued process improvement. The Software Engineering Institute is committed to broadening the benefits of software process improvement to the entire engineering organization through a new model called CMM Integration and to enable faster improvement through the Personal Software Process and the Team Software Process. The SEI is also committed to working with its colleagues in Korea so that industry can reap the benefits from this important and exciting work.

• The Transactions of the Korea Information Processing Society
• /
• v.5 no.4
• /
• pp.904-914
• /
• 1998

BPR(Business Process Reengineering), a radical improvement approach of business process, has been paying attention, and work-flow management and automation has been concentrated on progress velocity of business process and productivity of engineers. In software engineering, software process engineering which focus to process begin to be watched, and for the purpose of software productivity and quality progress and reduction of development term, study on SPR(Software Process Reengineering) is being progressed. In this paper, made workflow analysis and design method for construction of work-flow management system of software process to stand firm process reengineering methodology. In other words, we studied modeling process methods for SPR process, and software process structure and workflow analysis method which construct software process workflow model and specification definition method of workflow software.

• International Journal of Reliability and Applications
• /
• v.4 no.1
• /
• pp.1-12
• /
• 2003

Many software reliability growth models (SRGM's) based on a nonhomogeneous Poisson process (NHPP) have been proposed by many researchers. Most of the SRGM's which have been proposed up to the present treat the event of software fault-detection in the testing and operational phases as a counting process. However, if the size of the software system is large, the number of software faults detected during the testing phase becomes large, and the change of the number of faults which are detected and removed through debugging activities becomes sufficiently small compared with the initial fault content at the beginning of the testing phase. Therefore, in such a situation, we can model the software fault-detection process as a stochastic process with a continuous state space. In this paper, we propose a new software reliability growth model describing the fault-detection process by applying a mathematical technique of stochastic differential equations of an Ito type. We also compare our model with the existing SRGM's in terms of goodness-of-fit for actual data sets.