• Korean Journal of Child Studies
• /
• v.37 no.6
• /
• pp.145-155
• /
• 2016

Objective: The purpose of this study was to investigate trajectories of child peer interaction and to compare the causal effects of their predictors, including child individual variables (i.e., gender, language ability, and cognitive ability) and teacher variables (i.e., teacher efficacy and teacher-child interaction). Methods: The participants of this study were 263 children and their teachers from the forth to sixth waves of longitudinal data from the Korean Children and Youth Panel Survey by the Korea Institute of Child Care and Education. The data was analyzed using Pearson's correlation and latent growth modeling. Results and Conclusion: The findings of this study are as follows: First, there was a linear decrease in child negative peer interaction over the course of 3 years, and significant individual differences were found in the trajectories (intercept and slope). Second, the predictors had significant casual effects on the trajectories of child negative peer interaction. The trajectories of child negative peer interaction involving girls, higher cognitive ability, and greater teacher-child interaction showed lower degree of intercept and a quicker decrease. Finally, the implications of findings are discussed.

• Proceedings of the CALSEC Conference
• /
• 2004.02a
• /
• pp.318-326
• /
• 2004

The ebXML (Electronic Business using eXtensible Markup Language) Specification Schema is to provide nominal set of specification elements necessary to specify a collaboration between business partners based on XML. As a part of ebXML Specification Schema, BPSS (Business Process Specification Schema) has been provided to support the direct specification of the set of elements required to configure a runtime system in order to execute a set of ebXML business transactions. The BPSS is available in two stand-alone representations, a UML version and an XML version. Due to the limitations of UML notations and XML syntax, however, current ebXML BPSS specification is insufficient to specify formal semantic constraints of modeling elements completely. In this study, we propose a classification schema for the BPSS semantic constraints and describe how to represent those semantic constraints formally using OCL (Object Constraint Language). As a way to verify a Business Process Specification (BPS) with the formal semantic constraint modeling, we suggest a rule-based approach to represent the formal constraints and to use the rule-based constraints specification to verify BPSs in a CLIPS prototype implementation.

• Journal of the Korea Computer Industry Society
• /
• v.3 no.2
• /
• pp.167-178
• /
• 2002

XML documents used for exchanging structured documents between heterogeneous distributed systems are spreading among B2B and the industrial world rapidly. This condition brings an object-oriented visualization tool for modeling XML documents. It is hard to apply for DTD - the rule for declaring document type, which is employed in XML, to various industrial field. Thus, W3C announced Recommendation for XML Schema - the rule for declaring new document type which is adaptable to XML and satisfy to user. Document Type which has high reusability and flexibility can be defined owing to that XML Schema is designed by utilization of Object-Oriented-Modelling technique(UML). This document is proposed the specification and an algorithm for mapping XML Schema to UML.

• Journal of Internet Computing and Services
• /
• v.10 no.4
• /
• pp.139-149
• /
• 2009

In order to verify that a lot of legal requirements and regulations are correctly translated into software, this paper provides a solution for formal and computable representations of rules and requirements in data protection legislations with a DSML (Domain Specific Modeling Language). All policies are formally specified through Prolog and then integrated with DSML, According to the time of policy verification, this solution has two kinds of policies: static policies, dynamic policies.

• Journal of the Computational Structural Engineering Institute of Korea
• /
• v.24 no.2
• /
• pp.121-131
• /
• 2011

An object oriented programming(OOP) framework is presented to solve plane elastostatic contact problems by means of the boundary element method(BEM). Unified modeling language(UML) is chosen to describe the structure of the program without loss of generality, even though all implemented codes are written with C++. The implementation is based on computational abstractions of both mathematical and physical concepts associated with contact mechanics involving geometrical nonlinearities and the corner node problems for multi-valued traction. The overall class organization for contact analysis is discussed in detail. Numerical examples are also presented to verify the accuracy of the developed BEM program.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.1
• /
• pp.29-40
• /
• 2000

With increasing amounts of information on the web and needs to access accurately them, it is very important to standardize metadata and to store and manage system. The RDF(Rdsource Description Framework) is a framework for representing exchanging, and reusing metadata. And, it can be processing uniformly the standardized metadata, because it uses XML(eXtensible Markup Language) syntax. The RDF schema provides a basic type system for use RDF models. In this paper, we propose rules and an algorithm to convert the RDF schema into an UML(Unified Modeling Language) class diagram and formal models to represent an object-oriented schema for the RDF schema. The proposed rules and algorithm are useful for natural mapping and the object modeling of RDF schema can be easily converted into the object-oriented schema, and the formal models supports an efficient environment for retrieving and processing object-oriented documents.

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

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.3
• /
• pp.622-632
• /
• 1999

As the complexity of software development is increasing due to networking, multimedia, and diverse system architecture, the need for effective software development methodology is increasing. Especially, due to software standard and internalization of software market, it is necessary to accept international quality such as ISO 9000-3. In addition, object oriented development methodology is required due to rapid propagation of OO technology and standardization. Recently, UML was accepted by the OMG as standard object-oriented modeling language for distributed environment. When we UML was accepted by the OMG as standard object-oriented modeling language for distributed environment. When we develop Java and CORBA-based software, often UML is applied to Java and CORBA-based projects. However, current structural or OMT-based object-oriented methodologies. In this paper, we proposed UML-based development and concrete guidelines for each phase in order to apply UML to software development practically and effectively. Also, we define the transition guidelines and semantics between various development tasks. In addition, the analysis and design techniques of user interface and system development techniques needed in Web application development are presented.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.6 no.5
• /
• pp.661-666
• /
• 2002

We need the flexible method for communication network configuration and fault management business procedure. Therefore development of systematic integrating fault management system is essential to meet on these requests. We must design the integrating fault management system so that can run the repair processing for both data communication network management and new next generation data communication network of various type. In general it is effective that the system is consisted of decentralized module to be accessibele for business logic and datum to remote area. To Solve these problem, a method is to use object-oriented design technique. That is, it is to abstract reusability objects and make component module using the abstracted objects. In this paper, we propose a fault management system of communication network service using object-oriented design techniques which are UML(Unified Modeling Language) and EJB(Enterprise Java Bean).

• Journal of Korea Society of Industrial Information Systems
• /
• v.5 no.3
• /
• pp.87-93
• /
• 2000

Recently Software Industry has tended to enhance the productivity and quality with using the software architecture in software development and administration. The research of software component technique and software development methodology are just doing and making many applications. The software architecture is considered as the essential element for analyzing and maintaining the entire structure with organizing the software into components and describing the relations with connectors. The software modeling methodology that we propose is generating Happy Work Language describing the software structure with the modeling tool as Happy Work. We can use System Context Diagram, Component Diagram, Component Sequence Diagram, and they are composed of four Elements as Users, Systems, Components, Connectors.