Towards an integrated support for traceability of quality requirements using software spectrum analysis

ICSOFT 2010 - Proceedings of the 5th International Conference on Software and Data Technologies

Volumn 2, Issue , 2010, Pages 187-194

  Kaiya, Haruhiko ^a   Amemiya, Kasuhisa ^a   Shimizu, Yuutarou ^a   Kaijiri, Kenji ^a  

^a SHINSHU UNIVERSITY   (Japan)

Author keywords

Quality characteristics; Requirements specification; Source codes; Traceability

Indexed keywords

CURRENT TECHNIQUES; INTEGRATED SUPPORTS; QUALITY CHARACTERISTIC; QUALITY FEATURES; QUALITY REQUIREMENTS; REQUIREMENTS DOCUMENT; REQUIREMENTS SPECIFICATION; SOFTWARE DEVELOPMENT; SOFTWARE QUALITY; SOURCE CODES; TRACEABILITY; TRACEABILITY LINKS;

INTERFEROMETRY; QUALITY CONTROL; SOFTWARE DESIGN; SOFTWARE RELIABILITY; SPECIFICATIONS; SPECTRUM ANALYSIS;

COMPUTER SOFTWARE SELECTION AND EVALUATION;

EID: 78751532197     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (17)

1. Blaine, J. D. and Cleland-Huang, J. (2008). Software quality requirements: How to balance competing priorities. IEEE Software, 25(2): 22-24.
2. Cleland-Huang, J. (2005). Toward Improved Traceability of Non-Functional Requirements. In International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE), pages 14-19.
3. Cleland-Huang, J., Marrero, W., and Berenbach, B. (2008). Goal-centric traceability: Using virtual plumblines to maintain critical systemic qualities. IEEE Trans. Software Eng., 34(5): 685-699.
4. Cleland-Huang, J., Settimi, R., Zou, X., and Sole, P. (2006). The detection and classification of non-functional requirements with application to early aspects. In RE, pages 36-45.
5. Glinz, M. (2008). A risk-based, value-oriented approach to quality requirements. IEEE Software, 25(2): 34-41.
6. Gokyer, G., Cetin, S., Sener, C, and Yondem, M. T. (2008). Non-functional requirements to architectural concerns: Ml and nlp at crossroads. Software Engineering Advances, International Conference on, 0: 400-406.
7. International Standard ISO/IEC 9126-1 (2001). Software engineering - Product quality - Part 1: Quality model.
8. Kaiya, H., Tanigawa, M., Suzuki, S., Sato, T, and Kaijiri, K. (2009). Spectrum Analysis for Quality Requirements by Using a Term-Characteristics. In 21th International Conference Advanced Information Systems Engineering (CAiSE 2009), pages 546-560, Amsterdam, The Netherlands. LNCS 5565.
9. Kassab, M., Daneva, M., and Ormandjieva, O. (2008). A meta-model for the assessment of non-functional requirement size. In SEAA, pages 411-418.
10. Kassab, M., Ormandjieva, O., and Daneva, M. (2009). An ontology based approach to non-functional requirements conceptualization. Software Engineering Advances, International Conference on, 0: 299-308.
11. Lucia, A. D., Oliveto, R., and Tortora, G. (2009). Assessing ir-based traceability recovery tools through controlled experiments. Empirical Software Engineering, 14(1): 57-92.
12. Mandelin, D., Xu, L., Bodik, R, and Kimelman, D. (2005). Jungloid mining: helping to navigate the api jungle. In PLDI, pages 48-61.
13. Nakatani, X, Hori, S., Ubayashi, N., Katamine, K., and Hashimoto, M. (2008). A case study: Requirements elicitation processes throughout a project. In RE, pages 241-246.
14. Ncube, C, Lockerbie, J., and Maiden, N. A. M. (2007). Automatically generating requirements from * models: Experiences with a complex airport operations system. In REFSQ, pages 33-47.
15. Ratanotayanon, S., Sim, S. E., and Raycraft, D. J. (2009). Cross-artifact traceability using lightweight links. In TEFSE '09: Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering, pages 57-64, Washington, DC, USA. IEEE Computer Society.
16. Washizaki, H., Hiraguchi, H., and Fukazawa, Y. (2008). A metrics suite for measuring quality characteristics of javabeans components. In PROFES, pages 45-60. LNCS 5089.
17. Yoshikawa, X, Hayashi, S., and Saeki, M. (2009). Recovering traceability links between a simple natural language sentence and source code using domain ontologies. In ICSM, pages 551-554.