International Journal of Scientific & Technology Research

IJSTR@Facebook IJSTR@Twitter IJSTR@Linkedin
Home About Us Scope Editorial Board Blog/Latest News Contact Us

IJSTR >> Volume 6 - Issue 7, July 2017 Edition

International Journal of Scientific & Technology Research  
International Journal of Scientific & Technology Research

Website: http://www.ijstr.org

ISSN 2277-8616

Locking Editor: A Utility For Protecting Software Exercises In The Computer Laboratory Of AMA University

[Full Text]



Paul M. Grafilon, Jonathan Fuller, Shiitj B. Mer, Tristan Jay P. Calaguas



kirkpatrick, protectable, micro services, programming.



The student of AMA University persistence in computing which has the keys to providing their talent needed to fill the computer laboratory in the computing professions. A range of factors can affect a student’s decision to remain in a computing major or change to another major if ever they feel that computing education is difficult. This has to describe the activities in computer laboratory specifically exercises, machine problems, and computing case studies interacting different application programs as the basis of their skills and knowledge in programming capability. The nature of those activities addresses by using of IDE as open source in all programming applications which may result of specific intervention such as using the editor to create a source file, the code blocks, comments, and program statements are entered and the file saved. In case, there are no "corrective actions," taken as the editor does not know this is supposed to be a "source file" as opposed to notes for class. If working in a position-dependent language like Java, the developer would have to be very careful about indenting. The file has to be saved with the correct file extension and in a directory where the compiler can find it. Each source file has to be compiled separately, if the program has a few source files, they all have to be named separately in the compiler. When invoking the compiler, it has to be directed to look in the correct directory for the source files and where the output files should be stored. If there is an error in the source file, the compiler will output messages and fail to complete. For any errors, the developer goes back and edits the source file, working from line numbers and compiler messages to fix the problems and these steps continue until all the source files compile without errors. When linking, each object file is specified as being part of the build. Again, the locations for the object files and executable are given. There may be errors at this point because it is not until the entire program is linked that some errors can be detected. Assuming the linker finds all the variables and functions, it produces a file that can be run. If the program is running and working means all well for the developer. If it seems to do nothing, that means it's debugging time, since there is no insight to what the program is doing, the developer may go back and put in some brute force methods, like print statements to print messages out at certain points in the program or blink some light emitting diodes (LEDs) at strategic places, which means back to the editor, and the cycle continues. These are the causes of the developer can sort of sounds like rather than copying and pasting code from previous applications into a new one, that are rewriting the same functionality again and again. This is one of the varied reasons of the dry principle is geared more towards not having the same functionality duplicated throughout an entire system, but reusing code from other applications is better than rewriting it, since IDE is free and available as open source in any codes of environment. The main focus of the study is the development of utility for locking editor in protecting software exercises. Specifically, it sought to solve the following: To develop an editor that will lock the source code during programming laboratory exercises; To assess the propose system in Kirkpatrick model approach; To evaluate the testing assessment of the proposed system in terms of the following indicators: Efficiency, Usability, and reliability As the result, the locking editor for source code generation is a core program for the locking IDE software. It contains both the user interface such as students and instructor which work together in one package. The evaluation of multi-programming environment by testing the editor that, as it develops solutions keep in mind that locking editor uses the architecture and frameworks that most users are accustomed to see. It should build the development environment and use the tools in the way that makes the most sense for organization. The assessment of the proposed system in Kirkpatrick model approach such as reaction, learning, behavior and results with a weighted mean of 4.19, 4.37, 4.25 and 4.67 with a verbal interpretation of “Protectable” and “Highly Protectable” respectively. The determination in testing assessment of the proposed system based on ISO 9126 reveals of efficiency, usability and reliability with a weighted mean of 4.19, 4.58, and 4.75 interpreted “Highly Protectable” and “Protectable” respectively were the main features and characteristics of locking editor.



[1] S. Bilin Balaji, “What is the difference between source file, executable file and object file?” https://www.quora.com/What-is-the-difference-between-source-file-executable-file-and-object-file

[2] M. Rouse, “Integrated Development Environment” http://searchsoftwarequality.techtarget.com/definition/integrated-development-environment

[3] “Programming Language” https://www.computerhope.com/jargon/p/proglang.htm

[4] L. Elrick, “Is Computer Programming Hard? Not if You have these 6 Characteristics” http://www.rasmussen.edu/degrees/technology/blog/is-computer-programming-hard/

[5] E. Forest, “Kirkpatrick Model: Four Levels of Learning Evaluation” https://educationaltechnology.net/kirkpatrick-model-four-levels-learning-evaluation/