Lecture: Tuesday, Thursday, 3:00 p.m. – 4:20 p.m. Eastern Time

All-Hands, In Person: 158 Natural Resources

Split-Hands, Luke’s Teams: 152 Natural Resources
Split-Hands, Griffin’s Teams: 2250 Engineering
Split-Hands, Samantha’s Teams: 158 Natural Resources

All-Hands, Online: Microsoft Teams General Channel

Lab: TBA, 3340 Engineering, 3352 Engineering and 3358 Engineering

www.capstone.cse.msu.edu

In lieu of fixed, limited office hours, students can contact and interact with the instructors almost any time in a variety of ways including all of the following.

• The instructors are in their offices most business hours on most weekdays. Students are welcome to stop by any time.
• Students can email the instructors, who do email during most waking hours every day of the week and who respond as quickly as possible.
• Students can message the instructors using Microsoft Teams. The instructors have the Microsoft Teams app installed on their mobile phones, which means that students can text the instructors on their mobile phones.
• Students can meet with the instructors virtually using Microsoft Teams.
• Students can schedule a virtual or in-person meeting with the instructors via email.

Credits: 4 (2 – 4), Lecture/Recitation/Discussion Hours: 2, Lab Hours: 4.

Prerequisites: In order to enroll in CSE498, a student must have successfully completed each of the following in advance:

• CSE 300,
• CSE 325,
• CSE 335,
• at least two CSE technical 400-level courses chosen from CSE 402, CSE 404, CSE 410, CSE 415, CSE 420, CSE 422, CSE 425, CSE 431, CSE 434, CSE 435, CSE 440, CSE 450, CSE 460, CSE 471, CSE 472, CSE 476, CSE 477, CSE 480 or CSE 482,
• and a Tier I Writing Requirement (WRA 101 or WRA 195H).

Restrictions: Open only to students in the Computer Science Major or in the Lyman Briggs Computer Science Coordinate Major.

Description: Development of a comprehensive software and/or hardware solution to a problem in a team setting with emphasis on working with a project sponsor. Participation in a design cycle including specification, design, implementation, testing, maintenance, documentation. issues of professionalism, ethics, and communication.

In order to be enrolled in CSE498, a student must have successfully completed the prerequisites listed in the section titled Catalog Description. These requirements are prerequisites, which means that they must be completed successfully, in advance of the semester in which a student is enrolled in CSE498.

If a student has not met these prerequisites, they are disenrolled from CSE498 unless they have specific permission to enroll from one of the course instructors.

There are no required or recommended textbooks, software or course packets to be purchased for this course. Teams are provided with any and all software and hardware required to complete their project.

There are no formal lab sessions. However, students are required to meet weekly as a team with their teaching assistant, with their project sponsor, and with their other team members.

CSE498 is a four-credit course. Two of the credit hours correspond to the two weekly class meetings. The other two credit hours correspond to the weekly non-class meetings in lieu of a scheduled lab.

Throughout this syllabus, wherever a list of items begins with the word “including,” that word “including” implies the entirety of the phrase “including but not limited to.”

Unless indicated otherwise, all times specified are Eastern Time (ET), either Eastern Standard Time (EST) or Eastern Daylight Time (EDT), depending on the time of year.

These times include meeting times and submission deadline times.

One objective of this course is to give students a professional experience like that which they will encounter in their first position after graduation. Hence, we run this course as business-like as possible. We view each team as a small company engaged by a customer to deliver a significant software system on time and on budget.

Other course objectives for CSE498 include the following:

• design, develop, debug, document and deliver a complete software system,
• gather system requirements from a customer,
• become proficient with software development tools and environments,
• build and administer computer systems,
• work effectively in a team environment,
• develop written and oral communication skills,
• consider issues of professionalism and ethics,
• integrate knowledge and skills from other computer science courses, and
• transition from being students to professionals.

All of our meetings will be held in person.

Students are required to attend several weekly meetings in person including but not limited to

• two class meetings,
• a triage meeting, which is a team meeting with the team’s teaching assistant,
• team meetings with the team’s project sponsors who may be remote, and
• one or more meetings with the team members.

We coordinate with students to make reasonable accommodations for their schedules. However, students must be available for all weekly meetings including the non-class meetings. We do not make accommodations for students who are working an unreasonable amount of hours at a job such as a half-time or more internship or a full-time position. Students are strongly discouraged from working an unreasonable amount of hours at a job during the semester.

As a contingency, we have standing plans to pivot to meet online if necessary. Some of the language below relates to those plans. However, that language will only be relevant if and when we were to pivot to meeting online.

