• Journal of the Korean Society of Manufacturing Technology Engineers
• /
• v.8 no.5
• /
• pp.54-62
• /
• 1999

This paper describes the design and implementation of a PC(personal computer) based open architecture machine tool controller. The hardware of open architecture CNC has generally a motion control board on a PC for controlling a servo motor. But this paper describes open architecture hardware that consists of a PC, a counter board a DAC board and a DIO board only. This makes it easy to generate CNC software module in a hardware-independent way. The proposed open architecture CNC software runs on the MS-Windows NT. The paper describes a method of con-trolling servo motors using a real-time timer of MS-Windows NT and a commercial real-time operating system on the MS-Windows. NT. An open and reconfigurable software module is made up of an object and an API(application programming interface). Using the object and the API a new CNC system can be quickly configured to control dif-ferent machine tools. The proposed open architecture CNC system is applied to 4-axis lettering center.

• Journal of KIISE:Software and Applications
• /
• v.30 no.10
• /
• pp.955-972
• /
• 2003

As the next significant software abstraction, software agents have generated lots of excitements in recent years because of its promise as a new paradigm for conceptualizing, designing, and implementing software systems. This promise is particularly attractive for creating software that operates in environments that are distributed, open, and complex, such as the Internet. The effort of developing agent systems have, however, suffered from lack of generalized agent architecture because of various properties of an agent and nonexistence of a standard agent architecture. An agent architecture is an important criterion in order to not only identify agents in their domain but also determine the software architecture of the system. The major contribution of the work described here is an object-oriented design of an agent architecture that addresses fundamental properties, which are autonomy and interaction. Object-oriented design method is used for identifying the internal modules of an agent architecture and organizing correlation between the modules are identified.

• ETRI Journal
• /
• v.25 no.6
• /
• pp.464-474
• /
• 2003

Component-based development leverages software reusability and reduces development costs. Enterprise JavaBeans (EJB) is a component model developed to reduce the complexity of software development and to facilitate reuse of components. However, EJB does not support component assembly by a plug-and-play technique due to the hard-wired composition at the code level. To cope with this problem, an architecture for EJB component assembly is defined at the abstract level and the inconsistency between the system architecture and its implementation must be eliminated at the implementation level. We propose a component-based application development tool named the COBALT assembler that supports the design and implementation of EJB component assembly by a plug-and-play technique based on the architecture style. The system architecture is first defined by the Architecture Description Language (ADL). The wrapper code and glue code are then generated for the assembly. After the consistency between the architecture and its implementation is checked, the assembled EJB components are deployed in an application server as a new composite component. We use the COBALT assembler for a shopping mall system and demonstrate that it can promote component reuse and leverage the system maintainability.

• Journal of KIISE:Software and Applications
• /
• v.28 no.10
• /
• pp.743-756
• /
• 2001

Component-based software development (CBSD) is a method for building large software system by integrating previously-existing software components. Software development method using components has several advantages such that reducing time to delivery and development costs, and increasing productivity etc. But integrating components developed from multiple vendors is too difficult As a result it is required the understanding on the context of use to develop reusable components. The context of use for software component of determined by software architecture. Therefore, it is possible to develop an application based on components if is based on software architecture. Also, it is essential to consider domain concepts for CBSD. To increase the reusability of components. we should develop components in a domain which is a set of related systems. In this paper, we proposed a domain architecture development methodology that supports component-based software development. Domain architecture that represents components and their relationship is produced through domain analysis and design process. We believe that component development methodology using proposed domain architecture can efficiently develop highly reusable components as well as easily develop and application using information acquired from domain architecture.

• The KIPS Transactions:PartD
• /
• v.16D no.5
• /
• pp.755-766
• /
• 2009

