• Title/Summary/Keyword: UML extension

Search Result 43, Processing Time 0.023 seconds

Extension of MARTE Profile for Model-based Power Consumption Analysis of Embedded Software with UML 2.0 (UML 2.0을 사용한 모델 기반의 임베디드 소프트웨어 소모 전력 분석을 위한 MARTE Profile의 확장)

  • Pyeon, Ho-Rim;Kim, Jong-Phil;Hong, Jang-Eui
    • Journal of KIISE:Software and Applications
    • /
    • v.37 no.4
    • /
    • pp.252-263
    • /
    • 2010
  • The needs of low-power embedded software are being increased. Along with the needs, the studies to predict the power consumption of embedded software are also being increased. Although existing studies for power analysis have been performed in source code-based, these code-based analysis have some shortages of long analysis time and much feedback efforts. Recently some studies of power analysis based on software models are prompted. This paper describes on the model-based approach using UML diagrams in embedded software development process. Specially we focus on the extension of OMG's MARTE Profile to support model-based analysis. The MARTE extension gives the possibility of power analysis using just UML diagrams without any other analysis model in embedded software development.

Multiple Perspective Business System Modeling Using Unified Modeling Language (Unified Modeling Language를 활용한 다관점 업무 시스템 모형화)

  • Kim, Jong-U;Kim, Jin-Sam;Jo, Jin-Hui;Jeon, Jin-Ok
    • The Transactions of the Korea Information Processing Society
    • /
    • v.6 no.9
    • /
    • pp.2373-2383
    • /
    • 1999
  • Recently, due to the popularity of object-oriented programming languages, object-oriented modeling and development methodologies become widely applied to information system development. When object-oriented methodology is adopted, using object-oriented modeling languages for business analysis and redesign has the advantages such that business modeling results can be easily understood and referred by information system developers. In this paper, UML-B, Unified Modeling Language extension for Business modeling is proposed, which uses UML notation for modeling organization structure, actors, use cases, business processes, and entities in business systems. It also utilizes extension mechanisms of UML to facilitate business modeling activities, and supports business process reengineering with object-oriented modeling.

  • PDF

UML Extension for Code Generation (코드 생성을 위한 UML 확장)

  • Hyunseok Min
    • Proceedings of the Korea Information Processing Society Conference
    • /
    • 2008.11a
    • /
    • pp.480-483
    • /
    • 2008
  • OMG 가 시작한 MDA(Model Driven Architecture) 는 소프트웨어 개발자들사이에 빠르게 전파되고 있다. UML 은 OMG 에 의해 MDA 를 위한 언어로 선택되었는데, UML 은 PIM(Platform Independent Model)에서 PSM(Platform Specific Model)을 생성하기에는 충분하지 않다. 하지만, 이러한 PIM-PSM 변환을 가능한한 자동화할수 있는데 이 논문은 자동 코드 생성을 위해 UML 의 확장 방법인 Stereotype 과 Tagged-Value 에 대해 논하게 된다. 또한, Aspect-Oriented 접근을 위해서 AOP 로 확장된 UML 에서 비 AOP 언어로 코드 생성이 가능하게 되는 새로운 방법도 제안을 한다.

Extension and Implementation of Iconic Stereotype for GNSS Application in the UML Class Diagram

  • Wang Bo;No, Hye-Min;Yoo, Cheol-Jung;Chang, Ok-Bae
    • Proceedings of the Korean Information Science Society Conference
    • /
    • 2003.04c
    • /
    • pp.136-138
    • /
    • 2003
  • UML cannot meet all the requirements offered in different software system for diverse application domain. GNSS (Global Navigation Satellite System) application domain is an especial environment that requires precise measurement and precision calculation of real-world geographical entities with the help of GPS (Global Position System) in both temporal and spatial factor. Therefore in the paper new extended iconic stereotypes for better modeling GNSS application in the UML Diagram are proposed, and the implementation of a program called StereotypeCreator, which is able to create iconic stereotypes used in one of the most popular visual modeling tools for software development, Rational Rose, will be also proposed.

  • PDF

UML-based Quality Requirement Specifications and Design Traceability (UML 기반의 품질 요구 표현 및 설계 추적성 연구)

  • Seo, Dong-Su
    • Journal of Internet Computing and Services
    • /
    • v.10 no.1
    • /
    • pp.175-182
    • /
    • 2009
  • Less efforts has been made in developing specifications and verification techniques for quality requirements. This paper suggests specification and traceability methods supporting quality issues such as usability, performance, and understandability when developing information systems with UML notation. With traceability checking methods that augment quality extension to the use cases and sequence diagrams, developers can confirm the level of implementation for both functional and nonfunctional requirements beforehand.

  • PDF

