Tags: %TAGME{ tpaction="" web="Main" tag="" }% view all tags

SCMP318 Software Development

James Skon
Fall 2019
Location: Hayes 310, Time: 11:10, Days: MWF
Office hours: 2-3 Mon & Wed, 3-4 Tues & Thurs, 10-11 Fri
There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult. C. A. R. Hoare (1980 Turing Award Lecture)

Course Learning Outcomes

This course gives students experience designing, implementing, testing and debugging moderately complex systems of software components that collectively form a multilayer application. There will be an emphasis on crafting quality code, designing and implementing effective user interfaces, and building multicomponent architectures using a mix of off-the-self and custom code. Topics will include direct file I/O, inner-process and inter-system communication, multi-threading, and the synchronization of shared resources, web interfaces, data visualization and working with large data sets. For two projects students will work in project teams. Students will primarily use C++, but also will learn Javascript and other languages as needed. Prerequisite: SCMP 118 or permission of instructor.

Course Outcomes

At the completion of this course the students should

  1. Exhibit best practices in creating code that is well structured and organized using object-oriented concepts.
  2. Exhibit an understanding of quality use of identifier naming within code.
  3. Be capable of providing appropriate internal documentation within code.
  4. Understand and utilize proper use of internal barricading and error checking of values within a program.
  5. Be capable of creating detailed requirement for a problem bending solved.
  6. Be capable of creating architectural designs for multi-component software systems.
  7. Be capable of collaboration in software development including pair-programming, peer design and code reviews.
  8. Be capable of creating and using a MySQL database using SQL and phpmysql.
  9. Write JavaScript code using HTML, CSS and jQuery.
  10. Be able to create an HTML and JavaScript front end that communicate with a C++ program through an Apache2 web server.
  11. Design and develop web based data visualization components and user interfaces that use quality metaphoric concepts.
  12. Be able to produce JavaScript and/or C++ effectively processes XML documents.


Code Complete, Second Edition; Steve McConnell;
Microsoft Press; 2nd edition (June 19, 2004)


Due Date: All assignments are due as specified in the grading table below.

Missing Lab Assignments: Labs are an important part of this class; the effort spent on them is a crucial part of the learning process. Failure to submit labs is unacceptable: students earning 0s on two labs cannot receive a grade higher than a B- for the course; students earning three 0s on labs will receive an automatic F for the course.

Collaboration and Academic Honesty: In order to facilitate learning, students are encouraged to discuss assignments amongst themselves. Copying a solution is not, however, the same as “discussing.'' A good rule of thumb is the “cup of coffee'' rule. After discussing a problem, you should not take away any written record or notes of the discussion. Go have a cup of coffee or cocoa, and read the front page of the newspaper. If you can still re-create the problem solution afterward from memory, then you have learned something, and are not simply copying. (The “group work” are exempt from this, as they are intended to be done together.)

Homework 15 Due by class time on day assigned. Not accepted Late
Quizzes 10 In class, at beginning. Weekly. No makeup without medical note.
Individual Project 30 Due by midnight on day due. 5% penalty for for up to 12 hours late. One assignment may be up to 24 hours late with no penalty with instructor notification. Projects have intermediate milestones and final complete project. Each milestones are typically worth 10-20 points, while the final grade is 100 points.
Team Project 30 Similar grading as above. All members are typically given the same grade unless there is evidence of certain team mambers.
Exams 15 There is a traditional individual midterm, while the final is a public group presentation on the final project.

Technical Topics

  • Using the Linux Server
  • C++ Iterators and algorithms
  • Text Parsing
  • Haspmap and building an inverted index
  • Interprocess communication using FIFO class
  • Client/Server architectures
  • JavaScript, HTML and CSS
  • JavaScript with timing intervals.
  • AJAX and CGI communication
  • XML Processing
  • JQuery
  • SQL
  • SQL and C++
  • Set Up a Node.js App



cslab.kenyon.edu links




Disability Statement

