• 한국정보처리학회:학술대회논문집
• /
• 한국정보처리학회 2022년도 추계학술발표대회
• /
• pp.697-699
• /
• 2022

특허청에서 주관하는 아이디어 사업화 및 아이디어 경진대회를 PC 환경 웹 플랫폼으로 제공하고 있다. 본 논문에서는 아이디어 사업화 및 아이디어 경진대회를 바탕으로 웹 환경이 아닌 모바일 플랫폼으로 구축하고 사용 시 편리한 UI/UX, 모바일 특성을 활용한 모바일 애플리케이션을 설계하여 다양한 아이디어의 육성 및 사업화 추진을 돕고 다양한 문화와 창업 확산을 도울 수 있는 방안을 제시하고자 한다.

• 한국정보처리학회:학술대회논문집
• /
• 한국정보처리학회 2022년도 추계학술발표대회
• /
• pp.706-708
• /
• 2022

현대 사회에서 쓰레기 처리는 여러 사회 문제를 일으키고 있다. 넘쳐나는 쓰레기는 미관을 해치고 악취를 발생시킨다. 본 논문은 쓰레기 배출량이 쓰레기통의 수용 용량을 넘는 경우 웹과 앱을 통해 청소 관리자에게 알림을 제공하는 등의 편리한 쓰레기통 관리 시스템을 제안한다. 제공하는 앱과 웹은 데이터베이스와 아두이노 기반의 IoT 기술을 활용하여 쓰레기통 자동 개폐, 쓰레기 압축, 포화 용량 표시 등의 다양한 기능을 제공한다. 앱과 웹을 통하여 수집된 데이터는 추후 환경 관련 프로젝트에서 다방면으로 활용될 수 있다.

• ETRI Journal
• /
• 제25권2호
• /
• pp.121-132
• /
• 2003

To enhance the productivity of software development and accelerate time to market, software developers have recently paid more attention to a component-based development (CBD) approach due to the benefits of component reuse. Among CBD processes, the identification of reusable components is a key but difficult process. Currently, component identification depends mainly on the intuition and experience of domain experts. In addition, there are few systematic methods or tools for component identification that enable domain experts to identify reusable components. This paper presents a systematic method and its tool called a component identifier that identifies software components by using object-oriented domain information, namely, use case models, domain object models, and sequence diagrams. To illustrate our method, we use the component identifier to identify candidates of reusable components from the object-oriented domain models of a banking system. The component identifier enables domain experts to easily identify reusable components by assisting and automating identification processes in an earlier development phase.

• 한국컴퓨터정보학회논문지
• /
• 제21권12호
• /
• pp.219-226
• /
• 2016

In this paper, we propose an efficient repository model for online software education. The software education of app development consists of 7 stages: coding & debugging, submit, collaboration, review, validate, deployment, certification. Proposed repository model supports all 7 stages efficiently. In the coding & debugging stage, the students repeat coding and debugging of source. In the submit stage, the output of previous process such as source codes, project, and videos, are uploaded to repository server. In the collaboration stage, other students or experts can optimize or upgrade version of source code, project, and videos stored in the repository. In the review stage, mentors can review and send feedbacks to students. In the validate stage, the specialists validate the source code, project, and the videos. In the deployment stage, the verified source code, project, and videos are deployed. In the certification stage, the source code, project, and the videos are evaluated to issue the certificate.

• International Journal of Computer Science & Network Security
• /
• 제22권9호
• /
• pp.143-148
• /
• 2022

Component-based software development (CBD) is a methodology that has been embraced by the software industry to accelerate development, save costs and timelines, minimize testing requirements, and boost quality and output. Compared to the conventional software development approach, this led to the system's development being completed more quickly. By choosing components, identifying systems, and evaluating those systems, CBSE contributes significantly to the software development process. The objective of CBSE is to codify and standardize all disciplines that support CBD-related operations. Analysis of the comparison between component-based and scripting technologies reveals that, in terms of qualitative performance, component-based technologies scale more effectively. Further study and application of CBSE are directly related to the CBD approach's success. This paper explores the introductory concepts and comparative analysis related to component-based software engineering which have been around for a while, but proper adaption of CBSE are still lacking issues are also focused.

• Journal of Information Processing Systems
• /
• 제17권5호
• /
• pp.972-988
• /
• 2021

