• Journal of the Korean Society of Costume
• /
• v.66 no.1
• /
• pp.28-41
• /
• 2016

This paper is aimed at intensively examining the scope of legal protection for fashion designs under the Design Protection Act of Korea. For this purpose, this looked into how the Act defines the concept of design, its requirements, and the prerequisites for acquiring design rights. The study also reviewed statutory interpretations over the judgment of the identity and similarity of designs. For more practical and substantial discussions, this research utilized cases and precedents, which had relevant legal principles. This study also figured out how both the requirements for a design definition - such as merchantability, configuration, visibility, and aesthetics - and the prerequisites for acquiring design rights - like industrial applicability, novelty, and creativity - are interpreted and utilized in actual circumstances. The authors expressed their opinions regarding the criteria of judging the identity and similarity of designs, based on a study of previous cases. Previous rulings show that aesthetics of the exterior design is used as the criteria for determining whether a design is same or similar. So, two designs, which have different specific details, are deemed same or similar, if both designs show similarity in the dominant elements. This is because both designs will produce similar aesthetic qualities. However, if the dominant elements of a design are part of the public domain, and the specific details characterize the design, the latter has to be evaluated in the process. This paper examined scope of legal protection for fashion designs using relevant precedents. The study may serve as academic materials that lead to the establishment of rightful ownership in creative activities.

• Proceedings of the KAIS Fall Conference
• /
• 2003.11a
• /
• pp.191-194
• /
• 2003

Product factory is a real-time financial product design system for the Internet customers. Recently, as the number of the Internet customers increases, the importance of the product factory becomes more emphasized. However, there is not much research performed regarding its definition, properties, requirements, nor implementation. In this research, we make a clear definition of product factory, and analyze the requirements of the system from the perspectives of functions and services, and we propose an architecture that reflects the analyzed requirements. In additions, we implemented a prototypical system based on the proposed architecture to prove the usefulness of this research.

• Computers and Concrete
• /
• v.6 no.6
• /
• pp.491-503
• /
• 2009

This paper presents a design framework developed using axiomatic design (AD) theory that can be applied in the design process of porous concrete. The main contribution of this paper is the definition of an AD framework based on the needs and functional requirements of porous concrete. The framework shows how AD theory can be used to provide guidelines for proportioning and manufacturing porous concrete. The advantage of the AD approach is that it systemizes the way to decouple design parameters and makes designers to think rationally between what we want to achieve and how we propose to satisfy the functional requirements of porous concrete. In this paper, test results of laboratory-size porous concrete specimens under compression were analyzed to evaluate the performance of the porous concrete based on the desired functional requirements.

• Korean Journal of Computational Design and Engineering
• /
• v.21 no.4
• /
• pp.433-442
• /
• 2016

This paper aims to define the relational logic of in-between code articles as well as within atomic sentences in Korean Building Code, as an intermediate research and development process for the automated building permit system of Korea. The approach depicted in this paper enables the software developers to figure out the logical relations in order to compose KBimCode and its databases. KBimCode is a computer-readable form of Korean Building Code sentences based on a logic rule-based mechanism. Two types of relational logic definition are described in this paper. First type is a logic definition of relation between code sentences. Due to the complexity of Korean Building code structure that consists of decree, regulation or ordinance, an intensive analysis of sentence relations has been performed. Code sentences have a relation based on delegation or reference each other. Another type is a relational logic definition in a code sentence based on translated atomic sentence(TAS) which is an explicit form of atomic sentence(AS). The analysis has been performed because the natural language has intrinsic ambiguity which hinders interpreting embedded meaning of Building Code. Thus, both analyses have been conducted for capturing accurate meaning of building permit-related requirements as a part of the logic rule-based mechanism.

• Journal of the Korean Society of Systems Engineering
• /
• v.11 no.2
• /
• pp.61-73
• /
• 2015

The early-phase naval ship design demands requirements synthesis rather than design synthesis, which conducts engineering design for several domains on a detailed level. Requirements synthesis focuses on creating a balanced set of required operational capabilities satisfying user's needs and concept of operations. Requirements are evolved from capability based languages to function based language by statistical exploration and engineering design which are derived in the following order: concept alternative, concept baseline, initial baseline and functional baseline. The early-phase naval ship design process can be divided into three passes: concept definition, concept exploration and concept development. Main activities and outcomes in each pass are shortly presented. Concept definition is the first important step that produces a concept baseline through extensive design space exploration promptly. Design space exploration applies a statistical approach to explore design trends of existing ships and produce feasible design range corresponding to concept alternative. It further helps naval systems engineers and operational researchers by inducing useful responses to user and stakeholders' questions at a sufficient degree of confidence and success in the very early ship design. The focus of this paper is on the flow of design space exploration, and its application to a high-speed patrol craft. The views expressed in this paper are those of the authors, and do not reflect the official policy or rule of the Navy.

