• Journal of the Korea Society of Computer and Information
• /
• v.10 no.6 s.38
• /
• pp.167-176
• /
• 2005

The software architecture is an essential part of a software-intensive system. In addition, the architecture evaluation is a very important process and a cheap way to avoid a software disaster. This article introduces a new method to evaluate architecture by maturity levels. Maturity Models which are about software and software process, have gained wide scale acceptance over the last decade. We are applying these techniques to the software architecture and propose SW(Software Architecture Maturity appraisal Model). SAMM consists of six-levels. We expect that our maturity model SAMM describe the requirements that any architecture must have in order to improve its software architecture design and constitute a proven architecture within which to manage the improvement efforts. We can reduce our effort to design architecture, have a guideline to construct the high qualify architecture with SAMM, and evaluate architecture and make architecture level.

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

• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.515-528
• /
• 2003

Component Based Software Development has been recognized as a new software development paradigm, and received much attention among researchers. However, it requires software architecture based development to assure component reusability and efficient software development. This paper proposes the Component Based 4+1 View Model of software architecture to support component based software development. It is redefined on the basis of the existing 4+1 view model of software architecture developed by Kruchten. Also, we describe the elements of the view model in detail with UML. This architecture constructs the foundation of component based software such as increasing the understanding of software and providing the information about how the components interact with each other. It can be done by exposing the context for the use of software components to each views.

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

• Journal of Information Technology Applications and Management
• /
• v.20 no.2
• /
• pp.69-87
• /
• 2013

The expanded spiral model in this paper consists of five processes of architecture design, architectural construction, architectural maintenance, operation, and architectural management. The former four processes are executed alternatively, while the latter architectural management process is executed continuously interacting with the other processes during the whole life cycle of the system. The expanded spiral model provides a conceptual framework to sort discussions of architectural degeneration into those of product-oriented processes and those of management processes, making it possible to incorporate the models and body of knowledge about project and program management especially those of Project Management Institute, into discussions of architectural degeneration. A good architecture decomposes the software-intensive system into components mutually interacting in a well-formed structure. The architecture design process and the architectural construction process together create the object system with well-designed architecture. The architectural maintenance process prevents the implemented architecture deviate from the designed architecture. The architectural management process monitors the changes of requirements including architecturally significant requirements, supports the other processes to be executed reflecting various perspectives of stake-holders, and creates and documents the reasons of architectural decisions, which is considered as a key element of the architecture.

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

• Transactions of the Korean Society of Automotive Engineers
• /
• v.20 no.6
• /
• pp.117-125
• /
• 2012

This paper describes a model-based software development methodology for AUTOSAR-ready light software architecture(AUTOSAR-Lite). The proposed methodology briefly represents an application software modeling technique using Matlab/Simulink. Using the proposed technique, application software architecture elements (e.g. software components, runnables, and interfaces) and functional behaviors can be designed in a single modeling environment. From the designed model, the codes of application software is automatically generated using Real-Time Workshop Embedded Coder. The generated application software is easily integrated with hand-coded basic software using the proposed method. In order to evaluate the proposed methodology, a diesel engine management system for a passenger car was employed as a case study. Based on the methodology, 8 atomic software components and 52 runnables are successfully developed, and they are evaluated by engine experiments. From this case study, AUTOSAR compatible model-based application software was successfully developed, and the effectiveness of the proposed methodology was evaluated.

• Journal of Ship and Ocean Technology
• /
• v.8 no.4
• /
• pp.26-33
• /
• 2004

PFFEM software, PFADS has been developed for the vibration predictions and analysis of coupled system structures in medium-to-high frequency ranges. PFFEM is numerical method which solves energy governing equation using finite element technique for complicated structures where the exact solutions are not available. Through the upgrades, present PFADS R3 could cover the general beam and plate structures including various kinds of beam-plate rigid joints and other joint systems such as spring-damper junction and rigid bar connection. This software is composed of 3 parts; translator, model converter and solver. The translator makes its own FE-model from bulk data of commercial FE software, and the model converter is used to convert FE-model to PFFE-model automatically. The solver calculates vibrational energy density and intensity for PFFE-model by solving global matrix equations of PFFEM. For the applications of real transportation systems, a container ship model has been examined with respect to major parameters, and reliable results have been obtained.

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