• KSCE Journal of Civil and Environmental Engineering Research
• /
• v.29 no.2D
• /
• pp.175-181
• /
• 2009

Korean government has developed the 1st version of the National ITS Architecture in 1999 and utilized it as the framework for ITS planning, design, and standardization. The National Architecture now needs to be revised to accommodate environmental changes in ITS market and advancement of ITS core technologies. This study evaluates the current version of the architecture and suggests the directions for revision for a new national ITS architecture. The two most popular methodologies for architecture development-the process-oriented approach and the object-oriented approach-were reviewed, and the process-oriented approach was selected for new architecture development. The concept of the national architecture was then newly defined based on evaluation of the existing architecture. The new National ITS Architecture is suggested to be composed of ITS user services, logical architecture, physical architecture, and project architecture. This study must be followed by actual architecture development efforts and supporting policy actions for successful deployment of the new National ITS Architecture.

• Proceedings of the KOR-KST Conference
• /
• 1998.10a
• /
• pp.181-190
• /
• 1998

시스템 아키텍쳐는 시스템의 가장 상위수준 개념이다. 이러한 아키텍쳐의 정립이 1997년 8월에 완료된 2수준 아키텍쳐에 이어 3, 4수준 아키텍쳐가 연구되었다. 본 연구는 그중 고속도로교통관리시스템(FTMS)에 관한 것을 제시한다. 제 3수준 아키텍쳐는 2수준 아키텍쳐를 서비스 구현단위로 분해한 서브시스템이며, 다양한 ITS 서비스를 '제품(Package)'화 하여 ITS 서비스를 선택적, 점진적으로 구현 가능케 하였다. 제 4수준 아키텍쳐는 물리아키텍쳐 개념을 도입하여 3수준에서 분해된 서브시스템을 구성하는 각종 물리적 요소를 정의하고, 이들 간의 또는 외부요소와의 정보흐름을 정의하였다. 이에 따라, FTMS는 고속도로 교통관리 서브시스템, 고속도로 교통류제어/연계 서브시스템, 고속도로 돌발상황관리 서브시스템으로 분해/정의되었다.

• Proceedings of the Korean Association of Geographic Inforamtion Studies Conference
• /
• 2004.03a
• /
• pp.71-75
• /
• 2004

텔레매틱스 서비스를 통합적이고 원활하게 제공하기 위해서는 개별 시스템 구성 요소들 간의 연관관계를 규정하는 아키텍쳐의 수립이 필요하다. 현재 부분적, 개별적으로 연구 및 개발되고 있는 여러 시스템들의 기반이 되는 프레임워크(framework)로서의 텔레매틱스 아키텍쳐는 서비스가 활성화되기 전에 구축되는 것이 바람직하다. 본 논문에서는 외국의 국가 수준의 텔레매틱스 아키텍쳐의 구축 사례와 인접 분야인 ITS 분야의 국가 아키텍쳐를 고찰하여 텔레매틱스 아키텍쳐 구축을 위한 기본 방향을 제시하고자 한다. 본 논문은 총 4장으로 구성되었으며, 제1장 서론에 이어 제2장에서는 핀란드의 국가 텔레매틱스 아키텍쳐와 우리나라의 국가 ITS 아키텍쳐를 고찰하였다. 제3장에서는 제2장의 사례 고찰을 통하여 우리 나라의 텔레매틱스 아키텍쳐 구축 기본 방향을 제시하고 제4장에서 텔레매틱스 아키텍쳐 구축의 기대 효과와 향후 연구를 언급함으로써 결론을 맺었다.

• Journal of Korean Society of Transportation
• /
• v.19 no.6
• /
• pp.19-31
• /
• 2001

In this paper, 3 layered architecture model and related design guidelines are proposed, which have been actually applied in our national ITS-Architecture design. The domain architecture as the 1st layer is to structure all ITS related domains for maximizing the co-operability in national level. The logical architecture as the 2nd layer is to structure all ITS related application-systems for minimizing duplications, conflicts and dead-zones in service level and maximizing the co-operability in application-system level. The physical architecture as the 3rd layer is to structure all IT(Information Technology) related physical resources for maximizing.

