• Journal of Information Technology Services
• /
• v.9 no.4
• /
• pp.169-185
• /
• 2010

According to software growth, also software maintenance has been continuously improving. In addition, the existing concept of software maintenance process demands operational management and improvement of service task. However, when we perform maintenance task, we have several constraints about applying service based requirement to system. Therefore, in order to solve these problems, we need a study of task of process for service based maintenance. In this paper, we propose a Service based Software Maintenance Process. Proposed process based on MaRMI-RE standard for software development and maintenance and compares it with the service based representative standards. In a related works, we study activity of ITIL and identify activities and tasks for maintenance. After this, identified activities and tasks compare with activities of MaRMI-RE. And then, we derive activities and tasks of a Service based Software Maintenance Process. Finally, we validate a result by comparing the proposed process with a general service operational process.

• The KIPS Transactions:PartD
• /
• v.10D no.7
• /
• pp.1127-1136
• /
• 2003

Estimation of software project cost, effort and duration in the early stage of software development cycle is a difficult and key problem in software engineering. Most of models estimate the development effort using the function point that is measured from the requirement specification. This paper presents optimal team size and duration prediction based on function point in order to provide information that can be used as a guide in selecting the most Practical and productive team size for a software development project. We introduce to productive metrics and cost for decision criteria of ideal team size and duration. The experimental is based on the analysis of 300 development and enhancement software project data. These data sets are divide in two subgroups. One is a development project; the other is a maintenance project. As a result of evaluation by productivity and cost measured criteria in two subgroups, we come to the conclusion that the most successful projects has small teams and minimum duration. Also, I proposed that predictive model for team sire and duration according to function point size based on experimental results. The presented models gives a criteria for necessary team site and duration according to the software size.

• Journal of Korean Society for Quality Management
• /
• v.26 no.3
• /
• pp.141-149
• /
• 1998

It is of great practical interest to decide when to stop testing a software system in the development phase and transfer it to the user. This decision problemcalled an optimal software release one is discussed to specify the a, pp.opriate release time. In almost all studies, the software reliability models used are nonphomogenous Poisson process(NHPP) model with bounded mean value function. HNPP models with unbounded mean value function are more suitable in practice because of the possibility of introducing new faults when correcting or modifying the software. We discuss optimal software release policies which minimize a total average software cost under the constraint of satisfying a software reliability requirement. A numerical example illustrates the results.

• Journal of the Korea Society of Computer and Information
• /
• v.16 no.11
• /
• pp.57-65
• /
• 2011

Since software reuse and agile development methods are seen as ways to shorten development time and accept frequent requirement changes, respectively, there has been growing interest and research on integrating these approaches. But despite the increasing number of software companies which have successfully adopted agile development methods, there has been little research on reuse in agile methods to further improve productivity. In this paper, we identify a new type of reuse asset and propose a task factoring technique by taking advantage of iteration characteristics to support reuse in agile software development methods. In addition, we can apply the proposed technique and show prototyping of task reuse in a video rental application.

• Convergence Security Journal
• /
• v.12 no.6
• /
• pp.3-10
• /
• 2012

In this paper, make a study decision problem called an optimal release policies after testing a software system in development phase and transfer it to the user. When correcting or modifying the software, finite failure non-homogeneous Poisson process model, considering learning factor, presented and propose release policies of the life distribution, log linear type model which used to an area of reliability because of various shape and scale parameter. In this paper, discuss optimal software release policies which minimize a total average software cost of development and maintenance under the constraint of satisfying a software reliability requirement. In a numerical example, the parameters estimation using maximum likelihood estimation of failure time data, make out estimating software optimal release time.

• Convergence Security Journal
• /
• v.10 no.1
• /
• pp.55-61
• /
• 2010

It is of great practical interest to deciding when to stop testing a software system in development phase and transfer it to the user. This decision problem called an optimal release policies. In this paper, because of the possibility of introducing new faults when correcting or modifying the software, we were researched release comparative policies which based on infinite failure NHPP model and types of interval failure times. The policies which minimize a total average software cost of development and maintenance under the constraint of satisfying a software reliability requirement can optimal software release times. In a numerical example, applied data which were patterns, if intensity function constant or increasing, decreasing, estimated software optimal release time.

