• 한국IT서비스학회:학술대회논문집
• /
• 2006.11a
• /
• pp.170-176
• /
• 2006

B2B registries are information systems to registrate B2B related business information such as companies' profiles, business documents, business processes, services and to provide query facilities to find information about potential business partners. In this study, we focus on the design of the repository for B2B business processes. In this paper, a metadata ontology is designed to registrate B2B business processes. In practice, there are several competitive business process definition languages such as ebXML BPSS (Business Process Specification Schema), WSBPEL (Web Service Business Process Execution Language), BPMN (Business Process Modeling Notation), and so on. In order to registrate business processes based on different representation frameworks, the proposed metadata ontology consist of three layers, common metadata, language-specific metadata, and interrelationship metadata. To implement the proposed metadata ontology using ebXML registry, metadata mapping scheme to ebRIM (ebXML Registry Information Model) are also suggested.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.13 no.3
• /
• pp.1702-1721
• /
• 2019

A workflow process (or business process) management system helps to define, execute, monitor and manage workflow models deployed on a workflow-supported enterprise, and the system is compartmentalized into a modeling subsystem and an enacting subsystem, in general. The modeling subsystem's functionality is to discover and analyze workflow models via a theoretical modeling methodology like ICN, to graphically define them via a graphical representation notation like BPMN, and to systematically deploy those graphically defined models onto the enacting subsystem by transforming into their textual models represented by a standardized workflow process definition language like XPDL. Before deploying those defined workflow models, it is very important to inspect its syntactical correctness as well as its structural properness to minimize the loss of effectiveness and the depreciation of efficiency in managing the corresponding workflow models. In this paper, we are particularly interested in verifying very large-scale and massively parallel workflow models, and so we need a sophisticated analyzer to automatically analyze those specialized and complex styles of workflow models. One of the sophisticated analyzers devised in this paper is able to analyze not only the structural complexity but also the data-sequence complexity, especially. The structural complexity is based upon combinational usages of those control-structure constructs such as subprocesses, exclusive-OR, parallel-AND and iterative-LOOP primitives with preserving matched pairing and proper nesting properties, whereas the data-sequence complexity is based upon combinational usages of those relevant data repositories such as data definition sequences and data use sequences. Through the devised and implemented analyzer in this paper, we are able eventually to achieve the systematic verifications of the syntactical correctness as well as the effective validation of the structural properness on those complicate and large-scale styles of workflow models. As an experimental study, we apply the implemented analyzer to an exemplary large-scale and massively parallel workflow process model, the Large Bank Transaction Workflow Process Model, and show the structural complexity analysis results via a series of operational screens captured from the implemented analyzer.

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

• The KIPS Transactions:PartD
• /
• v.14D no.4 s.114
• /
• pp.435-446
• /
• 2007

B2B registries are information systems to register B2B related business information such as companies' profiles, business documents, business processes, and services and to provide query facilities to find information about potential business partners. Focusing on the design of the registry for B2B business processes, in this paper, a metadata ontology is designed to register B2B business processes. In practice, there are several competitive business process definition languages such as ebXML BPSS (Business Process Specification Schema), WSBPEL (Web Service Business Process Execution Language), BPMN (Business Process Modeling Notation), and so on. In order to register heterogeneous business processes based on different representation frameworks, the proposed metadata ontology consists of three layers, common metadata, language-specific metadata, and interrelationship metadata. To show the usefulness of the proposed metadata ontology, two examples which are represented by ebXML BPSS and WSBPEL respectively are described in order to show how the proposed metadata ontology is used to registry B2B business processes. To implement the proposed metadata ontology using ebXML registry, metadata mapping scheme to ebRIM (ebXML Registry Information Model) is also suggested.

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 2006.05a
• /
• pp.226-234
• /
• 2006

기업 활동의 근간을 이루는 비즈니스 프로세스들을 투명하게 관리하고 통제하기 위해 국내외 많은 기업들이 비즈니스 프로세스 관리(BPM: Business Process Management) 시스템을 도입하고 있다. 본 논문에서는 프로세스 모델링 및 표기법 측면에서 BPMN(Business Process Modeling and Notation), 프로세스 실행과 운영 측면에서 BPEL(Business Process Execution Language), 모니터링과 통제 측면에서 BPQL(Business Process Query Language)을 표준의 개요와 표준화 현황을 제시하였다. 또한, BPM 솔루션 공급업체들의 유형을 분류해 보고, 각 공급업체 유형별 장단점 분석을 기초로 BPM 표준을 자사 솔루션 개발에 적용하고자 하는 기업들에게 유용한 표준 도입 전략을 제시하였다.

• TTA Journal
• /
• s.88
• /
• pp.105-120
• /
• 2003

