GPCeditor

GPCeditor (and its sucessor, SODA: SOftware Design lAboratory) provided extensive support to students to facilitate their design of software in Pascal. Students using GPCeditor did not type code directly. Rather they assembled code segments called plans to achieve particular goals.

Key components of GPCeditor include:

• Lists of goals (statements of program objectives) and plans (code segments that achieve goals, or a list of subgoals which can in turn be achieved through subplans). (Upper left of figure.)
• A library of components.
• A textual code view.
• A graphical representation of the goal-plan hierarchy.

References

• Guzdial, M., Soloway, E., Blumenfeld, P., Hohmann, L., Ewing, K., Tabak, I., Brade, K., & Kafai, Y. (1992). The future of CAD: Technological support for kids building artifacts. In D. Balestri, S. Ehrmann, & D. L. Ferguson (Eds.), Learning to design, designing to learn: Using technology to transform the curriculum Norwood, NJ: Ablex Publishing Company.
• Hohmann, L., Guzdial, M., & Soloway, E. (1992). SODA: A computer-aided design environment for the doing and learning of software design. In Computer assisted learning: 4th international conference, ICCAL '92 proceedings (pp. 307-319). Berlin: Springer-Verlag.
• Soloway, E., Guzdial, M., Brade, K., Hohmann, L., Tabak, I., Weingrad, P., & Blumenfeld, P. (1993). Technological support for the learning and doing of design. In M. Jones & P. H. Winne (Eds.), Foundations and frontiers of adaptive learning environments New York: Springer-Verlag.

Contact information: