Software Paradigms

Description

2. Transition Overview of the “Four Software Paradigms” (length 1-page). What were the driving forces to create each paradigm. Why sustain the overlap bridge of paradigms.  3. Paradigms: 1) Imperative; 2) Functional; 3) Logical; 4) Object Oriented. Discuss (for each paradigm length 1-page):  a. History  b. Characteristics  c. Who were primary and secondary users  d. Era Advantages  e. Era Disadvantage f. Paradigm line chart relating programming approach (y-axis) to time (x-axis)  4. Chart the overlap bridge of paradigms: Plot all four software paradigms on one graph. Along the Y-Axis characteristic shift in difference between Imperative(the How) and Declarative(the What), along the X-Axis a timeline 1940’s to Present. Add a fifth line representing the programming approach over time. Note any intersections.  5. Programming approach summary: Declarative vs Imperative (length 1-page). Narrative elaboration and illustration diagram the Declarative-What vs Imperative-How. Declarative Languages – The programmer specifies what to be computed Imperative Languages – The programmer specifies how to be computed.  6. Question: Denote which came first the demand for change or change itself? Demand could be a thought about doing something which does not exist yet.