All Integrations
- Note taking at the introductory level via accountability for class notes
- Team work at the introductory level by working in pairs with a robot
- Professionalism at the introductory level by requiring all communications about the course to be at a professional level
- Ethics at an introductory level by covering:
- being honest about what your software can and cannot do
- encouraging their project to be socially responsible
- Cybersecurity at the introductory level by covering:
- secure programming in terms of what crazy input can be given to the program.
- Verbal communications at an introductory level by requiring each team to present their project and include the some grading of the quality of the presentation as part of the rubric with feedback on how to improve
- Note taking at the introductory level by requiring students to take lectures notes. Should include posting videos of some class lectures so they can review their technique.
- Technical writing at the introductory level by requiring written work to have section headers, decent size paragraphs, and giving feedback on transitions.
- Ethics at an introductory level by covering:
- digital divide
- ownership of digital material
- Cybersecurity at the introductory level by covering:
- securing one's self in social media
- the fundamental concept of cyber security
- Note taking at the introductory level by requiring students to take lectures notes.
- Technical writing at the introductory level by requiring written work to have section headers, decent size paragraphs, and giving feedback on transitions.
- Ethics at an introductory level by covering:
- digital divide
- ethics associated with AI
- Cybersecurity at the introductory level by covering:
- securing one's self in social media
- the fundamental concept of cyber security
- Self-learning at the introductory level by having some programming assignments that include using some simple features not covered in class (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
- Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
- Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
- Professionalism at the introductory level by having students track how long it takes to write programs (so that they are better equip to estimate this in the future) and comment on what they learned and what they would want to to better with a program if they could.
- Cybersecurity at an introductory level by requiring students to document possible invalid input what happens for all programs. By the end of the semester, they should handle some of the invalid input (i.e. secure programming).
- Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
- Self-learning at the introductory level by having some programming assignments that include using some simple features not covered in class (such as using a pre-defined data type)
- Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
- Technical writing at the application level by requiring students to do a formal software development report and requiring quality writing (and grading the quality of the writing), Also by the end of the semester by refusing to accept reports that don't meet a bare min. standard (such as standards, spell check, using bullet lists as appropriate.
- Team work at the introductory level by having at least two assignments where students are working in pairs with one developing the data structure and the other using it. Students need to take on both roles during the semester. Students also might have a third assignment where they are assigned one of the two roles and they have a partner that they don't know and must only communicate via the interface.
- Professionalism at the introductory level by having students track how long it takes to write programs (so that they are better equip to estimate this in the future) and comment on what they learned and what they would want to to better with a program if they could.
- Cybersecurity at an introductory level by requiring students to document possible invalid input what happens for all programs. By the end of the semester, they should handle some of the invalid input (i.e. secure programming).
- Ethics at an introductory level by having at least one program assigned that could have ethical implications and having the students discuss that in their reports.
- Note taking at the introductory level by requiring students to summarize what was said by the speakers with details not found in any posted slides
- Technical writing at the introductory level by requiring all writing to adhere to format standards
- Professional at the introductory level by having working professionals talk to the students about what it means to be a professional and by having inflexible deadlines.
- Cybersecurity at an introductory level by *. studying one current event associated with cybersecurity
- Ethics at an application level by *. studying one current event associated with computing ethics including the Christian perspective
- Self-learning at the introductory level by having the students learn a few sql functions on their own but having them part of the assignments. This could include formatting associated with dates, string functions, and dealing with nulls.
- Note taking at the introductory level by requiring students take class notes and listen and record given guidelines (that may or may not be on slides) for sql and ER diagramming.
- Professionalism at the introductory level by
- having students learn about the need for high quality work for table design
- having students learn to respect the knowledge of the domain expert when designing tables.
- not accepting any document/work that does not have a name on it
- Security at the introductory level by
- having students learn about only storing the data needed and nothing more
- having students learn about SQL injections.
- having students learn how to secure data via views, constraints, and permissions, and the weaknesses of each.
- Ethics at the introductory level by discussing the responsibilities that come from having access to a lot of data.
- Self-learning at the introductory level by having some programming assignments that include using some simple features not covered in class
- Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
- Technical writing at the application level by requiring students to do a formal software development report and requiring quality writing (and grading the quality of the writing), Also by the end of the semester by refusing to accept reports that don't meet a bare min. standard (such as standards, spell check, using bullet lists as appropriate.
- Team work at the introductory level by having at least two assignments where students are working in teams
- Professionalism at the introductory level by having students estimate how long it takes to write programs and then analyze their estimate based on how long it actually took. They will also comment on what they learned and what they would want to to better with a program if they could.
- Cybersecurity at an introductory level by requiring students to document possible invalid input what happens for all programs. By the end of the semester, they should handle some of the invalid input (i.e. secure programming).
- Ethics at an introductory level by having at least one program assigned that could have ethical implications and having the students discuss that in their reports.
To be determined
- Self-learning at the application level by
- having discussions about how to get the most out of online lessons
- demonstrating how to establish education goals, outcomes, and tasks to learn specific tasks.
- Note taking at the application level by grading the notes students take while in class and grading the notes
- Professionalism at the application level by holding discussions different ways to learn and the advantages of each
- Self-learning at the application level by
- having the technical material being covered by existing online lessons found in the ACM learning center and other professional sites
- having discussions about how to get the most out of online lessons
- demonstrating how to establish education goals, outcomes, and tasks to learn specific tasks.
- Note taking at the application level by grading the notes students take while working through online lessons
- Technical writing by requiring students to create at least one website covering a technical topic and grading it on the way it communicates the information
- Professionalism at the application level by holding discussions about the differences between building websites for oneself/friends (as a hobby) and doing it as a job.
- Security at the introductory level by covering at least two different security issues associated with website development
- Ethics at an introductory level by discussing the responsibilities of a website provider for the content of the material posted on the website.
- Verbal communications at the introductory level by requiring each student to make presentation (at least 5 minutes) discussing either what was learned in a lesson or presenting a website created by the student.
- Self-learning at the application level by
- having the technical material being covered by existing online lessons found in the ACM learning center and other professional sites
- having discussions about how to get the most out of online lessons
- demonstrating how to establish education goals, outcomes, and tasks to learn specific tasks.
- Note taking at the application level by grading the notes students take while working through online lessons
- Technical writing by requiring students to create at at least one document for their work and grading the manual on both content and writing ability.
- Professionalism at the application level appropriate to the topic
- Security at the application level appropriate to the topic
- Ethics at an introductory level by discussing TBD.
- Verbal communications at the introductory level by requiring each student to make a formal demonstration of their work
- Self-learning at the application level by
- having the technical material being covered by existing online lessons found in the ACM learning center and other professional sites
- having discussions about how to get the most out of online lessons
- demonstrating how to establish education goals, outcomes, and tasks to learn specific tasks.
- Note taking at the application level by grading the notes students take while working through online lessons
- Technical writing by requiring students to create at at least one user manual and grading the manual on both content and writing ability.
- Professionalism at the application level by holding discussions about the differences between maintain one's own (or friend's) systems and doing it as a profession and maintain many computers.
- Security at the application level by including modules on securing Windows servers and Linux boxes.
- Ethics at an introductory level by discussing TBD.
- Verbal communications at the introductory level by requiring each student to make a formal demonstration of their servers and grading not just the quality of the servers and what is installed but how well the presentation was organized.
- Self-learning at the application level by requiring students to learn one component of the topic on their own (with little assistance from the instructor)
- Note taking at that master level by
- not posting lecture slides,
- requiring students to track all requirements themselves
- having exam questions based on specifics in the lectures and presentations given by other students.
- Technical writing at the mastery level by requiring to write a technical report of a project for the class in a quality manner. Advanced discussion on things such as a theme, transitions, use of diagrams, focus, and other items should be covered in class and graded on.
- Security at an application level by covering at least two separate security issues associated with the topic of the course.
- Ethics at an application level by covering at least two separate ethical issues associated with the topic of the course.
- Verbal communications at the application level by requiring students to present their projects and/or supplementary material to the class.
- Self learning by using existing online lessons to learn the details about a specific cloud provider and bring those lessons to the class
- Note taking by using notes taken from online lessons to produce reports while disconnected from the lessons
- Technical writing and presentations by creating reports and presenting work to the class
- Professional by doing assigned learning tasks in a timely manner
- Cybersecurity by studying different aspects of security in the cloud
- Ethics by writing a report about the ethical components of associated with one or more aspects of cloud computing
- Self learning by using existing online lessons to learn the details about a specific AI or data science tool found in the cloud and using it to develop a proof of concept program.
- Note taking by using notes taken from online lessons to produce reports while disconnected from the lessons
- Technical writing and presentations by creating reports and presenting work to the class
- Professional by doing assigned learning tasks in a timely manner
- Ethics by writing a report about the ethical components of associated with one or more aspects of AI and data science in cloud computing
- Note taking at the application level. It is assumed that by this level students will be able to take quality notes in class. At least one assignment will have details only given in lecture requiring the students to take notes for any such assignment.
- Writing at the application level by requiring quality software development reports.
- Security at the introductory level by covering topics associated with secure programming in an object oriented environment
- Self learning by learning on additional data structure and developing a program using it.
- Technical writing by submitting high caliber software development reports
- Team skills by working on teams with at least two programs
- Professional by doing assigned learning tasks in a timely manner
- By implementing secure programming in each program and reporting on it and also existing security weaknesses.
- Ethics by writing a report about the ethical components of associated with two programs developed
- Self learning at the introductory level by requiring students to learn at least one aspect of Agile programming on their own and use it during the semester.
- Note taking at the application level by requiring students to take quality notes from meetings and grading those notes
- Technical writing at the application level by quality artifacts and documentation to be in a final form
- Team work at the application level by
- requiring most (if not all) project work to be done in teams. Switching team members during the semester should be considered
- having the roles in the team chance throughout the semester
- Professional at the application level by requiring students to treat all team meetings in a professional context and preparing their work to be at the professional level instead of homework level.
- Security at the application level by requiring all work on software to include a section on the security issues
- Ethics at the application level by
- requiring all work on software to include a section on ethical issues
- covering cases of software failure and the ethics associated with that
- Verbal communication at the application level by requiring each team to make at least two presentations to the class.
To be determined
to be determined
To be determined
- Note taking at the application level. It is assumed that by this level students will be able to take quality notes in class. At least one assignment will have details only given in
- lecture requiring the students to take notes for any such assignment.
- Writing at the application level by requiring quality software development reports.
- Security at the intermediate level by covering and using non-trivial topics associated with secure programming in an object oriented environment
To be determined
To be determined
- Life long learning skills by learning a complete topic on their own
- Technical communication skills by making at least 2 verbal presentations (on recorded) and writing a significant report (10 pages) on what was learned
To be determined
- Life long learning by taking what was covered in class and expanding on it in more detail