• Journal of Korea Multimedia Society
• /
• v.8 no.2
• /
• pp.233-248
• /
• 2005

An intrusion tolerant technology has been introduced as a solution to prevent intrusion accident for unknown fragility or attack. However, a systematic modeling technique is not applied into a system design and development based on intrusion tolerant technology. Especially, elements such as availability, integrity, reliability, confidentiality, and so on are important requirements in intrusion tolerant system. Nevertheless, current most of UML-based modeling techniques pass over or don't provide design techniques reflecting those requirements. Therefore, we know these weaknesses and propose both profile and design technique reflecting and applying intrusion tolerant requirements systematically in the development of application software based on intrusion tolerance. We expect that proposed technique can extend not only current UML's limitations but also can improve the quality of application software based on intrusion tolerance.

• Journal of the Korea Society of Computer and Information
• /
• v.23 no.12
• /
• pp.115-122
• /
• 2018

As the proportion of software in weapon systems increases, the impact of software on the overall system is growing. As a result, software quality management becomes important, and related regulations and work manuals for quality assurance activities at each stage in the R & D process are becoming more sophisticated. However, due to the characteristics of the weapon system software that is developed as a customized form for the purpose of a specific mission, there are limits to specifying and definitizing the detailed requirements (upper and lower level) according to various operational concepts during the development process. Due to this, software modification (patch change, shape change due to upgrade, etc.) occurs on account of many defects and performance improvement in the mass production and operation stage after the development is completed. In this study, we analyze the characteristics of these weapon system softwares and propose quality improvement methods based on ISO / IEC / IEEE 29119 test method.

• Journal of Distribution Science
• /
• v.13 no.1
• /
• pp.57-70
• /
• 2015

Purpose - Open source software has high utilization in most of the server market. The utilization of open source software is a global trend. Particularly, Internet infrastructure and platform software open source software development has increased rapidly. Since 2003, the Korean government has published open source software promotion policies and a supply promotion policy. The dynamism of the open source software market, the lack of relevant expertise, and the market transformation due to reasons such as changes in the relevant technology occur slowly in relation to adoption. Therefore, this study proposes an assessment model of services provided in an open source software service company. In this study, the service level of open source software companies is classified into an enterprise-level assessment area, the service level assessment area, and service area. The assessment model is developed from an on-site driven evaluation index and proposed evaluation framework; the evaluation procedures and evaluation methods are used to achieve the research objective, involving an impartial evaluation model implemented after pilot testing and validation. Research Design, data, and methodology - This study adopted an iteration development model to accommodate various requirements, and presented and validated the assessment model to address the situation of the open source software service company. Phase 1 - Theoretical background and literature review Phase 2 - Research on an evaluation index based on the open source software service company Phase 3 - Index improvement through expert validation Phase 4 - Finalizing an evaluation model reflecting additional requirements Based on the open source software adoption case study and latest technology trends, we developed an open source software service concept definition and classification of public service activities for open source software service companies. We also presented open source software service company service level measures by developing a service level factor analysis assessment. The Behavior-Structure-Evolution Evaluation Model (BSEM) proposed in this study consisted of a rating methodology for calculating the level that can be granted through the assessment and evaluation of an enterprise-level data model. An open source software service company's service comprises the service area and service domain, while the technology acceptance model comprises the service area, technical domain, technical sub-domain, and open source software name. Finally, the evaluation index comprises the evaluation group, category, and items. Results - Utilization of an open source software service level evaluation model For the development of an open source software service level evaluation model, common service providers need to standardize the quality of the service, so that surveys and expert workshops performed in open source software service companies can establish the evaluation criteria according to their qualitative differences. Conclusion - Based on this evaluation model's systematic evaluation process and monitoring, an open source software service adoption company can acquire reliable information for open source software adoption. Inducing the growth of open source software service companies will facilitate the development of the open source software industry.

• Journal of the Korean Society of Industry Convergence
• /
• v.25 no.2_2
• /
• pp.247-255
• /
• 2022

Robot Process Automation (RPA) is a computer technology called Robotic Process Automation, a form of business process automation based on the concept of software robots or artificial intelligence (AI) walkers. In general, in traditional workflow automation tools, software developers design software that creates a set of actions to automate tasks and interfaces for the back-end systems using internal APIs or dedicated script languages. However, in RPA software, automation can be implemented by configuring an operating processor as if the general user is directly performing the task of the application. In other words, it can be said that it is a suitable development method for automating simply repetitive tasks rather than developing specific programs in which all necessary functions are implemented, as in general software development. Thus, this is more appropriate for configuring and automating RPA software in traditional manufacturing companies that are not easy to develop and apply smart factories or high-end AI software. Therefore, this research aims to analyze the requirements required at the actual manufacturing companies, focusing on the manufacturer's case in Changwon, Gyeongsangnam-do, called SinceWin Co., Ltd., and to examine the possibility of RPA software in the manufacturing companies by implementing actual RPA software that supports office automation. Through the research, it was confirmed that the actually implemented RPA software met the requirements of the company and helped manufacturer practice significantly by automating the parts that were worked error-prone and manually periodically.

• Proceedings of the Korean Nuclear Society Conference
• /
• 2005.10a
• /
• pp.1099-1100
• /
• 2005

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

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.13 no.2
• /
• pp.83-92
• /
• 2013

Software globalization is the supporting process of adapting computer software to different country and culture. Most efforts for software globalization have been focused on the development of software implementation techniques or tools. However, global software sold worldwide has different requirements implied by different contexts, and the difference of requirements may derive different architectural design. In this paper, we define such architectural design knowledge as knowledge models and propose a method for developing and using the knowledge models for software globalization. Also we use set-top box middleware systems for digital data broadcast to validate the applicability of the proposed models and methods.

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

Because a medical embedded software is the software that control the medical devices that are relevant to a human life, it requires high qualify level. It is requires to develop and apply the quality test module that suitable for the requirements to meet the high quality requirements of the medical embedded software. Also, it needs to develop the process that complement the quality defects of software by feedback of the test result. In this study, we developed test module and quality inspection table which can test medical embedded software and produce result based on ISO/IEC 12119.

• The KIPS Transactions:PartD
• /
• v.13D no.6 s.109
• /
• pp.807-814
• /
• 2006

Along with the enlargement of application scope, the growth of requirements complexity, and the fast development of product for embedded system, lots of industries developing embedded software try to evolve their traditional development environment into the new paradigm such as product line engineering approach. In order to sufficiently support the evolution, software architecture is essentially required to develop the embedded software. In this paper, we propose a tool, named TToSA which translates the conventional software models to software architecture models. Our TToSA is developed with the critical implication about that an industry can approach toward the new development paradigm without the big change of the existing software development method.

• Journal of the Korea Society of Computer and Information
• /
• v.9 no.1
• /
• pp.17-23
• /
• 2004

Testing tools help software developers and test engineers to automate a part or the whole of test process and reduce the time and cost of software test. However. no automatic tools meet a variety of test requirements with various domains In this paper, we suggest a categorical taxonomy of automatic testing tools and analyze numerous commercial testing tools on its basis. Then we propose a development roadmap of software automatic testing tools. As a result of those analysis. we try to understand the complementary relations of the testing tools and seek for the direction of further development of the testing tools.