Revistas de investigación UNMSM

Interpreter to test a program written in pseudocode

Authors

  • Felix Huari Evangelista Universidad Nacional Mayor de San Marcos
  • Pablo José Novara Universidad Nacional del Litoral

DOI:

https://doi.org/10.15381/idata.v17i1.12039

Keywords:

algorithm, chart N-S, flowchart, program, PSeInt, pseudocode

Abstract

The purpose of this article is to acquaint the student community that begins in troubleshooting programmatically using the program called PSeInt. This is a program that allows to represent algorithms using pseudocode, chart N-S, flowchart, and then make the respective test. The obvious trend is that the student does not need to know any programming language to use this tool.

Downloads

Download data is not yet available.

Author Biographies

  • Felix Huari Evangelista, Universidad Nacional Mayor de San Marcos
    Ing. Industrial. Docente de la FII-UNMSM.
  • Pablo José Novara, Universidad Nacional del Litoral
    Ing. Informático. Docente Facultad de Ingenierías y Ciencias Hídricas de la Universidad Nacional del Litoral-Argentina.

Downloads

Published

2014-06-19

Issue

Vol. 17 No. 1 (2014)

Section

Sistemas e Informática

License

Copyright (c) 2014 Felix Huari Evangelista, Pablo José Novara

Creative Commons License

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

AUTHORS RETAIN THEIR RIGHTS:

a. Authors retain their trade mark rights and patent, and also on any process or procedure described in the article.

b. Authors retain their right to share, copy, distribute, perform and publicly communicate their article (eg, to place their article in an institutional repository or publish it in a book), with an acknowledgment of its initial publication in the INDUSTRIAL DATA.

c. Authors retain theirs right to make a subsequent publication of their work, to use the article or any part thereof (eg a compilation of his papers, lecture notes, thesis, or a book), always indicating the source of publication (the originator of the work, journal, volume, number and date).

How to Cite

Interpreter to test a program written in pseudocode. (2014). Industrial Data, 17(1), 101-110. https://doi.org/10.15381/idata.v17i1.12039