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

• The KIPS Transactions:PartD
• /
• v.12D no.4 s.100
• /
• pp.617-626
• /
• 2005

To design a software system many architecture styles have to be combined to construct the overall architecture of the system What to choose among various architecture styles or architectural approaches depends on the fact of what kind of functional or non-functional quality requirements the system should satisfy In this study, we define the method to choose suitable architectural approaches by the satisfaction level of system requirements that is evaluated through estimation about technical parts of architectural approaches, and verify the evaluation method by the case study that apply the evaluation method to choose architectural approaches for message system.

• Proceedings of the KIEE Conference
• /
• 2011.07a
• /
• pp.739-740
• /
• 2011

최근 변전소용 IED는 IEC61850의 적용을 기점으로 하여 기술적으로 더 많은 발전을 거듭하고 있다. IED에 더 다양한 기술을 포함하면서 안정적이고 확실한 동작을 요구하는 것은 기본이고, 사용자 위주의 Interface와 편리한 관리 도구도 요구되어 진다. 이에 따라 IED를 PC로 제어하고 관리하기 위한 소프트웨어 또한 기술적으로 발전해야 하는 상황이다. 소프트웨어는 기본적으로 실시간 관리와 프로젝트 관리 그리고 다수의 IED지원 등의 기능을 가져야 하며 이를 구현하기 위하여 여러 가지 방식의 아키텍처 패턴이 적용될 수 있다. 본 논문에서는 IED를 관리하는 소프트웨어에 적용될 수 있는 아키텍처를 제시함으로써 소프트웨어 구현에 대한 방향을 모색해 보았다.

• KIPS Transactions on Software and Data Engineering
• /
• v.6 no.8
• /
• pp.391-400
• /
• 2017

Software architecture plays a key role in satisfying non-functional requirement (NFR), i.e. quality requirements and constraints. Architecture design methods and tactics for conventional NFR are largely available in literatures. However, the methods for the target system-specific non-conventional NFRs are not readily available; rather architects should invent the design methods from their experiences and intuitions. Hence, the hardship to design architectures for non-conventional NFRs is quite high. In this paper, we provide a systematic architecture design methodology for non-conventional NFRs. We provide a five-step process, and detailed instructions for the steps. In the process, we treat the traceability among artifacts and seamlessness as essential values for supporting effective architecture design. We apply the methodology on designing architectures for a platform software system. We believe that the proposed methodology can be effectively utilized in designing high quality architectures for non-conventional NFRs.

• Journal of KIISE:Software and Applications
• /
• v.37 no.2
• /
• pp.95-103
• /
• 2010

Improving the competitiveness of software products in the market involves procuring the means to design software architecture that deliver qualities necessitated by stakeholder requirements within allocated budget, thereby improving the cost-effectiveness of the end product. Currently, software architecture evaluation methods are used to predict and review qualities inherent in software architecture designs and to choose a candidate architecture that delivers desired qualities. Existing software architecture evaluation methods, however, fail to address the cost considerations dependent on the architecture chosen for product implementation. In this paper we suggest a cost estimation method for software architecture which adapts the cost drivers in the software cost estimation model COCOMO II to support cost estimation during architecture evaluation. The suggested method can be performed in coordination with existing software architecture evaluation efforts and supplements existing architecture evaluation techniques with guidelines for identifying and evaluating cost drivers in candidate software architectures without incurring extra overhead. The accuracy of the cost estimation using the suggested method is verified through application of the method to the architecture candidates used in RPS (Robot Patrol System), a surveillance embedded system.

• Proceedings of the Korean Institute of Navigation and Port Research Conference
• /
• 2011.06a
• /
• pp.29-30
• /
• 2011

GNSS 시스템의 다원화에 따른 DGPS RSIM 기능도 DGNSS 체제로 기능적, 시스템적 고도화가 필요한 시점이 도래하고 있다. 이와 관련하여 차세대 DGNSS RSIM 아키텍처를 미국 해양경비대(USCG) NAVCEN에서 제안하였는데, 이 차세대 DGPS RSIM 아키텍처의 기본 요구조건은 PC 플랫폼 기반의 신규 신호 및 기술에 대한 충분한 유연성을 확보할 수 있고, 기존 사용자 수신기와 기존 기준국 시스템과의 충분한 호환이 가능해야 한다는 것이다. 그러나 위의 제시된 아키텍처는 DGPS RSIM 시스템의 소프트웨어 응용에 초점이 맞추어져 있어서 GNSS 다원화에 따른 DGNSS 기준국 기능 고도화에 한계가 있다. 그러므로 본 논문에서는 소프트웨어 DGNSS RSIM 개발을 위한 후속연구로서, 현재 운영 중인 GPS/GLONASS를 중심으로 보정정보 생성 및 그 측위정확도 성능분석에 중점을 두고자 한다. 기 설계된 DGNSS 소프트웨어 RSIM 아키텍처에 대해 설명하고, 설계된 아키텍처와 통합보정정보 생성 및 처리 기법이 적용된 GPS/GLONASS 통합보정시스템을 구현하여, 향후 소프트웨어 DGNSS RSIM을 위한 측위정확도 측면에서의 성능을 분석한다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2004.04b
• /
• pp.379-381
• /
• 2004

소프트웨어 아키텍처는 소프트웨어 시스템의 중요한 요소를 정의하고 이들 요소간의 상호관계를 나타낸 전체 시스템의 기본 구조이다. 시스템의 변경과 확장에 용이하고 시스템의 상호 연동성을 확보하는데 있어 아키텍처 기반의 기술 접근은 필수적인 요소이다. 이러한 소프트웨어 아키텍처를 명가하기 위한 다양한 방법들이 제시되고 있으며, 이 방법들은 비즈니스요구를 반영하고 품질속성에 따른 시나리오를 만들어 그것을 기반으로 소프트웨어 아키텍처를 평가하게 된다. 이에 본 논문에서는 ISO9126에서 제시한 소프트웨어의 품질을 기반으로 아키텍처 평가에 적용되어질 품질속성을 도출하기 위하여, 웹기반 전자상거래시스템인 B2C에서의 사용자요구사항을 분석 해 보고자 한다.

• The Journal of the Korea Contents Association
• /
• v.9 no.11
• /
• pp.63-73
• /
• 2009

Architecture base mechanism centers to construct software system. There is construction of successful software system how firmly define software. Reason that architecture base software is important is used and expresses early design decision item of system and is because reusability is possible by means of communication between comprehension person concerned. Analyzed special quality of pattern and importance of architecture and general requirement and portability and consider ISO/IEC 9126 and ISO/IEC 14598 and propose system and Metrik in this research. Also, do defect particulars and efficiency test that test according to examination formality of architecture base software and analyzed result.

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

• Journal of Internet Computing and Services
• /
• v.6 no.4
• /
• pp.9-20
• /
• 2005

To design a software system in success, architectural approaches which are in basis of architectural design, must be primarily selected. What to chose among various architecture styles as specific as architectural approaches, varies along with the system status of what kind of functional or non-functional quality requirements should satisfy. In this study, we propose the evaluation model for making a selection of architectural approaches, and select an architectural approach for message system actively using in diversified internet utilization and enterprise application integration, In other words, if there may be possibly existed several architectural approaches, we present the most suitable method of architectural approach out of them through an evaluation of analyzing the system requirements satisfaction level. In addition, when it performs specific design and implementation utilizing design patterns based on thread, developers would be able to link up the architecture design directly.