일반적으로 소프트웨어 R&D 프로젝트에서는 프로그램 코드와 문서 산출물이 생성된다. 이러한 소프트웨어 R&D 산출물들은 두가지로 분류할 수 있다. 첫 번째 분류는 연차 실적 계획서, 연구개발과제계획서, 연구성과보고서, 연구 노트와 같은 소프트웨어 연구 산출물들이 포함된다. 그리고 다른 분류는 소프트웨어 요구사항 명세서, 소프트웨어 설계 명세서, 소프트웨어 테스트 계획서, 프로그램 코드와 같은 소프트웨어 개발 산출물들이다. 프로젝트의 진행 방향을 확인할 때 프로그램 코드를 테스트하고 문서 산출물을 검증하는 것이 중요하다. 또한 연구 문서와 개발 산출물 사이에 완전성, 일관성 등의 관계를 확인해야 한다. 그러한 검증과 테스트는 프로젝트 관리자와 연구자들이 프로젝트를 진행하는 동안 올바르게 진행하고 있다는 확신을 준다. 그러므로 본 연구에서는 소프트웨어 R&D에서 생성되는 문서와 프로그램을 검증하는 프로세스를 제안한다. 본 프로세스는 문서 산출물을 검토하고 프로그램 코드를 테스트하는 활동으로 구성되어 있으며, Essence를 사용하여 정의된다. 그리고 본 연구에서 제안하는 프로세스의 효율성을 사례 연구를 통해 보인다.
일반적으로 소프트웨어 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 developm...
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.
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.
* AI 자동 식별 결과로 적합하지 않은 문장이 있을 수 있으니, 이용에 유의하시기 바랍니다.
문제 정의
They examine documents and code to monitor project progress and quality during software project where they verify both the code and documents. The purpose of this verification is to make contribution to software testing activity. Artifacts of software R&D project are divided into two groups.
제안 방법
The contribution of this paper is that we introduce a test process that conforms to software R&D projects and both software product and documents are able to be tested within the process.
The proposed test process has test planning document and test result document, SLTP and SLTR [15]. SLTP includes contents that related to planning of software testing such as test strategy, risk approach, test environment requirement, test case and scenario etc.
이론/모형
After test activities performed and concluded as instructed in SLTP, the test result is shown through Software Life-Cycle Test Report (SLTR). Table 1 shows all input and output documents of process activities.
[12] proposed a software development process that based on Rational Unified Process (RUP). The proposed process is a tailored version of RUP for Korean Core Instrumentation System. They evaluated the result by with typical waterfall lifecycle model and RUP.
성능/효과
[11] is a study which describes guidelines for implementing Capability Mature Model Integration (CMMI) based configuration management in Extreme Programming (XP). Therefore, this paper provides basic knowledge on CMMI and Extreme Programming and configuration management (CM) practices of CMMI were redefined in order customize them for XP. This study was useful for our research because we are developing a TMMi-based software test process where TMMi and CMMI are conceptually similar.
참고문헌 (17)
I. Jacobson, S. Huangb, M. Kajko-Mattssonc, P. McMahond, and E. Seymoure, "Semat-three year vision," Programming and computer software, vol. 38, no. 1, pp.1-12, 2012. http://dx.doi.org/10.15514/syrcose-2011-5-inv
I Jacobson, P. Ng, P. McMahon, I. Spence and S Lidman, "The essence of software engineering: the SEMAT kernel," Queue - Networks, vol. 10, no. 10, 2012. http://dl.acm.org/citation.cfm?id2389616
T. Sedano, and P. Cecile, "State-based Monitoring and Goal-driven Project Steering: Field Study of the SEMAT Essence Framework," In Proc. of the 36th International Conference on Software Engineering, pp.325-334, 2014. http://dx.doi.org/10.1145/2591062.2591155
I. Burnstein, A. Homyen, R. Grom, and CR Carlson, "A model to assess testing process maturity," Crosstalk the Journal of Defense Software Engineering, vol. 11, no. 11, pp.6-30, 1998. http://citeseerx.ist.psu.edu/viewdoc/download?doi10.1.1.434.1067&reprep1&typepdf
T. Ericson, A. Subotic, and S. Ursing. "TIM - A Test Improvement Model," Software Testing Verification and Reliability, vol. 7, no. 4, pp. 229-246, 1997. http://dx.doi.org/10.1002/(sici)1099-1689(199712)7:4 3.3.co;2-d
I. Burnstein, S. Taratip, and C. Robert, "Developing a testing maturity model for software test process evaluation and improvement," In Proc. of International Test Conference, pp. 581-589, 1996. http://dx.doi.org/10.1109/test.1996.557106
E. van Veenendaal, J. Jaap Cannegieter, "Test Maturity Model Integration (TMMi) Results of the first TMMi benchmark - where are we today?", pp.3, Euro Star Software Testing Community, 2013.
E. van Veenendaal, R. Grooff and R. Hendriks, "Test Process Improvement using TMMi," Testing Experience: The Magazine for Professional Testers, vol. 3, no. 19, pp.21-25, 2008. http://www.erikvanveenendaal.nl/NL/files/Test%20Proce ss%20Improvement%20using%20TMM(i).pdf
P. Ng, and S. Huang, "Essence: A framework to help bridge the gap between software engineering education and industry needs," In Proc. of IEEE 26th Conference on Software Engineering Education and Training (CSEE&T), pp-304-308, 2013. http://dx.doi.org/10.1109/cseet.2013.6595266
B. Elvesæter, G. Benguria and S. Ilieva, "A comparison of the Essence 1.0 and SPEM 2.0 specifications for software engineering methods," In Proc. of the Third Workshop on Process-Based Approaches for Model- Driven Engineering, no. 2, p. 2, 2013. http://dx.doi.org/10.1145/2489833.2489835
D. J. Han and H. S. Han, "Guidelines for Implementing Configuration Management in Extreme Programming based on CMMI," Journal of Internet Computing and Services, vol. 9, no. 2, pp. 107-118, 2008.
K. S. Lee and T. G. Lee, "A Software Development Process of Core Instrumentation System Based on the Rational Unified Process," Journal of Internet Computing and Services, vol. 5, no. 4, pp. 95-113, 2004.
S. W. Shin, H. K. Kim and S. W. Kim, "Framework for Improving Mobile Embedded Software Process," Journal of Internet Computing and Services, vol. 10, no. 5, pp. 195-209, 2009.
J. Cangussu, R. DeCarlo, A. MATHUR, "Using sensitivity analysis to validate a state variable model of the software test process," IEEE Transactions on Software Engineering, vol. 29, no. 5, pp.430-443, 2003. http://dx.doi.org/10.1109/tse.2003.1199072
K. H. Jin, S. M. Song, J. W. Lee and B. J. Lee, "Test Planning and Reporting for Constant Monitoring of Software R&D Projects," Korea Computer Congress, Vol. 42, No. 1, pp.597-599, 2015.
S. Imoto, Y. Yoshiyuki and W. Junzo. "Fuzzy regression model of R&D project evaluation." Applied Soft Computing, vol. 8, no. 3, pp.1266-1273, 2008. http://dx.doi.org/10.1016/j.asoc.2007.02.024
J. A. Kim, J. H. Kim, "Quality Assessment Framework for Medical Device specific SW R&D Project." International Journal of Software Engineering and Its Applications, vol. 8, no. 1, pp.371-376, 2014. http://dx.doi.org/10.14257/ijseia.2014.8.1.32
※ AI-Helper는 부적절한 답변을 할 수 있습니다.