• Journal of Convergence for Information Technology
• /
• v.7 no.2
• /
• pp.67-76
• /
• 2017

Along with shortening the life cycle of software utilization and supporting various types of user functions, the importance of software architecture development has been emphasized recently. If a software architecture is developed flexibly and reliably for expansion to support new functionality, it can quickly cope with new market demands. This paper proposes an architecture design method based on design recovery of open source software to reuse the software in the development of sustainable software system. When using open source software to develop a software system based on software architecture, we can develop a software system rapidly and also can improve the reliability of the system because we use the already proven open source software in the development.

• IEMEK Journal of Embedded Systems and Applications
• /
• v.8 no.4
• /
• pp.195-204
• /
• 2013

The embedded software has been developed in the forms of various versions that provides similar service based on product family. For increase usefulness of product family, software must has well-structured and reusable properties. Software architecture is important to improve adaptability in model-based development of embedded software mounted onto product family. In this paper, we proposed a technique of ADD(Attribute-Driven Design)-based software architecture design for low power software development. This technique provides a chance to consider the power consumption issue in design phase of software, and makes possible to develop low power embedded software.

• Journal of the military operations research society of Korea
• /
• v.31 no.2
• /
• pp.105-115
• /
• 2005

To ensure interoperability among TADILs, we need inter-operational system of tactical data link that allows sharing of specific, planned information among different TADILs. In this paper, we have proposed the design of a conceptual software architecture of inter-operational system. For developing of a conceptual software architecture, we analyze the actual condition of ADSI used in the US military and identify functions and quality-attributes. Based on these factors, we design the conceptual software architecture for inter-operational system of tactical data link using Attribute-Driven Design(ADD) method. ADD is consist of three phases - choose the module to decompose, refine the module, repeat the steps for every module that needs further decomposition. To evaluate of ADD results, we apply the Software Architecture Analysis Method(SAAM) which is consist of making evaluation scenarios, choosing indirect scenarios, evaluation scenarios' interaction, and creating an overall evaluation. Through the evaluation, we verify the conceptual software architecture of inter-operational system.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.10 no.4
• /
• pp.20-29
• /
• 2007

The engagement control software embedded in the weapon control computer of the fire control center for air defense missile system is large-scale real-time software. The use of typical software development methodologies is not appropriate to develop such large-scale embedded software in terms of reusability, reliability, and productivity for the reason that it is significantly complicated, and highly dependent on hardware platforms and developers. In this paper, a model-based software architecture using components based on UML 2.0 for the engagement control software is presented in order to solve these problems. This software architecture is verified using the black-box test, the scenario-based test, and the Ethernet packet monitoring test methods. The results demonstrate that the developed software architecture can be employed to enhance reusability, maintainability, and productivity of large-scale embedded software.

• International Journal of Computer Science & Network Security
• /
• v.24 no.5
• /
• pp.191-197
• /
• 2024

Software reuse gives the meaning for rapid software development and the quality of the software. Most of the Java components/libraries open-source are available only in Java Archive (JAR) file format. When a software design enters into the development process, the developer needs to select necessary JAR files manually via analyzing the given software architecture and related JAR files. This paper proposes an automated approach, JarBot, to suggest all the necessary JAR files for given software architecture in the development process. All related JAR files will be downloaded from the internet based on the extracted information from the given software architecture (class diagram). Class names, method names, and attribute names will be extracted from the downloaded JAR files and matched with the information extracted from the given software architecture to identify the most relevant JAR files. For the result and evaluation of the proposed system, 05 software design was developed for 05 well-completed software project from GitHub. The proposed system suggested more than 95% of the JAR files among expected JAR files for the given 05 software design. The result indicated that the proposed system is suggesting almost all the necessary JAR files.

• Journal of KIISE:Software and Applications
• /
• v.32 no.1
• /
• pp.10-21
• /
• 2005

Software architecture is increasingly being viewed as a key design in developing complex software systems, which largely affects the achievement of quality attributes. During the architecture-based software development, therefore, architectural transformation is needed to achieve quality attributes. Due to the variety of design alternatives and the poor predictability of the effects of the transformation, however, it is not easy to apply architectural transformation. Therefore, the method is needed to support architectural transformation through systematically analyzing the effects of applying various design alternatives to the architecture. This paper proposes an approach to support software architecture transformation. Based on architectural design decisions and the constraints on them included in the architecture, our approach defines a decision constraint graph representing the dependencies among architectural design decisions. Through using the decision constraint graph, architectural transformation can be systematically performed by understanding the effects of applying a transformation. While this work supports more understanding of applying architectural transformation, it also helps reconstruct a software architecture to improve the quality of the software.

• Journal of Information Technology Services
• /
• v.5 no.2
• /
• pp.155-168
• /
• 2006

Software product line is a software product or a set of software system, which has common functions. We can develop a specific software product, which satisfies requirements of a particular market segment and a mission in a specific domain by reusing the core asset such as the developed software architecture through the software product line. Software development methodology based on the software product line can develop a software more easily and fast by reusing the developed software core asset. Developed countries of software technology select software product line as a core field of software production technology, and support technology development. In case of USA, CMU/SEI(Carnegie Mellon University/Software Engineering Institute) developed product-line framework 4.0 together with the industry and the Department of Defense. Europe is supporting the development of product line technology through ITEA(IT for European Advancement) program. However, industries in our country understand the necessity of software production technology based on product line concept for the purpose of increasing productivity, it is not sufficient to invest for this technology development. In this paper, we aim to construct the common architecture of software product line for production of the software product line.

• IE interfaces
• /
• v.16 no.spc
• /
• pp.127-131
• /
• 2003

Component-based development approach is used in modern software system development projects that are very complex and large-scale. Technical components are more effective rather than business components in software development. However, on the Microsoft .net environment, the technical component-based development issues are not adopted. Moreover, software architecture on the .net environment is not studied yet because the development platform is recently used in the development of enterprise-level system. This paper proposes a technical component-based software architecture on .net environment. Seven technical components - configuration, data access, exception, file I/O, log, message, and paging - are contained in the architecture. The proposed architecture enables developers to reduce development time and to concentrate business logic rather than architectural issues. To verify the proposed architecture and the components, a partner management system is developed based on the architecture.

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

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