Skip Navigation

CSCI 427 - Systems Integration

Syllabus for section D1, Spring 2023.

This class is an asynchronous online course and does not have scheduled class meetings. However, there is a group project requirement, and your group will need to schedule synchronous meetings as needed.

Instructor Information

Dr. Mike Murphy
mmurphy2@coastal.edu
Office Location: Penny Hall (formerly AOC2) room 238
https://ww2.coastal.edu/mmurphy2

Office Hours

Student Learning Outcomes

Upon successful completion of this course, you should be able to:

  1. Translate user requirements into information technology requirements
  2. Analyze requirements and design an appropriate information architecture and corresponding implementation plan
  3. Implement an information technology infrastructure using current technologies, standards, and best practices, as a member of an implementation team
  4. Integrate an information architecture into an existing system at the software, hardware, and user levels.

ABET Assessment

This course measures the following Performance Indicators:

Texts and Materials

Technology Requirements

Grading

Grades will be broken into different categories and weighted as follows:

Category Weight
Project Outcome 30%
Project Process 20%
Participation 50%

The final course grade will be computed using the standard 10-point scale:

Grade Range
A 90-100
B+ 85-89
B 80-84
C+ 75-79
C 70-74
D+ 65-69
D 60-64
F 0-59

There is NO final exam in this course.

The Project

This course is based upon a hands-on technical project that is designed to require about 10 hours per week of effort for the entire length of the semester. Several project choices are available, and each project is broken into a series of logical milestones to guide you through the implementation process. Each milestone requires the submission of a recorded presentation and demonstration in MP4 or WEBM format.

Each milestone receives a progress grade that counts toward the Project Process category. This grade reflects how well the project has been implemented according to the timeline expected by the milestone. At the end of the semester, a separate grade is assigned for the Project Outcome, which will reflects how well the implementation meets requirements and specifications by the end of the semester.

Teamwork

As this course assesses an ABET-required group work outcome, teamwork is required for this course. You will be working with 1 or 2 other students as part of an implementation team to get the project working. Half your grade for this course is based upon your individual participation in the team effort; without satisfactory participation, passing this course with the required minimum grade (C or better) will not be possible. If you are unable to commit the time required for the group project this semester, I strongly advise that you delay taking CSCI 427 until a semester in which you can accommodate the group project in your schedule. There is no way to waive this requirement, since all degree programs in the Department of Computing Sciences must fulfill accreditation expectations.

The team will share the grade for the Project Outcome and Project Process assessments. Each individual team member will receive an individual Participation grade. It is your responsibility to ensure that your contributions are accurately reflected in the project submissions and that you have properly documented your involvement in the project.

I reserve the right to assign teams as required. In addition, if your teammates report that you are habitually absent from team meetings, are habitually late delivering contributions, or are otherwise not participating in the team project according to expectations, I may reassign you to a team in which other members are similarly unreliable. Your Participation grade will also receive a substantial negative impact.

Milestone Expectations

For each project milestone, your team will submit a single presentation in MP4 or WEBM video format. This presentation will contain both answers to milestone-specific questions and a live demonstration of your project implementation. Screenshots of the project implementation are NOT acceptable substitutes for the live demonstration. If your computer cannot run screen recording and virtualization software at the same time, then a team member will need to record the demonstration portion of the presentation using a cell phone or video camera. Be sure to leave sufficient time for post-processing the final video, as only one video file will be permitted for each milestone submission.

One common component for each milestone presentation will be a description of the individual contributions of each member of the team. These contributions will form the basis of the Participation grade for each milestone. Since this is the capstone course for the Information Technology degree, it is expected that each team member will make a substantial, technical contribution to each milestone.

For the avoidance of doubt, the following activities are NOT substantial, technical contributions to a milestone:

A good rule of thumb to use is that if a freshman could do it, then it probably isn’t a substantial, technical contribution. Failing to have substantial, technical contributions for a milestone will result in a low Participation grade for that milestone.

