• KIPS Transactions on Software and Data Engineering
• /
• v.5 no.10
• /
• pp.471-476
• /
• 2016

Software architecture is depend on software quality for in the design phase. Architecture interoperability have a effect in the software quality. As a result, the software quality will deteriorate. Therefore, we are need to check that configuration component for a flexible architecture and quality in the architecture. In this paper, we are suggest that configuration component of the architecture interaction.

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

• KIPS Transactions on Software and Data Engineering
• /
• v.5 no.10
• /
• pp.465-470
• /
• 2016

Project success is depend on requirement analysis and design for in the software engineering. Architecture error have a effect in the whole system. As a result, the software quality will deteriorate. Therefore, we are need to check that software interaction and modify for a stable architecture and environment in the design phase. In this paper, we are suggest that factors of the architecture environment consideration.

• Journal of Navigation and Port Research
• /
• v.43 no.6
• /
• pp.353-360
• /
• 2019

Technology-driven development of a new system makes it difficult for users and stakeholders to identify or intervene in the development process, resulting in systems with unnecessary functions and poor quality services. Applying the software architecture design process to the initial design of the navigation system platform of autonomous ships enables the development of a system that reflects the required functions and service quality of the stakeholders. The design, which includes all of the subsystems that make up an autonomous ship platform, is close to an enterprise architecture. Thus, we strived to design a navigation system platform suitable for the design range of the software architecture. This study analyzed the definition of functional requirements, and quality attributes by applying the software architecture design procedure. This study was conducted to identify the characteristics of the navigation system and platform needs, and the stakeholders were identified. To derive the functional requirements and constraints of the platform, a quality attributes workshop was held engaging stakeholders, and the results of the analysis of functional requirements and quality attributes were listed. Based on the results of this study, the architect can establish the evidence and technical solutions that are integral for the architecture development, and will facilitate the creation of quality attribute scenarios.

• Journal of Information Technology Applications and Management
• /
• v.19 no.2
• /
• pp.135-147
• /
• 2012

Software architecture, as a blueprint for the system, should provide a robust foundation for design, implementation, and maintenance, for communication and documentation, and for reasoning about important system properties. Software architecture plays a central role during the whole software life-cycle. There are so diverse definitions of the software architecture, however, and there is no common agreement about what software architecture is. Examining 27 'published' definitions of software architecture, we synthesize an extensive model on the essential elements of software architecture, which consists of components, interaction among components, well-formed structure, reasons, and various perspectives. Further, we explore the possibility of unifying diverse software architecture definitions into a software architecture life-cycle model.

• Transactions of the Korean Society of Automotive Engineers
• /
• v.21 no.1
• /
• pp.68-77
• /
• 2013

This paper presents AUTOSAR-ready light software architecture (AUTOSAR-Lite), which is a light weighted version of the AUTOSAR, for automotive embedded control systems. The proposed AUTOSAR-Lite reduces overhead problems caused by the excessive standard specifications of AUTOSAR. Concurrently, AUTOSAR-Lite keeps advantages of AUTOSAR such as a scalability, re-usability, reliability, and transferability. The fundamental design of AUTOSAR-Lite is originated from the AUTOSAR standard. AUTOSAR-Lite is composed of three layers such as an application software, runtime environment, and basic software layer. The application software layer adopts component-based design methodology as AUTOSAR. The runtime environment layer integrates interfaces between application and basic software layers. In case of the basic software layer, restrictions of the module configurations and interfaces of basic software are minimized. In order to validate the feasibility of AUTOSAR-Lite, a software design result based on AUTOSAR-Lite software architecture for electronic throttle control (ETC) system is suggested.

• Journal of the Korea Computer Industry Society
• /
• v.3 no.1
• /
• pp.117-124
• /
• 2002

In software development process, appropriate design can exist more than one. And software architectures can be restructured by modification and update during design processes. Therefore, the method that specify efficiently the modification elements of architectures, and manage different versions of architecture designed through various aspects is required. In this study, we propose software architecture restructuring mechanism that can restructure legacy architecture and a new software architecture designed with reuse of it in integrated form, and define specification elements and structure of the proposed restructured architecture specification. It provides the method that can reference and reuse architectures designed with various aspects of developers in architecture design processes. In addition, it supports flexible specification method for specification of modification elements such as revision, substitution, update of legacy software architecture.

• Journal of KIISE
• /
• v.42 no.3
• /
• pp.341-360
• /
• 2015

While architectural patterns provide software development solutions by providing schemas for structural organizations of software systems based on empirical knowledge, Jackson's problem frames provide a method of analyzing software problems. Problem frames are useful to understanding the software development problem, by putting emphasis on the problem domain, rather than on the solution space. Research exists that relates problem frames and software architecture, but most of this research uses problem frames only to understand given problems. Moreover, none of the existing research derives architectural patterns by considering both problem frames and quality attributes. In this paper, we propose a software architecture design method for pattern-based architecture design, by matching problem frames and architectural patterns. To that end, our approach first develops the problem model based on the problem frames approach, and then uses it to match with candidate architectural patterns, from the perspectives of both functionality, and quality attributes. Functional matching uses the problem frame diagram to match the problem model of an architectural pattern. We conduct a case study to show that our approach can systematically decide the right architectural patterns, and provide a basis for fine-grained software architecture design.

• Journal of Information Technology Applications and Management
• /
• v.20 no.3
• /
• pp.1-18
• /
• 2013

Software architecture is the blueprint for a software system and should provide consistent guidelines for design, implementation, and maintenance throughout the entire lifecycle of the system. Components, interactions between the components, well-formed structure, reasons, and various perspectives reflecting various stakeholders' concerns changing through the phases of software lifecycle are the key elements of software architecture. The architect identifies and engages the stakeholders, understands and captures stakeholder's concerns including those regarding life cycle, and lets the concerns reflected in the architecture. To do so, architect should take into consideration various contextual elements regarding the system too. We make an extended list of the elements, especially those of business application software architecture, that the architect should take into consideration and construct a model of the relationships between the elements.

• Journal of Korea Society of Industrial Information Systems
• /
• v.6 no.4
• /
• pp.39-47
• /
• 2001

Software architecture serves as a framework for understanding system component and their interrelationships. Software architectures can be reusable assets to achieve low costs, high productivity, and consistent quality. We have developed a software architecture design environment, called Happy Work. In this paper, we would like to present the structure and functions of Happy Work. Happy Work has two main functions. First, it provides a graphic editor for modeling of software architecture diagram. Second, it provides an ADL, called HWL(HappyWork language). HWL is a language that describes software architecture.