Our group meetings include lectures, team status reports, team formal presentations, viewing project videos, and possible guest speakers.

For some of our meetings, we meet as one single group, called “all-hands” meetings. For some meetings, we split up into three sections, called “split-hands” meetings. These three sections are based on a team’s teaching assistant. In particular, we meet in split-hands meetings on days when teams give team presentations throughout the semester and when we watch project videos during the last week of the semester.

While most of our meetings are held in person, some of our meetings may be held online.

All-hands in-person meetings are held in 158 Natural Resources. Split-hands in-person meetings are held in 152 Natural Resources, 2250 Engineering, and 158 Natural Resources.

Online meetings are held using Microsoft Teams. All-hands online meetings are held using our Microsoft Teams General Channel. Split-hands online meetings are held using three Microsoft Teams Channels, one for each teaching assistant.

Students must attend all in-person meetings in person.

To provide students with a professional experience, our meetings are conducted in a business-like environment.

While the dress code is normally casual, everyone is expected to look professional. Hence, hats, hoods (of coats or sweatshirts or hoodies) and coats may not be worn during our meetings.

As an exception, on the days when teams are making formal presentations, the dress code for the presenting teams is business casual.

For more information about professional dress expectations, google “dress code casual,” “dress code business casual,” and “dress code business.”

As with most business meetings, eating during our meetings is not allowed.

The use of laptops or any mobile devices during our all-hands meetings is prohibited except by a presenting team member while giving presentations and demonstrations. Laptops and mobile devices must be silenced and stowed away, out of view and out of reach.

Students who violate our Meeting Environment requirements may be marked absent.

Throughout the semester, we use a variety of means to communicate with students including meetings, email, and Microsoft Teams messaging. In addition to attending all meetings, students are required to check and read their email and Microsoft Teams messages regularly and carefully.

Missing a meeting, or missing or not reading an email or a Microsoft Teams message is not accepted as an excuse for anything.

Students should install and configure an email client and Microsoft Teams on their mobile devices to ensure that they are able to monitor email and messages remotely.

Students are required to read every communication regularly and completely.

All communications from students are expected to be professional and respectful including communications with instructors, other students, and project sponsors. Communications include conversation, email, texts, and messages. Unacceptable forms of communication include anything that is disrespectful, offensive, derogatory, or rude. The instructors are required to report complaints about communication even if the complainant requests otherwise.

One goal of this course is to give students a significant experience working on a team. Students may be working with people whom they did not know prior to the course and whose experiences and abilities may be very different from theirs. The challenge is to take a disparate group of individuals and form a real team. Each team may organize itself as it sees fit.

Each student team designs, develops, debugs, documents and delivers a complete software system for a project sponsor. The sponsor organizations range in type from industry to non-profits to academic and in size from small startups to large global corporations.

Project sponsor contacts are busy professionals. Their computing experiences may vary widely from basic software users to experienced software developers. With respect to CSE498, they are volunteers who are doing students and teams a favor. Students must work with their sponsors in a respectful manner. If teams experience any problems with their project sponsors, they should inform the course instructors as soon as possible.

Each team selects one team member who is the main contact for the project sponsor.

For most of a student’s academic experiences, they have been handed a complete system architecture with detailed specifications and asked to develop it. For this course, learning the underlying business processes, gathering the system requirements, and architecting the system are sometimes a difficult challenge, particularly when working with users who are not sure about what software technologies they need to solve their problem.

Each project must be the right level of difficulty. On the one hand, it must be difficult enough to warrant four credits in a computer science major from one of the top programs in the country, MSU. On the other, it must be simple enough to be completed and delivered in one semester. What constitutes the right level of difficulty is something that each team works out with their project sponsor and with the instructors. As a team scopes their project, they should do so with levels of deliverables where the first level is clearly achievable, the second is likely achievable and the third is possibly achievable.

Each team must deliver a completed project to their project sponsor on time. Period. There are no exceptions. No excuses are considered or accepted. Thus, it is in a team’s best interest to create a project plan that is acceptable to their sponsor and to the instructors. The instructors have the final say as to the required features of a project and what constitutes an acceptable project. If the instructors require features that the project sponsor does not require or no longer requires, those features must still be completed even if they are not included as part of the final deliverables to the sponsor.

Completed software and systems are submitted to the project sponsors at the end of the semester.

Teams are required to manage their own project including both hardware and software systems.