Kenyon College values diversity and recognizes disability as an aspect of diversity. Our shared goal is to create learning environments that are accessible, equitable, and inclusive. If you anticipate barriers related to the format, requirements, or assessments of this course, you are encouraged first to contact the office of Student Accessibility and Support Services (SASS) by emailing Erin Salva at salvae@kenyon.edu, then to meet with the instructor to discuss accommodation options or adaptations.


DateTopicReading / InfoQuizSlidesAssignment Due
Aug 30 Software Construction
Project 0: Programming in the Linux environment
Chapter 1
Census Name Information Demo (c++)
Census Name Demo (python) NamesDemo (C++)
NamesLookup (Python)
Software Construction Student Information
Sept 2 Software Metaphors Chapter 2 - Software Metaphors
Linux Introduction
Project 0, Atom
Notepad++, BBEdit , EMACS
Link Metaphors
Linux Slides
linux command summery
Sept 4
Name Data Demo - C++
NamesDemo code (github)
Web Names Lookup
Class Activity
Name Data Files - From US Census Data
Map STL c++
Sept 6 Name Data Demo - C++, Python Chapter 3.1-3.3 - Software Prerequisites
Examine C++ Code
Link Chapter 3 Project 0
Sept 9 Name Data Demo
Python Code
Chapter 3.4-3.6 - More Prerequisites
Project 1 Review
Sept 11 Project Preparation
Inverted Index
Project 1 Review
Requirements Checklist
[[SdProject1][Project 1] Map STL c++
Sept 13 Make Files Make Files, Make Tutorial Link Make Files Project 1 Object Oriented Design HW
Sept 16
NameDemo Web Code
Sept 18 Project 1, Part 2
NameDemo Web Code Review
C++ Github NameLookup
Python GitHub NameLookup
C++ String Parsing
Sept 20 Makefiles
Project 1, Part 2: Simple Web
The Demo code for Name program

C++ Web Programming
Project 1, Part 1

Sept 23 Javascript and JQuery. Javascript Tutorial , JQuery Tutorial , Learn JQuery , JavaScript & jQuery Tutorials Link JavaScript
Video to watch on Ajax

JavaScript & jQuery Tutorials
Sept 25 Bootstrap Bootstrap, BootStrap Course, BootStrap Tutorial Bootstrap JavaScript and JQuery Tutorial Work
Meet with Professor for code review
Sept 27 Web Programming with Ajax &
Ajax Tutorial for Beginners
Name Data Web Program Link
github Link
Sept 30 Project 1, Part 3: Client/Server Web Marvel Names with Client/Server
Fifo's for communication, Stateless server
Chapter 3 Bootstrap
Oct 2 Key Construction Decisions
Design in Construction
Chapter 4 - Key Construction Decisions Link Chapter 4
Chapter 5
Oct 4
Introduction to XML
XML Introduction , XML Tutorial - Review up to XML Attributes section before class for quiz. XML Overview
Introduction XML Part 1

Introduction XML Part 2
Introduction XML Part 3
Project 1, Part 2
Oct 7 Project 2: XML Lookup Chapter 5.1-5.3 , Tutorial: Parsing XML with JQuery
MathML , Shakespeare , Bible , Quran
XML Parser for C++ , Documentation
Demo Software: /home/class/SoftDev/cppXMLAJAX/
Link XML C++ Example , Bible C++ Link, Other examples
Oct 9
Processing XML using jQuery
Sample of C++ processing XML, CPP XML Example
XML processing with jQuery, XML with bootstrap
XML with Bible, GitHub Jquery XML, Python XML Parsing, Python XML Example
Design in Programming
Oct 14 Project 2
User Interfaces
Project 2: XML Project
User Interface Design Basics

Principles of User Interface Design
User Interface Design Tips, Techniques, and Principles
Interface Hall of Shame

User Interface Design
Project 1, Part 3

Oct 16 Introduction to Git and Github GIT Video - View for quiz , GitHub for beginners
Link GitHub.pdf
Introduction to git and github
Project 2, Design
Oct 18 Working Classes Ch 6 Working Classes
Oct 21 High-quality Routines Ch 7 Link High-quality Routines
Oct 23 Text game Demos Discussion of solutions. Demo Project 2 - partial operation
Oct 25 Defensive Programming Ch 8 Link Defensive Programming
Oct 28 Collaborative Programming Ch 21 Link Collaborative Programming
Oct 30 Midterm Exam - Study Guide Chapters 1-8, User Interface Design, GIT Link GIT HW
Nov 1 Project 3 Overview
PhoneApp Review
Project 3
PhoneApp - C++ ( GitHub), Python ( GitHub)
Project 2, Complete
Nov 4 MySQL and the World Database SQL World Database, phpmyadmin, SQLTutorial, phpmyadmin Tutorial Intro SQL
Project 3 Team Proposal
Nov 6 Introduction to SQL, phpmyadmin, node.js Learn SQL, Phone Number App Code, art.sql, PhoneApp Link PhoneApp Running with your Database
Nov 8 Project 3 Team Meeting C++/MySQL tutorials, Socket.io cheat Sheet, Chat App, Chat Code ProjectTeams Project 3 UI Design
Project 2 Code Review Deadline
Nov 11 General Issues with Variables Chapter 10 Link Variables Project 3 Software Design
SQL HW 2- phpmyadmin
Nov 13 Variable Names Chapter 11 Link Variable Names
Nov 15 Personal Character Chapter 33 Personal Character
Nov 18 Demonstrations Project 3 Prototype 1 - search and view art
Nov 20 Code Reviews Code Review Project 3
Nov 22 Automatic updating webpages Chat App , Chat Code, Live Monitoring Processes , code
Dec 2 The Software-Quality Landscape Chapter 20 Link The Software-Quality Landscape Project 3 Prototype 2
Dec 4 Developer Testing Chapter 22 Link Chapter 22
Dec 6 Demos
Dec 9 Debugging Chapter 23 Link Debugging Project 3 Prototype 3
Dec 11 Refactoring Chapter 24 Link Refactoring Checklist
Dec 13 Refactoring Presentations Final Review Signup Refactoring Slides
Final Project Complete
Dec 20 1:30-4:30am Final Presentation Project 5 Evaluation Form Final Presentation
Personal Statement

Software project grading rubric

Documented & Maintainable
(The program is well-documented with appropriate names and comments making it easy to understand.)
  • all naming conventions are followed
  • both in-line and header comments are included and clearly explain the what the code accomplishes and how
  • white space is used well
  • most naming conventions are followed
  • some comments are confusing or missing
  • white space is used well in most places
  • poor or no use of naming conventions
  • too few or too many comments are used and they are unclear or inaccurate
  • poor use of white space
Adaptable & Reusable
(The program is modular, using abstraction well and any limitations are clearly specified.)
  • all interfaces between objects are clear
  • appropriate utility functions are used and well-documented
  • most code can be reused
  • most object interfaces are clear
  • some appropriate utility functions are used and documented
  • some code can be reused
  • poor object interface definitions
  • few or no utility functions
  • no code can be reused
Robust & Correct
(The program provides the correct output for all possible input.)
  • the program works completely as expected
  • the output is displayed to specification for all valid input
  • the program responds appropriately for all invalid input
  • the program works as expected for most input
  • there may be minor errors in output formatting for valid input
  • not all invalid input is handled reasonably
  • the program does not produce correct output for even the sample input
  • the program fails to handle invalid input
  • exceptions are not caught
Efficient & Elegant
(The program uses both time and space on the computer effectively, without losing source code clarity.)
  • no extra variables or definitions are used
  • the code is small, efficient yet still easily understood
  • extra variables do not make the code harder to understand
  • brute-force problem solving approach
  • extra variables are pervasive and confusing
  • the code is unnecessarily long and patched together
25-20% 19-11% 10-0%
Topic revision: r1 - 2020-01-23 - JimSkon
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback