Earticle

In Korea, software education is being strengthened. As a result, the polarization in software education is getting worse due to the private education craze. Fortunately, there is room in South Korea to narrow the gap through after-school schools. However, the ability of after-school instructors and the acquisition of information are also important, so this study developed model textbooks. Model textbooks have recently applied Nobel Engineering, which has been gaining attention in South Korea. Through the developed model textbooks, we hope to help with fun software education by applying it to the school site after school.

ICT 융합환경과 클라우드 컴퓨팅, 빅데이터 등의 새로운 환경이 도래함에 따라, 기존의 소프트웨어공학 기법들을 어떻게 활용하느냐가 주요 관건이 되고 있다. 더불어 IoT 환경에서 안전한 소프트웨어 활용을 위한 요구사항분석 및 설계 단계의 중요성이 나타나고 있다. 그러나 그간의 연구들은 IoT 환경에 적용되는 기술들의 활용성에 주로 초점이 맞추어져 있으며, 그러한 기술들을 안전하게 현장에 적용하기 위한 선행 단계인 분석․설계를 내실 있게 만들기 위한 연구는 미흡한 실정이다. 이에 따라서 본 연구에서는 소프트웨어 공학 기반의 연구동향을 정리하고 그 관계를 분석하고자한다. 세부적으로 연구동향 메타분석을 수행하기 위하여 소프트웨어 공학 연구동향을 프로세스에 따라 구분하고 연차별 추이를 분석하였다. 그리고 키워드의 연관관계를 분석하여 주요 연구 흐름을 분석하였다. 이러한 분석을 바탕으로IoT 환경에서 고품질 소프트웨어를 개발하기 위한 방안으로 소프트웨어 공학 기법들의 활용성을 높일 수 있는 전략을제언하였다.

The new environments arrive such as ICT convergence, cloud computing, and big data, etc., how to take advanta ge of the existing software engineering technologies has become an important key. In addition, the importance of re quirement analysis for secure software and design phase has been shown in the IoT environment While the existing studies have focused on the utilization of the technique applied to IoT environment, the studies for enhancing analys is and design, the prerequisite steps for safely appling these techniques to the site, have been insufficient. So, we tr y to organize research trends based on software engineering and analyze their relationship in this paper. In detail, w e classify the research trends of software engineering to perform research trends meta-analysis, and analyze an ann ual development by years. The flow of the major research is identified by analyzing the correlation of the key word s. We propose the strategies for enhancing the utilization of software engineering techniques to develop high-quality software in the IoT environment.

A major fair-access issue has arisen regarding situations where a copyright holder attempts to restrict a reverse engineering right by copyright infringement litigation, contractual shrink-wrap licenses or a protective system that defeats the reverse engineering permissible under the "fair-use" doctrine. Reverse engineering computer software is defined as the process of studying a computer program to obtain useful and detailed insight into the functional mechanisms of the work. Reverse engineering commonly involves copying an original program without the permission of a copyright owner. Indeed, the owners seek to prevent reverse engineering by bringing infringement suits, imposing contractual limitations or installing technological impediments. In the United States, the Digital Millennium Copyright Act ("DMCA") provides a software vendor with extra protection for its protective system, and allows reverse engineering only for the purpose of interoperability. The Uniform Computer Information Transactions Act ("UCITA") makes a shrink-wrap license enforceable even if it contains a term prohibiting reverse engineering. These protectionist measures ensure that a copyright holder can dominate the computer software industryby restricting reverse engineering. Although the Computer Program Protection Act in Korea allows a reverse engineering purporting to achieve interoperability as exception, this is still not enough to strike balance between a copyright owner' interest and public rights to access to a copyrighted work. The current trend toward copyright protectionism undermines the copyright balance thus/ the critical question regarding clarification of the reverse engineering right should be answered by policymakers in terms of reconciliation between copyright, contract and competition policy.