Teams must use MSU’s GitLab to manage their project computer code. Course instructors must have complete access to every team’s repository.

If an external project sponsor would like access to a team’s repository, we are able to provide it working with MSU’s Information Technology Services. To request such access, contact Professor Mariani.

Projects are divided up into milestones with specific deliverables due on specific dates. While the completed project at the end of the semester is one very important milestone, all of the major milestones are considered important. Meeting the milestones factors significantly into the final course grade.

For a description of major milestones with due dates see Major Milestones.

Project deliverables include the following:

• Project Plan Presentation & Document,
• Alpha Presentation
• Beta Presentation,
• Project Video, and
• Project Software & Documentation.

The labs include rooms 3340 Engineering, 3352 Engineering and 3358 Engineering.

The Capstone Experience Labs have a key code, which we give to everyone.

Each team is assigned two iMacs and a rack-mounted server if required. In addition to Apple‘s macOS, these iMacs have the capacity to run virtual machines with Windows or Linux using VMware Fusion. These iMacs can be used for both software development and as servers.

Each team is completely responsible for their computers, including building them, maintaining them, securing them (both internally and externally), and backing them up.

All of the labs include hand sanitizer dispensers and sanitizing wipes, which should be used to sanitize keyboards, mice and table surfaces. Team members are required to sanitize their keyboards, mice and table surfaces before and after each use.

In addition to working in the labs in person, team members are able to access the iMacs in the labs remotely. Instructions are provided by the instructors.

The lab also includes a water cooler with bottled water, a refrigerator, a microwave and a coffee maker. Students are welcome to use all three at their own risk. These are shared resources. Please keep these appliances along with the entire lab clean.

Note that students may not use the Capstone lab space for joining or attending online meetings.

A student’s final course grade is based both on a team’s performance and a student’s individual performance. What follows is a list of grading categories along with the point distribution.

Every student must make significant technical contributions to their team’s project, including significant software contributions. Significant software contributions do not include doing initial research, code that is committed by someone else, code that does not work, or code that is not included in the final version of the project.

As stated above, teams must use MSU’s GitLab to manage their project computer code. When a student commits code to their team’s repository, the student must use their own repository account and only their own account. Students receive credit only for the lines of code committed by them using their own account.

If students engage in so-called pair programming, they must decide when committing the code who gets credit for which lines of code, keeping in mind that students receive credit only for the lines of code committed by them using their own account.

While the number of lines of computer code and the number of significant GitLab commits are not the only measures of the significance of a student’s technical contributions to team, they are important factors, which are used by the instructors.

Even though there is no exact formula for the number of lines of code, each team member is expected to write approximately the same number of lines of code. As a general rule, if a team consisting of N members writes a total of M lines of code, then each team member should write approximately 0.80×M÷N or more lines of code.

Lines of code that are committed by another student, do not work, are copied from any internet source including but not limited to ChatGPT or other large language models (LLMs), or are not included in the final project do not count. Trivial GitLab commits do not count. Attempts to inflate lines of code and/or GitLab commit counts will negatively affect the Technical Contribution grade. Moreover, in general, lines of CSS and HTML do not count as lines of computer code.

Project requirements may change during the semester for a variety of reasons, which may result in the addition, deletion, or reduction of scope of project features. If a student successfully completes a feature that a project sponsor no longer requires, that feature may still be considered as part of a student’s Technical Contribution grade even though it is not included in the final deliverables to the sponsor provided doing so is approved by the instructors.

If a project feature is deleted or reduced in scope, the student who was responsible for implementing that feature must either complete the feature or complete other features in lieu of the deleted or reduced feature. If a project feature is deleted or reduced in scope by a project sponsor, the student responsible for that feature must inform the instructors immediately and work with the instructors to devise a plan that requires an equivalent amount of technical contribution. That plan must receive written approval by the instructors and must be completed by the student. The fact that a project feature is deleted or reduced in scope is not an acceptable reason for not making technical contributions.

While all students are expected to do research on technologies, create UI/UX designs, create documents, style web pages using CSS, and create and give presentations, such contributions, while necessary, are not sufficient alone to constitute a significant technical contribution.

Students must be ready at all times to demonstrate and explain their software to the course instructors when asked to do so. They must be able to demonstrate and explain their software using one of the computers in the Capstone Lab or their personal device. Students cannot use as an excuse that their software only runs on the computer in their dorm room or apartment, or that they do not have the latest version of their software. If a student is not able to demonstrate and explain their software when asked, the course instructors will deem that it does not work and grade appropriately.

