• The KIPS Transactions:PartD
• /
• v.11D no.4
• /
• pp.873-884
• /
• 2004

This research provides the solution of defect problem and detection of defect and its causes that happen on software development. For developing a reliable software, a key factor is to find and manage defects that are during software development. Based on defect items analysis, we understand associated relation between defects and design defect opportunity tree. Developing the similar project, we can estimate defect and prepare to solve defect by using defect management opportunity tree.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.16 no.1
• /
• pp.691-696
• /
• 2015

The interest in software defects is growing. Companies are working on reducing them by various ways with a software development part, customer service part and quality management part. The defect data collected from them will be analyzed according to the condition and purpose to minimize the defect, and it will contribute to improving the quality of products. This study analyzed the software defect progress for companies based on the test maturity model, and set up the defect preventing process. They were applied to the project, and the number of defects decreased from 106 to 16. This study focused on the existing defect, which is a basic requirement for software quality management, and have importance by presenting a way to improve the software product quality with minimum resources.

• Journal of the Korea Computer Industry Society
• /
• v.3 no.3
• /
• pp.295-306
• /
• 2002

Successful project planning relies on a good estimation of the effort required to complete a project, together with the schedule options that may be available. Despite the extensive research done developing new and better models, existing software effort estimation models are present only the total effort and instantaneous effort function for the software life-cycle. Also, Putnam presents constant effort rate in each phase. However, the size of total effort are variable according to the software projects under the influence of its size, complexity and operational environment. As a result, the allocated effort in each phase also differ from project to project. This paper suggests the criteria for effort allocation in planning, specifying, building, testing and implementing phase followed by the project total effort. These criteria are derived from 183 different projects. This result can be considered as a practical guideline in management of project schedule and effort allocation.

• Knowledge Management Research
• /
• v.18 no.4
• /
• pp.287-306
• /
• 2017

This research focus on the effect of developers' participation structure in knowledge creation and knowledge sharing activities in open source software development projects. Based on preferential selection theory, hypotheses of relationship between a developers' concentration of knowledge creation/sharing activities and collaboration performance was derived. To verify the hypotheses, we use the Gini coefficient in the commit contribution of the developers (knowledge creation) and the centralization index in the repository issue network (knowledge sharing network). Using social network analysis, this paper calculates centralization index from developers in the issue boards in each repository based on data from 837 repositories in GitHub, a leading open source software development platform. As a result, instead of all developers creating and sharing knowledge equally, only a few of developers creating and sharing knowledge intensively further improve the performance of the open collaboration. In other words, a few developers predominantly providing commit and actively responding to issues raised from other developers enhance the project performance. The results of this study are expected to be used by developers who manage open source software project as a governance strategy, which could improve the performance of open collaboration.

• Journal of Engineering Education Research
• /
• v.21 no.6
• /
• pp.90-98
• /
• 2018

This paper proposes a framework of engineering education for product development processes based on product data management (PDM) software and 3D printing. The PDM software supports the product development process-oriented educational coursework, collaborative team projects and project-based learning environment. The 3D printing supports the prototyping step in the product development process and helps participants consider physical realization of their designs during the product design and development phases. The framework was implemented in an introductory course for engineering students to product design and development, and author found that it is important to support rich communication among participants including lecturers, teaching assistants and students to enhance the quality of education and to overcome the burden of learning various computer-aided tools and 3D printing techniques needed for the framework.

• Journal of KIISE:Software and Applications
• /
• v.30 no.3_4
• /
• pp.293-307
• /
• 2003

Object-oriented development has been generalized, but object-oriented project planning and scheduling techniques have not been studied enough. Furthermore, it is difficult to apply the conventional software management techniques to object-oriented projects. Especially, the large scaled projects are increasing, but the project planing techniques for these large scaled projects have not been proposed enough. In this paper, we propose systematic techniques for OO based project scheduling. We suggest a 7 step-process for deriving the OO project schedule from the use-case diagram which is describing the functional requirements of the system. The proposed process includes identifying use-cases, drawing preliminary chart through interdependency analysis, identifying characteristics of each use case, determining the number of iteration, assigning use-cases to iteration, considering available resource and constraints, drawing revised PERT chart. Each step has the explanation of the input, output, and the guidelines needed to perform the step. The project scheduling technique proposed in this paper ran be used effectively in the planning phase which the purpose is to plan a development schedule to yield the high quality software in minimum time.

• The Journal of the Korea institute of electronic communication sciences
• /
• v.17 no.4
• /
• pp.663-670
• /
• 2022

This study presents the method for integrating the software assets acquired before the weapon system software reliability test was not formed in the weapon system software development and management manual through JTDLS Batch II case. This paper describes the problems for applying manual's direction to JTDLS Batch II project, and decisions and expected effects.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.12 no.2
• /
• pp.233-241
• /
• 2012

The object of the project management is to succeed in the project. However, could you definitely judge that the result of project performance is a success? In addition, do both customer and developer agree with the result of your judgement? There are a lot of definitions and measure for the success and failure of the software development suggested, but there is no definite standard for the classification. This paper examines the measures in order to decide the development success and re-defines the success and the failure of the project. We suggest the measure and the standard that judge the project achievement based on these definitions. Applying the suggested measure and standard, it is possible to reduce arguments between the customer and the developer on the classification of the success and the failure.

• Journal of the Korea Computer Industry Society
• /
• v.2 no.6
• /
• pp.859-866
• /
• 2001

Successful project planning relies on a good estimation of the effort required to complete a project, together with the schedule options that may be available. Despite the extensive research done developing new and better models, existing software effort estimation models are present only the total effort and effort (or manpower： people per unit time) function for the software life-cycle. Also, Putnam presents constant effort rate in each subcycles. However, the size of total efforts are variable according to the software projects under the influence of its size, complexity and operational environment. As a result, the allocated effort in subcycle also differ from project to project. This paper suggests the linear and polynomial effort estimation models in specifying, building and testing phase followed by the project total effort. These models are derived from 128 different projects. This result can be considered as a practical guideline in management of project schedule and effort allocation.

• The KIPS Transactions:PartD
• /
• v.9D no.5
• /
• pp.865-876
• /
• 2002

Successful project planning relies on a good estimation of the effort required to complete a project, together with the schedule options that may be available. Existing software effort estimation models are present only the total effort and instantaneous effort function for the software life-cycle. Also, Putnam presents constant effort rate in each phase. However, the size of total effort varies according to the software projects under the influence of its size, complexity and operational environment. As a result, the allocated effort in each phase also differs from one project to another. This paper suggests models for effort allocation in planning, specifying, building, testing and implementing phases followed by the project size and development types. These models are derived from 155 different projects. Therefore, these models can be considered as a practical guideline in management of project schedule and effort allocation.