SWE Week8

 CST 438 Software Engineering - Week 8

List the 5 most important things that you learned in the course, and why you chose them.

-GH projects and its setup

-Agile development

-React

-Selenium

-SpringBoot

Were there topics would you like to see added or deleted from this course? 

I think adding Spring config and Spring security might be a good topics. Maybe even openAPI and Swagger for developer testing and exposing APIs.

I truly enjoyed this class. It aligns really well with my current job, so this has been my favorite class.

SWE Week 7

 SWE Week 7

Describe some of the differences between using an Agile process and using a  Plan and Document (or Waterfall) process

I use Agile at work but I always hear from senior engineers when they used to utilize the waterfall approach and how much of a pain that was because if you encountered one mistake, you will have to rollback all the way to the beginning causing productivy to drop. Meanwhile, the agile development process allows teams to always sync and move forward with their tasks and stories, so I think agile is a more productive environment and sprints make it easy to manage how much work it has been done for the program increment.

SWE Week 6

 Week 6 CST 438

Write a weekly entry describing important things you learned this week

I was only familiar with unit and integration testing. There are a few different things I learned this week since it is the first time I've performed a system test. I learned that system tests are more complex than unit tests because they evaluate how the front end, back end, databases, and other components work together. Their purpose is to verify the system’s overall interaction, not to repeat unit tests or focus on code coverage.

I also learned that system tests should make up about 10% to 30% of all tests, while most should be unit tests. Integration and functional tests fall between these two levels. Like unit tests, system tests should be repeatable, independent, and self-checking.

System testing can also include stress tests for heavy workloads, long-running tests for resource or performance problems, and failure tests to verify that the system continues working or switches to a backup when a service fails.