• KIISE Transactions on Computing Practices
• /
• v.23 no.8
• /
• pp.487-491
• /
• 2017

Open source software allows the users to freely use, copy, distribute and modify source code without any particular limitations, and this offers the advantages of low entry cost, fast and flexible development, compatibility, reliability and safety. The emergence of many useful open source projects has the advantage of achieving high levels of output with lower costs and time commitment for software development. However, this also increases the risks caused by the security vulnerabilities of the used open source software. There is still no separate process to verify security in using open source software. In this paper, we analyze the security weakness in open source and propose a secure coding scheme in adopting open source, which is known to be highly reliable from a security point of view.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.11 no.4
• /
• pp.1239-1247
• /
• 2010

In this paper, we were researched decision problem called an optimal release policies after testing a software system in development phase and transferring it to the user. The applied model of release time exploited infinite failure non-homogeneous Poisson process This infinite failure non-homogeneous Poisson process is a model which reflects the possibility of introducing new faults when correcting or modifying the software. The intensity function used Gompertz, Preto and Log-logstic pattern which has the efficient various property. Thus, optimal software release policies which minimize a total average software cost of development and maintenance under the constraint of satisfying a software reliability requirement becomes an optimal release policies. In a numerical example, after trend test applied and estimated the parameters using maximum likelihood estimation of inter-failure time data, estimated software optimal release time.

• Journal of the Korea Society of Computer and Information
• /
• v.15 no.5
• /
• pp.125-132
• /
• 2010

Decision problem called an optimal release policies, after testing a software system in development phase and transfer it to the user, is studied. The applied model of release time exploited infinite non-homogeneous Poisson process. This infinite non-homogeneous Poisson process is a model which reflects the possibility of introducing new faults when correcting or modifying the software. The failure life-cycle distribution used exponential and non-exponential family which has various intensity. Thus, software release policies which minimize a total average software cost of development and maintenance under the constraint of satisfying a software reliability requirement becomes an optimal release policies. In a numerical example, after trend test applied and estimated the parameters using maximum likelihood estimation of inter-failure time data, estimated software optimal release time.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.10 no.8
• /
• pp.1903-1910
• /
• 2009

In this paper, we were researched decision problem called an optimal release policies after testing a software system in development phase and transferring it to the user. The applied model of release time exploited infinite failure non-homogeneous Poisson process This infinite failure non-homogeneous Poisson process is a model which reflects the possibility of introducing new faults when correcting or modifying the software. The failure life-cycle distribution used the Weibull distribution which has the efficient various property which has the place efficient quality. Thus, optimal software release policies which minimize a total average software cost of development and maintenance under the constraint of satisfying a software reliability requirement becomes an optimal release policies. In a numerical example, after trend test applied and estimated the parameters using maximum likelihood estimation of inter-failure time data, estimated software optimal release time.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.14 no.2
• /
• pp.23-34
• /
• 2014

Though a dozen of different software life cycle models are suggested, there is no universal model which can satisfy all the characteristics of software. Organizations mix and match different life cycle models to develop a model more tailored for their systems and capabilities. We suggest overlapped-concurrent development life cycle model that is more suitable in various software development environment. Firstly, we divided the development process into abstract and implementation stage. Abstract stage is from software concept phase to detailed design starting time, and implementation stage is from detailed design phase to system testing phase. Next, the abstract stage introduced the overlapped phase concept that begins the next phase when the step is completed 20% by applying pareto's law. In the implementation stage, we introduced the concurrent development which the several phases are performed some time as when one use-case (UC) is completed the next development phase is started immediately. The proposed model has an advantage that it can reduce the inefficiency of development resource greatly. This model can increase the customer satisfaction with a great product at a low cost and on a short schedule. Also, this model can contribute to increase the software development success rate.

• Journal of the Korea Society for Simulation
• /
• v.32 no.3
• /
• pp.23-31
• /
• 2023

