• International Journal of Computer Science & Network Security
• /
• v.24 no.6
• /
• pp.17-22
• /
• 2024

Software cost and schedule estimation is usually based on the estimated size of the software. Advanced estimation techniques also make use of the diverse factors viz, nature of the project, staff skills available, time constraints, performance constraints, technology required and so on. Usually, estimation is based on an estimation model prepared with the help of experienced project managers. Estimation of software cost is predominantly a crucial activity as it incurs huge economic and strategic investment. However accurate estimation still remains a challenge as the algorithmic models used for Software Project planning and Estimation doesn't address the true dynamic nature of Software Development. This paper presents an efficient approach using the contemporary Constructive Cost Model (COCOMO) augmented with the desirable feature of fuzzy logic to address the uncertainty and flexibility associated with the cost drivers (Effort Multiplier Factor). The approach has been validated and interpreted by project experts and shows convincing results as compared to simple algorithmic models.

• Plant Journal
• /
• v.6 no.2
• /
• pp.56-61
• /
• 2010

In this paper, an integrated management software is developed to promote the business competitive power. The interoperability among the software accounts for an ever growing performance of petrochemical plant project. If the interoperability is built up, company has taken advantages of quality, schedule, cost, and safety by active communication. The advantage of an integrated management software is examined in three aspects. In efficiency aspect, It takes advantage of the saving about the various information and the standard of project performance procedure. In quality, the integration gave aid to a quality improvement through team collaboration and data management within project life cycle. In cost, poor communications between systems waste 30% of project costs. If information could be inputted once and used by all, reductions in delivery time up to 40% were possible. Therefore, 10% savings of engineering cost was also possible.

• Asia pacific journal of information systems
• /
• v.13 no.2
• /
• pp.199-217
• /
• 2003

Based on the IS literature on software project risk management, we developed an integrated model to investigate the risk factors and risk management factors in project development. We also analyzed the interrelation between project risk and project risk management. The questionaries are collected from 83 project leaders. We tested reliability and validity of the measure and analyzed the obtained data. The results support our risk-based hypothesis that shows the importance of risk management in reducing project risks and improving performance of project and process.

• Proceedings of the Safety Management and Science Conference
• /
• 2006.04a
• /
• pp.525-544
• /
• 2006

This paper is to introduce guidelines for project quality management system. International standards such as ISO 10006, IEC 62198, ISO/IEC TR 16326 and ISO 15188 are considered. This study is to discuss guidelines for quality management in projects, and application guidelines for project risk management, and guide for the application of ISO/IEC 12207 to software project management, and project management guidelines for terminology standardization.

• Journal of Information Technology Services
• /
• v.8 no.1
• /
• pp.125-142
• /
• 2009

The Ministry of Information and Communication announced "The Guideline for Management of Software Project" in October 2006. The public employees(acquirer) have to manage software projects with this guideline. The guideline was based on the International standard(ISO/IEC 12207) and IEEE standard(IEEE/EIA 12207), and was developed by considering the domestic software industry environment. The guideline can help to establish a software acquisition process for appropriate management of software projects, and the process can increase the management productivity of software projects. This study provides the explanation about the guideline with terms of 5W1H(who(user), what(summary), when(time to apply), where(domain of application), why(objective), how(method of use)) for understanding of the guideline.

• Journal of Information Technology Services
• /
• v.4 no.2
• /
• pp.33-46
• /
• 2005

Small/medium software businesses are often at a disadvantage when trying to win government contracts. Rather, most of small/medium software companies work with larger companies in the form of subcontracting. In its broadest meaning, subcontracting refers to the purchase of a part of a product or process from a different company. Appropriate subcontracting system helps both large and small software firms keep in healthy. However, many problems regarding subcontracting have been reported and recognized as one of major obstacles impeding advancement of the software industry. This paper examines the current problems in subcontracting system by conducting a field survey and proposes directions to improve the system for software project. It suggests revision of 'Software Industry Promotion Act' to induce fair relationship among software firms.

• Journal of the Korean Operations Research and Management Science Society
• /
• v.18 no.3
• /
• pp.129-149
• /
• 1993

The high level of activity in the development and maintenance of computer software makes the scheduling of software projects an importnat factor in reducing operating costs and increasing competitiveness. Software activity is labor intensive. Scheduling management of hours of software work is complicated by ther interdependencies between the segments of work, and the uncertainties of the work itself. This paper discusses issues of scheduling in software engineering management, and presents a modular decomposition model for software project scheduling, taking advantage of the facility for decomposition of a software project into relatively independent work segment modules. Modular decomposition makes it possible to treat scheduling as clustering and sequencing in the context of integer programming. A heuristic algorithm for the model is presented with some computational experiments.

• Journal of Software Assessment and Valuation
• /
• v.16 no.1
• /
• pp.21-26
• /
• 2020

The completeness appraisal of software is performed in various forms, such as assessing the completion level in the development process, calculating the defect rate, estimating the development cost, and calculating the redevelopment cost. Along with this, the problem that is often dealt with is estimation of the development time. Even in a dispute over completeness due to delays in software development, issues of calculating an appropriate development time required to develop a delivery software or a development time required for change requests are often included in the appraisal request. In this paper, we introduce the procedure and method for estimating the appropriate project time of software development so that the appraiser can be applied to the appraisal work for determining the completeness. The method is based on the manual for calculating the appropriate project period of software development project.

• Communications of the Korean Institute of Information Scientists and Engineers
• /
• v.30 no.9
• /
• pp.9-18
• /
• 2012

• Journal of the Korea Society of Computer and Information
• /
• v.16 no.12
• /
• pp.113-120
• /
• 2011

Information system gradually increases the complexity and scale of the project, while if the project fails to occur. To analyze the causes of failure of the project a lack of understanding of your project, unclear requirements and requirements change, etc. of the software development life cycle from requirements analysis phase is to find the source of most. In this paper, a software development project needs analysis derived from the traceability between features and functionality, and development needs throughout the life cycle requirements during the ongoing change management tool was designed to allow. And among those related to the project through consultation with a sufficient consensus to build a common understanding of effective communication will discuss the features required to support.