• Journal of Korean Society for Quality Management
• /
• v.52 no.2
• /
• pp.357-376
• /
• 2024

Purpose: The purpose of this study is to design an objective and comparable diagnostic system for diagnosing the technology level of military maintenance depots and verify its actual applicability. Methods: Literature Review, Capability Maturity Model Integration, Analytic Hierarchy Process. Results: Military maintenance depot maintenance quality level diagnosis items, Maintenance quality level by maintenance technology area, Guidelines for diagnosing maintenance quality level, Quality level comparison results by area and implications for improvement. Conclusion: In order to systematically evaluate the maintenance quality of military maintenance depots, this study was conducted with the goal of designing an overall maintenance quality diagnosis system, including diagnosis areas, diagnosis items, and a diagnosis score award system, by improving the existing evaluation method. In addition, the newly developed maintenance quality diagnosis system was applied to actual evaluation activities and the results were returned to members, confirming the usefulness of the developed maintenance quality diagnosis system in the field.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2012.10a
• /
• pp.210-213
• /
• 2012

The recently developed military system adopts System Engineering for quality insurance. The process of military system's development basically adopts specification(MIL-STD-499) and system engineering(ISO/IEC 15288) that was developed by America. Recently the level of company's capability maturity is granted by measurement and assessment for the level of CMM or CMMI that was developed by Carnegie Mellon University. This article introduces adopted range of process that developed military system adopted additional process of CMM. This article writes range of process for military system that is developing device adopted diverse process in the future.

• Journal of Internet Computing and Services
• /
• v.10 no.5
• /
• pp.195-209
• /
• 2009

The embedded software has been become more important than the hardware in mobile systems in ubiquitous society. The improvement models such as CMMI(Capability Maturity Model Integration) and SPICE(Software Process Improvement and Capability dEtermination) are used to improve the quality of software in general systems. Software process improvement is also necessary for mobile embedded software development to improve its quality. It is not easy to apply the general software improvement model to the mobile embedded software development due to the high cost effectiveness and heavy process. On the other hand, XP has the characteristics on focused communications with customers and iteration development. It is specially suitable for mobile embedded software development as depending on customer's frequent requirement changes and hardware attributes. In this paper, we propose a framework for development small process improvement based XP(eXtreme Programming)'s practice in order to accomplish CMMI level 2 or 3 in mobile embedded software development at the small organizations. We design and implement the Mobile Embedded Software Process Improvement System(MESPIS) to support process improvement. We also suggest the evaluation method for the mobile embedded software development process improvement framework with CMMI coverage check by comparing other process improvement model. In the future, we need to apply this proposed framework to real project for practical effectiveness and the real cases quantitative. It also include the enhance the functionality of MESPIS.

• Journal of Internet Computing and Services
• /
• v.9 no.6
• /
• pp.155-163
• /
• 2008

Project Monitoring and Control is one of the required activities in project management. This activity provides the information about whether a project is making a progress as it is planned. It is usually performed in weekly meetings or milestone meetings where the project manager checks the project's current status based on project measures such as schedule, cost and work performance. One of the popular method for project monitoring and control is EVM(Earned Value Management). The major characteristic of EVM is that it uses only one measure 'cost' for schedule and work performance so that it enables 2 independent graphs to be illustrated in one integrated graph based on cost. For applying EVM to a project, it is essential to break whole work to work packages and to assign value of cost to each work package at the initial stage of the project. Therefore EVM is well matched with the lifecycle which requires whole plan at the beginning of project. However, in XP(eXtreme Programming), whole customer requirements are difficult to define and to make a complete plan at the beginning and are more detailed in each Iteration. Therefore EVM is not comfortable method for XP. Therefore in this research we suggest 3 layer EVM which can be applied in XP, and develop a process guidelines based on CMMI(Capability Maturity Model Integration) PMC(Project Monitoring and Control) process area.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2005.05a
• /
• pp.251-254
• /
• 2005

