• Journal of KIISE:Computing Practices and Letters
• /
• v.15 no.6
• /
• pp.440-444
• /
• 2009

In order to improve the effectiveness of software process improvement, more than two models can be use to compensate the weakness of each other. One of integrated models is the one in which CMMI and software six sigma. However, it is very difficult for a small software development organization to select and apply an appropriate set of six sigma tools since there are a lot of six sigma tools and statistical knowledge is required. In this paper, we suggest a six sigma tool selection process to help small organizations select six sigma tools effectively based on organization business value. Thereby, small organizations can efficiently implement CMMI by adopting an appropriate set of six sigma toolkits.

• Journal of Platform Technology
• /
• v.8 no.4
• /
• pp.47-58
• /
• 2020

DO-330 Software Tool Qualification Considerations is a guideline for development of tools used to develop/verify software and hardware installed on aircraft. And among several processes, the verification process is very crucial as it occupies a large proportion for DO-330. Especially, in order to qualify tool with high safety level, test objectives must be performed with independence, accordingly, more time, cost, and manpower are required than other objectives. In addition, even if the test cases or test procedures are well defined, the higher the complexity of the test the higher probability of human error occurs. In this paper, we propose Script-based Test Automation Agent software structure for efficient DO-330 verification process of A661UAGEN tool developed by Hanwha Systems. Compared to the test performed manually by the test engineer, testing time of the Script-based Test Automation Agent is reduced by 87.5% and testing productivity is increased by 43.75%.

• Radiation Oncology Journal
• /
• v.30 no.1
• /
• pp.43-48
• /
• 2012

Purpose: To develop the dose volume histogram (DVH) management software which guides the evaluation of radiotherapy (RT) plan of a new case according to the biological consequences of the DVHs from the previously treated patients. Materials and Methods: We determined the radiation pneumonitis (RP) as an biological response parameter in order to develop DVH management software. We retrospectively reviewed the medical records of lung cancer patients treated with curative 3-dimensional conformal radiation therapy (3D-CRT). The biological event was defined as RP of the Radiation Therapy Oncology Group (RTOG) grade III or more. Results: The DVH management software consisted of three parts (pre-existing DVH database, graphical tool, and $Pinnacle^3$ script). The pre-existing DVH data were retrieved from 128 patients. RP events were tagged to the specific DVH data through retrospective review of patients' medical records. The graphical tool was developed to present the complication histogram derived from the preexisting database (DVH and RP) and was implemented into the radiation treatment planning (RTP) system, $Pinnacle^3$ v8.0 (Phillips Healthcare). The software was designed for the pre-existing database to be updated easily by tagging the specific DVH data with the new incidence of RP events at the time of patients' follow-up. Conclusion: We developed the DVH management software as an effective tool to incorporate the phenomenological consequences derived from the pre-existing database in the evaluation of a new RT plan. It can be used not only for lung cancer patients but also for the other disease site with different toxicity parameters.

• The KIPS Transactions:PartD
• /
• v.8D no.6
• /
• pp.761-770
• /
• 2001

As software industry is rapidly evolving, IT business enterprises have been meeting with cutthroat competition in developing software. As software reusability, time to market, and maintainability are considered as a competitive edge, software component techniques have lately attracted considerable attention. Currently, although there are some supporting tools for developing software components, they do not have tight connections among component developing processes such as component identification, component modeling, detailed design, code generation, deployment, and testing. And it is restrictive for users to construct various scales of components on component platform architecture. In this paper, we provide an implementation and a design of a supporting tool for constructing platform-independent software components, which covers all development lifecycles of components. In the phase of component modeling, platform independent, conceptual components are identified from domain model information in the view of system partitioning. Detailed design and implementation of a component are performed on the J2EE platform architecture. And the changes on the design model and source codes are consistently managed by using round-trip techniques.

• The KIPS Transactions:PartD
• /
• v.16D no.4
• /
• pp.571-582
• /
• 2009

