• Proceedings of the Korean Information Science Society Conference
• /
• 2007.10b
• /
• pp.108-113
• /
• 2007

소프트웨어 개발 프로젝트의 위험관리는 프로젝트의 성패를 좌우하는 매우 중요한 영역이다. 그러나 위험관리의 주체가 관리자의 역할을 가진 사람들에 의해 진행되고, 방법론이나 지침에서 제시하고 있는 위험관리 또한 여러 활동들과 산출물이 실제 위험관리정보를 필요로 하는 개발자들에게는 적절하게 연결이 되지 않고 있어서 개발자들이 필요한 정보를 파악하기에 문제점이 있다. 이에 따라 본 연구에서는 개발자들을 위한 위험관리방법으로, 요구사항추적테이블이라는 양식과 위험관리리스트간의 연결방안을 제안한다. 요구사항추적테이블은 소프트웨어 개발 생명주기 전체 과정에서 활용하고 있으며 개발자들이 사용하기 쉬운 양식이므로 요구사항추적테이블과 위험관리리스트를 연결하는 것으로 개발자들로 하여금 위험에 대한 정보를 파악하기 용이하게 하여 설계와 구현 시 관련 위험에 대해 예측이 가능하며 대처방안을 사전에 고려할 수 있다.

• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.503-514
• /
• 2003

In conventional development methodologies, requirements are considered to be not changing after analysis phase, and requirements specifications are used for the next step system design purpose. But in the real world, requirements can be changed and modified throughout the development life cycle according to end-user's more understanding about the target system, new IT technologies, changes of customer environment and market situation, and so on. So there needs a requirements change management process that can extend requirements management over the entire development life cycle and can support managing changes to the requirements after design phase. In this paper, a requirements change management process that can be integrated into conventional development methodologies is proposed to support the extension of requirements life cycle and managing changes to the requirements after design phase. This process was evaluated through an verification test with a widely used development methodology‘MaRMI’.

• Proceedings of the KAIS Fall Conference
• /
• 2009.05a
• /
• pp.800-804
• /
• 2009

최근 디지털 기술의 발전으로 인해 콘텐츠 제작자들은 텍스트, 오디오, 비디오 등의 콘텐츠를 고품질의 디지털 형태로 제작할 수 있게 되었다. 또한 인터넷 확산과 통신 기술의 발전은 컴퓨터 간의 상호 연결성을 증대시켜 디지털 콘텐츠를 쉽게 전파할 수 있게 되면서 디지털 콘텐츠 수요가 급격히 증가하고 있다. 소프트웨어의 품질은 생명주기 초기 단계가 좌우하며 초기 단계의 문제점이 수정되지 않으면 단계가 진행됨에 따라 또 다른 문제점을 야기하며 갈수록 오류 수정 및 보완이 곤란해진다. 본 연구에서는 디지털저작권관리 소프트웨어의 분석단계 품질평가 방법을 구축하였으며 이를 활용함으로써 국내 디지털저작권관리 소프트웨어 품질인식을 제고하고 개발 기술 및 품질 향상에 기여할 것이다.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.9 no.6
• /
• pp.1678-1689
• /
• 2008

Recently, OOM(Object-Oriented Method) access method which begins to apply to software development is emphasizing development cost and time reduction through independent software reuse. But because of planning to the exclusion of the lack of knowledge and expansion or performance for development technology many problems are coming out. Therefore, this thesis suggests Effective Object-Oriented Modeling methods considering the plan for higher productivity enhancement of software in the software development life cycle. Effective Object-Oriented Modeling method includes, methods, Use Case modeling methods, Analysis Modeling methods, Design Modeling methods and others. This thesis suggests Framework model method read in characteristics as follows. First, suggestion about effective object-oriented standard model development, Second, retrenchment of software development or maintenance cost, Third, solution about uncertain problems of projects in line with the application of new technology.

• 한국IT서비스학회:학술대회논문집
• /
• 2003.11a
• /
• pp.390-398
• /
• 2003

폭포수 모델 개발 생명주기를 근간으로 한 전통적 프로그램 개발방법론과 달리, 부품 형태의 컴포넌트를 조립하여 개발하는 방법론이 확산되고 있다. 컴포넌트 기반 개발(Component Based Development)의 감리에는 전통적 개발방법에 근간을 둔 감리기준이 아닌 컴포넌트 기반 개발방법에 적합한 감리가 실시되어야 한다. 본 연구에서는 전통적 개발방법론 근간의 감리기준과 CBD 적용 프로젝트 사례 분석을 통하여 감리기준의 개선점 여부를 탐색하고자 하였다. 연구 사례로는 정부 공공프로젝트와 금융기관의 차세대정보시스템 구축 프로젝트를 선정하였다. 기존의 정보시스템감리 기본점검표와 사례에서의 감리검토항목을 비교 분석한 결과 감리검토항목의 개선점을 발견할 수 있었다. 사례분석의 결과로 CBD 프로젝트에 적합한 감리검토항목을 제시하였으며, 연구결과는 소프트웨어 제품 개발의 효율성 제고 및 품질향상에 이바지 할 것이다.

