NEW ENGLAND INSTITUTE OF TECHNOLOGY

INFORMATION TECHNOLOGY DEPARTMENT

Software Engineering
AS Capstone Project
SE 265.06
Summer 2014
Meeting Days, Times, and
Rooms: Tuesdays: 5.45 -10.40 PM, N 208
We also meet on Friday 8/29 from 5.45-10.15 PM
Instructor/Title: Erik van Renselaar, Professor and Department Chair
Telephone/Extension: (401) 780-4190
E-mail address: evanrenselaar@neit.edu
Office location: N 240G
Office hours: MWR: 1.00-2:30 PM, T: 430-50 PM
Course prerequisites: SE 255 and SE 266 or instructors approval

Required textbook: None.

Course description: This course provides an opportunity for each student
to develop a substantial project in an area of interest.
The resulting project, in conjunction with a faculty
member, can include work conducted with companies
in the area. The culmination of this course is a major
presentation of project results.

Course objectives/Assessment measures:

The objective of the capstone project is to integrate skills learned during the
students time at New England Tech. A real world application is developed over a
period of 10 weeks. Your success in this class depends on the quality of your
documents and implementation.
Students are encouraged to come with their own suggestions for a project. The
project must be implemented using at least one of the following programming
languages: C++, C#, PHP or ASP.Net

The project will also need to include one major Enterprise DBMS such as SQL
Server, MySQL or Oracle. Depending on the complexity of the application, this
requirement may be waived by the instructor.

There is a strong emphasis on participation and demonstrating your weekly
progress. You are expected to utilize the class time to work on your project and
spend at least another 4 hours outside of the classroom. Teams will meet with
the instructor on a weekly basis to review the progress for each individual and
SE 265.56 Summer 2014
Page 2
the team as a whole. You will also need to submit a weekly report of your
progress for the week as well as a bulleted list of goals for the following week.

All of the documents will be graded based on completeness, neatness and
accuracy. Your score for the implementation is based on the correctness of your
solution as well as how you solved the problem (did you do it the hard or easy
way) and of course whether or not your application is well structured, easy to
read (comments, meaningful variable and constant names and so on).

You will receive a participation grade for each class. Its important to be punctual
and not leave early. You will lose 10 points for each 15 minutes that you come in
late or leave early.

You cannot pass the class without presenting the project.

Your presentation should be at least 10 minutes long but no longer than 15
minutes. Your presentation must include a Powerpoint presentation that as a
minimum discusses the following:

introduction of the team members
overview of your project
discussion of the timeline
database organization
discussion of obstacles overcome
discussion of technical design
summary

Your presentation you must also include a live demonstration of the finished
product. This must not take more than half of the presentation, however.

The web site that details your capstone project will be housed on ict.neit.edu. As
a minimum, you must include:
- Introduction of each of the team members and a detailed description of the
responsibilities of each member
- PDF version of your proposal
- PDF version of the prototype
- PDF version of the technical document
- Relationship Diagram of your database
- Screen shots of your application
- Copy of the Powerpoint presentation
In order to pass the class, every team member must email a URL to the
instructor no later than 11:59 PM on Tuesday, September 23
rd



SE 265.56 Summer 2014
Page 3
INSTRUCTOR POLICIES

Evaluation and Grading Criteria: maximum of 1600 points

Proposal : 100 points
Prototype : 150 points
Database design and implementation: 100 points
Technical Design : 100 points
Status Reports : 300 points
Participation: 100 points
Implementation : 500 points
Presentation week 10: 100 points
Web site documenting your project: 150 points

Tardiness:

Each deliverable turned in late will have its grade reduced by 10 points (out of a
possible 100) per day.

COLLEGE POLICIES

Academic Honesty Policy:
Any project, paper, or examination is expected to be the students own work, in
the students own words. Willful academic dishonesty (including but not limited to
copying another students work or allowing ones own work to be copied; using
notes or books during an examination without the instructors advance
permission; presenting information or images copied from a book, journal, or
online source as ones own) will not be tolerated.

Other Policies:
Each student is responsible for accessing the
http://wcb.neit.edu/shandbook/syllabuspolicies.pdf web site and becoming
familiar with all academic policies.
The design of this course as outlined in the syllabus requires you to do
work outside of class to be successful.

ACADEMIC SUPPORT
Academic support services are available through the Academic Skills Center,
Student Support Services, and the Library.

Caveat
NEIT reserves the right to change the above schedules and requirements without
advance notice.

SE 265.56 Summer 2014
Page 4


Schedule
Week Topic In-Class
Activity/Assignments
Out-of-Class
Activity/Assignments
Due
Dates
1 Proposal and
prototype
Review Sample Proposal.
Discuss Possible Topics.
Review Prototype
Process
Web Site Expectations

Complete Sample Proposal
with Team
Continue Prototyping
Create Weekly Status Report

J ul 27
2 Prototype Review current status of
prototype
Finish Prototype
Create Weekly Status Report
Work on web site skeleton

Aug 3
3 Database
Design
Tech Design
Review database design
Discuss Tech Document
Discuss Connection to DB
Complete tech design; SQL for
databases
Create Weekly Status Report

Aug 10
4
Implementation Work on Implementation Update web site
Create Weekly Status Report

Aug 17
5
Implementation Work on Implementation Update web site
Create Weekly Status Report

Aug 24
6
Implementation Work on Implementation Update web site
Create Weekly Status Report
Aug 31
7
Implementation Work on Implementation Update web site
Create Weekly Status Report

Sep 7
8
Implementation Work on Implementation Update web site
Create Weekly Status Report

Sep 14
9
Testing/Fixing Work on Implementation Update web site
Create Weekly Status Report

Sep 21
10
Testing/Fixing Final Presentation Finalize web site Sep 28