Personal Software Process with Automatic Requirements Traceability to Support Startups
DOI:
https://doi.org/10.6000/1929-7092.2017.06.38Keywords:
Personal Software Process, Software Improvement Process, Requirements Traceability, Incremental DevelopmentAbstract
This paper applies Personal Software Process (PSP) for software development activities, and uses PSP scripts to follow the activities in software development. In particular, we have adapted a development script in order to enable automatic traceability. The script is the cyclical process that is designed for developing a large program in a sequence of small incremental steps. Moreover, we have extended an XTraQue tool to enable an automatic traceability during using PSP. This enables the completeness of traceability during using PSP. The Part-of-Speech (POS) embedded XML-based templates of software artefacts for PSP-based development, that is, functional requirements (FR), use case, and class diagram are defined. We perform an explanatory case study in order to evaluate the effectiveness between manual and automatic traceability during the personal software process (PSP). In particular, the causal links between software artefacts created during software development are so-called traceability relations. The result evaluation are concerned with precision and recall measures on the creation of traceability relations.
References
https://doi.org/10.1109/TSE.2002.1041053
Egyed, A. 2003. “A Scenario-Driven Approach to Trace Dependency Analysis.” IEEE Transactions on Software Engineering 29(2): 116-132.
https://doi.org/10.1109/TSE.2003.1178051
Humphrey, W.S. 2005. PSP: A Self-Improvement Process for Software Engineers. Addison Wesley. ISBN: 0-321-30549-3.
Ingram, C. and S. Riddle. 2012. “Cost-Benefits of Traceability.” Pp. 23-43. in Software and Systems Traceability. edited by Huang, J., O. Gotel, and A. Zisman. Springer. ISBN: 978-1-4471-2239-5.
https://doi.org/10.1007/978-1-4471-2239-5_2
Jirapanthong, W. and A. Zisman. 2009. “XTraQue: traceability for product line systems.” Software System Model 8(1):117-144.
https://doi.org/10.1007/s10270-007-0066-8
Kim, D., S. Chang, and H. La. 2005. “Traceability Map: Foundations to Automate for Product Line Engineering.” In Proceeding of the 3rd ACIS International Conference on Software Engineering Research, Management and Applications (SERA’05), Pp. 274-281.
Marcus, A., J. I. Maletic. 2003. “Recovering Documentation-to-Source-Code Traceability Links using Latent Semantic Indexing.” In Proceeding of the 25th International Conference on Software Engineering (ICSE), Oregon, USA, May 03-10, Pp. 125-135.
https://doi.org/10.1109/icse.2003.1201194
Ramesh, B. and M. Jarke. 2001. “Towards Reference Models for Requirements Traceability.” IEEE Transactions on Software Engineering 27(1):58-93.
https://doi.org/10.1109/32.895989
Downloads
Published
How to Cite
Issue
Section
License
Policy for Journals/Articles with Open Access
Authors who publish with this journal agree to the following terms:
- Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License that allows others to share the work with an acknowledgement of the work's authorship and initial publication in this journal.
- Authors are permitted and encouraged to post links to their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work
Policy for Journals / Manuscript with Paid Access
Authors who publish with this journal agree to the following terms:
- Publisher retain copyright .
- Authors are permitted and encouraged to post links to their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work .
