Home   >   CSC-OpenAccess Library   >    Manuscript Information
Full Text Available

(444.49KB)
This is an Open Access publication published under CSC-OpenAccess Policy.
Requirement Engineering Challenges in Development of Software Applications and Selection of Customer-off-the-Shelf (COTS) Components
Sohail Asghar, Mahrukh Umar
Pages - 32 - 50     |    Revised - 30-6-2010     |    Published - 10-08-2010
Volume - 1   Issue - 2    |    Publication Date - July / August 2010  Table of Contents
MORE INFORMATION
KEYWORDS
Requirement Engineering, Customer-off-the-shelf (COTS), Multi-site software development
ABSTRACT
Requirement Engineering acts as foundation for any software and is one of the most important tasks. Entire software is supported by four pillars of requirement engineering processes. Functional and non-functional requirements work as bricks to support software edifice. Finally, design, implementation and testing add stories to construct entire software tower on top of this foundation. Thus, the base needs to be well-built to support rest of software tower. For this purpose, requirement engineers come across with numerous challenges to develop successful software. The paper has highlighted requirement engineering challenges encountered in development of software applications and selection of right customer-off-the-shelf components (COTS). Comprehending stakeholder’s needs; incomplete and inconsistent process description; verification and validation of requirements; classification and modeling of extensive data; selection of COTS product with minimum requirement modifications are foremost challenges faced during requirement engineering. Moreover, the paper has discussed and critically evaluated challenges highlighted by various researchers. Besides, the paper presents a model that encapsulates seven major challenges that recur during requirement engineering phase. These challenges have been further categorized into problems. Furthermore, the model has been linked with previous research work to elaborate challenges that have not been specified earlier. Anticipating requirement engineering challenges could assist requirement engineers to prevent software tower from any destruction.
CITED BY (34)  
1 Muqeem, M. (2016). Design of an Efficient Framework for Requirement Elicitation.
2 Huzooree, G., & Ramdoo, V. D. (2015). A Systematic Study on Requirement Engineering Processes and Practices in Mauritius. International Journal, 5(2).
3 Aljallabi, B. M., & Mansour, A. (2015, September). Enhancement approach for non-functional requirements analysis in Agile environment. In Computing, Control, Networking, Electronics and Embedded Systems Engineering (ICCNEEE), 2015 International Conference on (pp. 428-433). IEEE.
4 Aapaoja, A., & Haapasalo, H. (2014). A framework for stakeholder identification and classification in construction projects. Open Journal of Business and Management, 2014.
5 Bentmar, B., & Shiravand, M. Kravhantering inom landsting.
6 Massoud, A., & Ramadan, H. (2014). Kravhantering–Brister och lösningar.
7 Al-Tarawneh, f. h. a framework for cots software evaluation and selection for cots mismatches handling and non-functional requirements.
8 Bibi, S., Hafeez, Y., Hassan, M. S., Gul, Z., Pervez, H., Ahmed, I., & Mazhar, S. (2014). Requirement Change Management in Global Software Environment Using Cloud Computing. Journal of Software Engineering and Applications, 2014.
9 Malhotra, S. S. M. Requirement Elicitation Of Large Web Projects.
10 Björk, M., Söderström, J., & Ågren, S. (2014). Att möta det okända: Utmaningar vid implementering av ett processorienterat arbetssätt inom offentlig verksamhet.
11 Baykal, N. (2013).Use of project similarity for software development time estimation (Doctoral dissertation, MIDDLE EAST TECHNICAL UNIVERSITY).
12 Souza, C., Souza, C., Alencar, F. M., Castro, J., Figueiredo, E., & Cavalcanti, P. (2013). Avaliação de Modelos i* com o Processo AIRDoc-i. In ER@ BR.
13 Oliveira, K., Pimentel, J., Santos, E., Dermeval, D., Guedes, G., Souza, C., ... & Silva, C. (2013). 25 years of Requirements Engineering in Brazil: a systematic mapping. In Workshop on Requirements Engineering.
14 Hagal, M., & Alshareef, S. F. (2013, December). A systematic approach to generate and clarify consistent requirements. In IT Convergence and Security (ICITCS), 2013 International Conference on (pp. 1-4). IEEE.
15 Pillai, A. S. (2013, December). A study on the software requirements elicitation issues-its causes and effects. In Information and Communication Technologies (WICT), 2013 Third World Congress on (pp. 245-252). IEEE.
16 Castro, J., & Alencar, F. (2013). Uso de Modelagem Social na Engenharia de Requisitos. Jornada de Atualização de Informática-JAI.
17 Schneider, L., Hajji, K., Schirbaum, A., & Basten, D. (2013). Knowledge Creation in Requirements Engineering-A Systematic Literature Review. In Wirtschaftsinformatik (p. 114).
18 Latif, M. S., Sarwar, M. U., Talib, M. R., Khan, M. I., & Sarwar, M. B. (2013). Improvement in software quality with prioritization requirements. International Journal of Computer Science and Management Research, 2(4), 2171-2183.
19 ARSHAD, S., MUHAMMAD, S., & SHAHZAD, S. (2013). Empirical analysis of traditional and agile requirement engineering process. Science Technology and Development (Pakistan).
20 Abbasi, W. A. (2013).Fuzzy logic based intelligent software requirement elicitation technique selection model (Doctoral dissertation, Iqra University Islamabad).
21 Chugh, N., & Mishra, A. D. (2013). Assimilation of Four Layered Approach to NFR in Agile Requirement Engineering. International Journal of Computer Applications, 78(5), 25-28.
22 Siegemund, K. (2013). Contributions To Ontology-Driven Requirements Engineering.
23 Zeaaraoui, A., Bougroun, Z., Belkasmi, M. G., & Bouchentouf, T. (2013, August). User stories template for object-oriented applications. In Innovative Computing Technology (INTECH), 2013 Third International Conference on (pp. 407-410). IEEE.
24 Mahalakshmi, K., & Prabhakar, R. (2013). Performance Evaluation of Non Functional Requirements. Global Journal of Computer Science and Technology, 13(8).
25 ABE, J. O. An investigation of software requirements management practices in nigerian software development industries.
26 Lehto, J., Haapasalo, H., Distanont, A., & Vaananen, M. (2012). The Engagement between Knowledge Transfer and Requirements Engineering. International Journal of Management, Knowledge and Learning, (2), 131-156.
27 Distanont, A., Haapasalo, H., Vaananen, M., & Lehto, J. (2012). The engagement between knowledge transfer and requirements engineering. International Journal of Management, Knowledge and Learning, 1(2), 131-156.
28 Al-Fataftah, I. A., & Issa, A. A. (2012). A systematic review for the latest development in requirement engineering. World Acad Sci Eng Technol, 6, 691-698.
29 Christopher, D. F. X., & Chandra, E. (2012).Prediction of software requirements stability based on complexity point measurement using multi-criteria fuzzy approach. International Journal of Software Engineering & Applications, 3(6), 101.
30 Ramingwong, L. (2012). A review of requirements Engineering processes, Problems and models. International Journal of Engineering Science and Technology, 4(6).
31 Collaborative, i. ctechnica.
32 Rani, A., Solanki, K., & Jangra, G. (2011). Requirement Engineering: A Comprehensive Review. Software Engineering and Technology, 3(6), 275-280.
33 Zakaria, N. H., Haron, A., Sahibuddin, S., & Harun, M. (2011). Requirement engineering critical issues in public sector software project success factor. International Journal of Information and Electronics Engineering, 1(3), 200-209.
34 Nuric, A., Nuric, S., Kricak, L., & Negovanovic, M. (2010). Developing and Application of Software for Determining Parameters of Drainage on Designed Embankment. Mining magazine, 201(1/2).
1 Google Scholar
2 CiteSeerX
3 refSeek
4 Scribd
5 slideshare
6 PDFCAST
7 PdfSR
1 G. Maria C. de and J.Brelaz de. “Improving the Separation of Non-Functional Concerns in Requirements Artifacts.” In proceedings of the 12th IEEE International Conference on Requirements Engineering (RE 2004), 6-10 September 2004, Kyoto, Japan 2004.
2 A. Cortesi and F. Logozzo. “Abstract Interpretation-Based Verification of Non-functional Requirements.” Lecture Notes in Computer Science, Springer Berlin/Heidelberg, 3454: 54-59, 2005.
3 IEEE. IEEE Recommended Practice for Software Requirement Specification, 1988.
4 L. Chung, B.A. Nixon, E. Yu, and J. Mylopoulos. “Non-Functional Requirements in Software Engineering” Springer Berlin / Heidelberg, pp.363-379 (2009)
5 L. M.Cysneiros and E.Yu. “Perspectives on software engineering”, Julio Cesar Sampaio do Prado Leite, Jorge H. Doorn, Kluwer Academic Publishers, pp. 114-138 (2004).
6 L. Marcio and J.C. S. do Prado. “Using the Language Extended Lexicon to Support Non-Functional Requirements Elicitation.” Anais do WER01 - Workshop em Engenharia de Requisitos, Buenos Aires, Argentina. November 22-23, 2001.
7 J. Salim. “Requirement Engineering for Enterprise Application Development: Seven Challenges in Higher Education Environment.” World academy of Science, Engineering and Technology, 4:101, 2005.
8 H. d. Vries, H. Verheul and H. Willemse. “Stakeholder Identification in IT standardization processes.” Standard Making: A Critical Research Frontier for Information Systems MISQ Special Issue Workshop, 2003.
9 A.T. Bahill. and S. J. Henderson. “Requirements Development, Verification and Validation Exhibited in Famous Failures”. Wiley Periodicals, Inc, Systems Engineering, 8(1): 1-14, 2005.
10 F.T. Sheldon and H. Y. Kim. “Validation of guidance control software requirements specification for reliability and fault-tolerance.” In IEEE annual proceedings on Reliability and Maintainability Symposium, Washington, DC, USA 2002.
11 M.Oktay, A.B. Gülba?c?, and M.Sar?öz. “Architectural, Technological and performance issues in enterprise applications.” World Academy of Science, Engineering and Technology, 27: 224-230, 2007.
12 C. Alves, J. B.P. Filho, J.Castro. “Analyzing the tradeoffs among requirements, architectures and COTS components.” pp. 23-26, 2001.
13 C.Alves and A.Finkelstein. “Investigating Conflicts in Cots Decision-Making.” International Journal of Software Engineering and Knowledge Engineering, 13(3):1-21, 2003.
14 B.Thomas. “Meeting the challenges of Requirement Engineering.” News at Software Engineering Institute. 2009. Website: http://www.sei.cmu.edu/library/abstracts/news-at-sei/spotlightmar99pdf.cfm. Access date: January 2010.
15 C.Alves and A.Finkelstein. “Challenges in COTS Decision-Making: A Goal Driven Requirements Engineering Perspective.” In Proceedings of the 14th international conference on Software engineering and knowledge engineering. Ischia, Italy, 2002.
16 C.J. Fidge and A.M. Lister. “The challenges of Non-functional computing requirements.” Pp. 6-7.Website: http://sky.fit.qut.edu.au/~fidgec/Publications/fidge93c.pdf.
17 L.Goldin and A.Finkelstein. “Abstraction-based requirements management.” In Proceedings of the international workshop on Role of abstraction in software engineering. Shanghai, China, 2006.
18 A.V.Lamsweerde. “Requirements engineering in the year 00: a research perspective.” In proceedings of the 22nd international conference on Software engineering, Limerick, Ireland. 2000.
19 Endava: White paper on Requirements gathering and analysis, pp. 7-10, 2007. http://www.endava.com/resources/Endava.com-WhitePaper-RequirementsGathering.pdf Access Date: October 2008.
20 L.Goldin and D.Berry. “AbstFinder, A Prototype Natural Language Text Abstraction Finder for Use in Requirement Elicitation.” In IEEE Requirements Engineering, 1994. Proceedings of the First International Conference.
21 Volere. Website: http://www.volere.co.uk/tools.htm Access date: November 2008.
22 Requirement tools. Website: http://easyweb.easynet.co.uk/~iany/other/vendors.htm
23 L. K. Meisenbacher. “The Challenges of Tool Integration for Requirements Engineering.” In Proceedings of SREP’05, Paris, France, 2005.
24 B.Berenbach. “Impact of organizational structure on distributed requirements engineering processes: lessons learned.” In Proceedings of the 2006 international workshop on Global software development for the practitioner. Shanghai, China 2006.
25 S. Timea, H. Andrea and P. Barbara. “The challenges of Distributed Software Engineering and Requirements Engineering: Results of an Online Survey.” pp.9-13. Website: http://www-swe.informatik.uni-heidelberg.de/research/publications/TR_Distributed_RE_Version1.pdf. Access Date: October 2008
26 D.G. Firesmith. “Modern Requirements Specification.” Journal of Object Technology, 2(2):53-64, March-April 2003.
27 M.Gerdom and Dr. U. Rastofer. “Rapid requirements engineering – Does a specification Always need to come at the start?” pp.7.
28 M. Glinz. “Problems and deficiencies of UML as a requirement specification language.” In Proceedings of IEEE 10th International Workshop on Software Specification and Design. Washington, DC, USA, 2000.
29 F.S. Juan. “Taxonomy of verification and validation of software requirement and specifications.” Website: http://www.cs.utexas.edu/~jsequeda/pub/Sequeda_VV_req_spec.pdf
30 Advanced XML validation. Website: http://www.ibm.com/developerworks/xml/library/x-crsfldvalid/index.html Access Date: November 2008
31 Schematron: Validating XML using XSLT. Website: http://www.ldodds.com/papers/schematron_xsltuk.html Access Date: November 2008.
32 Y.Chen, S.Chen, H.Sum and S.C.Lin. “Functional requirements of metadata system: from user needs perspective.” In Proceedings of the international conference on Dublin Core and metadata applications: supporting communities of discourse and practice---metadata research & applications. Seattle, Washington 2003.
33 J.H.Hausmann, R.Heckel, G.Taentzer. “Detection of conflicting functional requirements in a use case-driven approach: a static analysis technique based on graph transformation.” In proceedings of the 24th International Conference on Software Engineering. Orlando, Florida 2002.
34 A.I. Anton, J. H. Dempster and D.F. Siege. “Managing Use Cases During Goal-Driven Requirements Engineering: Challenges Encountered and Lessons Learned.” Technical Report: TR-99-16, 1999.
35 DK.M: “Opportunities and Challenges of 21st Century Emerging Technologies.” Website: http://mi2g.net/cgi/mi2g/reports/speeches/220108.pdf Access Date: November 2008.
36 K.Thiagarajan. “Making provisions for external risks.” Website:http://www.thehindubusinessline.com/iw/2001/03/11/stories/0511e012.htm
37 N. Turbit. “Key Stakeholder Support” Website:http://www.projectperfect.com.au/info_key_stakeholder.php Access Date: December 2008.
38 B.Nuseibeh and S.Easterbrook. “Requirements engineering: a roadmap.” In Proceedings of the Conference on the Future of Software Engineering. Limerick, Ireland 2000.
39 Ian Sommerville: “Software Engineering” 7th Edition, Addison.W, pp.168-180 (2004)
40 Search software quality. Website:http://searchsoftwarequality.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid92_gci1335438,00.html Access Date: January 2009.
41 W.M. Wilson, L.H. Rosenberg , L.E. Hyatt. “Automated analysis of requirement specifications.” In Proceedings of the 19th international conference on Software engineering Boston, Massachusetts, United States 1997.
42 Automated Requirement measurement tool. Website: http://satc.gsfc.nasa.gov/tools/arm/ Access Date: January 2009.
43 Non Functional Requirements. Website: http://www.threesl.com/pages/webletter-February06/Non_Functional_Requirements.php Access Date: January 2009.
44 44. L. V., J. Donn. “Writing Software Requirements Specifications.” Website:http://www.techwrl.com/techwhirl/magazine/writing/softwarerequirementspecs.html Access date: January 2009.
45 Templates. Website: http://www.stcsig.org/mgt/reference.htm
46 Jeffrey L. W., Lonnie D. B. and, Kevin C. D. “Systems Analysis & Design Methods.” International Edition, Irwin Professional Publishing; pp. 12 (2000)
47 K. Ryan. “The role of natural language in requirements engineering.” In proceedings of IEEE International Symposium on Requirement Engineering, San Diego, CA, 1993.”
48 B.H. C. Cheng and J. M. Atlee. “Research Direction in Requirement Engineering.” In International Conference on Software Engineering on Future of Software Engineering. Washington, DC, USA, 2007.
49 AOF Requirements and Acceptance. Webiste:http://www.aof.mod.uk/aofcontent/tactical/randa/content/vandv.htm Access Date: January 2009.
50 Requirements Assistant. Website: http://www.requirementsassistant.nl/
51 SAT. Website: http://www.cassbeth.com/ Access Date: January 2009.
52 RavenFlow. http://www.ravenflow.com/ Access Date: January 2009.
53 W.J.Lloyd. “A Common Criteria Based Approach for COTS Component Selection.” Journal of Object Technology, 4(3):27-34, 2004.
54 E.Yu and J.Mylopoulos. “Why Goal-Oriented Requirements Engineering.” Website: http://www.cs.toronto.edu/pub/eric/REFSQ98.html. Access Date: January 2009.
55 L. Chung. “Representing and Using Non-Functional Requirements for Information System Development: A Process-Oriented Approach.” Website: http://www.cs.toronto.edu/~jm/Pub/TSE92.pdf. Access Date: January 2009.
56 R. Atan, A. A. Abd. Ghani, M. H. Selamat, R. Mahmod. “Automating Measurement for Software Process Models using Attribute Grammar Rules”. International Journal of Engineering, 1 (2): 24-33, 2007.
57 A.S.Poza, M. Altinkilinc, C. Searcy. “Implementing a Functional ISO 9001 Quality Management System in Small and Medium-Sized Enterprises”. International Journal of Engineering (IJE), 3(3): 220-228, 2009.
58 Kirti Seth, Arun Sharma, Ashish Seth. “Component Selection Efforts Estimation– a Fuzzy Logic Based Approach”. International Journal of Computer Science and Security, (IJCSS), 3 (3): 210-215, 2009.
Dr. Sohail Asghar
- Pakistan
Miss Mahrukh Umar
- Pakistan