• Asia pacific journal of information systems
• /
• v.11 no.1
• /
• pp.117-137
• /
• 2001

B2B(business-to-business) commerce has become the prime driver of contemporary electronic commerce. Under B2B commerce, corporations often must operate across organizational boundaries to share their business processes. Workflow management was proposed by Aalst(4, 5) to support several business partners that are involved in shared workflow processes in B2B commerce. We designed a messaging system for B2B workflow, where heterogeneous workflow management systems on each organization for trade were integrated. Based on Aalst's example in(4, 5), we analyzed B2B workflow by using class diagram, use case diagram, activity diagram, and statechart diagram of UML, and designed the messaging system, We also demonstrated a prototype system which was implemented by using Java API and XML. To compare with a holistic system such as EDI systems, the messaging system allows the business partners in B2B commerce to communicate with each other by dedicated messages and integrate each B2B interoperable workflow without any restrictions.

• Journal of KIISE
• /
• v.42 no.11
• /
• pp.1410-1422
• /
• 2015

In order to design a system, software developers use an object model such as the UML class diagram. Object-Relational Transformation Methodology (ORTM) is a methodology to transform the relationships that are expressed in the object model into relational database tables, and it is applied for the implementation of the designed system. Previous ORTM studies have suggested a number of transformation methods to represent one relationship. However, there is an implementation problem that is difficult to apply because the usage criteria for each transformation method do not exist. Therefore, this paper proposes a binary decision diagram-based modeling rule for each relationship. Hence, we define the conditions for distinguishing the transformation methods. By measuring the query execution time, we also evaluate the modeling rules that are required for the verification. After evaluation, we re-define the final modeling rules which are represented by propositional logic, and show that our proposed modeling rules are useful for the implementation of the designed system through a case study.

• Journal of Digital Contents Society
• /
• v.8 no.3
• /
• pp.269-277
• /
• 2007

Web service is an important technology to develop business to business e-commerce application. From a business perspective of time to market, dynamic evolution offers flexibility that software can adapt to unforeseen and fluctuating business requirements. OWL-S, based on OWL, is a service ontology language. The semantics provided by OWL support automation of service discovery, invocation, and service composition. In this paper we propose a framework to support dynamic evolution of service-oriented applications. We extend use-case analysis method to derive service description by defining requirements concept and mapping from requirement concept to activity diagram. A prototype is provided to show the validity of this framework.

• Journal of the Korea Society of Computer and Information
• /
• v.16 no.11
• /
• pp.25-34
• /
• 2011

In this paper we present an integrated design methodology for relational database based on object-oriented analysis and design. The integrated design methodology is based on business profile and has six phases. In the first phase, business use cases are identified and described by macroactivity diagrams and then the macroactivity diagrams are transformed to detailed business activity diagrams by using objects, object flows and business worker's responsibilities. In the third phase, the detailed business activity diagrams are transformed to business class diagrams that describe the static structure of the entire business system based on detailed business activity diagrams. In the four phase, the business class diagrams are transformed to class diagrams that represent the initial conceptual model of the target relational database. In the five phase, we add additional transformations on the class diagrams with generalization and specialization of associations, roles, activities, additional classes and redundant associations. Eventually, the final class diagrams are transformed to relational database schema. The methodology presented in this paper by applying that proposal for organic connection between object-oriented analysis and design methodology and relational database design methodology. And it will be able to deal with integration management. By the integrated design methodology, we can make more easily software systems based on relational database. In the case study, proposal integrated design methodology applied for a visa issuing system.

• Proceedings of the KSR Conference
• /
• 2010.06a
• /
• pp.448-454
• /
• 2010

Currently a KTX train of 20-car formation is 388m long and carries 931 passengers including one captain and three crews which is quite a few to cover the lengthy service area and many customers. On the other hand, if a passenger wants to talk to an attendant, he has to wait for an attendant passing by his/her seat or walk to an intercom which is placed at every other car. Any of these choices is inconvenient. So, in this paper, we presented a system design for developing an audio/visual communication system for a passenger and an attendant. The system was analyzed and designed according to the Object-Oriented methodology with UML (Unified Modeling Language). Based on a problem statement, a Use-case Diagram, Sequence Diagrams, Class Diagram, State Charts, collaboration Diagram were generated. The design will be used in system implementation to a HEMU-400X test train and to be tested.

• Journal of KIISE:Software and Applications
• /
• v.33 no.1
• /
• pp.1-16
• /
• 2006

As the size of software is getting huge, it has been impossible for testers to test all of source coed. Therefore, the method which uses information of requirements for testing has been researched and accepted. Although there are a lot of test methods based on requirement specification, each method has a different approach and coverage. So we should consider their various approach and coverage in the stage of test planning. This paper presents the empirical comparison and the result by applying various black-box testing methods to software system. For this experiment we studied five black-box testing methods including UML based specification technique. We applied the five testing methods to application system and evaluated the coverage of extracted test case.

• Journal of Korea Society of Digital Industry and Information Management
• /
• v.7 no.3
• /
• pp.37-42
• /
• 2011

Nowadays software developers are moving from conventional software process technologies to the object-oriented paradigm. To develope the object-oriented softwares efficiently, various software metrics have been suggested. Coupling refers to the degree of independence between components of the system. It has long been well known that good software practice calls for minimizing coupling interaction. Many researches have been studied coupling metrics of the object- oriented systems. We review Chidamber and Kemerer's work & Li's work. In this paper, we study the coupling of the overall structures of object-oriented systems by analyzing the class diagram of UML. We propose four coupling metrics for object-oriented softwares. First, we use an established coupling metric for object- oriented systems as a basic coupling metric. Then we modify the basic coupling metric by including indirect coupling between classes, We also suggest two relative coupling metrics to measure coupling between subsystems. We investigate the theoretical soundness of the proposed metrics by the axioms of Briand et al. Finally, we apply the presented metrics to a practical case study. This coupling metric will be helpful to the software developers for their designing tasks by evaluating the coupling metric of the structures of object-oriented system and redesigning tasks of the system.

• The KIPS Transactions:PartD
• /
• v.10D no.3
• /
• pp.471-488
• /
• 2003

A web-based information system, that is a dominant type of information systems, suffers from the “web crisis” in development and maintenance of the system. To cope with the problem, a technology of reengineering to web-based business process, which is one of web engineering, is strongly needed. In this paper, we propose a BPN(Business Process Net) model and reengineering guides along with an application example, which are used for modeling web-based business processes and migrating to web-based information system. BPN model is a type of not only a Beta-distributed stochastics Petri net, but also an executable Activity diagram. BPN is modeled by using the Use Case analysis method and the Beta-distribution. The later is used for the purpose of modeling the uncertainty of execution time and cost of a business process. BPN model and reengineering heuristics might be used as a formal common model for business process specification languages, and analysis and design method for Web-based Information system, respectively.