ACM Home Page
Please provide us with feedback. Feedback
RAPTOR: a visual programming environment for teaching algorithmic problem solving
Full text PdfPdf (269 KB)
Source Technical Symposium on Computer Science Education archive
Proceedings of the 36th SIGCSE technical symposium on Computer science education table of contents
St. Louis, Missouri, USA
SESSION: The first year: new ways to teach programming table of contents
Pages: 176 - 180  
Year of Publication: 2005
ISBN:1-58113-997-7
Also published in ...
Authors
Martin C. Carlisle  United States Air Force Academy, USAFA, CO
Terry A. Wilson  United States Air Force Academy, USAFA, CO
Jeffrey W. Humphries  United States Air Force Academy, USAFA, CO
Steven M. Hadfield  United States Air Force Academy, USAFA, CO
Sponsors
SIGCSE: ACM Special Interest Group on Computer Science Education
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 9,   Downloads (12 Months): 140,   Citation Count: 17
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1047344.1047411
What is a DOI?

ABSTRACT

When students are learning to develop algorithms, they very often spend more time dealing with issues of syntax rather than solving the problem. Additionally, the textual nature of most programming environments works against the learning style of the majority of students. RAPTOR is a visual programming environment, designed specifically to help students envision their algorithms and avoid syntactic baggage. RAPTOR programs are created visually and can be executed visually by tracing the execution through the program. Required syntax is kept to a minimum. Students preferred expressing their algorithms visually, and were more successful creating algorithms using RAPTOR than using a traditional language or writing flowcharts.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
Cardellini, L. An Interview with Richard M. Felder. Journal of Science Education 3(2), (2002), 62--65.
 
3
Crews, T., and Ziegler, U. The Flowchart Interpreter for Introductory Programming Courses. Proceedings of FIE '98, 307--312.
 
4
5
 
6
Fowler, L., Allen, M., Armarego, J., and Mackenzie, J. Learning styles and CASE tools in Software Engineering. In A. Herrmann and M.M. Kulski (eds), Flexible Futures in Tertiary Teaching. Proceedings of the 9th Annual Teaching Learning Forum, February 2000. http://ccea.curtin.edu.au/tlf/tlf2000/fowler.html
 
7
IBM (2004). WebSphere Studio: Application Developer Integration Edition. Available at http://www-306.ibm.com/software/integration/wsadie/.
 
8
Shackelford, R., and LeBlanc, R. Introducing Computer Science Fundamentals Before Programming. Proceedings of FIE '97, 285--289.
 
9
Sorensen, R. A Comparison of Software Development Methodologies. Crosstalk (January 1995).
10
 
11
vanDijk, J. AdaGraph. Online. Internet. Available: http://users.ncrvnet.nl/gmvdijk/adagraph.html.
 
12
Watts, T. SFC -- A Structured Flow Chart Editor Version 3. Faculty Poster SIGCSE 2003. Available at: http://www.cs.sonoma.edu/tiawatts/SFC/.
13
 
14

CITED BY  17
 
 
 
 
 
 
 
 

Collaborative Colleagues:
Martin C. Carlisle: colleagues
Terry A. Wilson: colleagues
Jeffrey W. Humphries: colleagues
Steven M. Hadfield: colleagues