• The KIPS Transactions:PartD
• /
• v.8D no.6
• /
• pp.673-680
• /
• 2001

When the developers develop the software, the cost and time of the software development can be reduced by using blocks that are implemented previously. We call these implemented blocks components. In the early stage of Web-based Instruction, it didn't gain preference in spite of it's benefit of convenience. The main reason is, I think, the lack of generality at the education system which eventually results in unsatisfactory facilities compared with the requirement of teachers and students. And the early systems don't make good use of the plenty data in distributed environment, and don't show so good reliablity due to lack of systematic design and development. In this paper, we suggest WBI developing technology using the concept of WBSE. WBI developing is consist of component of pre-developed education software, integration of component using its reusability, and production of more requirement-satisfactory education software.

• Journal of KIISE:Software and Applications
• /
• v.29 no.12
• /
• pp.873-882
• /
• 2002

Estimation of development cost, effort and time is difficult and a key problem of software engineering in the early stage of software development. These are estimated by using the function point which is measured from a requirement specification. However, it is often a serious Question of the staffing level required for the software development. The purpose of this paper is to show us the model which can be used to estimate a size of development team. Three hundred one software projects have been analyzed and studied for the model. First, an analysis was conducted for statistical algorithmic model. After various data transformation and regression analysis, it was concluded that no good model was available. Therefore, non-algorithmic model was suggested for analysis, which has random distribution of residuals and makes good performance using RBF (Radial Basis Function) network. Since the model provides a standard to determine the required size of development team, it ran be used as management information.

• Journal of the Korea Safety Management & Science
• /
• v.6 no.3
• /
• pp.211-235
• /
• 2004

Component based design is perceived as a key technology for developing advanced real-time systems in a both cost- and time effective manner. Already today, component based design is seen to increase software productivity, by reducing the amount of effort needed to update and maintain systems, by packaging solutions for re-use, and easing distribution. Nowdays, a thousand and one companies in If(Information Technology) industry such as Sl(System Integration) and software development companies, regardless of scale of their projects, has spent their time and endeavor on developing reusable business logic. The component software is the outcome of software developers effort on overcoming this problem; the component software is the way propositioned for quick and easy implementation of software. In addition, there has been lots of investment on researching and developing the software development methodology and leading If companies has released new standard technologies to help with component development. For instance, COM(Component Object Model) and DCOM(Distribute COM) technology of Microsoft and EJB(Enterprise Java Beans) technology of Sun Microsystems has turned up. Component-Based Development (CBD) has not redeemed its promises of reuse and flexibility. Reuse is inhibited due to problems such as component retrieval, architectural mismatch, and application specificness. Component-based systems are flexible in the sense that components can be replaced and fine-tuned, but only under the assumption that the software architecture remains stable during the system's lifetime. In this paper, It suggest that systems composed of components should be generated from functional and nonfunctional requirements rather than being composed out of existing or newly developed components. about implements and accomplishes the modeling for the Product Control component development by applying CCD(Contract-Collaboration Diagram), one of component development methodology, to MRP(Material Requirement Planning) System

• Journal of Convergence Society for SMB
• /
• v.1 no.1
• /
• pp.55-65
• /
• 2011

Due to the rapid advance of IT technologies such as mobile communication, sensor network, wearable computer, and so on, the needs of embedded software has increased. In those domain areas, the development of low-power embedded software is one of critical issues to enhance servicability of the system because almost embedded system depends on battery-based power supply system. Therefore this paper identifies the factors that can reduce the power consumption in embedded software operation, and proposes the method that how to handle the factors in software development process. Even though the existing and general studies about power reduction has been performed with code-based analysis, this analysis approach can lead reworks when the requirement for power consumption was not met. Our proposed techniques will support the power reduction in embedded software development process whenever the code was not developed. Our proposed process for lop-power embedded software development can gives the high quality in power-related serviceability.