IJSER Home >> Journal >> IJSER
International Journal of Scientific and Engineering Research
ISSN Online 2229-5518
ISSN Print: 2229-5518 5    
Website: http://www.ijser.org
scirp IJSER >> Volume 2, Issue 5, May 2011 Edition
Translation of Software Requirements
Full Text(PDF, 3000)  PP.  
Hanan Elazhary
Requirements, Software Engineering, Translation
Stakeholders typically speak and express software requirements in their native languages. On the other hand, software engineers typically express software requirements in English to programmers who program using English-like programming languages. Translation of software requirements between the native languages of the stakeholders and English introduces further ambiguities. This calls for a system that simplifies translation of software requirements while minimizing ambiguities. Unfortunately, this problem has been overlooked in the literature. This paper introduces a system designed to facilitate translation of requirements between English and Arabic. The system can also facilitate the analysis of software requirements written in Arabic. This is achieved through enforcing writing software requirements statements using templates. Templates are selected such that they enforce following best practices in writing requirements documents.
[1] I. Sommerville, Software Engineering. Addison Wesley, 8th edition, 2006.

[2] A. Lamsweerde, R. Darimont, and E. Letier, “Managing Conflicts in Goal-Driven Requirements Engineering,” IEEE Transactions on Software Engineering, vol. 24, no. 11, pp. 908-926, 1998.

[3] S. Schach, Object-Oriented and Classical Software Engineering. McGraw- Hill, 7th edition, 2006.

[4] C. Rupp, “Requirements and Psychology,” IEEE Software, vol. 19, no. 3, pp.16-18, 2002.

[5] C. Denger, D. Berry, and E. Kamsties, “Higher Quality Requirements Specifications through Natural Language Patterns,” Proc. IEEE SwSTE'03, 2003.

[6] K. Wiegers, Software Requirements. Microsoft Press, 2003.

[7] R. Young, Effective Requirements Practices. Addison-Wesley Longman Publishing Co., 2000.

[8] “IEEE Recommended Practice for Software Requirements Specifications,” IEEE/ANSI Standard 830-1998, Institute of Electrical and Electronics Engineers, 1998.

[9] P. Jain, K. Vema, A. Kass, and R. Vasquez, “Automated Review of Natural Language Requirements Documents: Generating Useful Warnings with User-extensible Glossaries Driving a Simple State Machine,” Proc. Second India Software Engineering Conference, 2009.

[10] G. Lami, “QuARS: A Tool for Analyzing Requirements,” Technical Report CMU/SEI-2005-TR-014, Carnegie Mellon Software, Engineering Institute, PA, USA, 2005.

[11] I. Hussain, O. Ormandjieva, and L. Kosseim, “Automatic Quality Assessment of SRS Text by Means of a Decision-Tree-Based Text Classifier,” Proc. the 7th International Conference on Quality Software, 2007.

[12] A. Ohnishi, “Software Requirements Specification Database Based on Requirements Frame Model,” Proc. the 2nd International Conference on Requirements Engineering, 1996.

[13] C. Ben Achour, “Guiding Scenario Authoring, Proc. the 8th European- Japanese Conference on Information Modeling and Knowledge Bases, 1998.

[14] Raven Software, www.ravensoft.com.

[15] H. Elazhary, “REAS: An Interactive Semi-Automated System for Software Requirements Elicitation Assistance,” Int. Journal of Engineering Science and Technology, vol. 2, no. 5, pp. 958-962, 2010.

Untitled Page