At present, DevOps environments are getting popular in software organizations due to better collaboration and software productivity over traditional software process models. Software artefacts in DevOps environments are vulnerable to frequent changes at any phase of the software development life cycle that create a continuous integration continuous delivery pipeline. Therefore, software artefact traceability management is challenging in DevOps environments due to the continual artefact changes; often it makes the artefacts to be inconsistent. The existing software traceability related research shows limitations such as being limited to few types of artefacts, lack of automation and inability to cope with continuous integrations. This paper attempts to overcome those challenges by providing traceability support for heterogeneous artefacts in DevOps environments using a prototype named SAT-Analyser. The novel contribution of this work is the proposed traceability process model consists of artefact change detection, change impact analysis, and change propagation. Moreover, this tool provides multi-user accessibility and is integrated with a prominent DevOps tool stack to enable collaborations. The case study analysis has shown high accuracy in SAT-Analyser generated results and have obtained positive feedback from industry DevOps practitioners for its efficacy.

• 한국컴퓨터정보학회논문지
• /
• 제21권5호
• /
• pp.119-126
• /
• 2016

Software maintenance becomes extremely difficult, especially caused by multiple versions in project-based or customer-oriented software development methodology. For reducing the maintenance cost, reengineering to software product line can be a solution to the software which either is a family of products nevertheless little different functionalities or are customized for each different customer's requirement. At an initial stage of the reengineering, the most important activity in software product line is feature extraction with respect to commonality and variability from the existing system due to verifying functional coverage. Several researchers have studied to extract features. They considered only a single version in a single product. However, this is an obstacle to classify the commonality and variability of features. Therefore, we propose a method for systematically extracting features from source code and its change history considering several versions of the existing system. It enables us to represent functionalities reflecting developer's intention, and to clarify the rationale of variation.

• 제어로봇시스템학회:학술대회논문집
• /
• 제어로봇시스템학회 2004년도 ICCAS
• /
• pp.932-935
• /
• 2004

In this paper, we present a framework that is easy to develop, modify, maintain and extend a control and monitoring software for any kinds of instruments. The presented framework is composed of three XML documents (IID, MAP, and CMIML) and two tools (Virtual Instrument Wizard, Generator). Interface information about behaviors and states of instruments is written on IID. Mapping information between the interface information in IID and API of a real instrument driver is written on MAP. Finally information about control and monitoring software is written on CMIML. IID, MAP and CMIML are written with XML format to provide common usage and platform independence of the suggested framework. VI Wizard generates CMIML (platform independent intermediate document) using IID and existing CMIML, and Generator generates source code of a control and monitoring software (platform dependent code) automatically using CMIML and MAP. The suggested framework that automatically generates control and monitoring software based on GUI provides easy development and maintenance. Also, reusability can be increased by reusing platform independent software description documents.

• International journal of advanced smart convergence
• /
• 제8권4호
• /
• pp.207-213
• /
• 2019

Assistance for the quality assurance management and developers to provide high quality software products. Using a bug record keeping system is exceptionally important in software progress, and it is followed vastly by majority of software producing companies in modern era. Regular application of a bug record keeping system is very helpful in developing software systems. We developed this system which helps the software testing team to keep a complete record of their testing activities during the software testing, also increases your confidence in the software quality, class and worth. Our proposed system offers trouble-free and effortless approaches to acquire desired information about bug, also produces different kinds of reports like summary reports, detailed reports etc. It gives facility to create, delete and update any project. Our developed application system is designed by using visual c# at front end and sql server 2008 management studio express at back end.

• 경영과학
• /
• 제9권1호
• /
• pp.31-40
• /
• 1992

The size of software collection at any organization is increasing rapidly with the use of computer becomes popular for various applications. This trend points out the importance of proper 'catalog'or 'directory' for software collections, however, only 'title list' is found in practice. The problem of no proper directory with software collection would be more serious than the problem with book collection since browsing is not possible with softwares. Many of the expensive softwares will be a waste of money to purchase and to hold if no catalog about them is provided. In this paper the difficulties in applying AACR2 to software cataloging and the most important characteristic of computer software are discussed as well as presenting the necessity of localized information due to the requirement of a machine to be used, the difficulty using subject-based-call-number scheme, an expected way of searching software to design a location indicator, software qualifications to be cataloged, and so on. In addition, an analysis of randomly selected softwares after a cataloging practice is followed.