• Journal of Korea Society of Industrial Information Systems
• /
• v.5 no.2
• /
• pp.47-55
• /
• 2000

To date many software engineering cost models have been developed to predict cost, schedule, and effort of the software under development. The COCOMO Ⅱ is well- suited for the new software development life cycle such as non-sequential and rapid- development processes. The traditional regression approach based on the least square criterion is the most commonly used technique for empirical calibration in the COCOMO Ⅱ model. It has a few assumptions frequently violated by software engineering data sets. The source data is also generally imprecise in reporting size effort, and cost-driver ratings, particularly across different organizations. And that the outlier for the source data is a peculiarity and indicates a data point. To cope with difficulties, in this paper, we propose a new regression method for calibrating COCOMO Ⅱ post-architecture model based on the minimum relative error(MRE) criterion. The characteristic of the proposed method is insensitive to the extreme values of the data in the empirical calibration. As the experimental results, It is evident that our proposed calibration method MRE was shown to be superior to the traditional regression approach for model calibration, as illustrated by the values obtained for standard deviation(^σ), and prediction at level LPRED(L) measures.

• IEMEK Journal of Embedded Systems and Applications
• /
• v.16 no.6
• /
• pp.267-276
• /
• 2021

The automotive industry and academic research have been continuously conducting research on standardization such as AUTOSAR (AUTomotive Open System ARchitecture) and ISO26262 to solve problems such as safety and efficiency caused by the complexity of electric/electronic architecture of automotive. AUTOSAR is an automotive standard software platform that has a layered structure independent of MCU (Micro Controller Unit) hardware, and improves product reliability through software modularity and reusability. And, ISO26262, an international standard for automotive functional safety and suggests a method to minimize errors in automotive ECU (Electronic Control Unit)s by defining the development process and results for the entire life cycle of automotive electrical/electronic systems. These design methods are variously applied in representative automotive safety-critical systems. However, since the functional and safety requirements are different according to the characteristics of the safety-critical system, it is essential to research the AUTOSAR functional safety design method specialized for each application domain. In this paper, a software functional safety mechanism design method using AUTOSAR is proposed, and a new failure management framework is proposed to ensure the high reliability of the product. The AUTOSAR functional safety mechanism consists of memory partitioning protection, timing monitoring protection, and end-to-end protection. The fault management framework is composed of several safety SWCs to maintain the minimum function and performance even if a fault occurs during the operation of a safety-critical system. Finally, the proposed method is applied to the Shift-by-Wire system design to prove the validity of the proposed method.

• Journal of the Korean Society for Railway
• /
• v.11 no.2
• /
• pp.139-144
• /
• 2008

Recent advances in embedded system technology have brought more dependence on automating train control. While much efforts have been reported to improve electronic hardware's safety, not so much systematic approaches to evaluate software's safety, especially for the vital software running on board train controllers. In this paper, we propose a new software tool to evaluate software safety for the train controller. We have reviewed requirements in the international standards and surveyed available tools in the market. From that, we identified necessary tests to meet the standards and proposed a tool that can be used during the whole software life cycle. We show the functional architecture and internal components of the tool. Our tool is unique in that it is a comprehensive tool specifically designed for software safety evaluation while other tools are not.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.21 no.11
• /
• pp.2115-2120
• /
• 2017

Presently, It is required to change convergence the role of hardware system and software technology that promoted trust of In-Vehicle for integrated complex system visibility evaluation. There is possibility for the period system can invoke unpredictable confusing blank state. The blank state systems have ecosystem characteristics that are supplied, maintained and operated through the complex interactions of technology and culture. Using universal middleware can support the life-cycle model and increase the visibility of complex systems and prepare for confusing situations. In this study, based on universal middleware, data and service dynamic standardized modules were evaluated to support stable system visibility platform. The system visibility module consists of Intelligent Pervasive Cloud module, Memorial Service module and Life Cycler connection module. In addition, the analysis results are supported by various network application service standards through platform independent system and architecture.

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

RUP(Rational Unified Process) is a development process which is based on object-oriented, use case centric, architecture centric, and iterative approach. Public projects performed previously adopt waterfall lifecycle model for development of large scale software. However, recently various projects adopt an iterative approach to minimize risks of a project and to enhance quality of software. But few research result on practices of RUP as the subprocess of system development process is available. This paper presents a system development process which uses RUP as the subprocess for a subset of the system. Thus we introduce a tailored RUP for K-CIS(Korean Core Instrumentation System). Moreover, we assess the application result of K-CIS with typical waterfall lifecycle model and RUP. We believe that the results of our work are useful for tailoring a system development process with RUP, reducing risks of development, and enhancing the quality of a final product.

