Department of
Mathematics and Computer Science
Adelphi
University
Spring 2015
0145-480-001 |
Senior Seminar in
Information Systems – 3 credits TR 1:40 – 2:55 in
SCI 227 Visiting
Professor Kristin Pepper 102
/ 103 Post Hall (516)
297-5241 |
Office Hours |
Tuesday
8:40 – 10:40; 12:30 – 1:30 Wednesday
2:15 – 4:15 Thursday 8:40 – 10:40 |
Course Description
and Purpose |
Form teams and apply expertise from other
CSC courses in solving substantial real-world information systems problems.
Each team will research, propose, design, implement, and report on solutions
to one or more such problems, with careful and professional-quality
documentation at each step. |
Gen Ed Learning Goals and
Distribution Requirements |
Quantitative
Reasoning Written
Communication Critical
and Integrative Thinking |
Course Learning
Goals |
Students will spend
most of the semester building a project of significant scope that requires
recall, integration, and application of techniques learned from many previous
courses. The team will manage code via a GIT repository. Database management skills will be reviewed
and incorporated into the project if appropriate. Students will use agile
project management methodology to control meeting deliverables, and will
demonstrate both system analysis and writing skills with UML diagrams,
technical specifications and user documentation. The project development
cycle will emphasize test driven development whenever possible. Teams will
periodically present their accomplishment of the deliverables via oral
presentations. The project should be a resume building project that may
interest a potential employer. |
Prerequisite |
Senior
Standing open only to CS and CMIS Majors. |
Required Texts |
Crookshanks, Ed. Practical Software Development Techniques: Tools and Techniques
for Building Enterprise Software. S.l.: Createspace Independent, 2013. ISBN: 978-1492334293 Fowler, Martin, and Kendall Scott. UML Distilled: A Brief Guide to the
Standard Object Modeling Language. Reading, MA: Addison Wesley, 2000.
ISBN: 078-5342193688 A flash drive is
also recommended. |
Topics |
NOTE
ON FINAL EXAM PERIOD: All students must attend the final exam period session
in which you and your colleagues will give a final presentation of your
projects. The schedule can be found at http://ecampus.adelphi.edu/registrar/exams.php ) |
Major Assignments |
The
final project is the major assignment, with the following deliverables:
(While some projects may need modified deliverables, ALL CHANGES to these
deliverables must be agreed to in writing.)
Each
project must meet the following qualities: (Teams are preferred, but
individual projects can be proposed. )
|
Grading |
The
project must be completed as a minimum for credit. 10% will be dropped for each day late. Be sure to back up your work frequently so that you do not lose work.
The
course grading scale is: A 93-100, A- 90-92, B+ 87-89, B 83-86, B- 80-82, C+
77-79, C 73-76, C- 70-72, D 60-69, and F is below 59. A+ is given at the
professor's discretion. The
final grade will be a traditional letter grade (A-F). Excessive absences,
lateness, and any activities which run counter to the best interests of the
class will be deducted at the end of the semester from the final grade as a
percentage to be determined by the professor. Grade
Percentages: Oral Presentations
- 20% Documentation
Deliverables – 40% Code or detailed
content Deliverables - 40% |
|
|
Attendance |
The
following is the Adelphi University General Attendance Policy: Only students who are registered for courses, and whose
name appears on the Official Class Roster may attend courses at the
University. Adelphi students make a commitment to be active participants in
their educational program; class attendance is an integral part of this
commitment. Attendance requirements for each course will be announced by the
faculty member at the beginning of each term. Students are expected to be
present promptly at the beginning of each class period, unless prevented by
illness or by other compelling cause. In the event of such absence, students
may request that faculty members be notified by the Office of Academic
Services and Retention. Students are responsible for completing course work
missed through absences. Students should wait a reasonable length of time for
an instructor in the event that the instructor is delayed. Additionally,
you are also responsible for whatever work is covered in class whether or not
you are there. If the University is closed for any class session
due to an emergency, log onto this course site under the MOODLE tab in eCampus each day for instructions and assignments. Please check your Moodle News on snow
closing days as snow days will be replaced with online meetings. |
Moodle |
All
course materials will be delivered through Moodle. The All Assignments task
will describe all assignments and due dates. Use Moodle to hand in all
assignments. A Moodle tutorial can be found at http://fcpe.adelphi.edu/moodle/student/ |
This
is a weekly schedule. All reading should be done by the beginning of the week.
The professor reserves the right to change this schedule.
Date |
Week |
Subject
and Deliverable |
Deliverables |
Assigned
Reading |
1/27,
1/29 |
1 |
Form
work groups Development
Methodology (Waterfall / Gantt chart ; Agile / Burn down chart) |
Practical:
chap 6 UML:
chap 2 |
|
2/3,
2/5 |
2 |
Software
Requirements Documentation UML
Diagrams – Activity, Use Case, Package |
Personal
Goal Setting statement |
Practical:
chap 8 UML:
chap 1, 9, 11 |
2/10,
2/12 |
3 |
UML
- CRC cards |
Project
proposal document |
Practical:
chap 9 UML
chap 4 |
2/17,
2/19 |
4 |
Just
enough SQL Agile
/ Burn Down Chart GIT
version control |
Weekly
progress report |
Practical:
chap 1 Practical: chap 7 |
2/24,
2/26 |
5 |
|
Requirements
Analysis Document Gantt
chart Oral
Presentation |
|
3/3,
3/5 |
6 |
Design
Patterns UML-Class,
Sequence and State diagrams |
Weekly gantt chart update |
UML: chap 3, 4, 10 |
3/10,
3/12 |
7 |
|
Technical Design Document Burn down chart Oral Presentation |
|
3/17,
3/19 |
|
NO
CLASSES |
|
|
3/24,
3/26 |
8 |
3/30 – Last day to withdraw Unit
testing and Test driven development and Test plan writing Build Tools |
Weekly burn down chart |
Practical:chap 2, 4 |
3/31,
4/2 |
9 |
|
Weekly burn down chart |
|
4/7,
4/9 |
10 |
|
Weekly burn down chart First sprint cycle result – working release code System Test plan Oral Presentation |
|
Date |
Week |
Subject
and Deliverable |
Deliverables |
Assigned
Reading |
4/14,
4/16 |
11 |
|
Weekly burn down chart Annotated reference material summary |
|
4/23 |
12 |
(no
class 4/21 – research Day) |
|
|
4/28,
4/30 |
13 |
|
Weekly burn down chart |
|
5/5,
5/7 |
14 |
|
Installation and training at end user sites Weekly burn down chart User Manual Installation Manual |
|
5/12
|
15 |
Note that 5/13 is a makeup day and attendance will
be optional |
Final Project Presentations Analysis of planned vs
actual hours on each task Future Release document listing backlog stories
and tasks skipped |
|
5/14
|
|
|
Final Project Presentations Critical Self Reflection |
|
Turnitin |
Adelphi
University has a license agreement with Turnitin.com, a service that helps
prevent plagiarism from Internet resources. I reserve the right to request an
electronic copy of any written assignment submitted in this course for review
through Turnitin.com. Please see Adelphi's tips for students on preventing
plagiarism and student instructions for Turnitin.com for more information. |
Students With
Disabilities |
If you have a disability that may impact your
ability to carry out assigned course work, and are not enrolled in the
Learning Disabilities Program, it is important that you contact the staff in
the Disability Support Services Office (DSS), University Center, Room 310,
(516) 877 3145. DSS@adelphi.edu. DSS will review your concerns and determine,
with you, appropriate and necessary accommodations. All information and
documentation of disability is confidential. |
Honor Code |
Students
enrolled in this course are expected to abide by the Adelphi University
Honor Code. The purpose of the Honor Code is to protect the academic
integrity of the University by encouraging consistent ethical behavior in
assigned coursework by students. Following is excerpted from the Student
Honor Code: The
code of academic honesty prohibits behavior, which can broadly be
described as lying, cheating, or stealing. Violations of the code of academic
honesty will include, but are not limited to, the following: 1.
Fabricating data or citations 2.
Collaborating in areas prohibited by the professor 3.
Unauthorized multiple submission of work 4.
Sabotage of others' work, including library vandalism
or manipulation 5.
Plagiarism: presenting any work as one's own that is
not one's own 6.
The creation of unfair advantage 7.
The facilitation of dishonesty 8.
Tampering with or falsifying records 9.
Cheating on examinations through the use of written
materials or giving or receiving help in any form during the exam, including
talking, signals, electronic devices, etc. Avoid
coding plagiarism: Any code you even vaguely take from the internet needs to
be cited in comments. If an algorithm you found was used as a basis, cite it.
Any person helping you, even a tutor, needs to be listed in the comments. If
you work with another person doing homework, include them in your
comments. If you include any piece of
code you do not fully understand for your final project, comment that you are
using it as a black box. You are responsible for explaining how every piece
of code works except those you designate as "black box" portions. |
Student Course Evaluations |
During
the last two weeks of the class, you will receive notification, via mail and eCampus, that the course evaluation is available for your
input electronically. Availability will end at the start of the final examination
period. Your feedback is valuable and I encourage you to respond. Please be
assured that your responses are anonymous and the results will not be
available to the instructor until after the end of the semester and therefore
after course grades have been submitted. |