• Title/Summary/Keyword: Software R&D

Search Result 672, Processing Time 0.072 seconds

The Roles and Characteristics of R&D Investment in the IT Firms: IT Hardware Firms vs. IT Software Firms

  • Lee, Myunggun;Park, Jongpil;Park, Woojin
    • Asia pacific journal of information systems
    • /
    • v.25 no.1
    • /
    • pp.61-81
    • /
    • 2015
  • Investment in research and development (R&D) is critical in the information technology (IT) firms, where newer and better technology is a quintessential goal that directly affects innovation and competitive advantage. This study investigates how R&D investment influences firm performance and value, and how the effect of R&D investment differs between IT hardware and software firms. We also analyze the relationship between firm age and R&D investment in order to identify learning effects on continuous R&D investment. The empirical investigation in this study, based on longitudinal archival data from 2001 to 2010, found a significant effect of R&D investment on firm performance in IT firms. Further, this study demonstrates causal relationship between firm age, and verifies that learning effects are present in R&D investment. Moreover, the results are found to differ between IT hardware and IT software firms.

The Case Study on Application of Software Reliability Analysis Model by Utilizing Failure History Data of Weapon System (무기체계의 고장 이력 데이터를 활용한 소프트웨어 신뢰도 분석 모델 적용 사례 연구)

  • Cho, Ilhoon;Hwang, Seongguk;Lee, Ikdo;Park, Yeonkyeong;Lee, Junghoon;Shin, Changhoon
    • Journal of Applied Reliability
    • /
    • v.17 no.4
    • /
    • pp.296-304
    • /
    • 2017
  • Purpose: Recent weapon systems in defense have increased the complexity and importance of software when developing multifunctional equipment. In this study, we analyze the accuracy of the proposed software reliability model when applied to weapon systems. Methods: Determine the similarity between software reliability analysis results (prediction/estimation) utilizing data from developing weapon systems and system failures data during operation of weapon systems. Results: In case of a software reliability prediction model, the predicted failure rate was higher than the actual failure rate, and the estimation model was consistent with actual failure history data. Conclusion: The software prediction model needs to adjust the variables that are appropriate for the domestic weapon system environment. As the reliability of software is increasingly important in the defense industry, continuous efforts are needed to ensure accurate reliability analysis in the development of weapon systems.

Describing Activities to Verify Artifacts(Documents and Program) in Software R&D (소프트웨어 R&D에서 산출물(문서와 프로그램) 검증을 위한 활동)

  • Dashbalbar, Amarmend;Lee, Eun-Chul;Lee, Jung-Won;Lee, Byeongjeong
    • Journal of Internet Computing and Services
    • /
    • v.17 no.2
    • /
    • pp.39-47
    • /
    • 2016
  • In software R&D artifacts including documents and program code are produced. There are two kinds of software R&D artifacts: Research artifacts and development artifacts. Research artifacts include software R&D planning document, annual report, final report, research note and so on. Software development artifacts include software requirements, software design description, testing plan, test report, and program code. It is important to verify the documents and to test code to check the direction of the R&D. Moreover, we should check relationships as such completeness and consistency between research and development artifacts. The verification and testing help project manager and researchers understand what they do during software projects. Therefore, in this study, we present a process to verify documents and program in software R & D. In the process we check documents produced in software R&D and test program code. We describe the process by using Essence elements including alpha, activity, and competency. We present a case study to show the effectiveness of the process.

A Study on R&D Project Management of The Public Sector Open Software (공공분야 공개소프트웨어 R&D 프로젝트 관리방안에 대한 연구)

  • Shim, Ho-Sung;Woo, Chan-Hee;Chun, Sam-Hyun;Kim, Jong-Bae
    • Proceedings of the Korean Institute of Information and Commucation Sciences Conference
    • /
    • 2016.05a
    • /
    • pp.627-629
    • /
    • 2016
  • Open source software when promoting development in R&D has many advantages and is becoming an open software - based R&D projects continuously created in a number of countries. However, there are still limits to the creation of effective performance in R&D projects, as well as difficulty of the project implementation because it not yet established an appropriate management plan for the open source R&D projects in the public sector. Therefore, through investigating a number of previous studies and practices, we intend to enhance the effectiveness of the system by suggesting concrete measures for promoting and managing open source nature in a preperiodic point of view on the public sector open source software R&D projects.

  • PDF