Software architecture allows us to make many decisions about a software system and analyze it even before it exists in order to make systematic and planned development possible. Similarly, architecture-based software evolution planningmakes planned evolution possible by allowing us to make many decisions about evolution of a software system and analyze its evolution at the level of architecture design before software evolution is realized. In this paper, we develop a framework for architecture-based software evolution planning for the class of deterministic evolution plans by defining and relating various essential concepts and developing its valuationmechanism so that a plan with the greatest value among candidate plans can be selected as an optimal plan. A case study is conducted for explicating the framework and exemplifying its usage.

• Journal of KIISE:Software and Applications
• /
• v.33 no.1
• /
• pp.17-31
• /
• 2006

Software architecture is the high level model of a software system. It should be specified with ADLs (Architecture Description Languages) for its clarity and preciseness. Most ADLs such as C2SADL have not come into extensive use in industries since ADL users should learn a distinct notation specific to architecture, and ADLs do not address all stakes of the development process that is becoming diversified everyday. On the other hand, UML is a do facto standard general modeling language for software developments. UML provides a consistent notation and various supporting tools during the whole software development cycle. But, UML is a general modeling language and does not provide all concepts that are important to architecture description. UML should be extended in order to precisely model architecture. In this paper, we defined a C2 architecture modeling language as a UML2.0 profile. We applied the defined C2 architecture modeling language to the modeling of a restaurant reservation system.

• Journal of KIISE:Software and Applications
• /
• v.33 no.2
• /
• pp.167-185
• /
• 2006

Software architecture, which is the high level model of a software system, should be specified with ADLs (Architecture Description Languages) for its clarity and preciseness. Most of ADLs such as ACME, however, have not come into extensive use in industries since ADL users should learn a distinct notation specific to architecture. On the other hand, UML is a do facto standard general modeling language for software developments. UML provides a consistent notation and various supporting tools during the whole software development cycle. UML, being a general modeling language, does not provide all concepts that are important to architecture description. UML should be extended in order to precisely model architecture. A number of researches on architecture modeling based on WML have been progressed. Ail of them, however, are based on the UML1.x. UML2.0 embraces much more concepts that are important to architecture modeling than UML1.x. In this paper. we defined an architecture modeling language based on UML2.0. We defined Generic ADL by extending UML2.0 and applied the defined Generic ADL to a restaurant reservation system.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.13 no.5
• /
• pp.852-860
• /
• 2010

An environment in which the software is operated become more complex and changed dynamically. Such software requires the ability to adapt in accordance with operating environments, by monitoring the changes of user requirements and operating environments. Especially, the mobile device used in military operation requires more dynamical adaptation than the mobile device in normal environment. In this paper, we propose MOSAIC architecture based on Self-Adaptive Software suitable for military mobile device and verify the results. The proposed architecture consists of context manager, evaluation manager and adaptation manager. We simulate the MOSAIC architecture by modelling PRE(Position Reporting Equipment) used in the army and verify four types of operational mode and dynamical reconfiguration of user interface.

• Journal of Software Engineering Society
• /
• v.26 no.1
• /
• pp.17-29
• /
• 2013

Software System Evolution is more planned and systematic maintenance process as well as a type of maintenance. The research of software evolution provides basis of decisions for maintenance value through cost-benefit analysis of legacy system and architecture-based software evolution enables engineers to reduce maintenance cost by automation of repetitive evolution tasks. This paper proposes a framework for software system evolution using architectural transformation pattern.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.27 no.2
• /
• pp.247-255
• /
• 2024

Development of electronic warfare(EW) software has become increasingly challenging due to stricter regulations, shorter development cycles, and increased reliability testing. Consequently, software development often proceeds without proper architecture design, which can lead to missing critical quality requirements and potential system redesigns. In this study, we propose using Attribute-Driven Design(ADD) 3.0 to design software architecture specifically tailored for EW systems, enabling a more systematic approach to address quality requirements. The paper presents an overview of EW software and ADD 3.0 methodology, followed by an analysis of the architecture design results using static and dynamic views. The paper concludes by discussing the effectiveness of the proposed architecture design.