• The Transactions of the Korea Information Processing Society
• /
• v.5 no.4
• /
• pp.904-914
• /
• 1998

BPR(Business Process Reengineering), a radical improvement approach of business process, has been paying attention, and work-flow management and automation has been concentrated on progress velocity of business process and productivity of engineers. In software engineering, software process engineering which focus to process begin to be watched, and for the purpose of software productivity and quality progress and reduction of development term, study on SPR(Software Process Reengineering) is being progressed. In this paper, made workflow analysis and design method for construction of work-flow management system of software process to stand firm process reengineering methodology. In other words, we studied modeling process methods for SPR process, and software process structure and workflow analysis method which construct software process workflow model and specification definition method of workflow software.

• Journal of Information Technology Applications and Management
• /
• v.20 no.3
• /
• pp.1-18
• /
• 2013

Software architecture is the blueprint for a software system and should provide consistent guidelines for design, implementation, and maintenance throughout the entire lifecycle of the system. Components, interactions between the components, well-formed structure, reasons, and various perspectives reflecting various stakeholders' concerns changing through the phases of software lifecycle are the key elements of software architecture. The architect identifies and engages the stakeholders, understands and captures stakeholder's concerns including those regarding life cycle, and lets the concerns reflected in the architecture. To do so, architect should take into consideration various contextual elements regarding the system too. We make an extended list of the elements, especially those of business application software architecture, that the architect should take into consideration and construct a model of the relationships between the elements.

• Asia-Pacific Journal of Business Venturing and Entrepreneurship
• /
• v.7 no.4
• /
• pp.49-54
• /
• 2012

In this paper, a software policy considering testing time and the number of errors corrected is presented. The software is tested until a specified testing time or the time to a specified number of errors are corrected, whichever comes first. The model includes the cost of error correction and software testing during the testing time, and the cost of error correction during operation. It is assumed that the length of software life cycle has no bounds, and the error correction follows an non-homogeneous Poisson process. An expression for the total cost under the policy is derived. It is shown that the model includes the previous models as special cases.

• Asia pacific journal of information systems
• /
• v.20 no.2
• /
• pp.87-101
• /
• 2010

Software as a service (SaaS) is one of the most-talked about trends in IT. Unlike traditional perpetual licensing model, software applications are sold on subscription bases and services are provided over web by the vendors. It is said that SaaS can make vendors to invest more on R&D than on marketing while offering its customers better quality software applications at lower costs. By empirically comparing vendors providing their software applications either by SaaS or by traditional perpetual licensing model, we examine whether or not SaaS really increases overall customer benefits in terms of cost efficiency, software quality, and customization. We show that SaaS may not provide better quality or cost efficient software applications than perpetual licensing does. Then we provide two practical tools which are useful for customers to evaluate whether SaaS is better than perpetual licensing for the purposes of software applications they want to adopt.

• The Journal of Society for e-Business Studies
• /
• v.7 no.2
• /
• pp.173-190
• /
• 2002

Over the past decade, numerous software managers and engineers have been concerned with measuring the size and complexity of software systems. Function point analysis technique is one of the most popular software sizing techniques. A reasonable software development plan through cost and time estimation should be a prerequisite for the successful project at the beginning stage of the project. It is generally known that software size measurement is useful for this kind of estimation and the function point analysis technique would be more effective than the others. However, it is difficult to apply the technique to object-oriented methodology widely used in the software industry. Thus, the purpose of this study is to present a case study on how to apply function point analysis technique to sizing of the software systems based on UML. The results of this study can be useful to managers and engineers.

• Journal of Distribution Science
• /
• v.11 no.2
• /
• pp.45-55
• /
• 2013