To be considered as part of a student’s Technical Contribution grade, all of the student’s project software must be a) committed to the main branch of the team’s Git repository, b) integrated with the team’s project software system, c) working correctly, and d) demonstrated and explained to the instructors by the date of the first Beta Presentation.

The Team Contribution Grade is based on a variety of factors including but not limited to attendance and participation in team meetings, project sponsor meetings and triage meetings, willingness to take on tasks, completing tasks correctly and on time, and making a significant technical contribution as described above.

The maximum Team Grade is 70 points, and the maximum Project Software & Documentation grade is 30 points so that the Project Software and Documentation grade represents about 43% of the Team Grade. As a result, if a student fails to make significant technical contributions to the project, the maximum Team Contribution grade that a student can earn is 57% or 5.7/10.0.

For a final grade, each student earns the sum of their individual grade plus a prorated percentage of their team’s Team Grade based on the corresponding percentage of their Team Contribution grade as follows:

Prorated Team Total = (Team Total) * (Team Contribution) / 10.0,

Grand Total = (Individual Total) + (Prorated Team Total).

Note that the Technical Contribution grade has a very significant effect on the Team Contribution grade, which in turn has a very significant effect on the final grade.

For example, if an individual’s Team Contribution grade is 10.0, then they earn 100% of the team grade. If the Team Contribution is 9.0, then they earn 90% of the team grade, and so on.

So, if a student is not a contributing team member, they run the risk of not passing CSE498, which is required for graduation.

Unexcused absences have a significant impact on the Team Contribution grade, particularly during times just prior to Major Milestones. In particular, since each week of the spring semester represents approximately 7% of the semester, a student who misses an unexcused week of the spring semester should expect to lose at least 7% of their Team Contribution grade for each such occurrence. If the week is during a time just prior to one of the Major Milestones, a student may lose considerably more than 7% of their Team Contribution grade for each such occurrence. A loss of 7% of the Team Contribution grade results in the loss of 4.9% of the final grade. See above.

In other courses, students may have experienced team projects in which one person or a few persons did all of the work, while everyone on the team received the same credit and the same grade for the entire team. This is not the case in CSE498. Each student is evaluated on their individual Technical Contribution and their Team Contribution. If a student does not contribute significantly in those categories, they risk not passing the course.

Students are required to make significant technical and team contributions throughout the semester. Students who make contributions during only the first or only the second half of the semester will have severely reduced Technical and Team Contribution grades, which may result in failure of the course.

If a student fails to meet course and team deadlines, thereby endangering the success of the team and forcing other team members to do the student’s work, that team may be allowed by the instructors to proceed on their project without the student, and the student will be required to work with the instructors to develop a plan to attempt to complete the course successfully. See EASE Reports below.

Final course grades are determined during the week of final exams. An email with final course grades is sent to each student on the Monday following the week of final exams. The final course grades are uploaded to the Registrar on the Tuesday following the week of final exams as per Michigan State University’s policies.

Since this course is required for graduation, students should keep these dates in mind before making plans for things such as but not limited to attending graduation, accepting a job offer, and signing a rental lease agreement. See Special Considerations for Final Grades below.

Every student must earn the following required minimal grades in each grading category.

Failure to earn the required minimal grades in any of the grading categories is grounds for receiving a final grade of 0.0 for the course.

Approximately halfway through the semester, students are given mid semester evaluations, which indicate a student’s capstone performance to date.

In addition to mid-semester evaluations, some students may receive a Michigan State University Enhancing Academic Success Early (EASE) report, which provides an official way to document a student’s capstone performance to date.

Students who receive EASE reports are required to meet with the instructors and to propose a specific list of technical tasks, which must be approved by the instructors and completed successfully exactly as proposed and approved by the date of the first Beta Presentation. Students may request changes to the list of tasks, but all such changes to the list of tasks must be approved in advance by the instructors.

Failure to complete the entire list of tasks by the date of the first Beta Presentation will have a significant negative impact on the student’s Technical and Team Contribution grades, and, a fortiori, a significant impact on the student’s final grade in the course, including a high probability of failure in the course.

The mid-semester evaluations and the EASE reports are not mid-semester grades in that they are not used in any way to compute final grades, but merely indicate a student’s performance to date. Depending on a student’s performance throughout the second half of the semester, a student’s final grades may be higher or lower, even significantly higher or lower.

Students are required to make significant technical and team contributions throughout the semester. Failure to do so during the second half of the semester will have a significant impact on a student’s Technical and Team Contribution grades, which may result in failure in the course.

