Northcentral Technical College Introduction To Programming
10-152-310
Introduction to Programming with JavaScript NTC 10-152-310

Learning Plan 5 5.3 Project Instructions

# 5.3 Project Instructions

> I love deadlines. I like the whooshing sound they make as they fly by. - Douglas Adams

#### Student

- Name:
- Section:
- Email:

### General Project Information

- The project consists of four parts. Each part has it's own page and specifications.
- The course projects are not group projects. You need to do you own work completely.
- If you need help on a project you should first ask your instructor. Each instructor will have their own procedure for getting help from them.
- You may talk to classmates but do not share code in any electronic or physical form. Conversations with classmates about projects should be general and not contain details about solutions.
- Don't sit down at a classmate's computer and type into their project.
- Don't ask classmates for their projects.
- There is sample output shown for each part.
- The instructor reserves the right to modify the project specifications in writing or verbally at any time. Non-attendance will not be an acceptable excuse for not completing the correct and final specifications. Changing specifications is a very real part of the IT experience.
- All code should be passed through the jsLint software, as an aid in catching course coding standards. see below.

### Important Note

> All projects must be complete and function according to the specifications before they will be graded. Be sure to ask questions about the meaning of specifications--in the world of IT, specifications are never completely free from the possibility of misunderstandings.
> There is no partial credit given for incomplete projects. Remember that if an incomplete project is submitted you will find a zero (0) in Blackboard and a message in Blackboard regarding which project parts are producing incorrect output. Review the syllabus and the "Getting Started . . ." booklet for the procedure for resubmitting an incomplete project once it has been corrected.

### Course Coding Standards

> With this project we will be looking more carefully at compliance with the course coding standards. Make sure that all parts of the project are good! Here's a link to them: JavaScript Coding Standards for 10-152-310

### jsLint

> All parts of the project should be verified by the site jsLint to help in finding standards violations. The required settings are found here. Any part of the project that doesn't pass standards requirement will be losing a number of points in this and the next Learning Unit, since those standards should now be understood. Note that Record Set processing is not known to jsLint, and any error messages regardng those functions should be ignored. For example, for a Record Set you will see something like this:

> If that is the only problem that jsLint finds that will be considered a pass of jsLint. Remember that jsLint may or may not catch all of the course coding standards. You must still check over the source code manually to doublecheck that all course coding standards have been met.

### 5.3 Project Pages

#### 5.3 Projects - Part 1

- We'll start off with debugging a program again. You can never have too much practice.
  - Part 1

#### 5.3 Projects - Part 2

- Now on to some coding.
  - Part 2

#### 5.3 Projects - Part 3

- Grade Report.
  - Part 3

#### 5.3 Projects - Part 4

- Just One More!
  - Part 4

### Project Submission

- Zip and submit your files in Blackboard
- Don't Forget to also zip the JavaScript File with you HTML File