• 제목/요약/키워드: software architecture model

검색결과 561건 처리시간 0.024초

소프트웨어 아키텍처의 성숙 평가 모델에 관한 연구 (A study on the Maturity Appraisal Model of Software Architecture)

  • 김경희
    • 한국컴퓨터정보학회논문지
    • /
    • 제10권6호
    • /
    • pp.167-176
    • /
    • 2005
  • 소프트웨어 아키텍처는 소프트웨어 집중적인 시스템의 가장 주요한 부분으로, 아키텍처 평가는 시스템에서 매우 중요한 과정이고 소프트웨어 재앙을 예방할 수 있는 가장 저렴한 방법이다. 본 논문은 성숙모델을 통하여 아키텍처를 평가하는 새로운 방법을 소개한다. 기존의 성숙모델들은 소프트웨어나 소프트웨어 프로세스에 관한 것으로 지금까지 빠른 속도로 발전되어 왔다. 본 논문에서는 이러한 기법들을 소프트웨어 아키텍처에 적용한 SAMM(Software Architecture Maturity appraisal Model)을 제안한다. SAMM은 여섯 등급으로 구성되어 있다 제안한 성숙 모델 SAMM은 시스템 개선을 관리하는 발전된 아키텍처를 구성하고 소프트웨어 아키텍처 설계를 개선하기 위해 필수적으로 요구되는 아키텍처 요구사항들을 명세한다. 또한, 아키텍처 설계를 위한 노력을 줄이고, 질 높은 아키텍처를 구성할 수 있는 지침을 마련해주며, 아키텍처를 평가하여 등급을 매긴다.

  • PDF

소프트웨어 아키텍처의 구성요소에 대한 포괄적 모델 (An Extensive Model on Essential Elements of Software Architecture)

  • 고석하
    • Journal of Information Technology Applications and Management
    • /
    • 제19권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.

컴포넌트 기반 소프트웨어 개발을 지원하는 소프트웨어 아키텍처 뷰 모델 ((The View Model of Software Architecture for Component Based Software Development))

  • 박준석;문미경;염근혁
    • 한국정보과학회논문지:소프트웨어및응용
    • /
    • 제30권5_6호
    • /
    • pp.515-528
    • /
    • 2003
  • 컴포넌트 기반 소프트웨어 개발 방법은 새로운 패러다임으로 인식되고, 활발한 연구가 진행되고 있다. 그러나 컴포넌트 기반 개발에서 컴포넌트의 재사용성과 효율적인 소프트웨어 개발을 보장하기 위해서는 소프트웨어 아키텍처를 기반으로 한 개발이 필요하다. 본 논문에서는 컴포넌트 기반 소프트웨어 개발을 지원하기 위해, Kruchten이 제시한 4+1 뷰 모델을 기반으로 재 정의한 컴포넌트 기반 4+1 소프트웨어 아키텍처 뷰 모델을 제안한다. 또한 뷰 모델의 요소와 UML을 이용한 뷰 모델 요소의 표현을 제시한다 이 아키텍처는 컴포넌트의 사용문맥을 각 뷰에 반영함으로써 소프트웨어에 대한 이해와, 컴포넌트의 상호 작용에 대한 정보 등 컴포넌트 기반 소프트웨어 구성에 대한 틀을 구성한다.

UML 2.0 모델 기반의 교전통제 소프트웨어 아키텍처 개발 (Development of the Engagement Control Software Architecture Based on UML 2.0 Model)

  • 유명환;배정일;신진화;조길석
    • 한국군사과학기술학회지
    • /
    • 제10권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.

프로그램 관리 관점에 기반을 둔 소프트웨어 아키텍처 생애주기 모델 : 확장된 나선형 모델 (A Software Architecture Life Cycle Model Based on the Program Management Perspective : The Expanded Spiral Model)

  • 고석하
    • Journal of Information Technology Applications and Management
    • /
    • 제20권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.

Contextual Models of Business Application Software Architecture

  • Koh, Seokha;Ji, Kyoung-Sook
    • Journal of Information Technology Applications and Management
    • /
    • 제20권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.

AUTOSAR 대응 경량화 소프트웨어 아키텍처를 이용한 어플리케이션 소프트웨어 모델링 및 통합 방법 (Application Software Modeling and Integration Methodology using AUTOSAR-ready Light Software Architecture)

  • 박인석;이우택;선우명호
    • 한국자동차공학회논문집
    • /
    • 제20권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.

Development of Ship Vibration Analysis Software PFADS-R3 and Its Applications

  • Hong Suk-Yoon;Seo Seong-Hoon;Park Young-Ho;Lee Ho-Won
    • Journal of Ship and Ocean Technology
    • /
    • 제8권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.

저전력 임베디드 소프트웨어 개발을 위한 ADD 기반의 아키텍처 설계 기법 (A Technique of ADD-based Architecture Design for Low Power Embedded Software)

  • 이재욱;홍장의
    • 대한임베디드공학회논문지
    • /
    • 제8권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.

비용을 고려하고 아키텍처 평가를 지원하는 소프트웨어 아키텍처 비용 추정 기법 (A Software Architecture Cost Estimation Method to Support Architecture Evaluation with Consideration of Cost)

  • 조시호;이준하;박수용
    • 한국정보과학회논문지:소프트웨어및응용
    • /
    • 제37권2호
    • /
    • pp.95-103
    • /
    • 2010
  • 소프트웨어 제품의 시장 경쟁력을 향상시키기 위해서는 이해관계자의 요구사항에 부합하는 품질을 제공하는 동시에 개발 예산 내에 개발 가능한 아키텍처를 획득할 수 있는 방안이 요구된다. 하지만 아키텍처의 품질 검토 및 선정을 위해 사용되는 기존 아키텍처 평가 기법은 아키텍처 설계를 통해 획득 가능한 품질속성에만 초점을 맞추고 있어 아키텍처가 개발 비용에 미치는 영향을 체계적으로 고려하지 않는다. 본 논문에서는 소프트웨어 비용 추정 모델인 COCOMO II를 적용한 아키텍처 비용 추정 기법을 제안하여 기존 아키텍처 평가와 병행 가능한 비용 분석을 통해 기존 아키텍처 평가 기법을 보완하며 품질과 비용이 함께 고려된 아키텍처 선정을 지원한다. 제안 기법의 정확성 검증을 위해 본 논문의 기법을 RPS (Robot Patrol System)의 아키텍처 후보 목록에 적용한 뒤 비용 추정 결과를 각 아키텍처 후보의 실측 공수와 비교하였다.