Students who receive a mid-semester evaluation or an EASE report of 1.5 or lower or both should consider themselves in danger of failing the course.

Students who a receive mid-semester evaluation of 2.0 or higher or who do not receive an EASE report may still fail the course if their technical and team contributions diminish during the second half of the semester.

Final course grades are determined during the week of final exams. An email with final course grades is sent to each student on the Monday following the week of final exams. The final course grades are uploaded to the Registrar on the Tuesday following the week of final exams as per Michigan State University’s policies.

Since this course is required for graduation, students should keep these dates in mind before making plans for things such as but not limited to attending graduation, accepting a job offer, and signing a rental lease agreement.

No special considerations are given for final grades for any reasons including but not limited to

• status in any academic program at MSU including CSE,
• the ability to enroll in CSE498 next semester,
• financial aid,
• hours worked in a job while a student at MSU,
• distance commuting to MSU,
• anticipated graduation from MSU,
• acceptance of a job in anticipation of graduation,
• rank in the armed forces,
• mortgage on a property,
• lease on a property,
• upcoming wedding, or
• visa status.

Meeting attendance and preparation is very important in the business world. Hence, meeting attendance and preparation is a significant factor in the final course grade comprising at least 5% of the final course grade. (See Final Course Grades.)

Students begin the semester with 5.0 Meeting Attendance, Preparation and Participation (MAPP) points. If a student is late to a meeting, 0.5 MAPP points are deducted. If absent, 1.0 MAPP point is deducted. Almost no excuses are accepted for being late or absent.

As preparation for weekly team triage meetings, each student is required to complete a Google Form and submit Google Slides. If either task is completed late or not at all, 0.5 MAPP points are deducted for each occurrence.

MAPP points continue to be deducted even after a student’s MAPP points reach zero so that a student’s final MAPP points grade may be negative, which effectively deducts points from other grade categories.

If a student’s MAPP points are low or negative, their Team Contribution grade may be affected as well, which may have a significant effect on their final grade.

Students are required to be “meeting-ready” at the designated meeting start time.

For in-person meetings, “meeting-ready” means seated with one’s team in the appropriate room, coat and hat off, and all mobile devices silenced and stowed. Examples of not being meeting-ready in person include entering a room, walking to a seat, and being in the process of sitting down.

For online meetings, “meeting-ready” means joined to the appropriate Microsoft Teams channel on an appropriate device in an appropriate location. Examples of not being meeting ready online include joining the wrong channel, joining a meeting using only a phone, and joining a meeting in an inappropriate place such as while driving in a car or standing in line at a bar.

If a student is meeting-ready by 3:00:00 p.m., they are marked present. If a student is not meeting-ready by 3:00:00 p.m. but is meeting-ready before 3:05:00 p.m., they are marked late. If a student is not meeting-ready by 3:05:00 p.m., they are marked absent.

Almost no excuses for lateness or absence are accepted. Excuses that are not accepted for in-person meetings include heavy traffic, bad weather including snow, missing a bus, or lack of parking. Excuses that are not accepted for online meetings include computer crashes, Microsoft Teams not working, or lack of an internet connection, either wired or wireless. Personal travel such as a vacation or visiting friends or family is not accepted as an excuse for missing any meeting. Students should not plan such travel during the semester on days when we have regularly scheduled course meetings. Problems such as cancellation of flights or bad weather when returning from personal travel will not be accepted as a reason for an excused absence.

A few meetings may be missed in the cases of job interviews and some university-approved events. Student must request to be excused well in advance and must provide the instructors with the meeting date to be missed and the reason well in advance. For job interviews, students must provide the name of the company as well as the name and contact information (email and phone number) of their recruiter. For other university-approved events, students must provide a description of the event along with appropriate documentation.

Students may request an excused absence in the case of illness or injury, but it must be requested in a timely manner, no later than two days from the date for which the excused absence is being requested. Students must supply written documentation from a licensed local medical provider such as the Olin Health Center as the result of an in-person visit stating that the student is unable to attend a meeting in person. Note that the documentation must say more than simply that the student had an appointment or a cold or some other diagnosis. The document must explicitly say that the student is unable to attend a meeting in person due to their illness or injury. Moreover, we will not accept documentation resulting from an out-of-state provider or a virtual visit.

In addition to the above, Michigan State University has a Grief Absence Policy to accommodate the bereavement process of a student who has lost a family member. It is the responsibility of the student to: a) notify the Associate Dean or designee of their college of the need for a grief absence in a timely manner, but no later than one week from the student’s initial knowledge of the situation, b) provide appropriate verification of the grief absence as specified by the Associate Dean, and c) complete all missed work as determined in consultation with the instructors.