Late Work

Each milestone has an automatic one-week extension between the DUE date and the closing date. There is no need to submit documentation or request an extension since one is provided automatically. That said, you should treat the DUE dates as due dates and not habitually submit work on or just before the closing date.

No work will be accepted after the corresponding closing date for ANY reason whatsoever. It is your responsibility to plan ahead and be prepared for any contingencies that might arise during the semester (including illness, family emergencies, work conflicts, and other things beyond your immediate control). It is also your team’s responsibility to ensure that you have adequate time for post-processing and transcoding your milestone submission videos. There is no such thing as an “excused” reason for an extension beyond the closing date for any work in this course. I am instead providing you with a no-questions-asked extension on every milestone to provide flexibility for handling unexpected events.

If a member of your team becomes unresponsive, or if you know that a team member is hospitalized or otherwise incapacitated, let me know immediately.

Incomplete Grades and Alternatives

I have structured the DUE dates in this course to avoid making anything due on the last week of class. Since an automatic one week extension is provided (which can run into exam week), there is already contingency time built into the course to account for illnesses and emergencies. For this reason, I will NOT assign grades of Incomplete for this class.

If you encounter a significant hardship early in the semester that precludes successful completion of this course, then it is advisable to drop the course by the deadline for a “W” grade. Should you have a health issue (physical or mental) that substantially impairs your ability to finish the course after the drop deadline, the University has a policy for medical and psychological withdrawal that should be followed. For hardships that are not covered by this policy, you may consult with your academic advisor regarding an Academic General Petition for a retroactive withdrawal from this course after final grades have been posted.

Attendance Policies

Regular participation in class is expected, but I do not record or grade attendance. Participation in team activities, as scheduled by the team, is a hard requirement. Your Participation grade may be negatively impacted if you miss or are late to team activities.

Please do NOT attend physical office hours if you are sick. Instead, please let me know via email at least an hour before the scheduled meeting so that you can participate electronically. Similarly, teams that elect to meet in person should make provisions for electronic meetings if anyone in the group becomes ill during the semester.

Other Policies

Academic Integrity

The CCU Academic Integrity Code applies to this course. In particular, making false statements, falsifying information on self or peer evaluations, hiring or permitting someone else to complete course activities, and willful and flagrant plagiarism are all examples of academic integrity violations. Violations of the CCU Academic Integrity Code in this course will result in a course grade of FX.

Communications Policy

I will normally reply to email within 1-2 business days. Email received over a weekend or on a holiday may not receive a response for 1-2 business days after the weekend or holiday. Please note that I’m only able to answer the phone and return phone calls on days where I work from the office (typically, days when I have posted office hours). Email is typically a much faster way to reach me and receive a reply.

Disability Accommodations

Per University policy, I can only grant you accommodations that are authorized through Accessibility and Disability Services. Please have your accommodations information sent to me within the first week of class or within a week of approval if accommodations are implemented in the middle of the semester.

Contingency Plan

Per the CCU Academic Continuity Plan, courses will continue online whenever the University is unable to hold in-person classes. If this course has a synchronous meeting time, then we will meet online using a University-licensed meeting platform. All other activities will proceed as scheduled, unless the University announces otherwise. ALWAYS take your laptop or other computer with you whenever you go out of town, including during University breaks, evacuations, and other travel. Remember that you could encounter travel difficulties and have issues returning on time, even if University operations are not affected.

For fall semester courses, please review my Hurricane Information page. Always monitor your email and the CCU Website for official announcements regarding irregular operations.

Disclaimer

Portions of this course may deal with issues related to cost analysis, laws, and ethics. I am not a lawyer, accountant, or financial advisor, and no portion of this class constitutes legal, financial, or other regulated professional advice. This syllabus is tentative and is subject to change with notice to the class during the semester. If a portion of this syllabus is found to be non-compliant with University policies or applicable laws, the remainder of this syllabus will remain effective.