• Korean Journal of Construction Engineering and Management
• /
• v.16 no.3
• /
• pp.101-112
• /
• 2015

In the 1950s, the concept of configuration management (CM) was started by the US Department of Defense (DOD). Later, it has begun to be applied in aerospace, software, engineering, construction, and nuclear power industry. However, configuration management (CM) in the Korean nuclear industry was firstly utilized in 2006 only for selected parts of facilities, while the US nuclear industry has applied CM for the facilities' entire systems since 1990s. Furthermore, configuration management (CM) is in its conceptual stage in the Korean nuclear industry because of ambiguous CM concepts, lacks of CM professional manpower, non-computerization, and inadequacy of CM procedures and processes. In order to address this issues, seven industries (including defense, aerospace, software, engineering, architecture, civil engineering, nuclear power) that utilize the concept of configuration management (CM) were compared and analyzed based on the CM purpose, technique, and life-cycle perspectives. By an extensive literature review and expert interviews, this paper developed a framework of configuration management (CM) for the nuclear industry. And also, a list of functions based on life-cycle stages and CM techniques are developed for clarifying CM framework in order to promote practical applications.

• 제어로봇시스템학회:학술대회논문집
• /
• 2000.10a
• /
• pp.416-416
• /
• 2000

The Systems Engineering, as a methodology for engineering and management of today's ever-growing complex system, is a comprehensive and iterative problem-solving process. The process centers on the analysis and management of the stakeholders'needs throughout the entire Life-cycle of a system and searches for an optimized system architecture. There are many essential needs and requirements to be met when a system development task is carried out. Systems Engineering Management PLan(SEMP), as a specification for system development process, must be established to satisfy constraints and requirements of stakeholders successfully and to prevent cost overrun and schedule delay. The paper suggests a systematic SEMP development process and demonstrates a data model and schema for computer-aided systems engineering software, RDD-100, for use in the development and management of SEMP These are being applied to the systems engineering technology development task for the next-generation high-speed railway systems in progress.

• The KIPS Transactions:PartD
• /
• v.13D no.2 s.105
• /
• pp.241-250
• /
• 2006

Software maintenance is an important and very expensive activity in software life cycle. To estimate the maintainability cost of software, many software metrics have been proposed. This paper presents the result of an experimental study to explore the relationship between maintainability and some software metrics. LCOM, RFC, DAC, and LOC are employed as metrics and time really spent for maintenance activity has been collected. In the experimental study, we have found that for some systems, the existing metrics may not be an indicator to maintenance effort, which is not consistent with our general knowledge on the relationship between them. Specifically speaking, we recognized that there should be more empirical study on the relationship between metrics and maintainability of softwares which have been developed using recent technologies such as software architecture and design pattern.

• Journal of KIISE:Software and Applications
• /
• v.35 no.6
• /
• pp.357-365
• /
• 2008

Requirements traceability enables to reuse various kinds of software artifacts, which are the results from software development life cycle, rather than reuse source code only. To support requirements traceability for reuse of software artifacts, 1) artifacts should be described based on requirements and 2) a requirements tracing method should be supported. In this paper, we provide a description model for annotating requirements information to software artifacts by using requirements ontology. We also provide semantic tagging method users to efficiently annotate artifacts with the requirements ontology. And we finally present how requirements traceability is supported based on requirements ontology and also suggest the system architecture for requirements traceability support.

• Proceedings of the Korea Society for Industrial Systems Conference
• /
• 2000.05a
• /
• pp.135-143
• /
• 2000

The COCOMO Ⅱ model is well-suited for the new software development life cycle such as non-sequential and rapid-development processes. The traditional regression approach based on the least square criterion is the most commonly used technique for empirical calibration in the COCOMO Ⅱ model. But it has a few assumptions frequently violated by software engineering data sets. It is true that the source data is also generally imprecise in reporting size, effort, and cost-driver ratings, particularly across different organizations. And that the outlier for the source data is a peculiarity and indicates a data pint To cope with difficulties, in this paper, we propose a new regression method for calibrating COCOMO Ⅱ post-architecture model based on the minimum relative erro(MRE) criterion. The characteristic of the proposed method is insensitive to the extreme values of the data in the empirical calibration. As the experimental results, It is evident that our proposed calibration method MRE was shown to be superior to the traditional regression approach for model calibration, as illustrated by the values obtained for standard deviation(^σ), and prediction at level L PRED(L) measures.