Meeting attendance is taken using a variety of mechanisms.

For in-person meetings, each teaching assistant circulates for their teams an attendance sheet, which students sign to indicate presence. Each teaching assistant also keeps track of students who are not meeting-ready by 3:00:00 p.m. and 3:05:00 p.m., marking them late and absent, respectively. Students who leave a meeting early are marked absent.

For online meetings, at the end of each meeting, we download from Microsoft Teams the meeting attendees, which includes a list of who joined and left the meeting, and when. If a student is shown to have left a meeting for more than one minute before it ends, they are marked absent.

In addition, at random times during a meeting, students are given one minute to complete a Google Form to indicate their attendance and alertness.

Finally, at the end of the meeting, students are given one minute to complete a final Google Form to indicate their attendance at the end of the meeting. If a student fails to complete a Google Form, we assume that they have left the meeting, in which case they are marked absent.

If a student arranges to have another student mark them present at a meeting or if a student marks another student present at a meeting, they may lose up to 5.0 MAPP points and they may receive a final grade of 0.0 in the course for academic dishonesty.

Students are required to remain in a meeting until the meeting is ended by the meeting host. Exceptions may be made in the event of a demonstrable emergency or conflict with another Michigan State University class, the latter of which must be approved by the instructors in advance. Students who leave a meeting early or who leave a meeting for an extended period of time will be marked absent.

Normally, our group meetings end at the scheduled time of 4:20:00 p.m. or earlier. However, from time to time, a meeting may extend past the scheduled ending time, particularly on days when teams make presentations including Status Report Presentations, Project Plan Presentations, Alpha Presentations and Beta Presentations.

Even if a meeting continues past the scheduled end time, students are required to remain in a meeting until the meeting is ended by the meeting host.

For online meetings, students are required to join a meeting using a device and a location that is appropriate for a business meeting. In general, appropriate devices include a laptop or a desktop, and an appropriate location is a quiet, semi-private place like a room in an apartment or at home, or a dorm room. Students may not join a meeting from within any of the Capstone labs, or from a public location such as a library or a restaurant. If the instructors deem that a student has joined a meeting using a device or from a location that is inappropriate, the student is marked absent for that meeting.

Students may not join an online meeting using shared devices. Each student must join a meeting using one or more devices dedicated to that student.

For online meetings, in addition to joining a meeting using a desktop or laptop computer, we strongly recommend that a student join the meeting simultaneously using a cellular device such as a mobile phone or tablet to ensure a continued, stable connection to Microsoft Teams.

Attendance at meetings during which teams make presentations is absolutely required. No excuses for absence or lateness are accepted, including job interviews. In particular, students should not plan any travel that may result in absence from a team presentation. In general, there are multiple meeting dates for each type of team presentation. We work with students and teams to coordinate as much as is reasonably possible team presentations to avoid scheduling conflicts, but only conflicts resulting from job interviews and some university-approved events. If a student is absent for any of their team presentations, they may lose up to 5.0 MAPP points and may also lose Team Contribution points.

We will watch the final project videos together during the regularly scheduled meeting times on April 16 and April 18, and during the scheduled final exam time, which is Thursday, April 25, 5:45 p.m. – 7:45 p.m. ET. Attendance by everyone for viewing all project videos is required. No trips should be scheduled that conflict with these meetings. Job interviews are not accepted as an excuse for missing any of the final project video viewings. If a student is absent for any of these final meetings, they may lose up to 5.0 MAPP points per meeting and may lose Team Contribution points, which may have a significant effect on their final grade.

All of our online meetings are hosted using Microsoft Teams.

For online meetings, students are required to use either a desktop or laptop computer equipped with a camera, microphone and speakers and must be able to handle receiving and sending clear audio and clear video, which includes screen sharing.

Students are required to have an internet connection that is reliable.

In general, internet connectivity issues are not acceptable excuses for any attendance issues including missing a meeting, joining a meeting late, leaving a meeting early, or missing an attendance check.

In addition to having a reliable internet connection, students are required to have an internet connection that has enough bandwidth to support high quality audio and video using Microsoft Teams.

Along with Microsoft Teams, Google Forms are used for taking attendance. Students must be able to access Google Forms reliably.

When meeting online, students may be asked to demonstrate project software. They must be able to demonstrate their software online when asked to do so, normally by sharing a screen in Microsoft Teams.

