• Journal of Internet Computing and Services
• /
• v.12 no.1
• /
• pp.119-130
• /
• 2011

As a de facto standard for system modeling, UML diagrams have been widely used in the industry. Of these, the class diagram is useful to visualize the classes and their relationships and thus directly influences the forward and reverse processes of system modeling and development. Many earlier studies have attempted to examine as to what impact the layout and complexity of the class diagram would have on the comprehension of system modeling. However, their findings have been equivocal and it is not easy to understand the effects of diagram layout. Accordingly this research relied on the guidelines of diagram layout suggested in the earlier studies and designed a 2 (layout) x 2 (complexity) factorial design to examine their impact on diagram comprehension. 47 subjects were participated in the experiment where class diagrams were provided differently in their layout and complexity. We found that a good layout was significantly more effective than the bad. Furthermore the results were significantly persistent in the complex group than the simple. However, there was no interaction effect between layout and complexity of the diagram.

• The KIPS Transactions:PartD
• /
• v.16D no.4
• /
• pp.527-540
• /
• 2009

State diagrams describe the dynamic behavior of an individual object as a number of states and transitions between these states. In this paper, we propose an automated technique to the generation of a state diagram from class operations with pre/post conditions. And I also develop a supporting tool, SDAG (State Diagram Automatic Generation tool). Additionally, we propose a complexity metric and a state diagram generation approach concerning types of each operation for decreasing complexity of generated state diagram.

• Journal of the Korean Institute of Intelligent Systems
• /
• v.14 no.6
• /
• pp.793-799
• /
• 2004

Many researches and validations for the complexity metrics of the object-oriented systems have been studied. Most of them are aimed for the measurement of the partial aspects of the systems, for example, the coupling between objects, the complexity of inheritance structures, the cohesion of methods, and so on. But the software practitioners want to measure the complexity of overall system, not partial. We studied the complexity of the overall structures of object-oriented systems by analyzing the class diagram of UML. The class diagram is composed of classes and their relations. There are three kinds of relations, association, generalization, and aggregation, which are making the structure of object-oriented systems to be difficult to understand. We proposed a heuristic metric to measure the complexity of object-oriented systems by putting together the three kinds of the relations. This metric will be helpful to the software developers for their designing tasks by evaluating the complexity of the structures of object-oriented system and redesigning tasks of the system.

• Journal of the Korean Institute of Intelligent Systems
• /
• v.15 no.6
• /
• pp.780-787
• /
• 2005

Many researches and validations for the complexity metrics of the object-oriented systems have been studied. Most of them are aimed for the measurement of the partial aspects of the systems, for example, the coupling between objects, the complexity of inheritance structures, the cohesion of methods, and so on. But the software practitioners want to measure the complexity of overall system, not partial. We studied the complexity of the overall structures of object-oriented systems by analyzing the class diagram of UML. The class diagram is composed of classes and their relations. There are three kinds of relations, association, generalization, and aggregation, which are making the structure of object-oriented systems to be difficult to understand. We proposed a heuristic metric to measure the complexity of object-oriented systems by putting together the three kinds of the relations. Tn analyze the complexity of the structure of a object-oriented system for the maintainability of the system, we measured the degree of understandability of it, the reverse engineering time to draw a class diagram from the source codes, and the number of errors in the diagram. The results of this experiment shows that our proposed metric has a considerable relationship with the complexity of object-oriented systems. The metric will be helpful to the software developers for their designing tasks by evaluating the complexity of the structures of object-oriented systems and redesigning tasks , of them for the future maintainability.

• KIPS Transactions on Software and Data Engineering
• /
• v.2 no.1
• /
• pp.19-26
• /
• 2013

To improve the reliability and quality of software system, many studies of the testing based on state-transition diagram have been in progress. Existing studies tried to solve the complexity problem of state-transition diagram. But the development of test case demands the better way to derive and manage the state diagram with low complexity. In this paper, the STMT(State-Transition Mapping Tree) is proposed to decrease the complexity of state diagram without changing or loosing the original state or transition information. Comparing with other methods, the proposed method turns out to be less complex.

• Proceedings of the Korea Society of Information Technology Applications Conference
• /
• 2007.05a
• /
• pp.55-68
• /
• 2007

