AN AUTOMATED APPROACH TO VALIDATE REQUIREMENTS SPECIFICATION
Requirements engineering processes aim to acquire functions, services and constraints. These processes are important to satisfy the customer by applying correctness, completeness through consistency according to the control instructions to achieve product quality. Both functions and services face changeability issue that is hard to regulate, depending on the precise request of the customer. This research addresses the achievement of correctness, completeness, and consistency by applying an automated approach. The evaluation is established using a standard use case diagram from the UML official website.Â The proposed approach detects the incorrect requirement specifications to enhance Software quality. The proposed approach includes three levels; the first level is the Structured Document, the second level is the Dynamic Language, which describes the transforming of use case diagram as dynamic, and the third level is the completeness checking procedures, which is based on the implemented standard rules. The approach is supported by a programmed tool on MS excel and XML due to IBM Rational Rose and Visual Paradigm and experimented â€œOnline Shoppingâ€ use case diagram as a case study.
J. Coughlan and R. D. Macredie, "Effective communication in requirements elicitation: a comparison of methodologies," Requirements Engineering, vol. 7, pp. 47-60, 2002.
J. Eckhardt, A. Vogelsang, H. Femmer, and P. Mager, "Challenging incompleteness of performance requirements by sentence patterns," in 2016 IEEE 24th International Requirements Engineering Conference (RE), 2016, pp. 46-55.
D. Zowghi and C. Coulin, "Requirements elicitation: A survey of techniques, approaches, and tools," in Engineering and managing software requirements, ed: Springer, 2005, pp. 19-46.
K. Swarnalatha, G. Srinivasan, N. Dravid, R. Kasera, and K. Sharma, "A survey on software requirements engineering for real time projects based on customer requirements," Intâ€™l J of Advanced Research in Computer and Communication Engineering, vol. 3, 2014.
M. DÃ¼chting, D. Zimmermann, and K. Nebe, "Incorporating user centered requirement engineering into agile software development," Human-computer interaction. Interaction design and usability, pp. 58-67, 2007.
M. dos Santos Soares and J. L. Vrancken, "Model-Driven User Requirements Specification using SysML," JSW, vol. 3, pp. 57-68, 2008.
W. J. Alzyadat, A. AlHroob, I. H. Almukahel, and R. Atan, "fuzzy map approach for accruing velocity of big data," Compusoft, vol. 8, pp. 3112-3116, 2019.
J. Larsson and M. Borg, "Revisiting the challenges in aligning RE and V&V: Experiences from the public sector," in Requirements Engineering and Testing (RET), 2014 IEEE 1st International Workshop on, 2014, pp. 4-11.
M. Kamalrudin and S. Sidek, "A review on software requirements validation and consistency management," International Journal of Software Engineering and Its Applications, vol. 9, pp. 39-58, 2015.
M. A. Naeem, U. Waheed, and S. F. A. Raza, "Requirement Correctness Problems and Strategies for Web Applications," Pakistan Journal of Engineering, Technology & Science, vol. 6, 2017.
ISO/IEC, "Software Product Quality," in 25010, ed, 2017, p. 3.
ISO/IEC, "Quality of Data Product," in 25012, ed, 2008, p. 4.
A. Al-Hroob, A. T. Imam, and R. Al-Heisa, "The use of artificial neural networks for extracting actions and actors from requirements document," Information and Software Technology, vol. 101, pp. 1-15, 2018.
A. A. Jahanshani, G. M. A. Hajizadeh, S. A. Mirdhamadi, K. Nawaser, and S. M. S. Khaksar, "Study the effects of customer service and product quality on customer satisfaction and loyalty," International Journal of Humanities and Social Science, 2014.
D. Zowghi and V. Gervasi, "The Three Cs of requirements: consistency, completeness, and correctness," in International Workshop on Requirements Engineering: Foundations for Software Quality, Essen, Germany: Essener Informatik Beitiage, 2002, pp. 155-164.
D. Zowghi, V. Gervasi, and A. McRae, "Using default reasoning to discover inconsistencies in natural language requirements," in Software Engineering Conference, 2001. APSEC 2001. Eighth Asia-Pacific, 2001, pp. 133-140.
D. Firesmith, "Common Requirements Problems, Their Negative Consequences, and the Industry Best Practices to Help Solve Them," Journal of Object Technology, vol. 6, pp. 17-33, 2007.
M. Kalinowski, M. Felderer, T. Conte, R. SpÃnola, R. Prikladnicki, D. Winkler, et al., "Preventing incomplete/hidden requirements: reflections on survey data from Austria and Brazil," in International Conference on Software Quality, 2016, pp. 63-78.
J. Kuchta, "Completeness and Consistency of the System Requirement Specification," in FedCSIS Position Papers, 2016, pp. 265-269.
G.Swathi,Dr.Ch GVN Prasad,Arruri Jagan, Int. J. Comp. Tech. Appl., Vol 2 (3), 631-638, "Writing Software Requirements Specification Quality Requirements: An Approach to Manage Requirements Volatility," 2011.
H. Femmer, D. M. FernÃ¡ndez, E. Juergens, M. Klose, I. Zimmer, and J. Zimmer, "Rapid requirements checks with requirements smells: two case studies," in Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering, 2014, pp. 10-19.
ISO/IEC/IEEE Draft International Standard - Systems and Software Engineering -- Life Cycle Processes --Requirements Engineering," in ISO/IEC/IEEE P29148_FDIS, September 2018 , vol., no., pp.1-104, 7 Sept. 2018.
Gigante G., Gargiulo F., Ficco M. (2015) A Semantic Driven Approach for Requirements Verification. In: Camacho D., Braubach L., Venticinque S., Badica C. (eds) Intelligent Distributed Computing VIII. Studies in Computational Intelligence, vol 570. Springer, Cham
A. A. Wael ALzyadat, "Development Planning in the Big Data Era: Design References Architecture," International Journal of Recent Technology and Engineering (IJRTE), vol. 8, p. 4, 2019.
UML. (2017, 5/12/2017). The Unified Modeling Language. Available: https://www.uml-diagrams.org/ (Last Accesed Nov. 2019)
IBM. (2017, 5/12/2017). Relationships in use-case diagrams. Available: https://www.ibm.com/support/knowledgecenter/SS8PJ7_9.5.0/com.ibm.xtools.modeler.doc/topics/crelsme_ucd.html (Last Accessed Nov. 2019)
The submitter hereby warrants that the Work (collectively, the “Materials”) is original and that he/she is the author of the Materials. To the extent the Materials incorporate text passages, figures, data or other material from the works of others, the undersigned has obtained any necessary permissions. Where necessary, the undersigned has obtained all third party permissions and consents to grant the license above and has all copies of such permissions and consents.
The submitter represents that he/she has the power and authority to make and execute this assignment. The submitter agrees to indemnify and hold harmless the COMPUSOFT from any damage or expense that may arise in the event of a breach of any of the warranties set forth above. For authenticity, validity and originality of the research paper the author/authors will be totally responsible.