• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.31 no.3
• /
• pp.80-89
• /
• 2008

Because of different hardware specifications, there are no unified protocol commands to use with various kinds of RFID readers. The current commercial RFID middlewares do not satisfy the various requirements from users to support business process logic representation. The EPCglobal, which is leading organization for the RFID research, suggested a RFID middleware architecture which is called ALE(Application Level Events) standard. However, their architecture also does not provide the application level's interfaces. Therefore, a new RFID middleware architecture is required to provide basic RFID functions, conform to ALE's specification and, additionally, support application level's business logic representation. This paper proposes a ALE-based RFID middleware architecture which provides business process logic representation. At first, the basic RFID control functionalities are identified. Secondly, the business process logic requirements in RFID applications are identified and classified Into six categories. Third, the Middelware architecture is implemented with Java and XML technology so that it can easily extended to support the various RFID hardware's protocols. Finally, an example RFID prototype system is developed to show the proposed architecture's feasibility and validate it. The proposed middleware is expected to be used In various application areas since it is using XML technology for easy adaptation and it also con- forms to ALE interface which is standard specification.

• Journal of KIISE:Software and Applications
• /
• v.31 no.3
• /
• pp.255-266
• /
• 2004

In the Web-based information systems, separating the business process logic from the data and presentation logic brings about a wide range of advantages. However, this separation is not easily achieved; even the data logic may be not separated from the presentation layer. So, it requires to define an model for business processes, and then to map the model into the user's dynamic interface using the logic separating strategy. This paper presents a stylesheet method to recognize the process by extending XSLT (Extensible Stylesheet Language Transformations), in order to achieve the logic separation. To do this, it provides an specification of the business process, and a scheme that extracts business model factors and their interactions using a Petri-net notation to show the business model into the process point of view. This is an attempt to separate users' interaction from the business process, that is, dynamic components of interaction Web document from the process structure of Web applications. Our architecture consist mainly of an XSLT controller that is extended by a process control component. The XSLT controller is responsible for receiving the user requests and searching the relevant templet rule related to different user requests one by one. Separation of concerns facilities the development of service-oriented Web sites by making if modular. As a result, the development of service-oriented Web sites would be very easy, and can be changed without affecting the other modules, by virtue of the modularization concept. So, it is easy to develop and maintain the Web applications in independent manner.

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 2003.05a
• /
• pp.1142-1149
• /
• 2003

Various organizational factors effect successful implementation of IT enabled business transformation. Among them, the most critical success factor is deemed to overcoming change management problem. Lots of studies have been made on Implementation methodologies and business process formalizations to encourage organizational members to accept new business process changes. However, the logic or process redesign still depends on qualitative problem solving techniques mostly depending on basically human intuition such as brainstorming. cause-and-effect analysis. and so on. In this paper, we focused on developing analytic framework to design to-be business process structure. which can complement qualitative problem solving procedures. With effective use of IT as an enabler, we provide algorithmic framework applicable to designing various business process changes such as process automation, business process resequencing, and more radical process integration. The framework follows dynamic programming approach in the literature, which is based on the decision making paradigm of organizations to abstract business processes as quantitative decision models. As such, our research ran fill the gap of limited development of theory based analytic methodologies for business process design, by providing objective rationale to reach the consensus among the organizational members including senior management.

• The KIPS Transactions:PartD
• /
• v.14D no.1 s.111
• /
• pp.97-106
• /
• 2007

In this paper, the business process was easily modeled by distinguishing between the business process and work logic. Based on this model, B2Bi collaboration Workflow modeling tool, which facilitates collaboration, was designed and implemented. The collaboration workflow modeling tool consists of 3 components; business process modeling tool, execution engine and monitoring tool. First, a business process modeling tool is used to build a process map that reflects the business logic of an application in a quick and accurate manner. Second an execution engine provides a real-time execution environment for business process instance. Third, a monitoring tool provides a real-time monitoring function for the business process that is in operation at the time. In addition to this, it supports flexibility and expandability based on XML and J2EE for the linkage with the legacy system that was used previously, and suggests a solution for a new corporate strategy and operation.

• Management Science and Financial Engineering
• /
• v.9 no.2
• /
• pp.21-45
• /
• 2003

Various organizational factors effect successful implementation of IT enabled business transformation. Among them, the most critical success factor is deemed to overcoming change management problem. Lots of studies have been made on implementation methodologies and business process formalizations to encourage organizational members to accept new business process changes. However, the logic of process redesign still depends on qualitative problem solving techniques mostly depending on basically human intuition such as brainstorming, cause-and-effect analysis, and so on. In this paper, we develop algorithmic procedure applicable to designing various business process changes such as process automation, business process resequencing, and more radical process integration. The framework is employed from dynamic programming approach in the literature, which is based on the decision making paradigm of organizations to abstract business processes as quantitative decision models. As such, our research can fill the gap of limited development of theory based analytic methodologies for business process design, by providing objective rationale to reach the consensus among the organizational members including senior management.