Students cannot use as an excuse that they are not able to demonstrate their software because it does not run on the device with which they are connected to a meeting. As an example, it is not acceptable for a student to say that they are not able to demonstrate their software because it only works on their laptop, but they are connected to the meeting using a mobile phone or tablet.

If a student is not able to demonstrate their software, we assume that they have not completed their assigned task and grade them accordingly. To this end, it is important to practice demonstrating software online with teammates in advance of online meetings.

Michigan State University’s semester schedules are published years in advance of the semester. Students are expected to be available to meet in person with their team and to do coursework with their team every week of the semester, including the first week, and the week of exams.

Requests for excused absences must be submitted well in advance. Acceptable reasons for excused absences are very limited. See Meeting Attendance, Preparation and Participation (MAPP) Grade and Meeting Attendance Policies and Procedures above.

Students should not plan any personal travel such as a personal or family vacation during the semester on days when we have regularly scheduled meetings since such travel is not an acceptable excuse for absence.

Students who obtain an approved absence will be excused from attending meetings and will not lose MAPP points during the time of their approved absence.

While students who obtain approved absence will be excused from attending meetings, they will not be excused from doing coursework, no matter what the reason for their absence. Failure to do coursework will have a significant impact on the Team Contribution grade, particularly during times just prior to Major Milestones.

For example, since each week of the spring semester represents approximately 7% of the semester, a student who fails to do coursework during a week of the spring semester should expect to lose at least 7% of their Team Contribution grade for each such occurrence. If the week is during a time just prior to one of the Major Milestones, a student may lose considerably more than 7% of their Team Contribution grade for each such occurrence. A loss of 7% of the Team Contribution grade will result in the loss of 4.9% of the final grade.

Students often say that they will do the coursework in advance. Given the nature of the team projects, it is often difficult or impossible to do coursework in advance. Also, students say that they will do coursework during their absence. Often this is impractical and seldom is much coursework accomplished during travel.

If a student misses a team presentation as the result of travel, even if the absence is approved, that student will be required to give the presentation to the instructors at an agreed upon time and will be graded separately from their team for the presentation.

On the last day of each semester, the College of Engineering sponsors an event called Design Day at which student teams demonstrate their projects to the public. Students are required to be involved in all aspects of Design Day including setup on Thursday, April 18 and the exposition, presentations to judges, tear down and an awards ceremony on Friday, April 19.

Everyone is required to attend and participate in Design Day on both Thursday, April 18 and Friday, April 19. Students should not schedule any trips during these times. Interviews are not accepted as an excuse for missing any of the Design Day activities.

If a student does not participate in Design Day, arrives late on Design Day, does not dress appropriately, does not actively participate in the exposition, leaves early on Design Day, does not attend the Awards Ceremony, or leaves the Awards Ceremony before it concludes, they may lose up to 5 MAPP points and they may lose Team Contribution points, which may have a significant effect on their final grade.

Throughout the semester, students and teams will be editing and submitting Microsoft Word documents and Microsoft PowerPoint presentations (slide decks) based on templates that are provided on our Downloads page. These Word documents and PowerPoint slide decks are processed in a variety of ways using custom software that utilizes various Microsoft Office 365 APIs.

In order for your and your team’s documents and presentations to be processed correctly by our custom software, and a fortiori, in order for you and your team to receive the appropriate credit for your documents and presentations, you must use only Office 365 running natively on a Windows 10 or Windows 11 computer, which may include the Windows 11 virtual machine running on team Capstone Lab Apple iMac. The underlying data structures vary between versions of Office 365 and other office software so that the APIs on which we rely only work with Office 365 running natively on a Windows 10 or Windows 11 computer.

Every team is required to create at least one Windows 11 virtual machine on one of their team’s Capstone Lab iMacs. A Windows 11 virtual machine is provided by us and includes Office 365. In addition, students can borrow Windows-based laptops from the Division of Engineering Computing Services (DECS).

In order to edit your or your team’s documents and presentations correctly, download the provided templates and edit them directly using Office 365 running natively on a Windows 10 or Windows 11 computer. Do not copy-and-paste anything from any other application.

Do not use the web version of Office 365, which includes the web version of Word or PowerPoint in any way, shape or form at any time. In particular, do not copy-and-paste anything from the web version of Office 365.

Do not use the collaborative version of Word or PowerPoint with Microsoft Teams since these versions are the web versions of Word and PowerPoint in any way shape or form at any time. In particular, do not copy-and-paste anything from the collaborative Microsoft Teams version of Office 365.

