You are here

Author Instructions

1. How should the chapters/essays be structured?

The book will be divided into two parts. Write-ups for each part will need separate chapters.

Part I: For instructors - Basic concepts and references on (i) what and (ii) how to teach PDC topics in the context of the existing topics in various core courses.This is expected to be at a higher level (to teach or serve as a rigorous reference for the instructors), and will include learning goals, advice on presentation and use of the material, indications of where it would be appropriate in certain courses, and possibly suggestions of how student learning can be evaluated. 

Part 2: For students - Supplemental textual material for core courses which students can rely on for learning and exercises.  This is envisioned as being at the quality of a textbook presentation, with many illustrations and examples, following a sequence of smaller steps to build larger concepts. We envision the student materials as supplemental sections that could be inserted into existing texts by instructors.

Part 1 should have easily identifiable sections/subsections to address the following aspectsfor readers' ease of finding them. 

- Definitions and Concepts - can be in-depth treatment of the topic(s)with appropriate references to literature, sufficient for a good understanding by instructors

-Progressively getting into more sophisticated content - multiple section going into more depth suitable for coverage in a spiral-like fashion in successive courses

- Which courses it could be covered in? Along with which existing topics? How?

- What are good examples to employ to illustrate this topic in lower level core courses (CS1, CS2, Systems, DS/A,etc.)?

- Illustrate any pitfalls/limitations

- Bibliography

Part 2 (for students) should address the following aspects.

- Major portions of the write up should be at a fundamental level, focused on principles of PDC topics, independent of languages and platforms as much as possible. 

- The bulk of the additional courseware material related to languages, labs and tools should be supplementary material, which may aid in instruction/learning.

- The write up will need to be accessible by students yet be complete and rigorous, and in the context of existing topics. 

- Provide the context(s) for use and other tips as instructor's guide.

- Provide supporting exercises.  

- Optionally, authors may also have bibliography, create assessment questions, develop assessment instruments, and develop presentation slides, sample programs, and tools.

Descriptor Elements

Both kinds of chapters should have the following descriptor elements

            •     Abstract

•     Relevant core courses

•     Relevant PDC topics and subtopics covered at what Bloom levels?

        - refer to the curriculum proposal:

•     Context for use

•     Learning outcomes

List of Symbols and Definitions

We also request you to help populate/edit/update the common lists of symbols, terms, and definitions posted here:

This is meant to help us remove ambiguities across chapters and collaboratively develop a glossary of terms and definitions. Send your gmail id for update level access to this list.

2. Formatting Instructions

For uniformity of styles across chapters and for overall styling of the CDER book, a latex template to help format your chapter is posted at    (Zip File)  (Tar File)

-Its Readme file has basic instructions on which files can be copied or replaced to insert your text, figures, and bibliographic entries.

-We will employ IEEE Citation Reference style:

For those not so familiar with latex, the template files have example to follow (cut and paste should mostly work) and the Readme file has installation and compilation instruction.  We can also provide assistance in formatting in latex.