• The KIPS Transactions:PartD
• /
• v.10D no.4
• /
• pp.697-708
• /
• 2003

In a software product line approach, developers first develop common software architecture and components by analyzing the characteristics of all software members, and then produce each application by integrating components. The approach is considered very effective means for developing and maintaining in parallel a software product family. Main disadvantage of this approach is that it requires a big up-front investment in preparing product line. Therefore, it takes time to deliver the first version. In this paper, we present an incremental method to develop software families, which requires small additional cost for initial versions and allows an organization to move smoothly to full-scale product line. We present our method by explaining how to record and upgrade the results of variations analysis, and show the application of our method by developing a family of YBS. Our method is a low-risk approach that can be effectively applied to an organization that starts developing software systems but has to deliver the first versions quickly to the market.

• Journal of Information Processing Systems
• /
• v.14 no.3
• /
• pp.607-620
• /
• 2018

The problem surrounding methods of implementing the software testing process has come under the spotlight in recent times. However, as compliance with the software testing process does not necessarily bring with it immediate economic benefits, IT companies need to pursue more aggressive efforts to improve the process, and the software industry needs to makes every effort to improve the software testing process by evaluating the Test Maturity Model integration (TMMi). Furthermore, as the software test process is only at the initial level, high-quality software cannot be guaranteed. This paper applies TMMi model to Automobile control software testing process, including test policy and strategy, test planning, test monitoring and control, test design and execution, and test environment goal. The results suggest improvement of the automobile control software testing process based on Test maturity model. As a result, this study suggest IT organization's test process improve method.

• The KIPS Transactions:PartD
• /
• v.11D no.5
• /
• pp.1105-1122
• /
• 2004

The organization and company's effort to improve software qualify contributes to the increase of software productivity and quality in some sense. However, it has not been a solution of root causes. This result is caused not because of people or technology, but process in-stitutionalization. Recently SQA (Software Quality Assurance), which provide mechanism to make sure that the software development process and products follow the assigned requirements, plan and standards, is applied to achieve the quality improvements. Several standards and models are developed for SQA activities. However, those standards and mode]s are written in form and do not provide information related to the detailed procedures, methods and outputs. Therefore, the organizations that want to adopt those models or standards have to put a lot of effort to acquire the knowledge about the models and to set up SQA Process that is tailored to meet organization's goal and objectives. In this research, we developed SQA support package to support the organization to develop their SQA process in more convenient and systematic ways. With this package, the organizations can establish SQA Process by tailoring those features necessary to reflect organization's characteristics. We expect this package contribute the organizations in a way that it reduce the effort and cost for establishing SQA process.

• Journal of Information Technology Applications and Management
• /
• v.27 no.2
• /
• pp.37-50
• /
• 2020

This paper is very exploratory and addresses the issue 'Is a general quality model of software possible?'. If possible, how specific can/should it be?' ISO 25000 Series SQuaRE is generally regarded as a general quality model which can be applied to most kinds of software. Usability is one of the 8 characteristics of SQuaRE's Product Quality Model. It is the main issue associated with SQuaRE's Quality in Use Model too. it is the most important concept associated software quality since using is the only ultimate goal of software products. Playability, however, is generally regarded as a special type of usability, which can be applied to game software. This common idea contradicts with the idea that SQuaRE is valid for most kinds, at least many kinds, of software. The empirical evidences of this paper show that SQuaRE is too specific to be a general quality model of software.

• KIPS Transactions on Software and Data Engineering
• /
• v.3 no.11
• /
• pp.465-470
• /
• 2014

The SP quality assessments from national IT industry promotion agency of Korea(NIPA) assesses ability of software development process. And the SP quality assessments is getting popular over the nation. But, in the SP quality assessments, there is no concern about security attribute. In this paper new secure process base on ISO 27001 is proposed for the organization that is already passed SP quality assessments. This process can detect security threatening factors and gives chance to protect those factors. Furthermore, since detected security weaknesses can be used as a measurement, the system can be managed in aspect to security attribute.

• The Korea Genome Conference
• /
• 2005.09a
• /
• pp.92-92
• /
• 2005

• Korean Management Science Review
• /
• v.9 no.1
• /
• pp.31-40
• /
• 1992

The size of software collection at any organization is increasing rapidly with the use of computer becomes popular for various applications. This trend points out the importance of proper 'catalog'or 'directory' for software collections, however, only 'title list' is found in practice. The problem of no proper directory with software collection would be more serious than the problem with book collection since browsing is not possible with softwares. Many of the expensive softwares will be a waste of money to purchase and to hold if no catalog about them is provided. In this paper the difficulties in applying AACR2 to software cataloging and the most important characteristic of computer software are discussed as well as presenting the necessity of localized information due to the requirement of a machine to be used, the difficulty using subject-based-call-number scheme, an expected way of searching software to design a location indicator, software qualifications to be cataloged, and so on. In addition, an analysis of randomly selected softwares after a cataloging practice is followed.

• Journal of Information Technology Services
• /
• v.8 no.3
• /
• pp.159-169
• /
• 2009

The issue of method of software testing process implementation has recently been in the spotlight in korea and some vendor make every effort to improve the software testing process through the evaluation of TMMi. The level of software process is at initial level, nevertheless, so the high quality of software is not guaranteed. This paper apply to the TMMi Level2 Assessment criteria of Automobile control software testing process. The test policy and strategy, test planning, test monitoring and control, test design and execution, test environment goal. The result need to emerge development process connection on the test policy and strategy process, test planning process etc. Also, the study analyzed the infra structure to reach the repeated level via key process area. As the result the process implementation in organization suggests the policy development and the implementation activity. Finally, the practical can refer to this paper in order to implementation the software testing process.

• International journal of advanced smart convergence
• /
• v.9 no.4
• /
• pp.167-172
• /
• 2020

In the 4th industrial revolution, there are many projects for diverse software applications of smart city environments. Most of the stakeholders focus on considering software quality for their developed software. Nobody doesn't guarantee requirement satisfaction after complete development. At this time, we can only work on user acceptance testing for requirement satisfaction on frequently changing requirements. Why keeps the requirement traceability? This traceability is to identify risks related to requirements, to assure correct software development based on customer requirements. To solve this, we are researching how to implement requirement traceability across each artifact's relationship to each activity of a whole development lifecycle.

• Genomics & Informatics
• /
• v.13 no.4
• /
• pp.119-125
• /
• 2015

RNA is a polymeric molecule implicated in various biological processes, such as the coding, decoding, regulation, and expression of genes. Numerous studies have examined RNA features using whole transcriptome sequencing (RNA-seq) approaches. RNA-seq is a powerful technique for characterizing and quantifying the transcriptome and accelerates the development of bioinformatics software. In this review, we introduce routine RNA-seq workflow together with related software, focusing particularly on transcriptome reconstruction and expression quantification.