Framework for Inspection-Based: Checking the Effectiveness and Efficiency in PHP Source Code
Keywords:
Code Inspection, Logical Errors, PHP, SQL Injections,Abstract
Code inspection process is one of the software inspection processes that is used to find faults, check, increase, and maintain the quality of the software. Typically, the source code inspection process will be conducted in order to find sources code-related issues such as Logical Errors, and Structured Query Language (SQL) Injections. Currently, source code inspection process is being done manually by the developer which leads to taking a long time to find faults as well as time-delay. Based on the literature reviews that had been done, many researchers have done a lot of work in this domain, but none of them have developed prototype containing Logical Errors and SQL Injections for Hypertext Preprocessor (PHP) structure source code in one prototype. Therefore, this research proposed a framework for identifying Logical Errors and SQL Injections. A prototype is developed to proof the concept of the framework. The proposed framework is evaluated using the prototype in terms of effectiveness and efficiency by comparing the manual code inspection and the prototype-based code inspection. The result shows the prototype-based is more effective and efficient compared to current practice (manual).Downloads
Published
How to Cite
Issue
Section
License
TRANSFER OF COPYRIGHT AGREEMENT
The manuscript is herewith submitted for publication in the Journal of Telecommunication, Electronic and Computer Engineering (JTEC). It has not been published before, and it is not under consideration for publication in any other journals. It contains no material that is scandalous, obscene, libelous or otherwise contrary to law. When the manuscript is accepted for publication, I, as the author, hereby agree to transfer to JTEC, all rights including those pertaining to electronic forms and transmissions, under existing copyright laws, except for the following, which the author(s) specifically retain(s):
- All proprietary right other than copyright, such as patent rights
- The right to make further copies of all or part of the published article for my use in classroom teaching
- The right to reuse all or part of this manuscript in a compilation of my own works or in a textbook of which I am the author; and
- The right to make copies of the published work for internal distribution within the institution that employs me
I agree that copies made under these circumstances will continue to carry the copyright notice that appears in the original published work. I agree to inform my co-authors, if any, of the above terms. I certify that I have obtained written permission for the use of text, tables, and/or illustrations from any copyrighted source(s), and I agree to supply such written permission(s) to JTEC upon request.