http://chineseinput.net/에서 pinyin(병음)방식으로 중국어를 변환할 수 있습니다.
변환된 중국어를 복사하여 사용하시면 됩니다.
Towards Enacting a SPEM-based Test Process with Maturity Levels
( Amarmend Dashbalbar ),( Sang-min Song ),( Jung-won Lee ),( Byungjeong Lee ) 한국인터넷정보학회 2017 KSII Transactions on Internet and Information Syst Vol.11 No.2
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.
소프트웨어 R&D에서 산출물(문서와 프로그램) 검증을 위한 활동
아마르멘드 ( Amarmend ),이은철 ( Eun-chul Lee ),이정원 ( Jung-won Lee ),이병정 ( Byeongjeong Lee ) 한국인터넷정보학회 2016 인터넷정보학회논문지 Vol.17 No.2
일반적으로 소프트웨어 R&D 프로젝트에서는 프로그램 코드와 문서 산출물이 생성된다. 이러한 소프트웨어 R&D 산출물들은 두 가지로 분류할 수 있다. 첫 번째 분류는 연차 실적 계획서, 연구개발과제계획서, 연구성과보고서, 연구 노트와 같은 소프트웨어 연구 산출물들이 포함된다. 그리고 다른 분류는 소프트웨어 요구사항 명세서, 소프트웨어 설계 명세서, 소프트웨어 테스트 계획서, 프로그램 코드와 같은 소프트웨어 개발 산출물들이다. 프로젝트의 진행 방향을 확인할 때 프로그램 코드를 테스트하고 문서 산출물을 검증하는 것이 중요하다. 또한 연구 문서와 개발 산출물 사이에 완전성, 일관성 등의 관계를 확인해야 한다. 그러한 검증과 테스트는 프로젝트 관리자와 연구자들이 프로젝트를 진행하는 동안 올바르게 진행하고 있다는 확신을 준다. 그러므로 본 연구에서는 소프트웨어 R&D에서 생성되는 문서와 프로그램을 검증하는 프로세스를 제안한다. 본 프로세스는 문서 산출물을 검토하고 프로그램 코드를 테스트하는 활동으로 구성되어 있으며, Essence를 사용하여 정의된다. 그리고 본 연구에서 제안하는 프로세스의 효율성을 사례 연구를 통해 보인다. 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.
Test Framework Requirements to Verify Artifacts in Software R&D Project
Sang-Min Song,Amarmend Dashbalbar,Jung-Won Lee,Byungjeong Lee 보안공학연구지원센터 2016 International Journal of Software Engineering and Vol.10 No.11
Researchers do not effectively manage and verify artifacts produced during software R&D projects. And testing software development artifacts cannot test the whole software R&D project. It is necessary to perform continuous and detailed verification of artifacts produced in each phase during software R&D project. Thus, a framework is required to test software and verify documents generated during software R&D project. In this paper, we present requirements of test framework to verify software R&D projects. The requirements are represented with scenarios and use cases for the framework. We show effectiveness of our approach by presenting a part of prototype in case study.