This paper provides a way to overcome limitations of general collaborative software development tools that completely restrict co-ownership of resources among individuals in a team oriented developmental environment. It also provides a solution for users to co-own resources and at the same time manage version control and collision problems that may occur due to the co-ownership of resources.The cooperative development support tool of developed software uses the conventional optimistic technique but employs the algorithm which is improved to reduce costs and efforts required for solving collision. The collaborative software development tool presented in this paper is made up of the classical client/server structure with the P2P(peer to peer) method which supports information exchange among individuals. This tool is developed based on open source software CVS(Concurrent Version System). Functional efficiency was confirmed by comparing it to the utility of prior existing collaborative software development tools.

• Journal of the Korea Institute of Information Security & Cryptology
• /
• v.17 no.2
• /
• pp.51-59
• /
• 2007

Software testing is the process of analyzing a software item to detect the differences between existing and required conditions and to evaluate the features of the software item. A traditional testing focuses on proper functionality, not security testing. Fuzzing is a one of many software testing techniques and security testing. Fuzzing methodology has advantage that low-cost, efficiency and so on. But fuzzing has defects such as intervening experts. Also, if there is no specification, fuzzing is impossible. ROAD Tool is automated testing tool for RPC(Remote Procedure Call) based protocol and software without specification. Existing tools are semi-automated. Therefore we must modify these tools. In this paper, we design and implement ROAD tool. Also we verify utility in testing results.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2008.05a
• /
• pp.591-594
• /
• 2008

This paper explores how to characterise security properties of software components, and how to reason about their suitability for a trustworthy compositional contract. Our framework provides an explicit opportunity for software composers as well as software components to test a priori security properties of software components in a system composition. The proposed framework uses logic programming as a tool to represent security properties of atomic components and reason about their compositional matching with other components.

• IE interfaces
• /
• v.9 no.1
• /
• pp.25-40
• /
• 1996

It is a time-consuming work to develop a control software for AGVS considering different physical arrangements and transport requirements in automated manufacturing systems. An integrated software environment is suggested to support the development of the control software by utilizing a simulation software which imitates changes in the target shop floor. First, the basic functions of the controller are defined and interactions between modules(function) are identified to enhance the modularity of the controller. Prototype software is developed for the simulation station and the control station, respectively, which are connected with each other by a communication link to transmit predefined messages.

• Journal of KIISE:Computing Practices and Letters
• /
• v.11 no.1
• /
• pp.15-25
• /
• 2005

Embedded systems have a set of tasks to execute. These tasks can be implemented either on application specific hardware or as software running on a specific processor. The design of an embedded system involves the selection of hardware software resources, Partition of tasks into hardware and software, and performance evaluation. An accurate estimation of execution time for extreme cases (best and worst case) is important for hardware/software codesign. A tighter estimation of the execution time bound nay allow the use of a slower processor to execute the code and may help lower the system cost. In this paper, we consider an ARM-based embedded system and developed a tool to estimate the tight boundary of execution time of a task with loop bounds and any additional program path information. The tool we developed is based on an exiting timing analysis tool named 'Cinderella' which currently supports i960 and m68k architectures. We add a module to handle ARM ELF object file, which extracts control flow and debugging information, and a module to handle ARM instruction set so that the new tool can support ARM processor. We validate the tool by comparing the estimated bound of execution time with the run-time execution time measured by ARMulator for a selected bechmark programs.

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.4
• /
• pp.932-940
• /
• 1999

Object-oriented programming is often touted as promoting software reuse. However it is recognized that objected-oriented software often need to be restructured before it can be reused. refactoring is the process that changes the software structure to make it more reusable, easier to maintain and easire to be enhanced wit new functionalities. This paper desirbes experience gained and lessons learned from restructuring OODesigner, a Computer Aided Software Engineering(CASE) tool that supports Objects Modeling Technique(OMT). this tool supports a wide range of features such as constructing object modeler of OMT, managing information repository, documenting class resources, automatical generating C++ and java code, reverse engineering of C++ and Java cod, searching and reusing classes in the corresponding repository and collecting metrics data. although the version 1.x was developed using OMT(i.e the tool has been designed using OMT) and C++, we recognized that the potential maintenance problem originated from the ill-designed class architecture. Thus this version was totally restructured, resulting in a new version that is easier to maintain than the old version. In this paper, we briefly describe its restructuring process, emphasizing the fact that the Refactoring of the tool is conducted using the tool itself. Then we discuss lessons learned from these processes and we exhibit some comparative measurements of the developed version.