Project Report Format

• Same as the proposal
• Gather/organize information from the project proposal and the assignments
• Update schedule and responsibilities to reflect what actually happened
• Add lessons learned and future work

May 9:

• gosecInterface
• HomebrewGUI
• ProjectProposer
• VSCR-Release
• Taniuki-Udon

May 6:

• GLOC
• Maestro Builder
• CrowdsourcingDatasetPlatform

May 4:

• TORIS
• exampleusageplz

May 2:

• Terminal GUI
• Reuse Dashboard

Apr 25, 27, 29:

• Finalize projects: no class

Apr 22:

• Finish deployment updates

Apr 20:

• Weekly scrum: updates, deployment example

Apr 18:

• Finish software measurement updates

Apr 15:

• No classes

Apr 13:

• Weekly scrum: updates, project measurement example

Apr 11:

• Technologies behind resilient applications
  • Kubernetes
  • Distributed stores: zookeeper, etcd
  • Automate set up of entire neworks
  • Distributed Databases

Apr 8:

• Work on projects

Apr 6:

• Weekly scrum: updates, static analysis example

Apr 4:

• Intro to Unity: Why/When/How it can help develop cross-platform games and interactive experiences

Apr 1:

• Work on projects

Mar 30:

• Weekly scrum: updates, code review example (please use github PR)

Mar 28:

• Intro to DevOps: basics of Ansible

Mar 25:

• Updateds missed from Wed: from TanukiUdon, ProjectProposer, Crowdsourcing Dataset Platform, and Reuse
• Work on projects

Mar 23:

• Weekly scrum: updates, discuss test case

Mar 21:

• GCP credits

Mar 11:

• Work on projects

Mar 9:

• Weekly scrum: this week just updates, test case due Wed after Spring break

Mar 7:

• Mongo/Clickhouse
• Using WoC to find popular packages, projects using certain packages, commits with certain text, etc

Mar 3:

• A paragraph/diagram for two architectural views of the system implemented by your project

Mar 1:

- Q&A
- Work on the project

Feb 28:

• Some background on how to contribute to OSS projects

Feb 25:

• A paragraph describing one use case for your project

Feb 23:

- Q&A
- Work on the project

Feb 21:

- Q&A
- Work on the project

Feb 18: Proposal due

• In addition to regular sections of the proposal please add a paragraph explaining your choice of the process for the class project
  • what it is
  • why it is sensible for your project as compared to at least two other choices of the process listed in the textbook (Section 2)
  • Remember that the user is some kind of software developer

Feb 16

- Q&A
- Work on proposals

Feb 14

- Q&A
- Work on proposals

Feb 11

• Scrum: each team presents update on the proposal and on the process choice (see textbook Section 2)
• Please don't forget to have milestones/issues for your project

Class 3: Fri Jan 28

1. I will continue describing software supply chains and World of Code infrastructure
2. We will spend the rest of the class discussing class projects

Class 2: Wed Jan 26

1. Make sure you have submitted the PR (see class 1 below)
2. Class recordings are here, please login to google using utk email
3. Based on the feedback a) All classes will have an online option (do not notify me if you can not attend in person) b) All Fridays (unless otherwise noted) will be online-only or self-directed c) All Mondays (unless otherwise noted) will be preferably in-person, unless it is inconvenient for you d) All Wednesdays (unless otherwise noted) will be preferably in-person, unless it is inconvenient for you. Depending on how many of you actually show up this may change in the future.
4. Class will be using Software Engineering textbook draft by Ravi Sethi (see lectures folder)
5. I will start by introducing the concept of software supply chains and World of Code infrastructure
6. We will spend the rest of the class discussing class projects

Class 1: Monday Jan 24

1. Fork https://github.com/CS540-22/students
2. Introduce yourself via a netid.md file (do not create netid.md, but replace netid by your own netid in all lowercase). Please provide at least one sentence on your background and one full paragraph explaining a project that you'd like to work on for this class.
3. Now go to your fork (https://github.com/yourGHid/students) and click on Create Pull Request on students repository

Syllabus and News for CS540: Advanced Software Engineering

• Course: [COSCS-540]
• ** MWF 09:15AM-10:05AM (Min Kao 405) and over zoom https://tennessee.zoom.us/j/99540828537 **
• Instructor: Audris Mockus, audris@utk.edu office hours MK613 - on request

The primary purpose of the course is to learn-by-doing multiple advanced software engineering techniques including:

1. Software Supply Chains
2. Open source software development
3. Software measurement
4. Software tools
5. Basics of Big Data inclding shell scripting
6. Basics of the cloud computing
7. Advanced software process

The semester-long group project will involve building an open source software tool that utilizes software development data to do measurement of software process, provide information, recommendations, or automation.