• 경영과정보연구
• /
• 제15권
• /
• pp.245-262
• /
• 2004

As the competition between countries has become higher and the notion of software quality has been widely spread. it has been necessary to develop technologies that can ensure and produce high quality software. With the advent of information-oriented society. quality control has to transfer to the quality control activities focused on software system instead of those activities focused on hardware system. If so, how do we get to handle the quality control on the basis of the new approach. Also, as software applications have grown, so too has the importance of software quality. In order to manage software quality, the technology to specify and evaluate both the software product quality and development process quality objectively quantitatively is most important. To produce products of good quality, we need a more progressive quality control system according to the need of software development life cycle. In other words, we do software right the first time or build quality in the process. On the basis intermediate and final time or build quality in the process. On the basis of data achieved, we can evaluate the products according to the consequences of the data, What are the problems to contrive the software quality control system?, we con promote the quality of products. To achieved that goal, we con provide a suitable the technique and method of software quality control.

• 경영정보학연구
• /
• 제6권2호
• /
• pp.195-208
• /
• 2004

소프트웨어 규모가 대형화 됨에 따라 개발에 소요되는 시간과 인력도 대형화 되고 있으며, 또한 원하는 수준의 소프트웨어 품질을 얻기 위해 필요한 테스트 비용도 점점 더 증가하고 있다. 소프트웨어 프로젝트 개발 과정에서 품질 관리를 위해 다양한 결함 제거 기법들이 사용되고 있으나, 이러한 결함제거 기법과 결함 제거 시간이 전체 일정에 미치는 영향은 아직까지 체계적으로 분석되지 못하고 있다. 본 논문에서는 일정한 소프트웨어 품질 수준을 달성하기 위해 소요되는 시간을 소프트웨어 개발 일정 관리에 반영한 새로운 일정관리 모델을 제안한다. 제안된 모델은 CMU의 PSP/TSP (Personal Software Process/Team Software Process)를 적용하는 개발 과정에서 수집된 결함 정보, 결함 제거 시간, 평균 결함 제거시간 및 단계별 결함 제거율을 사용하여 일정 지연 여부를 실시간으로 추적할 수 있도록 하고 있다. 이를 위해 본 논문에서는 소프트웨어 품질 달성에 필요한 작업량을 일정 관리 측정체계와 동일한 측정체계에서 사용할 수 있도록 하는 품질 지수(Quality Value)를 새로 제안한다. 본 연구의 결과는 일정과 품질을 분리하여 관리하는 기존의 일정 관리 방법을 보완하여 프로젝트 관리자를 비롯한 모든 관계자가 품질 관리의 중요성을 인식하고 품질 저하 문제를 사전에 예방하는데 활용될 수 있을 것으로 기대된다.

• 한국통신학회논문지
• /
• 제22권9호
• /
• pp.1880-1889
• /
• 1997

CMS-MX(CDMA Mobile System-Mobile eXchange) 이동통신교환기 소프트웨어는 그 규모가 크고 새로운 기능 추가에 따른 지속적인 변경이 요구되기 때문에 체계적인 버전 관리를 필요로 한다. 그러나 CMS-MX 소프트웨어는 다양한 형태의 파일들로 구성되어 있고 고유의 소프트웨어 개발 체계를 따르기 때문에 범용의 버전 관리 시스템을 그대로 적용하기가 어렵다. 본 논문에서는 CMS-MX 소프트웨어의 개발 환경 및 개발 체계에 적합하도록 구현된 CMS-MX 소프트웨어 버전 관리 시스템을 소개하고 그 구성과 기능에 대해 기술하였다. CMS-MX 소프트웨어 버전 관리 시스템은 소프트웨어 형상과 소프트웨어 개발자 정보를 하여 파일의 등록관리, 버전제어, 그리고 정보 관리의 기능을 수행하며 파일 전체 저장, 파일 검증, 소프트웨어 종합 작업과의 연계등의 특징을 가지고 있다.

• 정보처리학회논문지D
• /
• 제12D권7호
• /
• pp.965-978
• /
• 2005

소프트웨어 개발 시, 일정과 품질에 저해 요인이 되는 결함이 다수 존재한다. 일정과 품질의 저해 요인을 제거하고 동시에 체계적으로 이를 관리하기 위하여 본 논문에서는 opportunity tree 프레임워크를 설계한다. 유사한 프로젝트를 수행 시 영역 전문가의 지식을 활용한 opportunity tree 발생되는 문제점을 예측, 대비할 수 있게 하여, 소프트웨어 프로세스를 개선할 수 있다 본 연구에서는 소프트웨어 개발 시 발생하는 일정관리에 대한 결함을 찾아내고, 원인을 식별 및 해결책을 제시하고자 한다.

• 한국컴퓨터정보학회논문지
• /
• 제21권10호
• /
• pp.115-123
• /
• 2016

In this paper, we propose a Model Driven Development using UML(Unified Modeling Language) in an efficient Combat System Software development methods. UML is managed by the OMG (Object Management Group) as a Unified Modeling Language. Recently, In developing the software for the system, development time is contrary to a short, while it must meet a number of requirements of our customers. If you develop a non-efficient software early, the structure of the software become more complex in proportion to the number of requirements. As a result, a serious problem in the system, such as an increase in defective products due to the lowering of the reliability and communication problems between the developer has occurred. To overcome those problems, the aim of this paper is to develop a reusable high efficient Combat System Software by applying Model-Centric Development (Not Code-Centric Development). If Combat System Software development method using the UML proposed in this paper is used, easy communication among developers can help reduce the serious errors in systems. Also, it has the advantage that the future needs of software maintenance/repair become easy by using high readability object Model.

