Lists of programming tools with a brief description of their features are published several times on this and other Linux blogs. In this series of articles We intend to go one step further and give users the basic concepts they need to make their own decisions.
At previous articler we had established the differences between programming (the set of tasks ranging from determining user needs to developing an application that satisfies it) and coding (Instruct, using a programming language understandable to the device about the tasks to be carried out)
We also said that the difference between a code editor and an integrated development environment, is that the second includes tools for all stages of the programming process.
Stages for creating programs
The scheduling task consists of the following steps:
- Definition of the problem
- Solution planning
- Program coding
- Test the program
- Document the program
Definition of the problem
The word problem must be taken in a broad sense. Perhaps it would be more appropriate to change it by project. Basically there is a user who has certain needs that can be satisfied through the processing by a computer of the available data.
We can divide this stage into two activities:
- Determine the requirements
- Set the specs
Determine the requirements
This is where we decide what the program will have to do
For example, during the quarantine, restaurants saw their main activity change from selling food in their living room to home delivery. It is likely then that they have had to update their billing systems. A good idea would be to integrate the billing system into the ordering applications. As well as the invoicing of the day the orders actually delivered are added, the system must subtract those that for some reason could not be.
Set the specs
Once the requirements have been determined, it remains to be decided what the solution must do to satisfy them.
In our example we presume that it would be a good idea for the solution to automatically record the orders made from the applications. However, that would mean having access to their servers and we probably won't get it. Therefore, the most appropriate thing would be to establish a code in the billing system for each one and that, unless expressly indicated by the distributors, they are considered delivered.
Programmers have two very useful tools to help in the problem definition stage. Flowcharts and pseudocode writing. And, how could it be otherwise, there are applications available for Linux that allow us to use them.
Flowcharts are pictorial representations of what the program is supposed to do and how it is going to do it. Geometric figures indicate actions and arrows their sequence.
The American National Standards Institute (ANSI) has developed a standard set of flowchart symbols. Some of them are:
Rectangle: This symbol is used when a change is made to an item or input by manual or device operation. A brief description of the activity carried out is included within the rectangle.
Brilliant cut solitaire: This symbol is used to indicate the need to make a decision. According to what is taken, a certain path will be followed, so that from the diamond there is a bifurcation in the process. Each of the alternatives has a branch with its name. A brief description of the nature of the decision is included on the diamond.
Arrow: Connect the activities and decisions indicating the order in which they occur.
Big circle: Indicates a process stop to allow a review or approval. A brief description is included within the circle.
Triangle: Indicates the file of an output.
In the next article we will see what is the pseudocode that the program uses to write it and to make flow diagrams.
Great idea to make these posts to create programs in Linux!
Thank you