• International journal of advanced smart convergence
• /
• v.10 no.2
• /
• pp.130-137
• /
• 2021

In the current software project, it is still very difficult to extract and define clear requirements in the requirement engineering. Informal requirements documents based on natural language can be interpreted in different meanings depending on the degree of understanding or maturity level of the requirements analyst. Also, Furthermore, as the project progresses, requirements continue to change from the customer. This change in requirements is a catastrophic failure from a management perspective in software projects. In the situation of frequent requirements changes, a current issue of requirements engineering area is how to make clear requirements with unclear and ambigousrequirements. To solve this problem, we propose to extract and redefine clear requirements by incorporating Design Thinking methodologies into requirements engineering. We expect to have higher possibilities to improve software quality by redefining requirements that are ambiously and unclearly defined.

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

• Proceedings of the KSRS Conference
• /
• 2007.10a
• /
• pp.175-178
• /
• 2007

COMS (Communication Ocean Meteorological Satellite) is the geostationary satellite being developed by Korea Aerospace Research Institute for multi-mission: experimental communication, ocean monitoring and meteorological observations. The COMS operation is controlled by the on-board software running on the spacecraft central computer. The software is written in ADA language and developed under the software life cycle: Requirement analysis, Design, Implementation, Component test and Integration test. Most functional requirements are tested at component level on a software component testing tool, ATTOL. ATTOL provides a simple way to define the test cases and automates the test program generation, test execution and test analysis. When two or more verified components are put together, the integration test starts to check the non-functional requirements: real-time aspect, performance, the HW/SW compatibility and etc. This paper introduces the COMS on-board software and explains what to test and how to test the on-board software at component level using ATTOL.

• Proceedings of the KSRS Conference
• /
• 2007.10a
• /
• pp.460-463
• /
• 2007

COMS (Communication Ocean Meteorological Satellite) is the geostationary satellite being developed by Korea Aerospace Research Institute for multi-mission: experimental communication, ocean monitoring and meteorological observations. The COMS operation is controlled by the on-board software running on the spacecraft central computer. The software is written in ADA language and developed under the software life cycle: Requirement analysis, Design, Implementation, Component test and Integration test. Most functional requirements are tested at component level on a software component testing tool, ATTOL. ATTOL provides a simple way to define the test cases and automates the test program generation, test execution and test analysis. When two or more verified components are put together, the integration test starts to check the non-functional requirements: real-time aspect, performance, the HW/SW compatibility and etc. This paper introduces the COMS on-board software and explains what to test and how to test the on-board software at component level using ATTOL.

• Journal of Korea Society of Digital Industry and Information Management
• /
• v.6 no.2
• /
• pp.183-191
• /
• 2010

Decision problem called an optimal release policies, after testing a software system in development phase and transfer it to the user, is studied. The applied model of release time exploited infinite non-homogeneous Poisson process. This infinite non-homogeneous Poisson process is a model which reflects the possibility of introducing new faults when correcting or modifying the software. The failure life-cycle distribution used mixture which has various intensity, if the system is complicated. Thus, software release policies which minimize a total average software cost of development and maintenance under the constraint of satisfying a software reliability requirement becomes an optimal release policies. In a numerical example, after trend test applied and estimated the parameters using maximum likelihood estimation of inter-failure time data, estimated software optimal release time.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.21 no.6
• /
• pp.1197-1202
• /
• 2017

Security services that support electric energy service gateway require relatively high reliability. In particular, the application services that accompany communications and data are run organically. Each of the security services should support a secure service platform that supports a secure, scalable life cycle for existing services which should be extends security layer of Universal Middleware. In this convergence platform, it is the study of security transfer modular services that allow independent life cycle management of systems through Universal middleware. First, It is modular in terms of energy consumption service and data, enabling real-time operation, communications, remote management and applications. Second, the life cycle of the secure module to support start, stop and updating of the security module by applying the security policy module layer concept. It is modular system enabling to design of dyanmic models in the smart grid, the service was intended to be standardized and applied to the security service platform.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.6
• /
• pp.1803-1809
• /
• 2000

With the wide usage of the Internet, there use of pre-developed software is becoming important more and more in the development of various communication software. In this paper, the architecture to reuse the communication software is proposed. It is applied to the development of MIB-II system group of SNMP agent software for reusing. If Communication software is developed using this architecture, the software development life cycle will be abridged and the development cost will be reduced.

• Journal of Information Technology Services
• /
• v.2 no.1
• /
• pp.135-143
• /
• 2003

As the functional and nonfunctional requirements of defence systems become more complex and precise, concerning about the systematic development of software embedded into the defence systems has become surged up. In order to develop more reliable and correct software, and to extend the life cycle of the developing software, adoption of some engineering technologies such as development process, methodology, CASE tools and documentation is essentially required. This paper introduce an approach to technical information management in embedded software development process, with an instance, airborne ECM system development project. Particularly, we suggest and explain how to guide the software development according to process and methodology, and how to generate technical documents using CASE tool.

• Journal of Korean Society for Quality Management
• /
• v.25 no.4
• /
• pp.115-130
• /
• 1997

SQM (Software Quality Metrics) is a methodology whose primary objective is the measurement of compliances to requirements using a set of software life cycle properties called quality factors, which is based on the hierachical relationshiips between factors, criteria and elements. For this study, two factors (Correctness, Maintainability) and five criteria were selected. In addition, several tens of quality elements were developed to su, pp.rt them. Qualities of three computer programs which are being used for engineering purpose were measured. As a result, it is concluded that SQM is a valuable method for continuously monitoring the pulse of software quality development and that it can be used as a tool for software quality assurance.

• Journal of the Korean Society for Railway
• /
• v.11 no.3
• /
• pp.211-215
• /
• 2008

Generally, an EMU (Electronic Multiple Unit) is manufactured by assembling a large number of components and parts with extensive raw materials. Throughout its entire life cycle, much both the complicated system and long operating period. Therefore, it is necessary to the environmental performance of EMUs from raw materials to waste. In this study, RACE (Rail Assessment for Clean Environment) was developed as the software that can analyze the environmental RACE had several LCI (Life Cycle Inventory) database for main components as well as principal materials in EMUs. In the future, RACE can also be used as a tool for environmental communication between manufacturers and operators. Also, we will improve RACE continuously to assess more easily the environment of rolling stocks EMU for user.