• Journal of Information Processing Systems
• /
• 제16권6호
• /
• pp.1372-1390
• /
• 2020

An attractive user interface (UI) design with a clear user experience (UX) is the key for the success of applications. Therefore software development projects require very close collaboration between SI developers and front-end service developers. However, methodologies for software development only exist with inadequate development processes or work standards for collaboration. This survey derived 13 risk factors in developing UI/UX from 113 risk factors of IT projects through a questionnaire and factor analysis and proposed a collaboration-based UI/UX development model that can eliminate or mitigate six risks with high weights and reliability. To extract risk factors with high reliability, factor and reliability were analyzed to extract 13 major risks, and based on the expert opinions and the results of correlation analysis, UI/UX development stages were classified into planning, design, and implementation. The causal relationships between risks were verified through regression analysis. This study is the first to expertly analyze major risks based on collaboration in UI/UX development and derive a theoretical basis that can be used in project risk management. These findings are expected to provide a basis for research on development methodologies for higher levels of front-end services and to construct rational collaboration systems between SI practitioners and front-end service providers.

• 품질경영학회지
• /
• 제27권3호
• /
• pp.94-112
• /
• 1999

It is booming to use computer and information owing to the information society. As software applications have grown, so too has the importance of software quality. Therefore, software quality measurement and evaluation are necessary to satisfy the users who are using computers. The ISO/IEC 9126 defines six quality characteristics and twenty-one subcharacteristics including forty inter quality characteristics. We developed software measurement and evaluation technique using the check list in accordance with the ISO/IEC 9126 in design phase. We applied idea and concept of Total Quality Management in order to evaluate and measure the quality of software. Namely, it is the concept such as "you should do it right the first time." or "you have to build quality in the process." We executed the quantitative evaluation of software, also had shown the distinctive result in order that users and developers can find the errors easily. We evaluated the quality of academic softwares in order to verify developing technique at S college. As a result of the evaluation, this college has found it necessary to maintain the software as soon as possible because academic systems are not adequate for users at this present time.

• 한국컴퓨터정보학회논문지
• /
• 제16권12호
• /
• pp.113-120
• /
• 2011

정보시스템 구축 프로젝트의 복잡성과 규모가 점차 커지면서, 프로젝트가 실패하는 경우가 발생한다. 프로젝트의 실패의 원인을 분석해보면 사용자의 프로젝트 이해 부족, 불명확한 요구사항 및 요구사항변경 등으로 소프트웨어 개발 생명주기 중 요구사항 분석 단계에서 대부분의 원인을 찾을 수 있다. 본 논문은 소프트웨어 개발 프로젝트에서 요구분석을 통해 도출된 기능과 변경요구 기능간의 추적 등 개발 생명주기 전체 기간 동안 지속적인 요구사항 변경 관리가 가능하게 하는 도구를 설계하였다. 그리고 프로젝트 관련자들 사이에서 충분한 합의와 협의를 통해 공통의 이해를 구축하는 효과적인 의사소통을 지원하는데 필요한 기능에 대해 논의한다.

• International Journal of Computer Science & Network Security
• /
• 제24권8호
• /
• pp.145-152
• /
• 2024

Agile project management is an ongoing method to project completion that actually took place all across length of the project's life cycle. Because loop allows you to adapt as you go rather than maintaining a linear route, iterative methods are mainly applied in software development to ensure velocity and agility. Many pitfalls abound in agile software development adaptations that organizations fail to sidestep. New competitive challenges, fluctuating market dynamics, technological disruption, and the ever-changing demands of empowered customers confront organizations around the world. Organizations are all under tremendous pressure to adapt to change and deliver good products and services to customers more swiftly. Research measured at the challenges that could be encountered and offered advice for how agile development might flourish as it becomes a component of a company's family. Our paper gives a comprehensive review of the most significant obstacles that companies encounter while adopting agile techniques. Adaptability. The agile approach encompasses a variety of techniques, which each have different usage in various sectors. Because certain other standards existing today clash with agile methodology, the adaptation of any of the agile techniques in work environments posed a problem. In this paper, we will cover some of the challenges that firms face in adopting the agile software development life cycle.

• 제어로봇시스템학회:학술대회논문집
• /
• 제어로봇시스템학회 2000년도 제15차 학술회의논문집
• /
• pp.376-376
• /
• 2000

Several algorithmic models have been proposed to estimate software cost and other management parameters. In particular, early prediction of completion time is absolutely essential for proper advance planning and a version of the possible ruin of a project. However, estimation is difficult because of its similarity to export judgment approaches and for its potential as an expert assistant in support of human judgment. Especially, the nature of the Norden/Rayleigh curve used by Putnam, renders it unreliable during the initial phases of the project, in projects involving a fast manpower buildup, as is the case with most software projects. Estimating software development effort is more complexity, because of infrastructure software related to target-machines hardware and process characteristics should be considered in software development for DCS (Distributed Control System). In this paper, we propose software development effort estimation technique using adaptive neural fuzzy inference system. The methods is applied to case-based projects and discussed.