This paper presents the interrelationship between software quality character and engineering attributes. The software quality characteristics and subcharacteristics are excerpted from IS0/IEC 9126 standards, and the engineering attributes are from Deutsch and Willis〔4〕. Based on the previous studies a subjective judgement, trisected interrelationship(strong, medium, weak) bet these two groups are derived. The results are summarized in a table, and can be used as a quick reference guide to the software quality engineering application such as quality evaluations for software products, selection of key engineering attributes for high-quality software production, and so forth.

4차 산업혁명 이후 빠르게 변화하는 사회에서는 복잡한 문제를 해결할 수 있는 융합인재양성이 중요한 이슈로 대두되고 있다. 본 연구는 (사)한국공학교육인증원(이하, 공인원)에서 제시하고 있는 공학교육 인증기준인 융·복합분야 의 프로그램 학습성과를 설정하기 위해 필요로 하는 핵심역량을 제안하는데 그 목적이 있다. 연구의 목적을 달성하기 위해 사례연구방법론을 적용하였다. 분석사례는 국내외 대학의 디자인과 소프트웨어 융합 전공이다. 선정된 전공의 교 육목표 및 교과목의 강의계획서를 분석하였다. 연구결과 공인원에서 제시하고 있는 프로그램 학습성과 10개 외에 디자 인·소프트웨어 융합전공에서 추가로 달성해야할 핵심역량 4가지가 도출되었다. 새로 추가된 핵심역량은 융합능력, 창의 적 사고, 창업가능력, 디자인 능력이다. 이 연구의 결과는 향후 융합전공을 위한 공학교육인증 융·복합분야의 평가체계 개발에 기여할 수 있을 것으로 기대된다.

In the rapidly changing society since the Fourth Industrial Revolution, the cultivation of convergence talents that can solve complex problems is emerging as an important issue. The purpose of this study is to propose the core competencies required to establish the program learning outcomes of the engineering and education curriculum, which is the accreditation standard of engineering education proposed by ABEEK(Accreditation Board for Engineering Education of Korea). Case study methodology was applied to achieve the purpose of the study. The case of analysis is design and software convergence majors of domestic and foreign universities. The educational objectives and course syllabi were analyzed. As a result of the research, four core competencies to be achieved in the design and software convergence majors were derived in addition to the ten program outcomes presented by ABEEK. New core competencies are convergence ability, creative thinking, entrepreneurship, and design ability. The result of this study is expected to contribute to the development of the evaluation system for the convergence engineering education field.

This paper presents the interrelationship chart between software quality characteristics and engineering attributes. The software quality characteristics and their subcharacteristics are excerpted front IS0/1EC 9126 standards, and the engineering attributes are from Deutsch and Willis[4]. Based on the previous studies and subjective judgement, trisected interrelationship(strong, medium, weak) between these two groups are derived. The results are summarized in a table, and can be used as a quick reference guide to the software quality engineering applications such as quality evaluations for software products, selection of key engineering attributes for high-quality software production, and so forth.

소프트웨어 기반의 시스템 설계과정에서 설계자가 고려해야 하는 요소들이 다양해지면서 시스템 설계가 점점 어려워지고 있다. 다양한 설계 요소들이 존재하지만 사용자의 특성 및 직무, 사용가능한 정보기술의 특성 등이 핵심적인 요소로 간주된다. 또한 정보기술이 발달하면서 인간과 시스템의 상호작용이 점점 인지적인 특징을 지니게 되었다. 따라서 사용성 높고, 효율적이면서 안전한 소프트웨어 기반의 시스템을 개발하기 위해서는 시스템 설계자가 사용자의 인지적인 요구사항 및 그들의 직무를 시스템 설계과정에서 체계적으로 다룰 수 있어야 한다. 그러나 소프트웨어 공학, 시스템 공학 및 인간-컴퓨터 상호작용 등에서의 전통적인 시스템 설계 방법은 이러한 설계자의 설계활동을 효과적으로 지원하는데 한계가 있었다. 그 대안으로 인지시스템공학(cognitive systems engineering; CSE)은 인간중심의 설계철학을 바탕으로 소프트웨어 기반의 복잡한 시스템 설계과정에서 설계자의 활동을 체계적으로 도와줄 수 있는 유용한 개념과 방법을 제공해주고 있다. CSE는 원래 사람이 실시간으로 감시 및 제어해야 하는 복잡한 사회기술적 시스템(예: 원자력발전소 및 공항관제소)의 분석, 설계 및 평가를 위해 태동한 학문이다. 그러나 CSE에서 제공하는 이론적 및 방법론적 프레임워크는 소프트웨어 기반의 시스템을 설계하는 데에도 유용하게 활용할 수 있는 충분한 가능성을 갖고 있다. 이 논문은 CSE의 근간을 이루는 핵심 개념 및 원칙을 고찰하고 소프트웨어 기반 시스템 설계에의 활용가능성 및 그 방안을 논의한다.