디자인 패턴은 새롭게 만들어 지는 것이 아니라 기존의 검증된 지식, 관용법, 원칙들을 체계화한 것이다. 다시 말하면 디자인 패턴은 특정한 문제를 해결하기 위한, 검증된 설계 방법에 이름을 붙인 것이다. 그러므로 적절한 디자인 패턴 사용은 1) 개발자들간의 원활한 의사소통에 도움을 주며, 2) 하급자가 고급기술을 쉽게 익힐 수 있도록 할 수 있다. 3) 또한 사용된 디자인이나 아키텍처를 재사용할 수 있도록 하고, 4) 만들어진 시스템의 유지 보수를 보다 쉽게 할 수 있는 등의 장점을 얻을 수 있다. 반면에 필요하지 않은 곳에 까지 디자인패턴을 사용하게 되면 소프트웨어를 복잡하고, 유지보수도 어렵게 만들 수 있다. 디자인 패턴의 분류는 수 많은 패턴을 비슷한 속성을 지닌 그룹들로 조직화 하는 것이다. 이는 개발자가 특정 문제에 맞는 디자인 패턴을 쉽게 선택 할 수 있도록 도와 줄 뿐만 아니라, 디자인 패턴의 주요특성을 빠르게 이해하고 간파 할 수 있게 한다. 그래서 Beck 이 디자인패턴을 소개한 이후 GoF, Buschmann, Grand, Antoy 등은 디자인 패턴을 단순히 열거를 통해 소개하지 않고, 각자의 기준에 따라 체계적으로 분류하여 패턴을 설명 하고 있다. 본 연구는 객체지향 설계의 근본 개념인 Polymorphism (Inclusion Polymorphism) 과 '객체 지향 소프트웨어 설계 원칙' 그리고 이 근본 원칙들이 UML 클래스 다이어그램에 나타나는 구조적 특정에 의거해 디자인 패 턴 해석을 수행 하였다. 본 연구의 목적은 1) 객체지향의 근본 원칙으로 표현 되는 패턴과 2) 설계자의 전문적 인 Art를 포함하고 있는 패턴으로 분류하는데 있다.3: 재미는 용이성을 통해 채택의도에 정의 영향을 미친다. 가설4: 유용성은 채택의도에 정의 영향을 미친다. 가설5: 용이성은 채택의도에 정의 영향을 미친다. 가설6: 용이성은 유용성에 정의 영향을 미친다. 본 연구의 대상은 자발적으로 이러닝을 채택할 수 있는 대학생을 대상으로 하였고, 설문 데이터 분석을 통한 실증연구를 수행하였다. 분석방법으로는 PLS 분석도구를 사용하였다. 분석결과 가설6을 제외하고는 모두 유용한 것으로 입증되었다.97)은 배움의 용이성, 기억의 용이성, 오류, 효율성, 만족성으로 분류하고 있고(Nielsen, 1997), Shneiderman(1998)는 효과성(직무시간, 배움의 시간), 효율성(기억의 지속시간, 오류), 만족도를 품질의 특성으로 분류하였다. 이와 같은 소프트웨어의 품질은 소프트웨어 계획, 개발, 성장과 쇠퇴의 모든 과정에 적용되며, 환경적 변화에 따라 사용자들의 정보욕구를 적절하게 반영하여 만족도를 높이 는 것이라고 요약할 수 있다. 그러나 현재까지 소프트웨어 품질 평가에 대한 연구들 은 보편적인 평가 항목들을 대상으로 측정하여 일반적인 품질기준을 제시하고 있고, 유사한 측정 내용들이 중복되어 있다. 이러한 경향은 산업별 특수성이 강한 소프트웨어에 대해서는 정확한 품질측정이 어려웠고, 품질측정에 대한 신뢰성을 떨어뜨리는 계기가 되었다. 이러한 한계를 극복하고자 나타난 방법론이 최종사용자들의 요구사항을 얼마나 적절하게 시스템에 반영했는지에 대한 사용성(Usability) 측정이다. 사용성에 대한 정의는 사용자들이 실질적으로 일하는 장소에서 직접 사용자들의 시스템 운용실태를 파악하여 문제점을 개선하는 것으로 요약할 수 있다. ISO9124-1

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.9 no.2
• /
• pp.415-421
• /
• 2008

The increasing interest in ontologies is driven by the large volumes of information now available as well as by the increasing complexity and diversity of this information. These trends have also increased interest in automating many activities that were traditionally performed manually. We are currently engaged in this paper that have realized benefits in productivity and clarity by utilizing UML class diagrams to develop and to display complex OWL ontologies. UML has many features, such as profiles, global modularity and extension mechanisms that are not generally available in most ontology languages. However, ontology languages have some features that UML does not support. Our paper identifies the similarities and differences between UML and the ontology languages RDF and OWL. To reconcile these differences, we propose a modification to the UML metamodel to address some of the most problematic differences.