• Proceedings of the IEEK Conference
• /
• 2002.07b
• /
• pp.1339-1342
• /
• 2002

It is difficult to design system software to meet a better separation of concerns, which can provide a number of benefits such as adaptability, extensibility, and modularity in the design and implementation. During design, some aspectual properties, such as synchronization, scheduling, performance and fault tolerance, crosscut the basic functionalities of the system software. By separating functional components from the different aspectual components of the system software in the design, we can provide a better generic design model of system software. Aspect-Oriented Programming is a methodology that aims at separating components and aspects from the early stages of the software life cycle, and using techniques to combining them together at the implementation phase. In this paper we discuss an aspect-oriented framework that can simplify system software design and implementation by expressing it at a higher level of abstraction. Our work concentrates on how to achieve a higher separation of aspectual components, functional components, and layers from each other. Our goal is to achieve a better design model for implementing system software in terms of modularity, reusability and adaptability.

• Journal of The Korean Association of Information Education
• /
• v.11 no.4
• /
• pp.483-495
• /
• 2007

In this paper, to establish a way controlling educational contents, range of contents for quality control are offered. And a life-cycle suitable for present circumstance has defined and successive quality control process has suggested supporting development and use of the contents through analyzing the life cycle of its software and previous contents. A life cycle is defined as whole process from formation of contents to its extinction. The developing process includes stages of planning, designing, manufacturing, and the applying process includes evaluation, circulation and management. Suitable quality control guidelines for each process have established and offered. Aim of this paper is also to develop a model which is applicable to developers as well as supporters who help the developing process.

• The KIPS Transactions:PartD
• /
• v.9D no.6
• /
• pp.1083-1090
• /
• 2002

The software development methodology has not caught up with the rapid change of information technology. Most of the software development projects use structural methodology or information engineering methodology. If established software development methodologies don't reflect technologies applied to the project, the project may be performed ineffectively. This paper describes a model in which we can apply a new information technology to an already existed structural methodology or information engineering methodology. This model uses the technique of the divide and conquer that software development life cycle is divided into phases, each phase is divided into viewpoint- areas and the software development processes of a new information technology are applied to each small area. By using the design phase this paper shows application example, in which I applied web-based development processes to CS@RoadMap Methodology of KCC Information & Communication, a system provider in Korea. The CS@RoadMap Methodology reflecting the Web technology, Web@RoadMap Methodology, has been applied to the public-domain projects.

• Journal of the Korea Computer Industry Society
• /
• v.5 no.1
• /
• pp.9-18
• /
• 2004

Successful project planning relies on a good estimation of the manpower required to complete a project in addition to the schedule options that may be available. Existing software manpower estimation models present the total manpower and instantaneous manpower distribution for the software life cycle. Putnam's Rayleigh and Phillai et al.'s Gamma models present a model with assumption that the manpower is needed at the system delivery. This means that 40 percent of total manpower is applied at the software development, and the other 60% is applied during maintenance phase. However Warburton observes the manpower is needed during development phase with the peak at the completion of the software design phase. So, the existing models were not appropriate to be applied to practical projects. This paper suggests the Sigmoid model which does not consider the point of manpower peak to fix the problem above. The suggested model showed some improvement when practical data was applied. Therefore, the Sigmoid model can be used as alternative of Rayleigh and Gamma model to estimate distribution of manpower during software development phas.

• The Transactions of the Korea Information Processing Society
• /
• v.3 no.4
• /
• pp.846-854
• /
• 1996

In this paper, we propose a solution to the software maintenance problem that is a primary factor of software crisis. We surveyed and analyzed the current software maintenance problems through questionnaires and interviews. As a result, we defined the software maintenance management life cycle and established a fundamental strategies to solve the software maintenance problems efficiently. We also designed a software maintenance management support systems to construct an automated software maintenance management tool. Furthermore, tp improve the formalization and reliability of the software maintenance management procedure, we defined acost predictive model using a fixed-single parameter based on comprehensive program size for the source code and delivered effort(person/month). We elaborated the model by considering an experience level of maintainer, a skill- level defined by the manager, and a reliability level required by the model of maintenance management.

• Journal of Institute of Control, Robotics and Systems
• /
• v.13 no.12
• /
• pp.1179-1185
• /
• 2007

