• Journal of Information Technology and Architecture
• /
• v.9 no.2
• /
• pp.155-166
• /
• 2012

Recently EA(Enterprise Architecture) has been receiving growing attentions again from the public sectors. It is because EA maturity result is reflected to the organization's informatization level and EA maturity ratio has been enlarged. There has been more participation from the Chief Information Officers of the public sectors. EA research in the public sectors has influenced IT environment since the research started in late '90, the legislation work done in '05, and the maturity model developed in '06. However, there are some remaining tasks to solve. EA policy is introduction oriented, its contribution to the consecutive the best UN e-Government rank is limited, and its user-friendly responding system is still lacking. Related research outcomes are rather microscopic focusing only on the models and maturity than implicating on the public policy in a macroscopic manner. In this respect, this study will provide the implication on how EA policy should be. Requirements derived from EA stakeholders and the tasks will be arranged in accordance with its domain, then the performance and tasks will be demonstrated. As guiding EA stake holders and information related officers to setup the EA policy with these results, this study is expected to support information the policy drivers.

• Proceedings of the Korean Information Science Society Conference
• /
• 2002.10e
• /
• pp.190-192
• /
• 2002

EJB(Enterprise Java Bean)컨테이너에서 보안은 크게 사용자 인증과 빈의 메소드 호출에 대한 접근 제어로 구분된다. 기업이 가지고 운영 중인 다양한 보안 플랫폼 상에 EJB 컨테이너가 구동되기 때문에 EJB 컨테이너는 개별 보안 시스템과 독립적인 방법으로 빈에 대한접근 제어 방법을 정의하고 있다. 본 논문에서는 E504(Enterprise 504) EJB 컨테이너 시스템에서의 사용자 인증 및 접근 제어 방법에 대해 논의한다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2002.10c
• /
• pp.127-129
• /
• 2002

EJB(Enterprise Java Beans)는 웹 응용 서버 스펙인 J2EE(Java2 Enterprise Edition)의 핵심으로서, 비즈니스 로직을 컴포넌트 형태로 작성하여 재 사용성을 높이기 위한 서버 측 컴포넌트 프로그래밍 모델이다. EJB는 컴포넌트를 특성에 따라 일반적인 비즈니스 로직을 나타내는 세션 빈(Session Bean), 데이터베이스에 저장된 정보와 같은 여러 클라이언트에 의해 공유되며 영속 장치에 저장되는 엔터티 빈(Entity Bean) 그리고 JMS 메시지를 처리하는 메시지 드리븐 빈(Message-driven Bean)으로 구분한다. 본 논문에서는 ETRI에서 개발한 E504 EJB 서버에서 엔터티 빈의 데이터베이스 접근을 자동화 해주는 영속성 관리자(Persistence Manager)에 대해 논의한다.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.13 no.6
• /
• pp.1113-1120
• /
• 2010

In this paper, we have proposed Architecture Development methodology which can connect both operational view and system view. The Functional Architecture can connect both user and developer, and it is located between Activity analysis and System analysis. We suggest the new architecture methodology using the Functional Architecture and it provides effect to analyze the connection between user(military) and developer(enterprise) in Defence R&D and the new Architecture with the feedback analyze activity on a point of system view and the new architecture make the functional architecture.

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 2005.10a
• /
• pp.182-185
• /
• 2005

To survive in rapidly changing business environment, the enterprise should adapt its business process to the changing environment. The system integration is an important issue to tackle this challenge. It is unavoidable direction that SOA (Service Oriented Architecture) is accepted as an upcoming IT standard to support flexible business processes and integration. In this paper, SOA is introduced, and the Web services and ESB (Enterprise Service Bus) ate also introduced as a foundation technology to implement SOA-enabled solutions. The pilot project, which is introduced in this paper, will be a good reference for future SOA implementation.

• Proceedings of the Korea Association of Information Systems Conference
• /
• 2005.12a
• /
• pp.455-462
• /
• 2005

