User acceptance test of an enterprise system based on software requirement specifications
Ashari Imamuddin(1)*, Rizal Broer Bahaweres(2), Detia Jumral(2), Ahmad Shukri Mohd Noor(3), Ahmad A. Al Rababah(4), Umar Tsani Abdurrahman(1), Mohamad Anas Sobarnas(1)

(1)Computer Science Department, Sekolah Tinggi Teknologi Muhammadiyah Cileungsi, Indonesia
(2)Informatics Engineering Department, Universitas Islam Negeri Syatif Hidayatullah Jakarta, Indonesia
(3)Faculty of Ocean Engineering Technology, University Malaysia Terengganu, Malaysia
(4)Department of Computer Science, King Abdulaziz University, Saudi Arabia
*Email: ashari[at]sttmcileungsi.ac.id

Abstract

Since the main function of the user acceptance test of any software system is to evaluate, verify, and validate the quality of the software in order to decide it can be accepted to the operational environment. The paper proposes a user acceptance test based on software requirement specifications which was conducted for an enterprise resource planning (ERP) system named Qinova. The methodology of this study is by exploring the software requirement specifications and developing functional requirement dependencies matrix (FRDM) and Module Dependency Network (MDN). This matrix is used to describe dependency between functionalities within the system, a functionality (R) is a determinant if other functionality (S) depends on the R functionality. The S functionality is dependent. The matrix is the foundation of developing test scenarios to determine that R functionality has to be tested prior S functionality. The MDN describes dependency between modules within the software. Then, we developed the test plan, the test scenarios and test cases. The stages continued by the quality assurance (QA) team conduct the testing and rise issues and bugs found in the test processes. Then, the technical team carried out the findings by resolving the issues and fixing the bugs. Performing of testing and bug fixing were done incrementally in a loop until all found bugs were resolved. The study conducted the four rounds of testing and the results respectively showed that 80% pass of 82 test cases in the first round, and successively 63% pass of 10 test cases, 67% pass of 4 test cases, and 100% pass of 2 test cases until the last round. All bugs resolved after the fourth run. The research produced a model in performing the requirements-based user acceptance test and the UAT results indicated that the system can be accepted in the operational environment. The FRDM and the MDN drove the team in prioritizing the execution of the test cases and it is helpful to minimize findings during the test.

Keywords: enterprise system, ERP, software requirements, software evaluation, user acceptance test, test results, test scenario, test cases

Topic: Computer Science