Software development involves a series of stages, including requirements analysis, design, implementation, unit testing, and integration testing, similar to those used in the system engineering process. This study utilized MathWorks' model-based design platform to develop multi-function radar software and evaluated its feasibility and efficiency. Because the development of conventional radar software is performed by a unit algorithm rather than in an integrated form, it requires additional efforts to manage the integrated software, such as requirement analysis and integrated testing. The mode-based platform applied in this paper provides an integrated development environment for requirements analysis and allocation, algorithm development through simulation, automatic code generation for deployment, and integrated requirements testing, and result management. With the platform, we developed multi-level models of the multi-function radar software, verified them using test harnesses, managed requirements, and transformed them into hardware deployable language using the auto code generation tool. We expect this Model-based integrated development to reduce errors from miscommunication or other human factors and save on the development schedule and cost.

• Journal of the Korea Computer Industry Society
• /
• v.7 no.3
• /
• pp.191-198
• /
• 2006

Area of software measurement is active more than thirty years. There is a huge collection of researches but still no concrete software development effort, duration and cost estimation model. The data sets used to conduct previous studies in the duration estimation model are often small and not too recent, these types of models should not be apply in recent projects that have complex architecture and various development environment. Therefore, Oligny et al. presents empirical models that predict software project duration in accordance with project platform based on project effort using the log data transformation. These models are based on the analysis of 396 project data provided by release 4 of the ISBSG Benchmark. Applying Oligny et al.'s models to 534 project data provided release 6 of the ISBSG Benchmark, the project duration is affected by development type more than development platform. Therefore, This paper presents the model of duration estimation according to development type. This paper proves the duration is more affected by development type than development platform. And, The model according to development type is more adequate for duration estimation.

• Journal of rehabilitation welfare engineering & assistive technology
• /
• v.11 no.4
• /
• pp.279-285
• /
• 2017

In this study, feasibility analysis was performed by estimating the costs and effects of daisy reading auxiliary machine development project. The development cost of a Daisy player device, hardware/prototype and software, with only essential functions and with low price was estimated to be \307,101,664, and the production cost for a player was calculated to be \112,000. The development of Daisy viewer software and input/output assistive devices, application, was estimated to be \284,294,08, and an input/output device was set a price of \6,600. Based on these results, we looked at the economic ripple effects on the people with disabilities by promoting daisy - reading assistive device development project. The results of this study could be used to determine whether the project is to proceed. It is expected that it provides valuable information to actively cope with the changing business environment in the future.

• Journal of Software Assessment and Valuation
• /
• v.17 no.2
• /
• pp.11-17
• /
• 2021

In this study, problems of software completeness appraisal are pointed out and their solutions are presented by analyzing appraisal cases and judicial precedents. Completeness appraisal, ready-made appraisal, defect appraisal, and cost appraisal have been classified as and have been evaluated with extant software completeness appraisals. From a legal point of view, and in judicial precedents, however, there is a big difference between the definition of completeness and the completion rate. This is because the degree of completeness is evaluated under the premise that the software's development is complete, whereas the ready-made appraisal inspects the development progress of unfinished software. Often, in cases involving software completion rate, the total completion level is calculated by weighting each step of the software development process. However, completeness evaluations use the software's realization-operation as its sole criterion. In addition, another issue not addressed in existing software completeness appraisal cases is that there is no mention of who is responsible for software defects, whereas in case law, the responsible party is determined by finding who caused the dispute. In this paper, we systematically classify these problems, and present a novel evaluation method that separates software completeness evaluations from software completion evaluations.

• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.398-413
• /
• 2003

Component-based Software Development(CBSD) supported by both component and reusability can reduce development time and cost, and also can achieve high productivity. To support component reusability systematically domain analysis and design in parallel with CBSD-process is needed. And also it is needed to suggest objective analysis process to fine out commonality and variability in domain, which is lacked in current domain analysis and design method. And to abstract domain component from the information which is well reflected in domain model, and to express it in domain architecture is needed. In this paper, we suggest the method to define, analyze and design domain systematically for enhancing reusability effectively in Component-base Software Development. We abstract components which can be reusable in domain, in other word, which have commonality from requirement analysis level. We sustain and refine them. And we reflect them to the products of each level. From these process, we can produce the domain component which have commonality. On this basis, we can design domain architecture. In this paper, to produce reusable software we investigate new systematic approach to domain analysis and design from the view point of software reusability.