SCMP 318.0X Software Development F21

James Skon, Hayes 310, 740-427-5369

Department of Mathematics and Statistics

Location: Hayes 203
Time: 12:10, Days: MWF

Office hours (in person and remote):

Tutor – Ryan Schultz:

Email: schultz4@kenyon.edu)
Tutor Location: Hayes 309
Tutor Times:

  • Monday: 4-5pm
  • Tuesday: 12-1pm
  • Wednesday: 5-6pm
  • Thursday: 10-11am
  • Friday: 2-3pm

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 Overview

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 Objectives

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. Create and set up virtual machince running Linux in the cloud (Azure)
  9. Be capable of creating and using a MySQL database using SQL and phpmysql.
  10. Write JavaScript code using HTML, CSS and jQuery.
  11. Be able to create an HTML and JavaScript front end that communicate with a C++ program through an Apache2 web server.
  12. Design and develop web based data visualization components and user interfaces that use quality metaphoric concepts.
  13. Be able to produce JavaScript and/or C++ effectively processes XML documents.

Text

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

Grading

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.)

Category%Notes
Homework20%
Quizzes15%
Individual Projects45%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 Project20%Similar grading as above. All members are typically given the same grade unless there is evidence of certain team mambers.
TOTAL100%

Class server

This call will use a server at: http://jimskon.com. However, if it is down you can also get to it via: http://98.100.252.181/.

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
  • AJAX and CGI communication
  • XML Processing
  • JQuery
  • SQL
  • SQL and C++
  • Set Up a Node.js App

Tools

cslab.kenyon.edu links

Languages/Libraries

Tutorials/Reference

Links

Schedule

View Page

Date Topic Reading/Info Quiz Slides
Video
Assignment Due
Aug 27 Course Intro
Software Construction
Chapter 1  

Intro
Software Construction

Student Information
Aug 30 Introduction to Linux
First Program on Linux
Windows SSH
PuTTY
Mac OS SSH
linux command summary
  Linux  
Sept 1 Linux
Console Programming Ubuntu Environment
Read: Linux for beginners
Atom
Ftp-remote-edit
Quiz Linux Linux HW
Sept 3 Software Metaphors
Inverted Index
Chapter 2 – Software Metaphors
Text Search code
C++ github
Python github
Map STL c++
Quiz Metaphors HW – Your console program on Linux.
           
Sept 6 Make Files Make Files
Make Tutorial
Quiz Make Files  
Sept 8 Name and Text Search Programs Operation, Installation C++ and Python Namesdemo
Shakespeare C++
Shakespeare Python
Sorted Dictionary
Name Data Files
Map STL c++
     
Sept 10 Project 1 Overview Chapter 3.1-3.3 – Software Prerequisites
Project 1
drawio in Google
Designing Classes using drawio
Quiz Chapter 3 HW – Console Programs on Linux
Sept 13 Project Preparation Chapter 3.4-3.6 – More Prerequisites
C++ parsing CSV lines: String, Int
Quiz   Project 1 Object Oriented Design HW
Sept 15-17 NameDemo
Web Code Overview

NamesDemo C++
NamesDemo Python
C++ Github
Python GitHub

 

JavaScript
JSON
HTML
Fetch

 
Sept 20 Key Construction Decisions
Design in Construction
More review of Web Code
Chapter 4 – Key Construction Decisions Quiz Chapter 4  
Sept 22 HTML, CSS HTML Tutorial
CSS Tutorial
Quiz HTML&CSS  
Sept 24 Project 1 – part 2 Overview
BootStrap
Bootstrap, BootStrap Course, BootStrap Tutorial   Bootstrap Project 1, Part 1
HW – Web Name Program on server
Sept 27 Web page communication

How JavaScript Fetch Works

Python CGI Programming
C++ Web Programming
Shakespeare Web Program, C++ github
Python Version, Python github
Create Web Shakespeare 

  CGI and AJAX
Class Video
 
Sept 29 Javascript and the DOM Javascript Tutorial, Another
JavaScript Video
Javascript DOM access
Course on JavaScript
Quiz Javascript and DOM HTML, CSS, Bootstrap
Oct 1 Chapter 5.1-5.3 Chapter 5 – Design in Construction Quiz Chapter 5  
Oct 4 Project 1, Part 3:Client/Server Web Marvel Fifo’s for communication, Stateless server
Name Server Client/Server:
C++, C++ Github, Python, Python Github
   

Project 1, Part 2

Javascript HW

Oct 6 Chapter 5.4-5.6
Client/Server Code review
  Quiz Chapter 5 HW – Client Server Name Program on Web
Oct 11 Introduction to XML XML Introduction, XML Tutorial– Review up to XML Attributes section before class for quiz. Quiz XML Overview
Introduction XML Part 1

Introduction XML Part 2
Introduction XML Part 3
 
Oct 13 Project 2: Zork Project 2: XML Project   Inheritance in JavaScript  
Oct 15 XML Lookup Tutorial: Parsing XML with JQuery
Watch: Reading XML File with jQuery 1 & 2
MathML, Shakespeare
XML Parser for C++ , Documentation
    Project 1, Part 3
Oct 18 User Interface Design User Interface Design Basics
Principles of User Interface Design
User Interface Design Tips, Techniques, and Principles
Interface Hall of Shame
  User Interface Design
Video
 
Oct 20 Introduction to Git and Github  GitHub for beginners Quiz Introduction to git and github
SampleCode
 