본 논문은 워크플로우 기술의 표준화 및 기술 동향을 소개하는 세 번의 연재* 중 그 세 번째인 마지막 내용으로 지난 호에서 소개한 비즈니스 프로세스 관리(Business Process Management: BPM) 기술과 이의 기반기술인 워크플로우 관리기술과 연관된 국내외 표준화 기구와 그들의 활동 내용에 관하여 기술한다. 특히, 비즈니스 프로세스 관리 기술의 국제표준화 기구인 BPMI(Business Process Management Initiative)와 워크플로우 관리 기술의 국제표준화 기구인 WfMC(Workflow Management Coalition)는 최근에 웹서비스나 B2B 기술 등의 비즈니스 프로세스 관련 단일화된 표준안을 개발하고자 여러 번에 걸친 합동회의를 개최해오고 있어 이 합동회의에서 진행되고 있는 표준안 개발 활동 내용을 소개한다. 특히, 워크플로우 모델링 표준 언어인 XPDL(XML Process Definition Language)과 비즈니스 프로세스 모델링 언어인 BPMN(Business Process Modeling Notation) 그리고 대표적인 워크플로우 모델로서 연구분야에서 많이 이용되고 있는 ICN(Information Control Net)을 확장한 Kyonggi-ICN의 상호 매핑관계를 요약정리한다. 끝으로, 현재 국내의 워크플로우 기술관련 표준화기구인 한국정보통신기술협회 산하 표준화위원회인 워크플로우기술연구반의 표준화 활동과 이번에 새로이 정보통신부 표준화전략포럼중의 하나로 창립된 워크플로우 및 비즈니스 응용기술포럼(약칭 WABA 포럼: Workflow and Business Applications Technology Forum)을 소개한다.

• Journal of Information Technology Services
• /
• v.5 no.2
• /
• pp.107-123
• /
• 2006

The objectives of this study is to develop a strategy for the adoption of BPM(Business Process Management) standards and an implementation guideline of the BPM standard for BPM solution developers focusing on BPEL(Business Process Execution Language) which is regarded as the most important BPM standard. In the heterogeneous and distributed IT environments, every type of enterprise software requires standards to enhance interoperability. BPMS(Business Process Management System), which is a type of enterprise software requires BPM standards such as BPEL(Business Process Execution Language), BPMN(Business Process Modeling and Notation), BPQL(Business Process Query Language) and so on to achieve multi-system interoperability and component interoperability with their BPM solutions. It is quite helpful to provide the adoption strategy concerning BPM standards for each type of BPM solution vendors who need the BPM standards. Since the BPEL is conceived as the most important BPM standard and widely adopted by many BPM vendors, we have proposed a reference architecture for BPEL implementation and also developed the detail implementation guideline of core components of the BPM system supporting the BPEL standard. Using the strategy and implementation guideline proposed in this work, BPM solution vendors can establish their own standard adoption strategy and they can also develop their BPM solutions supporting the BPM standards more efficiently.

• Journal of the Korea Institute of Building Construction
• /
• v.12 no.3
• /
• pp.299-314
• /
• 2012

One of reasons for introducing Building Information Modeling (BIM) is to support clash detection tasks by means of a 3D product model. In the conventional construction project process, clashes have been found during construction phase. However, it can cause cost overrun and time delay. In order to investigate and correct clash detections at design phase, relevant business process and guide for this task should be provided. This study aims to identify hindrances in clash detection tasks at the design phase and analyze its current process using IDEF0 model. Despite the convenience of IDEF0 as a systems analysis tool, professional participants might have difficulties to understand their own tasks according to business process. For this reason, in this research, Business Process Model and Notation (BPMN) is introduced to provide ideal process and required decision making governance. The provide BPMN model will provide insights for a BIM-based collaborative environment to enhance the constructability through the construction project.

• The KIPS Transactions:PartD
• /
• v.16D no.2
• /
• pp.223-236
• /
• 2009

BPMN is a standard business process description notation developed by OMG. It allows the user to have an abstract view of a process that hides its details with the Collapsed Sub-Process notation. While it is a useful direction of abstraction that can be called the horizontal abstraction, a different kind of abstraction, the vertical abstraction, is necessary when different stakeholders of business would like to have different views of the business process form their own viewpoints of interest. For example, stakeholders may want to see a process from the viewpoint of a particular group of actors or from the viewpoint of a certain set of goals. This paper first extends horizontal abstraction capability of BPMN by introducing the notion of super edge and, moreover, adds the vertical abstraction capability to it by introducing the notions of 'aspect attribute' and 'interest specification' and notations for them.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.11 no.2
• /
• pp.1217-1233
• /
• 2017

Effective monitoring and testing during each step are essential for document verification in research and development (R&D) projects. In software development, proper testing is required to verify it carefully and constantly because of the invisibility features of software. However, not enough studies on test processes for R&D projects have been done. Thus, in this paper, we introduce a Test Maturity Model integration (TMMi)-based software field R&D test process that offers five integrity levels and makes the process compatible for different types of projects. The Software & Systems Process Engineering Metamodel (SPEM) is used widely in the software process-modeling context, but it lacks built-in enactment capabilities, so there is no tool or process engine that enables one to execute the process models described in SPEM. Business Process Model and Notation (BPMN)-based workflow engines can be a solution for process execution, but process models described in SPEM need to be converted to BPMN models. Thus, we propose an approach to support enactment of SPEM-based process models by converting them into business processes. We show the effectiveness of our approach through converting software R&D test processes specified in SPEM in a case study.