• 한국ITS학회:학술대회논문집
• /
• 2003.11a
• /
• pp.257-261
• /
• 2003

• 한국ITS학회:학술대회논문집
• /
• 2003.11a
• /
• pp.269-274
• /
• 2003

• Journal of the Society of Disaster Information
• /
• v.12 no.1
• /
• pp.105-115
• /
• 2016

The purpose of this study is to present in-vehicle dynamic route guidance systems based upon object-oriented ITS LSA. We expect to apply efficiently for connection and expansion of systems what is more to present systems based upon object-oriented of the other ITS LSA.

• Journal of KIISE:Software and Applications
• /
• v.29 no.5
• /
• pp.295-310
• /
• 2002

Software architecture representing a common high-level abstraction of a system can be used as a basis for creating mutual understanding among all stakeholders of the system. In determining a software architecture's fitness with respect to its desired qualities as well as in improving a software architecture, software architecture evaluation is importantly performed. However moat of architecture evaluation methods are not still sufficient in that they do not explicitly consider artifacts discussed during architecture evaluation and their processes are net systematic. As a result, we are hard to follow them. To address these problems, this paper presents the method to evaluate systematically a software architecture with respect to its desired qualities. In this approach, the functional and non-functional requirements are separately handled, and software architecture is represented in the 4+1 view model using UML. Through this initial consideration, the important artifacts such as goals, scope, and target of evaluation are clearly determined. Also, the method provides the well defined process to produce the important evaluation artifacts such as sub-designs, design decisions, rationale, qualities from inputs. In addition, it enables us to determine satisfaction of a architecture with respect its desired qualities or improve a architecture through the structured evaluation results.

• Journal of KIISE:Software and Applications
• /
• v.28 no.7
• /
• pp.478-492
• /
• 2001

본 논문은 다양한 종류의 분산 인공지능 문제들을 에이전트라는 추상적 단위와 에이전트간의 상호작용을 토대로 해결하는 다중 에이전트 시스템을 개발하는 체계적 접근방법으로서 개발 방법론의 핵심인 아키텍쳐의 개발방법을 제안한다. 목표를 기반으로 문제영역을 이해하고, 여기에서 추출된 에이전트들을 이용하여 시스템을 개발함에 있어 지침이 되는 아키텍쳐 개발공정을 다중 에이전트 시스템의 특성인 조정과 자율성을 고려하여 제안한다. 각 관점마다 적용될 수 있는 아키텍쳐 스타일과 패턴들을 정의하고, 제안한 아키텍쳐를 UML(Unified Modeling Language)을 이용하여 표현하며, 아키텍쳐를 설명하는 ADL(Architecture Description Language)을 이용하여 정형화시킨다. 또한, 이를 지능형 교통시스템의 출발전 교통정보 안내 서브시스템에 적용, 구현함으로써, 제안하는 아키텍쳐를 검증해 보고, 이를 기반으로 소프트웨어를 개발하는 기초를 마련한다.

• Journal of KIISE:Software and Applications
• /
• v.33 no.2
• /
• pp.167-185
• /
• 2006

Software architecture, which is the high level model of a software system, should be specified with ADLs (Architecture Description Languages) for its clarity and preciseness. Most of ADLs such as ACME, however, have not come into extensive use in industries since ADL users should learn a distinct notation specific to architecture. On the other hand, UML is a do facto standard general modeling language for software developments. UML provides a consistent notation and various supporting tools during the whole software development cycle. UML, being a general modeling language, does not provide all concepts that are important to architecture description. UML should be extended in order to precisely model architecture. A number of researches on architecture modeling based on WML have been progressed. Ail of them, however, are based on the UML1.x. UML2.0 embraces much more concepts that are important to architecture modeling than UML1.x. In this paper. we defined an architecture modeling language based on UML2.0. We defined Generic ADL by extending UML2.0 and applied the defined Generic ADL to a restaurant reservation system.