Week 9 Class 17 Thu Nov 02 Posted: Nov 02
After Class:
sortTDD Posted score and any feedback in Brightspace. I also added the generated report Report.md in your repository. Generated from your source code, it shows various parts of your program, and builds and tests every commit. This is a shortened version of what I will generate for Project 3.
CPSC 489-010 T: DevOps Spring 2024
I will be offering a Special Topic course on DevOps in Spring 2024. The prerequisite for the course is "Permission of Instructor". I will grant permission to anyone who has passed CPSC 480 Software Engineering. The course description:
A comprehensive overview of the culture and practice of DevOps, the automated, continuous, and secure integration of version control, testing, packaging, configuration management, and containers.
"DevOps", a compound of "development" and "operations", is an approach to build and deploy software. Leveraging automation, it ties together version control, software testing, packaging, configuration management, and containers for continuous integration to distribute software updates frequently and with high quality. DevOps combines version control (e.g., git), containers (e.g., Docker), continuous integration tools, system administration, SSH and SSH keys, program build tools, and installer packages (e.g., deb and rpm), combined with software validation and testing.
Announcements
Class Meeting on Tuesday, Nov 7
I will be in Salt Lake City on Monday, Nov 6, and Tuesday, Nov 7, for the 2023 NSF CIRC PI meeting where the srcML grant, "Enabling Automated Language Support for the srcML Infrastructure" [2016465], is a highlighted project. As a PI on an NSF grant, I am required to attend this meeting.
Although I will be away on Tuesday, there will be a class meeting. A Team Exercise that counts double is due by the end of the class meeting. Mr. Kyle Rossi, my RA, will be present to handle any questions. My Office and Advising Hours are canceled on those days.
Class
Exercise 41: Team Use Case Diagram
Create a Use Case Diagram for your project. Use the user stories as use cases. Select up to 10 of your user stories.
Use yuml.me to draw the diagram.
Each member of the team must either create their own diagram at yuml.me, or draw a diagram on paper.
By the end of the class period, upload to Brightspace a PDF of the diagram, or a photo of your hand-drawn diagram.