User Tools

Site Tools


dido:public:s_cli:05_contents:01_prt:02_basics:03_paradigim:procpro

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dido:public:s_cli:05_contents:01_prt:02_basics:03_paradigim:procpro [2021/05/01 21:29]
nick ↷ Page moved from dido:public:s_cli:05_contents:02_basics:03_paradigim:procpro to dido:public:s_cli:1_part:05_contents:05_contents:02_basics:03_paradigim:procpro
dido:public:s_cli:05_contents:01_prt:02_basics:03_paradigim:procpro [2021/08/13 13:13] (current)
murphy
Line 1: Line 1:
 ====== 2.1.3.1 Procedural Programming ====== ====== 2.1.3.1 Procedural Programming ======
-[[dido:​public:​s_cli:​05_contents:​02_basics:​03_paradigim:​start | Return to Programming Paradigm ]]+[[dido:​public:​s_cli:​05_contents:01_prt:​02_basics:​03_paradigim:​start| Return to Programming Paradigm ]]
  
-[[dido:​public:​ra:​xapend:​xapend.a_glossary:​p:​procedurallanguage]] break a problem down into a small set or procedures (i.e., Functions or Procedures) that when put together can solve the original bigger problem. In addition to the procedure calls there is the control and flow of which procedures need to be called and in which order (control flow). In addition, data can be shared and stored between the invocation of the procedures. A very important, simplistic used to visualize the activities in Procedural programming is the **Flow Chart**. However, the number and quantities of graphical tools used to represent many procedural processes is much greater than the simple [[+[[dido:​public:​ra:​xapend:​xapend.a_glossary:​p:​procedurallanguage]] break a problem down into a small set or [[dido:​public:​ra:​xapend:​xapend.a_glossary:​p:​procedure|procedures]] (i.e., Functions or Procedures) that when put together can solve the original bigger problem. In addition to the procedure calls there is the control and flow of which procedures need to be called and in which order (control flow). In addition, data can be shared and stored between the invocation of the procedures. A very important, simplistic used to visualize the activities in Procedural programming is the **Flow Chart**. However, the number and quantities of graphical tools used to represent many procedural processes is much greater than the simple [[
 dido:​public:​ra:​xapend:​xapend.a_glossary:​f:​flowchart dido:​public:​ra:​xapend:​xapend.a_glossary:​f:​flowchart
 ]]. For more details, see UML/​SysML/​SOAML as well as UPDM(( ]]. For more details, see UML/​SysML/​SOAML as well as UPDM((
Line 11: Line 11:
 )). )).
  
-  * **Note:** Flowcharts are NOT required to when representing programs or applications BUT a flowcharting technique can be used to help explain a program or an application,​ than it is most likely is using a Procedural Paradigm.+  * **Note:** Flowcharts are NOT required to when representing programs or [[dido:​public:​ra:​xapend:​xapend.a_glossary:​a:​application|applications]] BUT a flowcharting technique can be used to help explain a program or an application,​ than it is most likely is using a Procedural Paradigm.
  
 Some examples of Procedural Programming languages are: Some examples of Procedural Programming languages are:
Line 17: Line 17:
   * C/C++   * C/C++
   * C#   * C#
-  * ECMAScript (i.e., Javascript)+  * ECMAScript (i.e., ​[[dido:​public:​ra:​xapend:​xapend.a_glossary:​j:​javascript|Javascript]])
   * FORTRAN   * FORTRAN
   * Java   * Java
Line 26: Line 26:
  
 <figure proclang>​ <figure proclang>​
-{{  dido:​public:​s_cli:​05_contents:​02_basics:​screen_shot_2021-04-12_at_10.40.00_pm.png?​600 ​ |}}+{{  dido:​public:​s_cli:​05_contents:01_prt:​02_basics:​screen_shot_2021-04-12_at_10.40.00_pm.png?​600 ​ |}}
 <​caption>​Procedural Programming Control Flow</​caption>​ <​caption>​Procedural Programming Control Flow</​caption>​
 </​figure>​ </​figure>​
dido/public/s_cli/05_contents/01_prt/02_basics/03_paradigim/procpro.1619918947.txt.gz · Last modified: 2021/05/01 21:29 by nick