In order to succeed in today's changing business environment, the enterprise should adapt their process flexible. To increase their business process flexibility they need to establish and end-to-end integration internally as well as among partners. Now that SOA (Service Oriented Architecture) is accepted as an upcoming IT standard to support flexible business processes and integration. In this paper, SOA is introduced And the Web services and ESB (Enterprise Service Bus) are also introduced as a foundation technology to implement SOA-enabled solutions. The pilot project, which introduced in this paper, will be a good reference for future SOA study.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.30 no.4
• /
• pp.96-102
• /
• 2007

The most fundamental method in IT innovation up to today is the SOA which has been accepted as the standard for the system integration and makes the business more flexible. Although it is important to classify the workflow of enterprise into the unit of services, there is no systematical research on this topic yet. This paper proposes a SOA deployment methodology, which composed of 6 steps. By utilizing this methodology, an enterprise can build up the SOA applied environment easily to achieve its business objectives and to make a linkage between services and business processes more effectively and efficiently, which is proved through Analytic Hierarchy Process. It is considered that Service Oriented Architecture can be the future standard for the IT integration beyond the individual application.

• Journal of Information Technology Applications and Management
• /
• v.12 no.2
• /
• pp.107-128
• /
• 2005

Recently a new IT planning effort, Enterprise Architecture (EA), is being carried out by a number of organizations. According to many previous studies, this EA effort intrinsically differs from information systems planning (ISP). In practice, however, it is often performed just like ISP, pursuing identical objectives with just a few more modeling methods. It might lead to a misunderstanding that EA is no different from ISP. In an effort to clarify the difference, we investigate how these two planning efforts differ one from another in richness of architectural description. 19 RFP(request for proposal)s were empirically analyzed to see the difference between EA and ISP in terms of the richness of architectural description.

• 한국IT서비스학회:학술대회논문집
• /
• 2006.05a
• /
• pp.424-429
• /
• 2006

정부의 행정 서비스를 보다 효과적이고 효율적으로 제공하는 것은 정부혁신의 핵심키워드이다. 이를 위한 수단으로 정부 공공기관들은 전사적 아키텍처(Enterprise Architecture)를 적극적으로 도입, 활용해야 한다. 전사적 아키텍처란 아직까지도 진화중인 개념으로 해당 기관 정보화 업무의 전 영역을 업무 프로세스(Business Processes), 정보 흐름 및 관계(Information Flow and Relationships), 애플리케이션(Applications),데이터 명세 및 관계(Date Descriptions and Relationships), 그리고 기술 하부구조(Technology Infrastructure)로 구분 짓고 각각을 구조화된 산출물로 정리함으로써 공공정보화의 청사진을 제시한다. 이렇게 구축된 아키텍처 결과물은 기관 내 뿐 아니라 타 기관 EA와의 연계를 통해 상호 운용되어야 하며, 이 과정에서 어휘의미중의성(Word Sense Ambiguation)등 상호운용성 문제가 핵심 이슈로 대두되리라 예상된다. 공공분야로 한정짓더라도 200여 정부부처 EA간의 상호운용성 문제는 정부조직 간 경계를 넘어 통합된 EA정보를 취합, 활용하는 데 있어 가장 큰 장애요인이 되리라 예상된다. 본 논문에서는 온톨로지를 사용하여 각기 서로 다른 EA간 상호운용성 문제를 해결하는 방안에 대해 논의하고자 한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2008.05a
• /
• pp.316-319
• /
• 2008

국방 정보화 사업은 국방개혁 "2020"의 핵심인 작지만 강한 군대건설을 위해서 네트워크 중심의 개념 및 교리 발전, 각급 전장 요소에 정보기술 능력을 장착하여 지능화 및 정밀화, 전력요소 네트워크화를 충족 정보의 실시간 공유 및 광역 동시전파가 가능한 정보우위를 달성하기 위해 전사적 아키텍처(EA : Enterprise Architecture) 기반의 종합발전계획(Master Plan)을 수립 시행하고 있는 가운데, 국방 전장관리, 자원관리, 정보 통신망, 컴퓨터 체계, 정보보호, 정보화 환경 등에 국방EA 사업이 미치는 영향을 제시하고자 한다.