Content-Based Conformance Assurance Between Software Research Documentation and Design Guideline

Research-oriented software groups are groups that carry out research on original technology for software. The groups on development phase experience poor documentation because of two reasons. One is the lack of resources (i.e. time, costs) since the development phase is much shorter than their research phase. The other one is that the artifacts they worked on research phase are rarely used on the development documents. Therefore, we propose a method that can reduce poor documentation regarding their research documents and development (R&D) documents. We construct design guidelines from best practices and represent it by queries of semantics-aware traceability links. Then, we use a semi-automated method of conformance assurance between R&D documents with guidelines. Finally, we provide an explanatory guideline to assessment results. We evaluated documents generated from our previous R&D project to show the possibility of our method. Our method can help software R&D project documents for better quality with reduced time.

[1]  Reinhold Plösch,et al.  Automatic Checking of Quality Best Practices in Software Development Documents , 2011, 2011 11th International Conference on Quality Software.

[2]  Linda H. Rosenberg,et al.  Automated Analysis of Requirement Specifications , 1997, Proceedings of the (19th) International Conference on Software Engineering.

[3]  Byungjeong Lee,et al.  Content-based Configuration Management System for Software Research and Development Document Artifacts , 2016, KSII Trans. Internet Inf. Syst..

[4]  Kalman J. Cohen Certification of Algorithm 30: Numerical solution of the polynomial equation , 1962, CACM.

[5]  Alex Kass,et al.  Automated review of natural language requirements documents: generating useful warnings with user-extensible glossaries driving a simple state machine , 2009, ISEC '09.

[6]  Nakornthip Prompoon,et al.  Quality Assessment Method for Software Requirements Specifications Based on Document Characteristics and Its Structure , 2015, 2015 Second International Conference on Trustworthy Systems and Their Applications.

[7]  Eric Allman,et al.  Managing technical debt , 2012, Commun. ACM.

[8]  Mario Trapp,et al.  The Parameterized Safety Requirements Templates , 2015, 2015 IEEE/ACM 8th International Symposium on Software and Systems Traceability.

[9]  V. Basili Software modeling and measurement: the Goal/Question/Metric paradigm , 1992 .

[10]  Carole A. Goble,et al.  Better Software, Better Research , 2014, IEEE Internet Comput..

[11]  Tim Kelly,et al.  The Goal Structuring Notation – A Safety Argument Notation , 2004 .

[12]  Julia Rubin,et al.  Model traceability , 2006, IBM Syst. J..

[13]  Andrian Marcus,et al.  Using traceability links to identifying potentially erroneous artifacts during regulatory reviews , 2013, 2013 7th International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE).