CS Online Learning Journal

This was our last week in CST 438 - Software Engineering. Reflection For this journal we were asked to list the five most important things we learned from this class. Unit Tests:  As I have mentioned before, we have had to write unit tests before in a previous class. However, this class didn't explain why adding unit tests is important, so at the time it simply felt like another assignment. Learning why unit tests are important, to help to catch bugs or breaks in code, has changed how I look at assignments for tests and has motivated me to start adding tests in my personal projects. AGILE:  With it being widely used in the industry I had heard of AGILE before, but I didn't know much about it. Learning about AGILE has helped me understand better how the industry operates, and it has helped prepare me for it. Waterfall:  Similar to AGILE, I knew that teams may choose to document a project or piece of software before starting to work on it. The main example I was familiar wi...

This was our seventh week in CST 438 - Software Engineering. Reflection Last week we finished the group project for the class. As one of our assignments this week we temporarily set up our project on Amazon Web Services (AWS) and briefly tested it before removing everything from AWS. While AWS is clearly a very powerful tool, it also seems complicated and difficult to learn. While it was easy to get our project running locally, and other web services like Render I have used in the past have been straighforward, AWS required several steps and individual services to be able to run our project. Although most of the services we made were free, some were paid. I was surprised by how expensive the AWS services would have been each month if I had kept them running. This week we explored the Plan and Document, also called Waterfall, process. I described some of it in the next section, but basically the Waterfall process seeks to describe all of a project's requirements and time estimates b...

 This was our sixth week in CST 438 - Software Engineering. Reflection Last week we coded the front end for our group project, making the web services fully functional (at least when being ran locally). This week we added system tests to portions of the website. Instead of testing individual methods with like unit tests, the system tests we wrote test that the services that make up the website work correctly when running. I wrote a system test that logged in as an instructor, created an assignment, and graded said assignment. The code reveiw for my code went well, with only minor changes being suggested.   We also read about   CaaS, which a wrote a little about below.  SAG Ch. 25 CaaS stands for Compute as a Service , and involves either buying or renting the computing power to run programs.   Overtime an organization may experience an increase in the following metrics: Number of different applications to be managed Number of copies of an application that needs...