Extension of UML to Represent Components Interface Focusing on Interaction (상호작용 중심의 컴포넌트 인터페이스를 표현하기 위한 UML의 확장)

  • Park, Seong-Ho;Choe, Eun-Man
    • The KIPS Transactions:PartD
    • /
    • v.9D no.1
    • /
    • pp.65-74
    • /
    • 2002
  • This paper focuses components interactions which is important factor in designing software components. We classified several types of interaction between components and suggested appropriate graphical notation to extend UML and design process with extended method. Suggested notation and process was verified by practical experiment which is performed in travel agent component application. Representing interaction between components is not same to representing association between classes. UML in current version needs to be extended for representing this kind of components interaction. This research covers UML extension for components interaction and experiment for showing effectiveness.

UML 2.0 Profile for an Architecture Modeling (아키텍쳐 모델링을 위한 UML 2.0 프로파일)

  • 노성환;김경래;전태웅;승현우
    • Proceedings of the Korean Information Science Society Conference
    • /
    • 2004.10b
    • /
    • pp.412-414
    • /
    • 2004
  • UML을 기반으로 소프트웨어 아키텍쳐를 모델링 하기 위한 많은 연구가 진행되어 왔다. 특히 UML을 확장(extension)하여 UML이 지원하지 않는 핵심적인 아키텍쳐 개념을 명시적으로 표현하기 위한 노력이 진행되어 왔다. 그러나 기존의 대부분의 연구들은 UML1.x을 기반으로 한다 이에 비해 공식 발표될 예정인 UML2.0은 아키텍쳐 모델링에 관한 개념을 보다 많이 포함하고 있다. 하지만 UML2.0에도 명시적인 표현이 어려운 아키텍쳐의 핵심 개념들이 여전히 존재한다. 또한 UML2.0은 아키텍쳐 기술에 불필요하거나 관련이 적은 모델링 요소들도 많이 포함하고 있다 본 논문에서는 UML2.0에서 표현된 아키텍쳐 모델링 요소를 살펴보고, 아키텍쳐를 표현하기 위해서 UML2.0을 어떻게 아키텍쳐 기술 언어에 대한 프로파일로 확장하고 정의할 것인지를 고려한다.

  • PDF

A Study on Extension of Executable UML for Modeling Real-time Embedded Software (실시간 임베디드 소프트웨어 모델링을 위한 xUML 확장에 관한 연구)

  • Kim Woo-Yeol;Kim R. Young-Chul
    • Proceedings of the Korea Information Processing Society Conference
    • /
    • 2006.05a
    • /
    • pp.231-234
    • /
    • 2006
  • 현재까지는 실시간 임베디드 소프트웨어 개발을 위한 효율적인 소프트웨어 모델링 언어가 부족하다. 그런데 모델 자체가 코드처럼 수행 가능한 통합 모델링언어를 xUML(Executable UML)이라 한다[2,4,7]. 이는 기존의 UML x.x에 실행과 관련된 개념과 시간에 관련된 규칙을 더한 것이다. 다시 말해 xUML의 모델은 실행과 테스트, 디버깅이 가능하다[2,4]. 본 논문에서는 기존의 UML x.x버전들과 xUML이 실시간 임베디드 소프트웨어를 모델링 하는데 적합한지를 비교/분석한 후, 임베디드 소프트웨어 모델링에 xUML을 적용하고자 부족한 면을 보완 및 확장하였다. 확장된 xUML의 노테이션은 병렬과 실시간 처리까지도 표현이 가능하도록 제안하였다. 사례 연구로서 두개의 터치센서로 동작하는 실시간 임베디드 시스템의 모델링을 보여준다.

  • PDF

The Modification of UML for Developing of the Efficient Ontology (효율적인 온톨로지 개발을 위한 UML의 변경)

  • Kim, Young-Tae;Lim, Jae-Hyun;Kim, Chi-Su
    • Journal of the Korea Academia-Industrial cooperation Society
    • /
    • v.9 no.2
    • /
    • pp.415-421
    • /
    • 2008
  • The increasing interest in ontologies is driven by the large volumes of information now available as well as by the increasing complexity and diversity of this information. These trends have also increased interest in automating many activities that were traditionally performed manually. We are currently engaged in this paper that have realized benefits in productivity and clarity by utilizing UML class diagrams to develop and to display complex OWL ontologies. UML has many features, such as profiles, global modularity and extension mechanisms that are not generally available in most ontology languages. However, ontology languages have some features that UML does not support. Our paper identifies the similarities and differences between UML and the ontology languages RDF and OWL. To reconcile these differences, we propose a modification to the UML metamodel to address some of the most problematic differences.