Software has been a significant part of modern society for a long time. In particular, this paper is concerned with various software development process models. Software process model is a description of the sequence of activities carried out in a software engineering project, and the relative order of these activities. It represents some of the development models namely, waterfall, v-shaped, incremental, RAD, iterative spiral and agile model. Therefore, the main objective of this paper is to represent different models of software development and different aspects of each model to help the developers to select specific model at specific situation depending on customer demand.

As a practice-oriented discipline, Software Engineering is most effectively taught by using a variety of hands-on experiences. Team-based projects where students can practice their technical and soft skills are a key feature of many software engineering courses aimed to prepare students for the realities of industrial software development. This paper surveys the objectives of software development projects in undergraduate courses and summarizes four roles in which the instructor can participate in student projects: a customer, an architect, a team manager, and a mentor. The paper is concluded with case studies illustrating the nature of these roles.

A great deal of difficulty in the task of developing software can be traced to the initial phase of its life cycle, when requirements are analyzed and design schemata are constructed. The process involves modeling that part of reality the software system is intended to address. The problem is that some 2014 studies have shown that more than a third of IT projects are cancelled before being completed, the costs of more than half of these projects will be higher than their original estimates, and, on average, barely more than one in six software projects are ever completed on-time and on-budget. The main reasons for these problems include lack of user input and incomplete requirements and specifications. Accordingly, even though previous decades have witnessed a great deal of progress in the area of software development, these difficulties point to the fact that such advancement has not furnished new paradigms that might further advance development in this field. This paper is a contribution in this direction in the area of requirements analysis and design. The paper proposes adopting a new modeling method for use in the software development phase of requirements analysis and design that can contribute to alleviating the problems of lack of user input and incomplete requirements specifications. The basic idea in the proposed method, called Thing-Oriented (TO) modeling, bases requirements analysis and design on “things” that flow. Without loss of generality, TO modeling is contrasted with Object-Oriented modeling. The results point to the feasibility of using TO modeling as a multilevel diagrammatic language with a constrained number of notions.

The development of mobile applications becomes increasingly popular in our daily life due to the intensive use of applications in mobile devices like smartphones and tablets. The diversity and variety of mobile operating systems (Android, iOS, Black Berry, Windows Phone, etc.) make software engineers in front of a big challenge to develop the same application for these different platforms. This paper presents a methodology based on the Model Driven Architecture (MDA) to develop mobile applications according to the principle “develops once, use everywhere”. Our approach exploits UML modeling and Acceleo to generate specific code in order to accelerate and facilitate the development of mobile applications.

This research study introduces the operationalization process for the requirements activity of software engineering discipline to build renewable energy projects. It describes a new development approach composed of three phase’s methodology to undertake the operationalization process combined with the development of an operational model. A theoretical implementation is provided in addition to the development of a practical implementation on a standalone photovoltaic system case study. Moreover, the author’s expect that this will help in a better understanding of the principles of software engineering, in the implementation of these principles for the development of renewable energy projects as well as to contribute to build the research knowledge of software engineering foundations.