Oct 22 Working Classes Ch 6 Quiz Working Classes Project 2, Design
Oct 25 Introduction to SQL
phpmyadmin
MySQL and the World Database
SQL World Database, phpmyadmin, SQLTutorial, phpmyadmin Tutorial Quiz Intro SQL
SQL
 
Oct 27 PhoneApp Review PhoneAppC++( GitHub), Python( GitHub)      
Oct 29 Project 3 Overview Project 3   Class Video  Git HW
SQL HW 1- phpmyadmin
Nov 1 High-quality Routines
Group Formation
Ch 7 Quiz High-quality Routines
Class Video
Project 2 – partial operation
MySQL HW 2

 

Nov 3 Node.js Introduction to Node.js
Node with Express (read and review both)
Rest Interfaces
Favicon Generator REST API
JSON
Class Video
PhoneApp
Project 3 Team Proposal
  Node.js and Express
PhoneApp
Introduction to Node.js
Node.js and Express
PhoneNodeREST, github, socketChat, github
Draw on Canvas Node.js
Socket.io
Socket.io tutorial
Class Video
 
Nov 8 Adventure Demos Project 3 Teams     Project 2, Complete
Nov 10 Defensive Programming
PhoneApp
Ch 8 Quiz Defensive Programming
Class Video
Set up apps with node.js
Node JS ports
Nov 12 Collaborative Programming Ch 21 Quiz Collaborative Programming
Class Video
Project 3: Conceptual Design proposal
Nov 15 UI Presentations     Class Video  
Nov 17 General Issues with Variables
Variable Names
Chapter 10, 11
PhoneBook program using socket.io
Quiz Variables
Variable Names
Project 3 Software Design
Node.js updated App
Nov 19

Debugging

Chapter 23
Bootstrap Tutorial
Bootstrap Modal, Bootstrap Modal
Quiz Debugging
Class Video
Project 3: Prototype 1
Presentation of project status
Nov 29 Personal Character Chapter 33 Quiz Personal Character
Class Video
 
Dec 1 Demonstrations Demos of partially working solution
Updating Node Version
  Slides  
Dec 3 Code Reviews Code Review Instructions   Cookie Example Node.js updated App
Project 3: Code review
Dec 6 The Software-Quality Landscape Chapter 20 Quiz The Software-Quality Landscape
Class Video
Project 3: Prototype 2
Dec 8 Developer Testing Chapter 22 Quiz Developer Testing
Class Video
 
Dec 10 Refactoring Chapter 24 Quiz Refactoring
Class Video
Final Project Complete
Dec 15 Final Exam
1:30-4:30 pm
       

View Page

Project Grading Rubric

View Page

CriteriaExcellentAcceptableUnacceptable
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%

Team Demo Rubric

RequirementCommentsPointsScore
Meets Functional Expectations40
Presentation Organization30
Preparation – Team is prepared with examples30
Total100

Non Discrimination Statement

Kenyon College does not discriminate in its educational programs and activities on the basis of race, color, national origin, ancestry, sex, gender, gender identity, gender expression, sexual orientation, disability, age, religion, medical condition, veteran status, marital status, genetic information, or any other characteristic protected by institutional policy or state, local, or federal law. The requirement of non-discrimination in educational programs and activities extends to employment and admission.

All employees, including faculty, are considered Responsible Employees and must notify the College’s Civil Rights & Title IX Coordinator with any relevant information.

For further information, please refer to the following Kenyon College policies:

Sexual Misconduct & Harassment: Title IX, VAWA, Title VII:
Pythonps://www.kenyon.edu/directories/offices-services/ocr/title-ix-vawa/kenyon-policies/title-ix-policy/

Discrimination & Discriminatory Harassment Policy (non sex or gender):
Pythonps://www.kenyon.edu/directories/offices-services/ocr/discrimination/

ADA & Section 504:
Pythonps://www.kenyon.edu/directories/offices-services/ocr/discrimination/504-ada-grievance/student-grievance-procedure-resolving-complaints-under-ada-section-504/

Disabilities

If you have any disability and therefore may have need for some type of accommodation in order to participate fully in this class, please feel free to discuss your concerns in private with Erin Salva, director of Student Accessibility and Support Services (SASS). (phone: (740) 427-5453).

Statement on Title IX

Kenyon College does not discriminate in its educational programs and activities on the basis of race, color, national origin, ancestry, sex, gender, gender identity, gender expression, sexual orientation, disability, age, religion, medical condition, veteran status, marital status, genetic information, or any other characteristic protected by institutional policy or state, local, or federal law. The requirement of non-discrimination in educational programs and activities extends to employment and admission.

All employees, including faculty, are considered Responsible Employees and must notify the College’s Civil Rights & Title IX Coordinator with any relevant information.

For further information, please refer to the following Kenyon College policies:

Sexual Misconduct & Harassment: Title IX, VAWA, Title VII:

https://www.kenyon.edu/directories/offices-services/ocr/title-ix-vawa/kenyon-policies/title-ix-policy/

Discrimination & Discriminatory Harassment Policy (non sex or gender):

https://www.kenyon.edu/directories/offices-services/ocr/discrimination/

ADA & Section 504:

https://www.kenyon.edu/directories/offices-services/ocr/discrimination/504-ada-grievance/student-grievance-procedure-resolving-complaints-under-ada-section-504/

Scroll to Top