• Proceedings of the KIEE Conference
• /
• 2006.10d
• /
• pp.244-246
• /
• 2006

Softwares in railway system are being used in the area of railway control system, directly associated to safety. Because the instinct characteristic of Software is uncertainty, Software development without safety insurance is very hazardous situation. In order to derive safety certification process in the railway system, certification and approval processes in the nuclear, aviation, and military area are studied. Software quality should be improved by two aspects : one is product aspect, another is process aspect. GS(Good Software) and ES(Excellent Software) certification can be exemplified in a product aspect approach. In those process certification, CMMI (Capability Maturity Model Integration) or SPICE (Software Process Improvement and Capability dEtermination : ISO/IEC15504) is being used as models for assessing process maturity of organization. Following the studies, safety management procedure in the railway system is suggested.

• Management & Information Systems Review
• /
• v.18
• /
• pp.201-222
• /
• 2006

As the competition between countries has become higher and the notion of software quality has been widely spread. it has been necessary to develop technologies that can ensure and produce high quality software. With the advent of information-oriented society. quality control has to transfer to the quality control activities focused on software system instead of those activities focused on hardware system. If so, how do we get to handle the quality control on the basis of the new approach. Also, as software applications have grown. so too has the importance of software quality. In order to manage software quality, the technology to specify and evaluate both the software product quality and development process quality objectively quantitatively is most important. To produce products of good quality, we need a more progressive quality control system according to the need of software development life cycle. In other words, we do software right the first time or build quality in the process. On the basis intermediate and final time or build quality in the process. On the basis of data achieved, we can evaluate the products according to the consequences of the data, What are the problems to contrive the software quality control system?, we con promote the quality of products. To achieved that goal, we con provide a suitable the technique and method of software quality control.

• The KIPS Transactions:PartD
• /
• v.13D no.4 s.107
• /
• pp.593-602
• /
• 2006

Software development methodology has been developed for satisfying goals of improvement in productivity and reduction in time-to-market through the reuse of software assets. The current methods that implement software product-line, one of software development methodologies, interfere massively with the core assets, which require high cost in assembly level reducing the effectiveness. In this paper, we introduce Aspect-Oriented Programming (AOP) as a method for improving assembly process in software product-line. The method that assembles core assets and variabilities is described by grammar elements such as Join point, pointcut and advice without code-change. We analyze requirements of a mini-system as an example adapting AOP and design using UML. Our study implements the variabilities, which are from design stage, using an Aspect-Oriented Programming Language, AspectJ and prove usability and practicality by implementing the proposed idea using an Aspect-Oriented Programming Language, AspectJ.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.35 no.2
• /
• pp.57-63
• /
• 2012

Software release planning model of software product lines was formulated as a precedence-constrained multiple 0-1 knapsack problem. The purpose of the model was to maximize the total profit of an entire set of selected features in a software product line over a multi-release planning horizon. The solution approach is a dynamic programming procedure. Feasible solutions at each stage in dynamic programming are determined by using backward dynamic programming approach while dynamic programming for multi-release planning is forward approach. The pre-processing procedure with a heuristic and reduction algorithm was applied to the single-release problems corresponding to each stage in multi-release dynamic programming in order to reduce the problem size. The heuristic algorithm is used to find a lower bound to the problem. The reduction method makes use of the lower bound to fix a number of variables at either 0 or 1. Then the reduced problem can be solved easily by the dynamic programming approaches. These procedures keep on going until release t = T. A numerical example was developed to show how well the solution procedures in this research works on it. Future work in this area could include the development of a heuristic to obtain lower bounds closer to the optimal solution to the model in this article, as well as computational test of the heuristic algorithm and the exact solution approach developed in this paper. Also, more constraints reflecting the characteristics of software product lines may be added to the model. For instance, other resources such as multiple teams, each developing one product or a platform in a software product line could be added to the model.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2012.05a
• /
• pp.524-526
• /
• 2012

기존의 제품 수명주기 관리 프로그램은 공급망 관리(SCM :Supply Chain Management)의 목적이 강해 그의 기능이 풍부한 반면 PLM적인 요소가 부족하다. 따라서 본 논문에서는 PLM을 구성하는 PDM, CPD, CNM, PPM 4가지 요소 중에 하나인 PDM(Product Data Management) 요소를 보강하기 위한 모듈을 개발하여 구현한다. PDM의 기능은 핵심적인 고객가치를 지원하기 위한 제품정보를 관리하는 영역으로 제품구조관리(BOM), 기술문서 관리, 설계변경 관리, 제품 기준정보 관리, Software 형상관리, 환경 유해 물질 관리, 공용화 기능을 포함하고 있는데, 그 중 제품구조관리(BOM)가 가장 중요한 부분이므로 이 부분에 대해 구현한다.