Do not use Apple’s Office suite and then export documents or presentations to the Microsoft Office suite. In particular, do not copy-and-paste anything from an Apple Office application to a Microsoft Office application.

Some Office 365 products include a switch with the label “Try the new…” as in “Try the new Outlook.” Do not enable this switch. The “new” version of these Office products is the web version, which will not work.

Consider the following subtle example of something that will not work. If you download a PowerPoint template, edit it in Microsoft Teams, download a fresh copy of the template, and then copy-and-paste entire slides from the Teams presentation to the new template, that will not work. You must copy only the plain text from the Teams presentation to the new one.

If you or your team’s document or presentation is not processable by our custom software because you or your team failed to follow these requirements, neither you nor your team will be allowed to resubmit your document or presentation, and you will not receive any credit for it.

Teams traveling to their project sponsor may be reimbursed for mileage for the use of a personal car. Travel reimbursement is limited to travel within the State of Michigan outside of the Lansing area. Reimbursement is also limited to one car per team per trip.

To be reimbursed for travel mileage, see one of the administrative assistants in the CSE office in advance. If a student does not request permission to travel and be reimbursed in advance, they may not be reimbursed.

Michigan State University is committed to providing equal opportunity for participation in all programs, services and activities. Requests for accommodations by persons with disabilities may be made by contacting the Resource Center for Persons with Disabilities at (517) 884-RCPD or on the web at rcpd.msu.edu. Once a student’s eligibility for an accommodation has been determined, they are issued a Verified Individual Services Accommodation (VISA) form. Please inform the instructors at the start of the semester as soon as possible.

The Department of Computer Science and Engineering expects all students to adhere to MSU's policy on Integrity of Scholarship and Grades, which includes the statement, “...all academic work will be done by the student to whom it is assigned, without unauthorized aid of any kind” (Academic Programs, General Procedures and Regulations). General Student Regulation 1.00 in the student handbook (Spartan Life) also addresses this issue.

Academic dishonesty includes but is not limited to the following.

Any type of computer code that is not written by the student, such as code taken from any internet source including code generated by tools like GitHub Copilot, ChatGPT and other large language models (LLMs), and is committed by the student to a team’s GitLab main branch is considered academic dishonesty.

Demonstrating software that the student claims to have written but did not is considered academic dishonesty.

Attempting to inflate a student’s technical contribution by committing non-project related lines of code to the team GitLab repository or by making numerous trivial commits or by any other means is considered academic dishonesty.

Providing false information to the instructors, teaching assistants or fellow team members about matters related to the course is considered academic dishonesty.

In the event of academic dishonesty by a student, the instructors will file an Academic Dishonesty Report (ADR) with MSU’s Office of the University Ombudsperson and the student will be assigned a final grade of 0.0 for the course.

A student has the right to appeal grades using the steps given below. If the process reaches the final step, a student must demonstrate that their instructors used inappropriate or irrelevant factors in determining the student’s final course grade.

If a student wishes to appeal the grades received in this course, Michigan State University policy requires that they complete the following steps in the order given. In particular, the n^th step must be completed before the (n + 1)^st step.

• Step 1: Attempt to figure out how the grade was determined.
• Step 2: Meet with the course instructors.
• Step 3: Meet with Professor Charles Owen, Associate Chair for Undergraduate Studies, who will act to mediate the dispute between the student and the instructors.
• Step 4: Request a hearing before the University Academic Grievance Hearing Board. If a student pursues this option, they must be aware that in a formal Academic Grievance Hearing, the student must demonstrate that their instructors used inappropriate or irrelevant factors in determining the student’s final course grade.

After the end of the fall semester, the instructors are focused on preparing for the spring semester and getting the course up and running well into the last weeks of January. After the spring semester, the instructors are focused on wrapping up for the academic year as well as planning for the fall semester. As a result, the course instructors may not be available to meet for Step 2 until many weeks after the semester is over.

Hence, it is very important for students to note that, due to a variety of factors, a formal Academic Grievance Hearing most likely will not be able to be scheduled for a two or more months after the end of the semester. So, an appeal from the fall semester would most likely not be heard until the middle or end of the spring semester, and an appeal from the spring semester most likely would not be heard until the middle or end of the summer, or possibly until the fall semester.

Michigan State University and the College of Engineering provide a variety of resources for students. See Resources for Students.

This Syllabus web page is the one and only official version of the syllabus.

We reserve the right to make reasonable changes to this syllabus during the semester with reasonable notice.