소프트웨어 품질의 중요성이 커짐에 따라, 기업들은 품질을 높이기 위해 테스트에 많은 노력을 기울이고 있다. 최근에는 테스트 성과를 높이기 위한 방법중의 하나로 테스트 프로세스 개선이 주목 받고 있다. 이를 위해 기업들은 SW-CMM(Capability Maturity Model for Software), CMMI(Capability Maturity Model Integration)와 같은 일반적인 프로세스 개선 모델들이나, TMM (Test Maturity Model), TPI (Test Process Improvement Model), TCMM (Testing Capability Maturity Model)과 같은 테스트 프로세스 개선 모델들을 적용하고 있다. 그러나 일반적인 프로세스 개선 모델들은 테스트 관련 이슈를 충분히 다루고 있지 않고, 테스트 프로세스 개선 모델들은 구조가 불완전하거나 내용이 충분하지 않아 적용 시 많은 어려움이 있다. 이에 본 논문에서는 TMM 과 CMMI 를 기반으로 조직들의 테스트 프로세스 확립이나 개선을 지원할 수 있는 새로운 테스트 프로세스 성숙도 모델인 TPMM(Test Process Maturity Model)을 연구, 개발하였다. 개발된 TPMM 을 통해 조직에서 테스트 프로세스를 개선하고, 심사하는 것을 지원할 수 있을 것으로 기대된다.

• The KIPS Transactions:PartD
• /
• v.12D no.7 s.103
• /
• pp.937-946
• /
• 2005

In the current marketplace, there are maturity models, standards, methodologies and guidelines that can help an organization improve the way it does business. All SPI models including ISO/IEC I5504 and CMMI provide the capability level of software process. However, most available improvement models focus on a specific goals and Practices of the processes So my assessors need an objective process measure how to estimate achievement of goals and practices. We proposed quantitative process capability metric (PCM) which can determine the degree of capability And the effective measuring approach help SPI assessor as well as organization unit.

• Journal of Software Assessment and Valuation
• /
• v.16 no.2
• /
• pp.87-98
• /
• 2020

Recently, IoT, artificial intelligence, cloud, big data, and mobile fields have converged, leading to a new industrial era called the 4th industrial revolution. This 4th industrial revolution has been expanded to all industry area and Software has been taken as important role in this revolution. Thus Software Safety is the huge factor because Software is highly relevant to human safety in accordance with Software expansion. However this Software Safety has been focused on not organization improvement activities but current design/development, In this paper, to solve this issue, Software Safety Maturity level and relevant Process Area is defined. This study is expected to contribute to systematic software safety activities.

• The Journal of Society for e-Business Studies
• /
• v.11 no.4
• /
• pp.21-32
• /
• 2006

When Enterprise Architecture(EA) is defined and applied, it is needed to assess the EA capability, and to identify guides for improvement. According to these needs, this paper presents an enterprise architecture maturity model to assess the EA capability, to identify the details for improving EA, to suggest the guides for improvement, and to support decision-making for investment. The model which refers to the continuous representation of CMMI consists of 5 maturity levels, 4 capability areas including 15 capability elements, and capability indications to make a determination of maturity level by capability elements. The model concentrates on the development/stabilization of EA and the connection/coordination over the federal agencies.

• Journal of Korea Society of Digital Industry and Information Management
• /
• v.9 no.4
• /
• pp.239-249
• /
• 2013

The role of software process is getting more important to make good quality softwares. One of the measures to improve the software process is Defect Removal Efficiency(DRE). DRE gives a measure of the development team ability to remove defects prior to release. It is calculated as a ratio of defects resolved to total number of defects found. Software Engineering Levels are usually decided by CMMI Model. The model is designed to help organizations improve their software product and service development, acquisition, and maintenance processes. The score of software engineering levels can be calculated by CMMI model. The levels are composed of the three groups(absent, average, and advanced). This study is to find if there is any difference among the three categories in term of the result of software engineering levels on DRE. We propose One way ANOVA to analyze influence of software engineering levels on DRE. Bootstrap method is also used to estimate the sampling distribution of the original sample because the data are not sampled randomly. The method is a statistical method for estimating the sampling distribution of an estimator by sampling with replacement from the original sample. The data were collected in 106 software development projects by the survey. The result of this study tells that there is some difference of DRE among the groups. The higher the software engineering level of a specific company becomes, the better its DRE gets, which means that the companies trying to improve software process can increase their good management performance.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.15 no.1
• /
• pp.28-35
• /
• 2012

We propose the live fire test process model based on systems engineering which consists of 4 phases i.e., review, setup, conduct and result. We also suggest the 4 phases acquisition model consisting of planning, execution, evaluation and disposal for test infrastructure. CMMI, TMMi and PMBOK are referred and hierarchial analysis method are adopted in developing the models. Thus, the detailed sub-processes are designed after defining higher level processes first. The higher level processes are defined by extracting common areas of all the test types. The low level processes for each specific test are designed by tailoring the higher level processes. By applying the proposed test process models into collaboration tool and information system, effective and systematic test processes for weapon systems are established.