• Journal of Korea Technology Innovation Society
• /
• v.5 no.2
• /
• pp.167-188
• /
• 2002

Summary: This paper analyzes Indian software industry in the perspective of innovation cluster. The research shows that the software industry has been following an upstream clustering process, where the major value activity is expanding from low value product/services to high value product/services. The growth of software industry could be successful because there was appropriate initial condition of Bangalore, such as the availability of high qualified human resources, excellent research institutes, small high-tech companies. The role of government was helpful for the late growth of software industry but not a critical factor for the initial development of the S/W cluster. It is suggested that government should consider the initial condition of a concerned location critically to implement a cluster-type innovation policy.

• Journal of Internet Computing and Services
• /
• v.5 no.4
• /
• pp.125-134
• /
• 2004

Recently a lot of researches on the component-based software product lines and on applying generative programming into software product lines are being performed actively. This paper proposes an automatic component reconfiguration tool that could be applied in constructing the component-based software product lines. Our tool accepts the reuser's requirement via a feature model which is the main result of the domain engineering, and makes the feature configuration from this requirement. Then it generates the source code of the reconfigured component according to this feature configuration. To accomplish this process, the component family in our tool should have the architecture of GenVoca that is one of the most influential generative programming approaches. In addition, XSLT scripts provide the code templates for implementation elements which are the ingredients of the target component. Taking the ‘Bank Account' component family as our example, we showed that our component reconfiguration tool produced automatically the component source code that the reuser wants to create. The result of this paper would be applied extensively for creasing the productivity of building the software product lines.

• Journal of KIISE:Software and Applications
• /
• v.41 no.7
• /
• pp.469-480
• /
• 2014

Software Product Line (SPL) is a software development paradigm that guarantees high productivity, reduced cost, and shorter time-to-market by systematically planning and reusing commonality and variability. In order to maximize the benefits of SPL engineering, testing should be integrated into the SPL engineering lifecycle processes that consist of domain engineering and application engineering and should be performed with as little test efforts as possible. This paper proposes a systematic software product line test cases derivation method using combinatorial test design. By applying combinatorial test design to product line test cases derivation and exploiting commonality between products at the same time, the number of generated test cases is dramatically reduced with the result that they can be effectively reused by the products of the given product line. Case studies conducted in this paper show the efficacy of our method compared with other methods that use only commonality or combinatorial design or neither of them in terms of the number of derived test cases.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.40 no.3
• /
• pp.27-37
• /
• 2017

As the global uncertainty of manufacturing has increased and the quality problem has become global, the recall has become a fatal risk that determines the durability of the company. In addition, as the convergence of PSS (product-service system) product becomes common due to the development of IT convergence technology, if the function of any part of hardware or software does not operate normally, there will be a problem in the entire function of PSS product. In order to manage the quality of such PSS products in a stable manner, a new approaches is needed to analyze and manage the hardware and software parts at the same time. However, the Fishbone diagram, FTA, and FMEA, which are widely used to interpret the current quality problem, are not suitable for analyzing the quality problem by considering the hardware and software at the same time. In this paper, a quality risk assessment model combining FTA and FMEA based on defect rate to be assessed daily on site to manage quality and fishbone diagram used in group activity to solve defective problem. The proposed FTA-FMEA based risk assessment model considers the system structure characteristics of the defect factors in terms of the relationship between hardware and software, and further recognizes and manages them as risk. In order to evaluate the proposed model, we applied the functions of ITS (intelligent transportation system). It is expected that the proposed model will be more effective in assessing quality risks of PSS products because it evaluates the structural characteristics of products and causes of defects considering hardware and software together.

• The KIPS Transactions:PartD
• /
• v.16D no.5
• /
• pp.747-754
• /
• 2009

Software product line engineering is an approach to creating core assets by systematically exploits common that can be highly reusableand different characteristics in related system families that is domain. By adapting this approachin object and component paradigm, software productivity is extended. Recently, Software development paradigm is changed to service oriented paradigm which is using services that are core assets. Therefore, to develop service oriented software more flexible, systematic and to enhance business agility about business changes, we need adaptation of product line to creation of services that are core assets. In this paper, we propose an approach to create and specify domain service through combine of product line and service oriented paradigm. Domain service explicitly specifies commonality and variability by domain service common/optional property variability, operation type variability, message type variability. By using this approach, it can support efficient and flexible service oriented development by producing various services through customization of domain service for the purpose.