[{"data":1,"prerenderedAt":1241},["ShallowReactive",2],{"content-page:\u002Fsystems-integration\u002Fsyllabus":3,"content-page-quiz:none":3,"book-module-total-pages":4,"content-section-pages:none":5,"content-directory-pages:\u002Fsystems-integration\u002Fsyllabus":6},null,[],[],[7],{"id":8,"title":9,"audience":10,"body":11,"contentType":1219,"course":50,"description":1220,"estimateBasis":3,"estimatedDiscussionMinutes":3,"estimatedLiveMinutes":3,"estimatedTotalMinutes":3,"extension":1221,"meta":1222,"module":1224,"navigation":1225,"order":1226,"path":1227,"promptAssist":1228,"seo":1229,"status":1230,"stem":1231,"tags":1232,"videoDuration":1236,"videoId":1237,"videoLink":1238,"videoTitle":1239,"week":1224,"__hash__":1240},"content\u002Fsystems-integration\u002Fsyllabus\u002Fsummer-2026.md","IT490 - Systems Integration Syllabus","student",{"type":12,"value":13,"toc":1171},"minimark",[14,18,23,134,138,160,164,168,201,204,226,229,231,235,239,242,245,248,251,254,257,261,264,267,284,288,291,323,327,402,405,409,487,491,494,497,534,537,541,544,547,570,573,576,579,583,586,590,593,596,631,634,637,640,644,647,651,654,677,681,684,687,691,694,698,701,705,743,747,750,848,852,855,858,861,864,867,870,873,876,893,897,900,903,906,910,913,945,949,953,956,959,962,965,969,972,975,996,999,1002,1006,1009,1019,1022,1026,1029,1032,1041,1048,1052,1055,1064,1067,1070,1074,1083,1087,1090,1099,1103,1106,1110,1113,1116,1119,1133,1136,1140,1143,1146,1149,1157,1161,1164,1168],[15,16,9],"h1",{"id":17},"it490-systems-integration-syllabus",[19,20,22],"h2",{"id":21},"general-information","General Information",[24,25,26,39],"table",{},[27,28,29],"thead",{},[30,31,32,36],"tr",{},[33,34,35],"th",{},"Item",[33,37,38],{},"Details",[40,41,42,51,59,67,75,83,91,99,107,119,127],"tbody",{},[30,43,44,48],{},[45,46,47],"td",{},"Course",[45,49,50],{},"Systems Integration",[30,52,53,56],{},[45,54,55],{},"Catalog number",[45,57,58],{},"IT490",[30,60,61,64],{},[45,62,63],{},"Section(s)",[45,65,66],{},"450",[30,68,69,72],{},[45,70,71],{},"Semester",[45,73,74],{},"Summer 2026",[30,76,77,80],{},[45,78,79],{},"Date and time",[45,81,82],{},"N\u002FA",[30,84,85,88],{},[45,86,87],{},"Modality",[45,89,90],{},"Asynchronous online",[30,92,93,96],{},[45,94,95],{},"Credits",[45,97,98],{},"3",[30,100,101,104],{},[45,102,103],{},"Instructor",[45,105,106],{},"Matt Toegel",[30,108,109,112],{},[45,110,111],{},"Email",[45,113,114],{},[115,116,118],"a",{"href":117},"mailto:matthew.toegel@njit.edu","matthew.toegel@njit.edu",[30,120,121,124],{},[45,122,123],{},"Discord",[45,125,126],{},"MattToegel",[30,128,129,132],{},[45,130,131],{},"GitHub",[45,133,126],{},[19,135,137],{"id":136},"office-hours","Office Hours",[24,139,140,150],{},[27,141,142],{},[30,143,144,147],{},[33,145,146],{},"Time",[33,148,149],{},"Location",[40,151,152],{},[30,153,154,157],{},[45,155,156],{},"General availability",[45,158,159],{},"Discord, email, or Canvas Inbox",[161,162,163],"p",{},"General availability is provided through the course communication channel. Discord is the preferred place for project coordination questions because many IT490 issues involve team workflow, server state, deployment, and troubleshooting context.",[19,165,167],{"id":166},"course-catalog","Course Catalog",[161,169,170,171,177,178,183,184,177,189,194,195,200],{},"Prerequisites: ",[115,172,176],{"href":173,"rel":174},"https:\u002F\u002Fcatalog.njit.edu\u002Fsearch\u002F?P=CS%20113",[175],"nofollow","CS 113"," or ",[115,179,182],{"href":180,"rel":181},"https:\u002F\u002Fcatalog.njit.edu\u002Fsearch\u002F?P=CS%20115",[175],"CS 115",", ",[115,185,188],{"href":186,"rel":187},"https:\u002F\u002Fcatalog.njit.edu\u002Fsearch\u002F?P=IS%20331",[175],"IS 331",[115,190,193],{"href":191,"rel":192},"https:\u002F\u002Fcatalog.njit.edu\u002Fsearch\u002F?P=CS%20331",[175],"CS 331",", and ",[115,196,199],{"href":197,"rel":198},"https:\u002F\u002Fcatalog.njit.edu\u002Fsearch\u002F?P=IT%20340",[175],"IT 340",".",[161,202,203],{},"The course introduces the major design, implementation, and distributed deployment issues related to:",[205,206,207,211,214,217,220,223],"ul",{},[208,209,210],"li",{},"System integration",[208,212,213],{},"Network Operating Systems (NOS)",[208,215,216],{},"Cross-platform database integration",[208,218,219],{},"E-commerce and e-business applications",[208,221,222],{},"Cross-server and multi-location e-session migration",[208,224,225],{},"Related communication security topics",[19,227,103],{"id":228},"instructor",[161,230,106],{},[161,232,233],{},[115,234,118],{"href":117},[19,236,238],{"id":237},"course-format","Course Format",[161,240,241],{},"Class will be asynchronous. Course material will normally be released each Monday and is expected to be reviewed during that module window.",[161,243,244],{},"Assignments, quizzes, project deliverables, and participation tasks may be due at the end of the current or following week. Students are expected to monitor Canvas, Discord, and NJIT email for updates.",[161,246,247],{},"Canvas is the main hub for mapping course content, deadlines, assignment instructions, quizzes, and submission requirements. The Learn Courses Platform may be used for project evidence gathering, structured worksheet output, or course-specific workflow support when directed.",[161,249,250],{},"It's recommended to reach out over Discord, email, or Canvas Inbox as a backup rather than using Canvas Comments. Canvas Comments should be used for things that are ok being seen when grading occurs, but if there's a more immediate issue or question, one of the other means of communication is faster.",[161,252,253],{},"Respondus will be required for asynchronous exams with webcam requirements. Students are responsible for making sure Respondus works on at least one device that can meet the assessment requirements.",[161,255,256],{},"Attendance and participation will be monitored through Canvas activity, required submissions, Discord or Canvas participation, project evidence, and other announced course checks.",[19,258,260],{"id":259},"objective","Objective",[161,262,263],{},"This course consolidates and applies knowledge from earlier IT and CS courses. It emphasizes real-world, project-based learning in a team environment.",[161,265,266],{},"Students will work in teams to develop a full-stack application and supporting deployment architecture covering:",[205,268,269,272,275,278,281],{},[208,270,271],{},"System, network, and database administration",[208,273,274],{},"Software engineering",[208,276,277],{},"Full-stack development",[208,279,280],{},"Project and deployment strategies",[208,282,283],{},"Team coordination and documentation",[19,285,287],{"id":286},"learning-outcomes","Learning Outcomes",[161,289,290],{},"By the end of the course, students should be able to:",[205,292,293,296,299,302,305,308,311,314,317,320],{},[208,294,295],{},"Plan and document a team-based systems integration project with clear scope, responsibilities, and milestone evidence",[208,297,298],{},"Use GitHub branches, issues, pull requests, project boards, and review comments to coordinate team work",[208,300,301],{},"Design a full-stack system that integrates frontend, backend, database, messaging, logging, and deployment components",[208,303,304],{},"Simulate a multi-server cluster with development, QA, production, and failover or load-balancing concerns where required",[208,306,307],{},"Apply system, network, and database administration concepts to Linux server environments",[208,309,310],{},"Integrate third-party data, APIs, ETL-style workflows, or service interfaces into an approved project design",[208,312,313],{},"Configure, monitor, troubleshoot, and document public deployment environments",[208,315,316],{},"Maintain evidence of server health, deployment behavior, team decisions, project changes, and operational risk",[208,318,319],{},"Explain change management, disaster recovery, rollback, and security decisions for a distributed application",[208,321,322],{},"Present individual contributions and connect those contributions to the larger team system",[19,324,326],{"id":325},"grading-breakdown","Grading Breakdown",[24,328,329,340],{},[27,330,331],{},[30,332,333,336],{},[33,334,335],{},"Category",[33,337,339],{"align":338},"right","Weight",[40,341,342,350,357,365,373,381,388,395],{},[30,343,344,347],{},[45,345,346],{},"Assignments",[45,348,349],{"align":338},"10%",[30,351,352,355],{},[45,353,354],{},"Quizzes",[45,356,349],{"align":338},[30,358,359,362],{},[45,360,361],{},"Project Proposal",[45,363,364],{"align":338},"5%",[30,366,367,370],{},[45,368,369],{},"Milestones",[45,371,372],{"align":338},"20%",[30,374,375,378],{},[45,376,377],{},"Midterm",[45,379,380],{"align":338},"15%",[30,382,383,386],{},[45,384,385],{},"Midterm Milestone",[45,387,380],{"align":338},[30,389,390,393],{},[45,391,392],{},"Final Project \u002F Demo",[45,394,372],{"align":338},[30,396,397,400],{},[45,398,399],{},"End of Semester Change Log",[45,401,364],{"align":338},[161,403,404],{},"All points will be converted to a final percentage and letter grade at the end of the semester. Canvas will apply the weights automatically.",[19,406,408],{"id":407},"grading-scale","Grading Scale",[24,410,411,421],{},[27,412,413],{},[30,414,415,418],{},[33,416,417],{},"Grade",[33,419,420],{},"Percentage Range",[40,422,423,431,439,447,455,463,471,479],{},[30,424,425,428],{},[45,426,427],{},"A",[45,429,430],{},"89.5% to 100%",[30,432,433,436],{},[45,434,435],{},"B+",[45,437,438],{},"84.5% to below 89.5%",[30,440,441,444],{},[45,442,443],{},"B",[45,445,446],{},"79.5% to below 84.5%",[30,448,449,452],{},[45,450,451],{},"C+",[45,453,454],{},"74.5% to below 79.5%",[30,456,457,460],{},[45,458,459],{},"C",[45,461,462],{},"69.5% to below 74.5%",[30,464,465,468],{},[45,466,467],{},"D+",[45,469,470],{},"64.5% to below 69.5%",[30,472,473,476],{},[45,474,475],{},"D",[45,477,478],{},"59.5% to below 64.5%",[30,480,481,484],{},[45,482,483],{},"F",[45,485,486],{},"Below 59.5%",[19,488,490],{"id":489},"materials-and-technologies","Materials And Technologies",[161,492,493],{},"This course uses online resources instead of a required textbook. Required resources, assignment details, and supporting materials will be mapped through Canvas.",[161,495,496],{},"Students should expect to use:",[205,498,499,502,505,508,511,519,522,525,528,531],{},[208,500,501],{},"Canvas for official assignments, assessments, grades, and announcements",[208,503,504],{},"Learn Courses Platform for project evidence gathering or course workflow support when directed",[208,506,507],{},"Discord, Canvas Inbox, or email for course communication",[208,509,510],{},"GitHub for the team repository, branches, issues, pull requests, project boards, and change history",[208,512,513,514],{},"A public project host such as AWS, GCE, Azure, DigitalOcean, or another approved hosting environment\n",[205,515,516],{},[208,517,518],{},"Exposing local virtual machines via ZeroTier\u002FTailScale is also fine, but teams should discuss an uptime schedule",[208,520,521],{},"Ubuntu 24.04+ where a Linux server environment is needed",[208,523,524],{},"VirtualBox, VMware, cloud VMs, or similar environments when they support the approved team architecture",[208,526,527],{},"A database system appropriate to the approved project design",[208,529,530],{},"Messaging, logging, API, ETL, or service integration tools appropriate to the approved project design",[208,532,533],{},"Logs, screenshots, diagrams, meeting notes, server notes, and written documentation as project evidence",[161,535,536],{},"Students need administrative access to their computer or a suitable development environment for required software and deployment tools.",[19,538,540],{"id":539},"team-workflow-expectations","Team Workflow Expectations",[161,542,543],{},"This course simulates a professional team environment. Each team will use GitHub as the source of truth for planning, implementation, review, and project evidence. Once teams are formed, a GitHub repository will be created for them and invites will be sent out.",[161,545,546],{},"Teams are expected to use:",[205,548,549,552,555,558,561,564,567],{},[208,550,551],{},"Branches for all task work",[208,553,554],{},"Issues for tasks, bugs, documentation, deployment work, and team process work",[208,556,557],{},"Pull requests to merge work into the main team branch",[208,559,560],{},"Peer review before merging pull requests (required for a Pull Request to be credited for grading consideration)",[208,562,563],{},"Project boards or equivalent tracking to show team progress",[208,565,566],{},"Meeting notes, decision logs, diagrams, and team communication evidence",[208,568,569],{},"Teams may use other tools as long as content is mapped back to the provided GitHub repository",[161,571,572],{},"Each team member may be assigned responsibility for one or more VMs or services. VM ownership means that the member is the point of contact for the health, updates, and documentation of that VM. It does not mean that the member owns only one technical domain. Team members are expected to work across domains to demonstrate their full degree.",[161,574,575],{},"The project may grow from an initial set of development VMs into development, QA, production, and replicated production or failover environments depending on the milestone. Teams should document who is responsible for each server, what each server does, and how the servers communicate.",[161,577,578],{},"Technical domains are shared. A team member may gravitate toward frontend, backend, DevOps, messaging, or database work, but students are expected to understand and demonstrate the parts of the system their features touch and to assist teammates when needed.",[19,580,582],{"id":581},"submission-criteria","Submission Criteria",[161,584,585],{},"Project submissions must include evidence that demonstrates both behavior and process.",[587,588,361],"h3",{"id":589},"project-proposal",[161,591,592],{},"The project proposal must be posted as a Markdown file in the team's GitHub repository and approved. A missing or unapproved proposal may result in a zero for the project and related milestones.\nTeams may use a Google Doc for initial planning during the pre-approval stages.",[161,594,595],{},"The proposal should identify:",[205,597,598,601,604,607,610,613,616,619,622,625,628],{},[208,599,600],{},"Project objective: what the system is trying to accomplish and who it is for",[208,602,603],{},"Core user workflows: what users can do in the application and what value they get from it",[208,605,606],{},"External API data: which external API or APIs will be used, what data will be pulled in, and how that data supports the project objective",[208,608,609],{},"Stored data model: what project-specific data the team will store in its own database",[208,611,612],{},"User data associations: how stored records connect to a logged-in user, team, role, profile, or other user-owned entity",[208,614,615],{},"CRUD operations and features: what users can create, read, update, and delete, and which screens or API endpoints are needed for those actions",[208,617,618],{},"User interaction with data: how users search, filter, select, compare, modify, or act on the stored and external data",[208,620,621],{},"Team members and expected responsibilities",[208,623,624],{},"Major services: frontend, backend, database, message queue, API gateway, workers, logging, or other required components",[208,626,627],{},"MVP (Midterm) goals: what the team expects to have working for the project MVP before completing the final requirements",[208,629,630],{},"Stretch features: goals the team would like to accomplish that may be beyond the original core scope",[587,632,369],{"id":633},"milestones",[161,635,636],{},"Each milestone is a working demo checkpoint. Teams should be ready to present the current system state, show the relevant feature or infrastructure behavior live, explain what changed since the previous checkpoint, and point to supporting GitHub evidence, deployment or server evidence, logs, diagrams, or documentation.",[161,638,639],{},"Milestones are smaller versions of the final presentation. The scope is usually defined by the specific milestone requirements, but the expectation is still to demonstrate working behavior, explain implementation choices, and identify what remains for the project MVP or final demo.",[587,641,643],{"id":642},"final-presentation","Final Presentation",[161,645,646],{},"Each group member must present their role and contributions. Contributions will be verified through GitHub activity, project artifacts, documentation, communication evidence, and the final demo.",[587,648,650],{"id":649},"change-log","Change Log",[161,652,653],{},"The end-of-semester change log must include:",[205,655,656,659,662,665,668,671,674],{},[208,657,658],{},"GitHub repository and relevant branch names",[208,660,661],{},"Pull requests or commit references associated with each team member",[208,663,664],{},"Server and deployment documentation",[208,666,667],{},"Team communication evidence such as Discord messages, meeting minutes, and group chats",[208,669,670],{},"Architecture, service, or VM responsibility changes",[208,672,673],{},"Significant changes and why they were made",[208,675,676],{},"Known limitations or unresolved issues",[19,678,680],{"id":679},"project-guidelines","Project Guidelines",[161,682,683],{},"All projects must simulate a multi-server or distributed system and implement basic networking and security features.",[161,685,686],{},"There will be a required architecture and team workflow to follow to receive credit for the project submissions.",[587,688,690],{"id":689},"option-a-software-as-a-service","Option A: Software As A Service",[161,692,693],{},"Use third-party data to build a functional online service, such as sports statistics, server status, business data, public datasets, or another approved source. The project should do more than display a static utility. It should integrate data into a usable service with team-owned backend behavior, persistence, and deployment documentation.",[587,695,697],{"id":696},"option-b-mobile-or-web-game","Option B: Mobile Or Web Game",[161,699,700],{},"Design a server-backed game with user tracking, state management, and a frontend for web or mobile use. External API data should be used where applicable, and at least one external data source is expected unless the instructor approves another integration plan.",[19,702,704],{"id":703},"course-topics","Course Topics",[205,706,707,710,713,716,719,722,725,728,731,734,737,740],{},[208,708,709],{},"Software as a Service",[208,711,712],{},"Project management",[208,714,715],{},"ETL: Extract, Transform, Load",[208,717,718],{},"Messaging layers",[208,720,721],{},"Server-side development",[208,723,724],{},"Change management",[208,726,727],{},"Disaster recovery",[208,729,730],{},"GitHub workflows",[208,732,733],{},"Scripting",[208,735,736],{},"Deployment documentation",[208,738,739],{},"Team troubleshooting and operational evidence",[208,741,742],{},"Multi-server environments and service responsibility",[19,744,746],{"id":745},"illustrative-schedule","Illustrative Schedule",[161,748,749],{},"The schedule is a guideline and may change based on class pace, project needs, team troubleshooting needs, and deployment issues. Some modules may span more than one week.",[751,752,754],"data-table",{"variant":753},"schedule",[24,755,756,766],{},[27,757,758],{},[30,759,760,763],{},[33,761,762],{},"Module",[33,764,765],{},"Topics",[40,767,768,776,784,792,800,808,816,824,832,840],{},[30,769,770,773],{},[45,771,772],{},"Module 1",[45,774,775],{},"Introduction, groups, team repository setup, GitHub links due",[30,777,778,781],{},[45,779,780],{},"Module 2",[45,782,783],{},"Communication layer demo, project proposal due, project planning discussions",[30,785,786,789],{},[45,787,788],{},"Module 3",[45,790,791],{},"Milestone: centralized logging functional",[30,793,794,797],{},[45,795,796],{},"Module 4",[45,798,799],{},"Milestone: user authentication and authorization functional",[30,801,802,805],{},[45,803,804],{},"Module 5",[45,806,807],{},"Midterm exam",[30,809,810,813],{},[45,811,812],{},"Module 6",[45,814,815],{},"Midterm milestone: minimal viable product",[30,817,818,821],{},[45,819,820],{},"Module 7",[45,822,823],{},"Milestone: three-tier cluster due",[30,825,826,829],{},[45,827,828],{},"Module 8",[45,830,831],{},"Milestone: deployment system functional",[30,833,834,837],{},[45,835,836],{},"Module 9",[45,838,839],{},"Wrapping up, stabilization, documentation, change log work",[30,841,842,845],{},[45,843,844],{},"Module 10",[45,846,847],{},"Final project, presentations, demos, and change logs due",[587,849,851],{"id":850},"schedule-notes","Schedule Notes",[161,853,854],{},"Although the schedule separates topics by module, systems integration work is cumulative. Teams should expect earlier decisions about GitHub, server structure, logging, database design, communication layers, and deployment to affect later milestones.",[161,856,857],{},"Security, operational risk, and best practices will be discussed throughout the semester when they apply to project work.",[19,859,346],{"id":860},"assignments",[161,862,863],{},"Assignments may include setup checks, system diagrams, GitHub evidence, deployment documentation, scripting tasks, short written explanations, and troubleshooting reports related to the current project phase.",[161,865,866],{},"Assignments are generally graded out of 10 points unless otherwise noted.",[19,868,354],{"id":869},"quizzes",[161,871,872],{},"Weekly online quizzes may be used to check current module understanding. Quizzes are generally completed in Canvas by the assigned due date.",[161,874,875],{},"Unless otherwise noted:",[205,877,878,881,884,887,890],{},[208,879,880],{},"Quizzes are closed notes",[208,882,883],{},"Quizzes are individual work",[208,885,886],{},"Quizzes are graded out of 10 points",[208,888,889],{},"Quizzes have time limits and attempt limits",[208,891,892],{},"Quizzes require a passphrase",[19,894,896],{"id":895},"exams","Exams",[161,898,899],{},"The midterm will use Respondus Lockdown Browser with Webcam. Students should have a compatible device available for the assessment.",[161,901,902],{},"The midterm will cover the first portion of the course and the integration concepts, project workflows, and operational practices introduced before the exam.",[161,904,905],{},"Exams are generally graded out of 100 points.",[19,907,909],{"id":908},"project-evidence-expectations","Project Evidence Expectations",[161,911,912],{},"Students should expect to submit evidence that demonstrates both behavior and process:",[205,914,915,918,921,924,927,930,933,936,939,942],{},[208,916,917],{},"Team GitHub repository link",[208,919,920],{},"Branch, issue, pull request, commit, or project board evidence when requested",[208,922,923],{},"Public deployment link when required",[208,925,926],{},"Screenshots or command outputs when requested",[208,928,929],{},"Server, database, log, or monitoring evidence when requested",[208,931,932],{},"Architecture diagrams or written documentation when requested",[208,934,935],{},"Team communication, meeting, or decision evidence when requested",[208,937,938],{},"VM or service responsibility notes when requested",[208,940,941],{},"Explanation of what changed and why",[208,943,944],{},"AI collaboration disclosure when used",[19,946,948],{"id":947},"policies","Policies",[587,950,952],{"id":951},"team-work-and-ownership","Team Work And Ownership",[161,954,955],{},"This course simulates a professional team environment. Group work must clearly distinguish ownership of tasks. Students are expected to contribute meaningfully, communicate clearly, and document their work.",[161,957,958],{},"Students should not rely on one teammate to understand or produce the entire system. Each member must be able to explain their own contributions and how those contributions connect to the larger project.",[161,960,961],{},"To receive proper credit, each team member must have documented and approved work properly recorded on GitHub for their tasks.",[161,963,964],{},"Team members should not overwrite another team member's work. If such a situation happens, there must be a documented and agreed-upon reason from the team to show it was intentional and why.",[587,966,968],{"id":967},"github-and-project-evidence","GitHub And Project Evidence",[161,970,971],{},"Each team will use a team GitHub repository. Individual forks may be used when appropriate, but final team work must be pushed to the original team repository unless the instructor approves another workflow.",[161,973,974],{},"Common branch prefixes include:",[205,976,977,984,990],{},[208,978,979,983],{},[980,981,982],"code",{},"feature\u002F"," for new feature work",[208,985,986,989],{},[980,987,988],{},"bugfix\u002F"," for bug fixes",[208,991,992,995],{},[980,993,994],{},"chore\u002F"," for documentation, refactoring, maintenance, or other non-feature work",[161,997,998],{},"Pull requests must be reviewed by at least one teammate before merging. If a pull request is not approved, the team should document why and what needs to change.",[161,1000,1001],{},"Issues should be granular enough that ownership is clear. Issues should include a useful title, description, acceptance criteria, assignee, and links to related pull requests when applicable.",[587,1003,1005],{"id":1004},"project-structure-and-required-artifacts","Project Structure And Required Artifacts",[161,1007,1008],{},"Assignments and project deliverables must follow the required repository structure, artifact names, documentation expectations, and submission instructions unless the assignment explicitly allows another approach.",[161,1010,1011,1012,177,1015,1018],{},"Teams should keep project documentation, meeting notes, decision logs, architecture diagrams, server notes, and milestone evidence in the team repository, typically in a ",[980,1013,1014],{},"docs\u002F",[980,1016,1017],{},"team\u002F"," area unless another structure is approved.",[161,1020,1021],{},"Submissions that replace the expected project evidence with unrelated generated code, unsupported frameworks, or undocumented architectures may receive no credit because they cannot be fairly evaluated against the course objectives.",[587,1023,1025],{"id":1024},"academic-integrity","Academic Integrity",[161,1027,1028],{},"The work done is expected to be your own, any group work should clearly distinguish ownership of tasks. Use of snippets\u002Fmaterial from others should be kept to a minimum and the source should be accredited where applicable.",[161,1030,1031],{},"Academic Integrity is the cornerstone of higher education and is central to the ideals of this course and the university. Cheating is strictly prohibited and devalues the degree that you are working on. As a member of the NJIT community, it is your responsibility to protect your educational investment by knowing and following the academic code of integrity policy that is found at:",[205,1033,1034],{},[208,1035,1036],{},[115,1037,1040],{"href":1038,"rel":1039},"http:\u002F\u002Fwww5.njit.edu\u002Fpolicies\u002Fsites\u002Fpolicies\u002Ffiles\u002Facademic-integrity-code.pdf",[175],"NJIT Academic Integrity Code",[161,1042,1043,1044,200],{},"Please note that it is my professional obligation and responsibility to report any academic misconduct to the Dean of Students Office. Any student found in violation of the code by cheating, plagiarizing, or using any online software inappropriately will result in disciplinary action. This may include a failing grade of F, and\u002For suspension or dismissal from the university. If you have any questions about the code of Academic Integrity, please contact the Dean of Students Office at ",[115,1045,1047],{"href":1046},"mailto:dos@njit.edu","dos@njit.edu",[587,1049,1051],{"id":1050},"ai-usage-policy","AI Usage Policy",[161,1053,1054],{},"The expectation of this course is for students to work through the course without assistance from any type of artificial intelligence to better develop their own skills in this content area. While artificial intelligence (AI) is permitted in this course as a tool or aid, it is not permitted to be used to blindly complete assignments, generate full solutions, or replace your own analysis and implementation.",[161,1056,1057,1058,1063],{},"Additionally, if and when students use artificial intelligence in this course, the AI must be cited as shown in the ",[115,1059,1062],{"href":1060,"rel":1061},"https:\u002F\u002Fresearchguides.njit.edu\u002FAI\u002Fcite",[175],"NJIT Library AI citation page for AI",". If and when used, failure to clearly disclose the usage of AI within the constraints of this policy will result in a zero for the entire assignment.",[161,1065,1066],{},"Generally, if the course contains code, there is an expected style, library, toolkit, or course material provided that must be utilized.",[161,1068,1069],{},"Broad codebase changes from AI, especially that overwrites the work of another student, will receive a zero for the feature\u002Fassignment.",[587,1071,1073],{"id":1072},"requesting-accommodations","Requesting Accommodations",[161,1075,1076,1077,1082],{},"Students who need accommodations due to a disability should contact the ",[115,1078,1081],{"href":1079,"rel":1080},"https:\u002F\u002Fwww.njit.edu\u002Fstudentsuccess\u002Faccessibility",[175],"Office of Accessibility Resources & Services"," to discuss their needs. A Letter of Accommodation Eligibility from OARS is required before accommodations can be applied.",[587,1084,1086],{"id":1085},"resources-for-njit-students","Resources For NJIT Students",[161,1088,1089],{},"NJIT provides student services including technical support:",[205,1091,1092],{},[208,1093,1094],{},[115,1095,1098],{"href":1096,"rel":1097},"https:\u002F\u002Fdocs.google.com\u002Fdocument\u002Fd\u002F1xGO2qcVEF1tsOgZn-_W1LjSOKn_jhEVs9IWI_6jeuPs\u002Fedit?usp=sharing",[175],"NJIT Services for Students",[587,1100,1102],{"id":1101},"proctoring","Proctoring",[161,1104,1105],{},"NJIT policy requires midterm and final exams to be proctored regardless of delivery mode unless an assessment type is exempt. Exams for this course may use Respondus with webcam requirements. Students are responsible for having a compatible device that can meet exam requirements.",[587,1107,1109],{"id":1108},"professionalism-and-misconduct","Professionalism And Misconduct",[161,1111,1112],{},"Students are expected to maintain professional conduct. Disrespect, harassment, or abusive communication will not be tolerated.",[161,1114,1115],{},"This course requires team troubleshooting. If there is conflict within a team, troubleshooting the issue is part of the team's responsibility. Students should document concerns, communicate professionally, and contact the instructor early when team issues affect progress and cannot be resolved internally (evidence of attempted resolution will be required).",[161,1117,1118],{},"Students are expected to:",[205,1120,1121,1124,1127,1130],{},[208,1122,1123],{},"Respect teammates",[208,1125,1126],{},"Communicate effectively",[208,1128,1129],{},"Troubleshoot team conflicts respectfully",[208,1131,1132],{},"Adhere to NJIT's Code of Student Conduct",[161,1134,1135],{},"Students are responsible for checking Canvas regularly, reviewing each module's posted work, and keeping track of their own progress, deadlines, submissions, team responsibilities, and feedback.",[587,1137,1139],{"id":1138},"late-policy","Late Policy",[161,1141,1142],{},"Deliverables may receive a 5% penalty per day late based on the posted due date. Canvas will automatically mark late or missing assignments as zero until grading is completed.",[161,1144,1145],{},"Assignments may also have a lock date. After the lock date, the assignment can no longer be submitted without an approved Dean of Students reason.",[161,1147,1148],{},"Missed exams or quizzes will result in a zero, but may be rescheduled within a reasonable timeframe with an approved Dean of Students reason.",[161,1150,1151,1152,200],{},"If you will miss class activity or cannot submit an assignment, contact the instructor as soon as possible. Emergency absence situations should go through the ",[115,1153,1156],{"href":1154,"rel":1155},"https:\u002F\u002Fwww.njit.edu\u002Fdos\u002Fstudent-absence-verification",[175],"Dean of Students absence verification process",[587,1158,1160],{"id":1159},"attendance-policy","Attendance Policy",[161,1162,1163],{},"Students are expected to keep up with each scheduled module and complete required participation, quiz, assignment, and project work by the posted deadlines. Attendance or participation will be recorded through Canvas activity, required submissions, communication activity, or other announced course checks.",[19,1165,1167],{"id":1166},"closing-notes","Closing Notes",[161,1169,1170],{},"This syllabus is subject to change. Monitor Canvas, Discord, and NJIT email to stay current.",{"title":1172,"searchDepth":1173,"depth":1173,"links":1174},"",2,[1175,1176,1177,1178,1179,1180,1181,1182,1183,1184,1185,1186,1193,1197,1198,1201,1202,1203,1204,1205,1218],{"id":21,"depth":1173,"text":22},{"id":136,"depth":1173,"text":137},{"id":166,"depth":1173,"text":167},{"id":228,"depth":1173,"text":103},{"id":237,"depth":1173,"text":238},{"id":259,"depth":1173,"text":260},{"id":286,"depth":1173,"text":287},{"id":325,"depth":1173,"text":326},{"id":407,"depth":1173,"text":408},{"id":489,"depth":1173,"text":490},{"id":539,"depth":1173,"text":540},{"id":581,"depth":1173,"text":582,"children":1187},[1188,1190,1191,1192],{"id":589,"depth":1189,"text":361},3,{"id":633,"depth":1189,"text":369},{"id":642,"depth":1189,"text":643},{"id":649,"depth":1189,"text":650},{"id":679,"depth":1173,"text":680,"children":1194},[1195,1196],{"id":689,"depth":1189,"text":690},{"id":696,"depth":1189,"text":697},{"id":703,"depth":1173,"text":704},{"id":745,"depth":1173,"text":746,"children":1199},[1200],{"id":850,"depth":1189,"text":851},{"id":860,"depth":1173,"text":346},{"id":869,"depth":1173,"text":354},{"id":895,"depth":1173,"text":896},{"id":908,"depth":1173,"text":909},{"id":947,"depth":1173,"text":948,"children":1206},[1207,1208,1209,1210,1211,1212,1213,1214,1215,1216,1217],{"id":951,"depth":1189,"text":952},{"id":967,"depth":1189,"text":968},{"id":1004,"depth":1189,"text":1005},{"id":1024,"depth":1189,"text":1025},{"id":1050,"depth":1189,"text":1051},{"id":1072,"depth":1189,"text":1073},{"id":1085,"depth":1189,"text":1086},{"id":1101,"depth":1189,"text":1102},{"id":1108,"depth":1189,"text":1109},{"id":1138,"depth":1189,"text":1139},{"id":1159,"depth":1189,"text":1160},{"id":1166,"depth":1173,"text":1167},"syllabus","Summer 2026 syllabus for IT490 Systems Integration.","md",{"semester":74,"sourcePath":1223},"related\u002Fdoc-server\u002Fdocuments\u002FIT490\u002FSyllabus-Summer-2025.adoc","0",true,"1","\u002Fsystems-integration\u002Fsyllabus\u002Fsummer-2026",false,{"title":9,"description":1220},"published","systems-integration\u002Fsyllabus\u002Fsummer-2026",[1233,1234,1219,1235],"systems-integration","it490","summer-2026","38:28","FpPcSeNN8bo","https:\u002F\u002Fyoutu.be\u002FFpPcSeNN8bo","IT490 Syllabus Summer 2026","hGINCXICGUnuIVXBuQjDKy8i7aVIi8p0m2LrKwfEOEU",1780581685498]