Supporting Systematic Software Test Process in R&D Project with Behavioral Models

  • Choi, Hyorin;Lee, Jung-Won;Lee, Byungjeong
    • Journal of Internet Computing and Services
    • /
    • v.19 no.2
    • /
    • pp.43-48
    • /
    • 2018
  • Various artifacts that are produced as software R&D project progresses contain research plan, research report, software requirements and design descriptions, etc. When conducting a software R&D project, it is necessary to confirm that the developed system has implemented its research requirements well. However, various research results make it difficult to design appropriate tests. So, there is a practical need for us to comprehensively handle the planning, execution, and reporting of software test for finding and verifying information related to the research. In this paper, we propose a useful method for software test process in R&D project which supports model based software testing. The proposed method supports automation of test design and generation of test data by explicitly separating each step of System Under Test (SUT). The method utilizes the various models representing the control flow of the function to extract the information necessary for testing the system. And it supports a systematic testing process based on TMMi and ISO 29119. Finally, we show the validity of the method by implementing a prototype with basic functionality to generate test data from software behavioral models.

The Next Generation Energy Management System: Analysis and Performance Improvement of the Contingency Analysis Program (차세대 에너지 관리시스템: 상정사고 해석 프로그램 성능 개선 방안 분석)

  • Bae, Ae-Kyoung;Kang, Ho-Young;Kim, Young-In;Kim, Hong-Joo;Shin, Yong-Hark
    • Annual Conference of KIPS
    • /
    • 2014.11a
    • /
    • pp.134-136
    • /
    • 2014
  • 차세대 에너지 관리시스템에서 계통 해석 프로그램은 집중원격감시 시스템으로부터 취득된 데이터를 이용해 토폴로지, 상태추정, 조류계산, 상정사고, 고장해석 등의 해석 정보를 계통 운영자에게 전달한다. 지속적으로 증가하는 전력수요에 신속하게 대처하기 위해서 계통 해석 프로그램은 대규모 계통의 계획과 운영을 빠르고 정확하게 분석하여 대책을 수립할 수 있어야 한다. 본 논문에서는 계통 해석 프로그램들 중 특히 많은 시간이 소요되는 상정사고 해석 프로그램의 특성을 분석하고 성능 개선 방안을 제안한다.

Methods of Extracting and Providing R&D Documentation Guideline for Licensing Medical Device Software

  • Kim, DongYeop;Lee, Byungjeong;Lee, Jung-Won
    • Journal of Internet Computing and Services
    • /
    • v.20 no.3
    • /
    • pp.69-75
    • /
    • 2019
  • The safety and performance of medical device software is managed through life-cycle processes, which represent the entire process of research and development (R&D). The life-cycle process of medical device software is represented by an international standard called IEC 62304, ISO/IEC 12207. In order to license the product, the manufacturer must have document artifacts that comply with the IEC 62304 standard. However, these standards only describe the content of the activity and do not provide a method or procedure for documentation. Therefore, this paper suggests R&D documentation guidelines that assist medical device software developers to have R&D documents conforming to the standards. For this purpose, this study identifies the requirements related to documentation among the requirements existing in the standard and extracts them in the form of guidelines showing only the core information of the requirements. In addition, through the Web framework implemented based on this research, the developer can evaluate whether the technical documents are written in accordance with the R&D document guidelines. Medical device software manufacturers can efficiently produce high-quality research and development documents through R&D documentation guidelines, and they can have standards-compliantresearch and development documentation required for licensing procedures.

Towards Enacting a SPEM-based Test Process with Maturity Levels

  • Dashbalbar, Amarmend;Song, Sang-Min;Lee, Jung-Won;Lee, Byungjeong
    • KSII Transactions on Internet and Information Systems (TIIS)
    • /
    • v.11 no.2
    • /
    • pp.1217-1233
    • /
    • 2017
  • Effective monitoring and testing during each step are essential for document verification in research and development (R&D) projects. In software development, proper testing is required to verify it carefully and constantly because of the invisibility features of software. However, not enough studies on test processes for R&D projects have been done. Thus, in this paper, we introduce a Test Maturity Model integration (TMMi)-based software field R&D test process that offers five integrity levels and makes the process compatible for different types of projects. The Software & Systems Process Engineering Metamodel (SPEM) is used widely in the software process-modeling context, but it lacks built-in enactment capabilities, so there is no tool or process engine that enables one to execute the process models described in SPEM. Business Process Model and Notation (BPMN)-based workflow engines can be a solution for process execution, but process models described in SPEM need to be converted to BPMN models. Thus, we propose an approach to support enactment of SPEM-based process models by converting them into business processes. We show the effectiveness of our approach through converting software R&D test processes specified in SPEM in a case study.