• ETRI Journal
• /
• v.42 no.3
• /
• pp.433-445
• /
• 2020

A denial-of-service (DoS) attack is a serious attack that targets web applications. According to Imperva, DoS attacks in the application layer comprise 60% of all the DoS attacks. Nowadays, attacks have grown into application- and business-layer attacks, and vulnerability-analysis tools are unable to detect business-layer vulnerabilities (logic-related vulnerabilities). This paper presents the business-layer dynamic application security tester (BLDAST) as a dynamic, black-box vulnerability-analysis approach to identify the business-logic vulnerabilities of a web application against DoS attacks. BLDAST evaluates the resiliency of web applications by detecting vulnerable business processes. The evaluation of six widely used web applications shows that BLDAST can detect the vulnerabilities with 100% accuracy. BLDAST detected 30 vulnerabilities in the selected web applications; more than half of the detected vulnerabilities were new and unknown. Furthermore, the precision of BLDAST for detecting the business processes is shown to be 94%, while the generated user navigation graph is improved by 62.8% because of the detection of similar web pages.

• The Journal of the Korea Contents Association
• /
• v.9 no.5
• /
• pp.61-75
• /
• 2009

Generally, the development of the database application includes the requirement analysis phase of creating ERD (Entity Relationship Diagram) and process models, coding, and testing. From the above phases, the analysis phase is not most formalized. It is usually hard task because (1) customers don't know the details of the desired system; (2) developers can't with ease understand the business logic of the customers; (3) the outcomes of the analysis, which are ERD and process models, are not easy to understand to the customers. This paper propose that the executional forms, which are better to understand the systems, should be presented to the customers instead of the ERD. These forms should accept the data input so that customers can review the various aspects of the outcome models. The developers should be able to instantly implement the business logic and also should be able to visually demonstrate the logic in order to get the details of it. For this goal, the customer supplied business logic should be able to be implemented by the references between forms, actions, constraints from the perspective of the data flow. The customers try to execute the forms implementing the business logic and review their supplied logic find new necessary business logic of their own. Iterating these processes for the requirement analysis would result in the success of the analysis which is sufficiently detailed without conflicts.

• Journal of Korean Institute of Industrial Engineers
• /
• v.27 no.1
• /
• pp.37-46
• /
• 2001

Business process(workflow) analysis has been recognized as a core step to building information systems. However, most analysts have recognized that deriving consistent business process artifacts even in a simple business domain is very difficult, since most analysis methods give the designers narrative and/or diagrammatic tools that do not support rigorous analysis rules. This often generates inconsistent analysis results, leading to create useless information systems and resulting in tremendous budget wastes. To overcome this weakness, this paper presents a declarative business process modeling method called contract-collaboration net(cc-net), which is not only somewhat formal but also useful to the practitioners. A case study on bank domain is presented to illustrate our approach.

• Proceedings of the Korean Information Science Society Conference
• /
• 2005.11b
• /
• pp.205-207
• /
• 2005

최근 수많은 정보를 통해서 증명 되듯이 비즈니스 프로세스 관리(Business Process Management, BPM)는 기업의 소프트웨어 시장의 가장 중요한 부분을 차지하고 있다. 비즈니스 프로세스 관리는 프로세스 전 라이프 사이클을 지원하고자 하는 개념으로 급변하는 경영 환경의 변화에서 기업의 경쟁력을 재고 하기위하여 필요로 되는 새로운 기업 컴퓨팅 패러다임이다. 비즈니스 프로세스 관리의 핵심적인 정보시스템 역할을 수행하는 워크플로우(Workflow)에서의 스케줄링은 정확한 업무 순서를 명세하기 위한 시간적인 제약들에 집중되어 있다. 워크플로우와 BPM과 같은 비즈니스 프로세스에서의 또 하나의 중요한 측면은 자원할당관리이다. 현재 대부분 다양한 자원들을 모델링하는데 초점을 맞추어 왔으며 자원들과 연관된 제약에서의 스케줄링에 대한 관심은 많지 않은 편이었다. 본 논문에서는 First Order Logic 기반의 CTR(Concurrent Transaction Logic)을 이용하여 각 비즈니스 프로세스 스케줄링을 위한 자원할당에 따른 제약들을 논리적인 모형으로 구체화하고, 모형에 필요한 변환 규칙을 소개하고자 한다.

• The KIPS Transactions:PartD
• /
• v.11D no.7 s.96
• /
• pp.1477-1482
• /
• 2004

Software development process consists of five phases : requirement, analysis, design, implementation and testing. There is almost always a gap between the system design and implementation stages, caused by a combination of the difficulty of programming and frequent changes on the system design. The goal of this paper is to reduce the gap between system design and implementation, and we design a tool producing a application program by recognizing business logic for a more rapid and flexible developing of software. The core idea of Application Program Generator is : firstly, to recognize that business application in the same domain share business logic and presentation logic : secondly, to treat system design as persistent meta-data ; thirdly, to use the persistent meta-data to build or customize applications as required.