• Journal of Navigation and Port Research
• /
• v.43 no.6
• /
• pp.353-360
• /
• 2019

Technology-driven development of a new system makes it difficult for users and stakeholders to identify or intervene in the development process, resulting in systems with unnecessary functions and poor quality services. Applying the software architecture design process to the initial design of the navigation system platform of autonomous ships enables the development of a system that reflects the required functions and service quality of the stakeholders. The design, which includes all of the subsystems that make up an autonomous ship platform, is close to an enterprise architecture. Thus, we strived to design a navigation system platform suitable for the design range of the software architecture. This study analyzed the definition of functional requirements, and quality attributes by applying the software architecture design procedure. This study was conducted to identify the characteristics of the navigation system and platform needs, and the stakeholders were identified. To derive the functional requirements and constraints of the platform, a quality attributes workshop was held engaging stakeholders, and the results of the analysis of functional requirements and quality attributes were listed. Based on the results of this study, the architect can establish the evidence and technical solutions that are integral for the architecture development, and will facilitate the creation of quality attribute scenarios.

• Proceedings of the Korean Society of Precision Engineering Conference
• /
• 2002.05a
• /
• pp.555-560
• /
• 2002

This paper addresses the methodologies for manufacturing systems design. While a number of design methods are used in product or part design, methods for manufacturing systems design are rarely known. Two approaches, simulation and axiomatic design theory, are discussed with respective case examples. The usual purpose of using simulation is to identify the bottleneck of a manufacturing system or to evaluate its performance with the aim of configuring the manufacturing system. The simulation typically proceeds in steps such as problem definition, model building, numerical experimentation, analysis and evaluation. The axiomatic design method transforms customer attributes into functional requirements and repeats mapping processes between functional domain and physical one until a satisfactory level of refinement of the functional requirements and the design parameters is reached. Possible design alternatives are evaluated by applying the independence axiom as well as the information axiom.

• Laser Solutions
• /
• v.10 no.3
• /
• pp.15-24
• /
• 2007

In this paper laser micromachining system design process for commercialization is suggested. The constructed system design process is properly adjusted for laser micromachining area after tailoring engine process of system engineering process such as requirement analysis, functional analysis and allocation, system synthesis and system optimization process. In the current laser machining system design, system components and specifications are determined on the basis of experimental experience which a laser is being used in machining some materials as well as the current machining and research trend. In this paper, however, systematic process is suggested in addition to experimental experience, which the laser and system components and their specifications are decided in the process of definition of functional requirements and engine design variables of system to satisfy the customer's requirements.

• Journal of Astronomy and Space Sciences
• /
• v.32 no.3
• /
• pp.257-268
• /
• 2015

Characteristics of delta-V requirements for deploying an impactor from a mother-ship at different orbital altitudes are analyzed in order to prepare for a future lunar CubeSat impactor mission. A mother-ship is assumed to be orbiting the moon with a circular orbit at a 90 deg inclination and having 50, 100, 150, 200 km altitudes. Critical design parameters that are directly related to the success of the impactor mission are also analyzed including deploy directions, CubeSat flight time, impact velocity, and associated impact angles. Based on derived delta-V requirements, required thruster burn time and fuel mass are analyzed by adapting four different miniaturized commercial onboard thrusters currently developed for CubeSat applications. As a result, CubeSat impact trajectories as well as thruster burn characteristics deployed at different orbital altitudes are found to satisfy the mission objectives. It is concluded that thrust burn time should considered as the more critical design parameter than the required fuel mass when deducing the onboard propulsion system requirements. Results provided through this work will be helpful in further detailed system definition and design activities for future lunar missions with a CubeSat-based payload.

• Journal of the Korea Society for Simulation
• /
• v.19 no.1
• /
• pp.153-160
• /
• 2010

Most part of errors in software development process are included during the stage of requirements definition and design. And correction or elimination of errors from those stages requires much more efforts and costs than those from the later part of software development process. However, despite of the importance of the validation of requirement definition and design stages, several kinds of problem have made it hard to be done successfully. Therefore, in this paper, we introduce a novel validation process for the preliminary design stage. The validation process is based on simulations of model and it can be used to validate requirements and model simultaneously. Models in the validation process will take only the behavior of software and be built on Ptolemy framework. The usability of our validation process is confirmed with a case study over DNS system environment. And the result of simulation shows well-known errors or vulnerabilities can be found with simulations of model which has the behavior of software. This means our validation process can be used as a process to validate requirements and models during the early stage of software development process.