• KIPS Transactions on Computer and Communication Systems
• /
• v.10 no.4
• /
• pp.107-116
• /
• 2021

In the 4th Industrial Revolution situation it is essential to need the high quality of software in diverse industrial areas. In particular current software centered schools attempt to educate the creative thinking based coding to non-major students and beginners of computer. But the problem is insufficient on the definition and idea of the creative thinking based software. In addition in a aspect of coding education for non-major and new students we recognize to have no relationship between creative thinking methods and coding. In other words we should give them how to practically code and design through learning the creative thinking. To solve this problem we propose the codification of design thinking mechanism without the knowledge of software engineering through mapping creative thinking with software development process. With this mechanism we may expect for students to have some coding ability with the creative design.

• Journal of the Korea Institute of Information Security & Cryptology
• /
• v.25 no.2
• /
• pp.363-374
• /
• 2015

Instrumentation and control(I&C) system has been mainly designed and operated based on analog technologies in existing Nuclear Power Plants(NPPs). However, As the development of Information Technology(IT), digital technologies are gradually being adopted in newly built NPPs. I&C System based on digital technologies has many advantages but it is vulnerable to cyber threat. For this reason, cyber threat adversely affects on safety and reliability of I&C system as well as the entire NPPs. Therefore, the software equipped to NPPs should be developed with cyber security attributes from the initiation phase of software development life cycle. Moreover through cyber security assessment, the degree of confidence concerning cyber security should be measured and if managerial, technical and operational work measures are implemented as intended should be reviewed in order to protect the I&C systems and information. Currently the overall cyber security program, including cyber security assessment, is not established on I&C systems. In this paper, we propose cyber security assessment methods in the Software Development Life Cycle by drawing cyber security activities and assessment items based on regulatory guides and standard technologies concerned with NPPs.

• The KIPS Transactions:PartD
• /
• v.13D no.1 s.104
• /
• pp.87-96
• /
• 2006

This paper focused on the method for customizing software development path, considering the project environments and characteristics. he selection standard of development path is composed of ten items, based on the process of ISO/IEC TR 15721 Information Technology Guide for ISO/IEC 12207 (Software Life Cycle Process) and ISO/IEC 15504 Information technology - Process assessment. The ten items were reflected the project environments and characteristics, at the same time the items conduct the adjustment item of selecting project development path. An algorithm for selecting software development path through items of the project environments and characteristics is presented. To test the algerian in this paper, a system for selecting development path, which reflected algorithm was developed. The development project for web-based system were also adopted to the system for selecting development path. In addition, provened hand-worked project path process differed from machine-worked project path process. The reason why it differs is that outputs were mixed or their names were changed. The effect is to select easily software development route suitable for project environment and characteristics.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.7 no.6
• /
• pp.1351-1359
• /
• 2003

Extreme programming is the most representative methodology among agile software development methodologies which is agile in business environment which change fast. As software industry is matured, usability of software quality characteristics is emphasized gradually, but effort to obtain usability in extreme programming is insufficient. To improve usability of extreme programming, in this thesis, a software life cycle is defined by six phase as exploration, planning, iterations to release, productionizing, maintenance, and death phase. In this thesis, an extreme programming process which can improve usability is proposed by definition of 11 activities including integration testing and acceptance testing for usability testing, The proposed process is validated with four aspects. The proposed process is enhanced to support acceptance testing activity. The proposed extreme programming process is able to support CMM level 4 and quality assurance practice of CMM.

• KIPS Transactions on Computer and Communication Systems
• /
• v.5 no.9
• /
• pp.275-284
• /
• 2016

The software used in the nuclear safety field has been ensured through the development, validation, safety analysis, and quality assurance activities throughout the entire process life cycle from the planning phase to the installation phase. However, this evaluation through the development and validation process needs a lot of time and money, and there are limitations to ensure that the quality is improved enough. Therefore, the effort to calculate the reliability of the software continues for a quantitative evaluation instead of a qualitative evaluation. In this paper, we propose a reliability evaluation method for the software to be used for a specific operation of the digital controller in a nuclear power plant. After injecting weighted faults in the internal space of a developed controller and calculating the ability to detect the injected faults using diagnostic software, we can evaluate the software reliability of a digital controller in a nuclear power plant.