This paper presents a new approach to automotive embedded systems development and validation. Recently automotive embedded systems become even more complex and the product life cycle is getting reduced. To overcome these problems AUTOSAR, a standardized software platform and component based approach, was introduced. Model-based approach has been widely applied in the development of embedded systems and has strong benefits such as early validation and automated testing. In this paper cooperative development and validation of AUTOSAR and model-based approach are introduced and automated testing techniques are proposed. With the proposed techniques we can improve complexity management through increased reuse and exchangeability of software module and automated testing is realized.

• The KIPS Transactions:PartD
• /
• v.11D no.5
• /
• pp.1123-1132
• /
• 2004

Successful project planning relies on a good estimation of the manpower required to complete a project. The good estimation can be derived from Rutnam's Rayleigh Model or Phillai et al.'s Gamma Model. These models only can be applied for the projects which the need of manpower is increased exponentially and the highest of manpower is required at the end of development phase. However, in a practical project, most manpower is required during development phase and a small amount of manpower is assigned during maintenance phase. In addition, the Waterfall Model and Unified Process only can be adopted for development phase. So the current development environments cannot be adopted into the existing manpower distribution models which the highest manpower is required at the end of development phase. This paper suggests an appropriate model for development phase to solve this problem. First, the appropriate manpower distribution for development phase of the Waterfall model was derived from Putnam's manpower distribution and then manpower distribution of development phase was derived for Unified Process. After comparing the required manpower of two Processes, total manpower distribution is similar each other even though the required manpower and task is different for each point of development phase. From this result, a unified model is derived and it can be applied for both development processes.

• Structural Engineering and Mechanics
• /
• v.62 no.2
• /
• pp.225-236
• /
• 2017

The purpose of this work is to predict ductile fracture of structural steel under extremely low cyclic loading experienced in earthquake. A cumulative damage model is proposed on the basis of an existing damage model originally aiming to predict fracture under monotonic loading. The cumulative damage model assumes that damage does not grow when stress triaxiality is below a threshold and fracture occurs when accumulated damage reach unit. The model was implemented in ABAQUS software. The cumulative damage model parameters for steel base metal, weld metal and heat affected zone were calibrated, respectively, through testing and finite element analyses of notched coupon specimens. The damage evolution law in the notched coupon specimens under different loads was compared. Finally, in order to examine the engineering applicability of the proposed model, the fracture performance of beam-column welded joints reported by previous researches was analyzed based on the cumulative damage model. The analysis results show that the cumulative damage model is able to successfully predict the cracking location, fracture process, the crack initiation life, and the total fatigue life of the joints.

• Journal of Platform Technology
• /
• v.11 no.5
• /
• pp.3-15
• /
• 2023

Requirements traceability link information is the basis for determining whether requirement change requested throughout the software development life cycle should be reflected in the system. Setting up complete requirements traceability links requires considerable effort. However, the commensurate benefits can be obtained in later development or further maintenance phases. For this reason, setting up and managing requirements traceability links in the software development phase are tasks that cause considerable resistance to developers. This study proposes a method for generating requirement traceability links in business applications. The key feature of the proposed method is that the traceability link from the requirements element, which is the basis of the corresponding element to the analysis element, is automatically established at the same time the elements of the analysis model are identified. This can be a way to reduce developer effort while increasing the efficiency of the traceability model. A case study on a Course Registration System demonstrates the feasibility of applying the proposed requirements traceability management method to actual software development.

• Korean Journal of Air-Conditioning and Refrigeration Engineering
• /
• v.25 no.12
• /
• pp.693-699
• /
• 2013

This paper describes a method for size optimization of the major design variables for solar water heating systems at the stage of concept design. The widely used RETScreen simulation tool was used for optimization. Currently, the RETScreen tool itself does not provide a function for optimization of the design parameters. In this study, an optimizer was combined with the software. A comparative study was performed to evaluate the RETScreen-based approach with the case study of a solar heating system in an office building. The optimized results using the RETScreen model were compared to previously published results with the TRNSYS model. The objective function of the optimization is the life-cycle cost of the system. The optimized design results from the RETScreen model showed good agreement with the optimized TRNSYS results for the solar collector area and storage volume, but presented a slight difference for the collector slope angle in terms of the converged direction of the solutions. The energy cost, life-cycle cost, and thermal performance regarding collector efficiency, system efficiency, and solar fraction were compared as well, and the RETScreen model showed good agreement with the TRNSYS model for the conditions of the base case and optimized design.