• Journal of Convergence Society for SMB
• /
• v.2 no.1
• /
• pp.59-67
• /
• 2012

As industrial software domain is recognizing with one of areas producing high added values, almost software company is running around in securing skilled workers. However, the hiring of software engineers without the consideration of long-term business goals can be caused the lack of manpower again. Also if there is no strategic workforce management plan, it is impossible to gain high performance despite many software engineers have been employed. One of ways to empower the software development capability, this paper identifies the software job functions in detail and proposes how to define the competency profile for the job function. We also propose the career path management scheme using the profile. The proposed workforce management approach which is based on the competency profile, enables to keep the appropriate size of human resources, and to achieve the business performance of software organization.

• The Journal of Information Systems
• /
• v.13 no.1
• /
• pp.1-20
• /
• 2004

Most of the software development projects bear risks that need analysis and management. Risk management plays a critical role for the success of software project management. In this study, we have used delphi method to delineate critical risk factors. The study pulls out 20 project risk factors from 21 project managers. It is certainly clear that certain features are more risky than others. Our study shows that unrealistic cost estimation and changes in scope and objective are more risky than other features.

• Industrial Engineering and Management Systems
• /
• v.11 no.1
• /
• pp.70-81
• /
• 2012

The subject of "Design Requirements" (DR) is central to the design of software and engineering systems. The main reason for this is that quality aspects are usually closely tied to requirements, among other things. In this review paper, we consider how the subject of requirements is being managed in these two seemingly different design disciplines. Two important aspects are covered, namely: (a) requirements development, describing various activities leading to requirements documentation, and (b) requirements change management, describing various activities needed for the proper treatment of the inevitable changes in requirements. Similarities and differences on how these two aspects are handled in software and engineering systems are highlighted. It is concluded from this literature survey that the management of software requirements is quite coherent and well established as a science. On the other hand, management of engineering systems requirements suffer from being unstructured, in particular when requirements changes are involved. Important gaps and future important research areas are identified.

• Proceedings of the Safety Management and Science Conference
• /
• 2001.05a
• /
• pp.77-81
• /
• 2001

Burn-in is a test procedure to find and eliminate the inherent initial failure of a product during or at the final stage of production process. Software testing is the validation and verification process which is used to cut off the faults from a software. The two have the common function and objective of "debugging". This article summarizes some significant models on the optimal hardware and software burn-in time, and provides the relevant paper lists. The need for the development of the unified burn-in policy of a hardware-software system is addressed.addressed.

• Management & Information Systems Review
• /
• v.18
• /
• pp.201-222
• /
• 2006

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.

• Journal of the Korea Society of Computer and Information
• /
• v.25 no.11
• /
• pp.147-155
• /
• 2020

System support software is one of the software that makes up ship combat management system and has the characteristics of being mounted in the combat management systems of all ships but with little functional change. However, despite these characteristics, software modifications due to equipment, etc. are inevitable in the application of new ships. Modification of software causes software reliability testing which is a key factor in increasing development costs. In this paper, the structure of the existing system support software was analyzed to identify and supplement the code change factors, and the system support standardization architecture was designed. The feature model elicited common and variable elements of system support software, and applied white-box reuse to improve software design. In addition, the results of comparing existing system support software with the new architecture in terms of development elements and time to perform reliability test were presented to verify the effectiveness of the new one.

• Korean Management Science Review
• /
• v.23 no.2
• /
• pp.75-91
• /
• 2006

The purpose of this paper is to propose a new software development cost estimation method using SVR(Support Vector Regression) SVR, one of machine learning techniques, has been attracting much attention for its theoretic clearness and food performance over other machine learning techniques. This paper may be the first study in which SVR is applied to the field of software cost estimation. To derive the new method, we analyze historical cost data including both well-known overseas and domestic software projects, and define cost drivers affecting software cost. Then, the SVR model is trained using the historical data and its estimation accuracy is compared with that of the linear regression model. Experimental results show that the SVR model produces more accurate prediction than the linear regression model.

• The KIPS Transactions:PartD
• /
• v.9D no.1
• /
• pp.81-90
• /
• 2002

More than 50% of defects and errors in the software development projects are related to the requirements[14]. But the development methodologies can not provide enough supports to the requirements management and changes. In the real world, the requirements keep changing as the requirements at the early development phase are usually incomplete, the developer′s understanding of the problem will be constantly changed during the software process, and new requirements may emerge with the organizational and environmental changes. In this paper, a requirements management process that can be integrated into the development methodologies is proposed to extend the requirements management over the whole development life-cycle and to support the requirements changes at the design/implementation/test phases. To evaluate the proposed process, it was compared to the existing requirements managements processes and models, and examined through a integration test with a widely used development methodology "MaRMI" to show the expected improvements at each development phase.

• Proceedings of the Computational Structural Engineering Institute Conference
• /
• 2008.04a
• /
• pp.532-537
• /
• 2008

Existing management of bridge is being writing management paper at field and computing at office. These are instability factor on bridge structure because of authenticity deterioration, disutility data management. Therefore, this paper is possibility expedient and objectivity inspection considering check situation at field for solve these problem. And development software which is intelligent bridge maintenance based Ubiquitous. This software can increase authenticity of data through computerization of maintenance data and reduce of time. Also, we confirm effective and facilitate maintenance management using ubiquitous.

• Korean Management Science Review
• /
• v.19 no.2
• /
• pp.191-204
• /
• 2002

As the portion of information systems (IS) budget to the total government budget becomes greater, the cost estimation of IS development and maintenance projects is recognized as one of the most important problems to be resolved for scientific and efficient management of IS budget. Since IS budget makes much effect on the delivery time, quality and productivity of IS projects, the exact cost estimation is also necessary for the successful accomplishment of IS projects. The primary concern in the cost estimation of IS projects is software cost estimation, which requires the measurement of the size of softwares. There are two methods for sizing software : line-of-code approach, function point model. In this paper, we propose a function-point-based model for estimating software cost. The proposed model is derived by collecting about fifty domestic IT projects in public sector and analyzing their relationship between cost drivers and development effort. Since the proposed model is developed by simplifying the function point model that can be used only when detailed user requirements are specified, it can be also applied at project planning and budgeting phase.