• The KIPS Transactions:PartD
• /
• v.8D no.6
• /
• pp.747-752
• /
• 2001

UML is a standard language that models an analysis and design process in the development of an application system or components, CORBA, COM+, EJB and others are the techiniques that are realized reuse of components. After it is distinguished between reusable components and new components on the components development process and is developed, the developing cost of components or application system can be reduced and the components of superior in quality can be created. This paper defines the extended UML notation that needed in modeling of the products created from the development process of components. Also, this paper introduces a modeling of components and UML application method that needed in development of an auction system based on Web.

• The KIPS Transactions:PartD
• /
• v.9D no.1
• /
• pp.65-74
• /
• 2002

This paper focuses components interactions which is important factor in designing software components. We classified several types of interaction between components and suggested appropriate graphical notation to extend UML and design process with extended method. Suggested notation and process was verified by practical experiment which is performed in travel agent component application. Representing interaction between components is not same to representing association between classes. UML in current version needs to be extended for representing this kind of components interaction. This research covers UML extension for components interaction and experiment for showing effectiveness.

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

• Journal of Internet Computing and Services
• /
• v.3 no.3
• /
• pp.39-53
• /
• 2002

Since domain model affects largely on the development of object model and design decisions, this model is widely used in the object-oriented and component-based system development. Current $\infty$ methods and UML notation, however, do not support both engineering with reuse and engineering for reuse, This problem causes delay in project development time and inadequate domain model. The integration of extended UML notation and reuse process method can provide a solution to the reusability problem. In this paper, we designed UML based domain model template for the reuse of domain model and proposed domain model development method for the reuse of analysis information, In addition, it was possible to represent reusable domain model template in UML and to develope domain model in the internet sales domain.

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

Software architecture is the high level model of a software system. It should be specified with ADLs (Architecture Description Languages) for its clarity and preciseness. Most ADLs such as C2SADL have not come into extensive use in industries since ADL users should learn a distinct notation specific to architecture, and ADLs do not address all stakes of the development process that is becoming diversified everyday. 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. But, UML is a general modeling language and does not provide all concepts that are important to architecture description. UML should be extended in order to precisely model architecture. In this paper, we defined a C2 architecture modeling language as a UML2.0 profile. We applied the defined C2 architecture modeling language to the modeling of a restaurant reservation system.

• Proceedings of the CALSEC Conference
• /
• 2001.08a
• /
• pp.671-679
• /
• 2001

사례연구를 통하여 UML Component Design Process의 일관성 및 정확성을 검증한다. Business Concept Model과 Use Case Model을 이용하여 Component Specification Process의 산출물인 Interface, Component Specification 및 Component Architecture 작성 UML Notation을 확장해서 Component 명세에 적용하는 것이 올바른 것인지 확인한다. <>,<>,<>,<>,<>, <>:로 Component Specification이 충분한지를 확인 OCL을 이용하여 Component Specification 중 Component Specification, Interface Specification, Operation Specification, Constraint, Pre/Post Condition의 정의에 유용한지 확인(중략)

• Journal of Internet Computing and Services
• /
• v.4 no.4
• /
• pp.35-44
• /
• 2003

XML becomes the standard for exchanging documents and data on the Web. Schema is used to define XML documents. Among schema, XDR schema, developed chiefly by Microsoft, is a leading schema for practical use. UML is a notation in object-oriented software development and a useful tool to represent the structure of a system. In this paper, we study the transformation method and algorithm from XDR schema to UML diagram. By this transformation, the structure of XDR schema is represented graphically. Thus we can easily understand the structure of XDR schema and we can create XML documents effectively by enhancing reusability and flexibility.

• Journal of Convergence Society for SMB
• /
• v.4 no.4
• /
• pp.31-36
• /
• 2014

Recent advancement in Wireless Sensor Networks (WSNs) has paved the way for WSNs to enable in various environments in monitoring temperature, motion, sound, and vibration. These applications often include the detection of sensitive information from enemy movements in hostile areas or in locations of personnel in buildings. Due to characteristics of WSNs and dealing with sensitive information, wireless sensor nodes tend to be exposed to the enemy or in a hazard area, and security is a major concern in WSNs. Because WSNs pose unique challenges, traditional security techniques used in conventional networks cannot be applied directly, many researchers have developed various security protocols to fit into WSNs. To develop countermeasures of various attacks in WSNs, descriptions and analysis of current security attacks in the network layers must be developed by using a standard notation. However, there is no research paper describing and analyzing security models in WSNs by using a standard notation such as The Unified Modeling Language (UML). Using the UML helps security developers to understand security attacks and design secure WSNs. In this research, we provide standard models for security attacks by UML Sequence Diagrams to describe and analyze possible attacks in the three network layers.

• Journal of Internet Computing and Services
• /
• v.10 no.1
• /
• pp.175-182
• /
• 2009

Less efforts has been made in developing specifications and verification techniques for quality requirements. This paper suggests specification and traceability methods supporting quality issues such as usability, performance, and understandability when developing information systems with UML notation. With traceability checking methods that augment quality extension to the use cases and sequence diagrams, developers can confirm the level of implementation for both functional and nonfunctional requirements beforehand.

• The KIPS Transactions:PartD
• /
• v.16D no.6
• /
• pp.927-934
• /
• 2009

This paper presents a commonality and variability analysis method for UML CASE tool frameworks. Commonality and Variability analysis increase extension and reusability by separating common area and variable area. We suggest class category based on property and the notation to represent commonality and variability. It is also implements frameworks based on analysis method and verify method using defect removal efficiency.