Purpose - The development and implementation of OSS (Open Source Software) led to a dramatic change in corporate IT infrastructure, from system server to smart phone, because the performance, reliability, and security functions of OSS are comparable to those of commercial software. Today, OSS has become an indispensable tool to cope with the competitive business environment and the constantly-evolving IT environment. However, the use of OSS is insufficient in small and medium-sized companies and software houses. This study examines the need for OSS Intermediaries in the Software Distribution Channel. It is expected that the role of the OSS Intermediary will be reduced with the improvement of the distribution process. The purpose of this research is to prove that OSS Intermediaries increase the efficiency of the software distribution market. Research design, Data, and Methodology - This study presents the analysis of data gathered online to determine the extent of the impact of the intermediaries on the OSS market. Data was collected using an online survey, conducted by building a personal search robot (web crawler). The survey period lasted 9 days during which a total of 233,021 data points were gathered from sourceforge.net and Apple's App store, the two most popular software intermediaries in the world. The data collected was analyzed using Google's Motion Chart. Results - The study found that, beginning 2006, the production of OSS in the Sourceforge.net increased rapidly across the board, but in the second half of 2009, it dropped sharply. There are many events that can explain this causality; however, we found an appropriate event to explain the effect. It was seen that during the same period of time, the monthly production of OSS in the App store was increasing quickly. The App store showed a contrasting trend to software production. Our follow-up analysis suggests that appropriate intermediaries like App store can enlarge the OSS market. The increase was caused by the appearance of B2C software intermediaries like App store. The results imply that OSS intermediaries can accelerate OSS software distribution, while development of a better online market is critical for corporate users. Conclusion - In this study, we analyzed 233,021 data points on the online software marketplace at Sourceforge.net. It indicates that OSS Intermediaries are needed in the software distribution market for its vitality. It is also critical that OSS intermediaries should satisfy certain qualifications to play a key role as market makers. This study has several interesting implications. One implication of this research is that the OSS intermediary should make an effort to create a complementary relationship between OSS and Proprietary Software. The second implication is that the OSS intermediary must possess a business model that shares the benefits with all the participants (developer, intermediary, and users).The third implication is that the intermediary provides an OSS of high quality like proprietary software with a high level of complexity. Thus, it is worthwhile to examine this study, which proves that the open source software intermediaries are essential in the software distribution channel.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2014.05a
• /
• pp.63-65
• /
• 2014

Open source software has a feature that offers its service by the subscription method without getting a license fee. Therefore, this business style needs a different form of estimate criteria from other proprietary software, which is paid by license fees and maintenance service fees. However, consumers, including the public sector, don't understand this feature. This problem has kept the open source software business from attaining prosperity. I would like to provide a model for the estimate criteria that can apply to the open source software business by investigating and developing various advanced research and market examples.

• The Journal of Society for e-Business Studies
• /
• v.22 no.2
• /
• pp.39-60
• /
• 2017

Software product line engineering is widely recognized as an effective way for systematic software reuse, and many studies have been conducted to convert existing software development practices and processes into software product line. In order to convert existing software development into product line, a lot of investments are required such as dedicated development units, appropriate process selection and adaptation, and tool support. In particular, small businesses need business cases and specific practices for applying software product line engineering before its full-scale adoption. In this paper, we present a practical case of applying software product line engineering to the development of web system families and a process of systematically building and reusing software assets. To do this, we analyzed a number of web development projects and presented the experiences and various considerations of small software companies adopting software product line.

• Proceedings of the Korean Information Science Society Conference
• /
• 2003.10b
• /
• pp.247-249
• /
• 2003

Currently there are a variety of different tools may be used to analyze, model, describe and document a business process. However, it is difficult to exchange the information of a business process created in different tools because of the distinct information formats used in different tools. The XML Process Definition Language (XPDL) of the Workflow Management Coalition (WfMC) forms a common interchange standard that enables products to continue to support arbitrary internal representations of process definitions with an import/export function to map to/from the standard at the product boundary. Generally a business process model can be represented by the UML activity diagram, but there is a difficult task to directly generate an XPDL document from a business process model represented by the standard activity diagram. In the paper we will propose an approach to generate an XPDL document from a business process model represented by the extended UML activity diagram.

• International Journal of Contents
• /
• v.13 no.1
• /
• pp.38-44
• /
• 2017

Increased use of software and complexity of software functions, as well as shortened software quality evaluation periods, have increased the importance and necessity for automation of software testing. Automating software testing by using machine learning not only minimizes errors in manual testing, but also allows a speedier evaluation. Research on machine learning in automated software testing has so far focused on solving special problems with algorithms, leading to difficulties for the software developers and testers, in applying machine learning to software testing automation. This paper, proposes a new machine learning framework for software testing automation through related studies. To maximize the performance of software testing, we analyzed and categorized the machine learning algorithms applicable to each software test phase, including the diverse data that can be used in the algorithms. We believe that our framework allows software developers or testers to choose a machine learning algorithm suitable for their purpose.