CST Week 4

With whom did you work?

I worked with my group of Saria, Gary, and Rahim.

 

What was your strategy for solving the assignments?

 I started with the UML diagram and then moved to reading the whole prompt. Then I went and focused on one method at a time reading the prompt for that method in detail. I only started writing code once I had a general idea of what each method was meant to do.

 

 What was THEIR strategy for solving the assignments

 Their strategy was to begin by reviewing the prompt and analyzing the provided UML diagram. The diagram serves as a visual representation of the relationships between classes, fields, and methods. They then reread the class descriptions, paying attention to the purpose and data types of each field and method. With a clear understanding of the requirements, they started coding, using the prompt as a roadmap to guide me.

 

 How would you change your strategy having worked on the assignment?

I would change my strategy in the order I did the methods. I went from the top down, but I think I would do it more based on dependencies if I were to do it again.

 

 According to your classmate(s): how well does your code follow the Google Java Style Guide?

My code contains a bit too many spaces, I like to but my catch blocks on a new line and it is something I can clean up.

Comments

Post a Comment

Popular posts from this blog

CST 334 Week 4

     This week in our course, we focused on memory virtualization and memory management. In our lab, we concentrated on FIFO (First-In-First-Out), a page replacement strategy that uses a queue to manage page entries.      In FIFO, pages are loaded into memory and placed in a queue. When a page needs to be replaced, the oldest page in the queue is evicted. This approach can lead to inefficient page replacement because even if a page has been recently used, it will still be evicted if it has been in memory the longest.      In contrast, LRU (Least Recently Used) tracks the usage history of pages. LRU replaces the page that hasn't been used for the longest period of time. Because it takes into account the actual usage patterns of pages, LRU typically provides better performance, whereas FIFO only considers the order in which pages were loaded into memory.
Read more

CST363 Week 1

1. Relational database tables and spreadsheets look similar with both having rows and columns.  What are some important differences between the two?   Relational databases and spreadsheets might look similar because they both have rows and columns, but they are quite different in how they manage data. Databases can handle lots of data and keep it organized using rules like unique IDs and links between different tables. They’re built to deal with many users working at the same time and can keep track of complex relationships between data. Spreadsheets are great for smaller tasks and simpler data, but they can get messy with a lot of information and don’t handle multiple users very well. They also don’t have the same level of data protection or advanced searching features that databases offer.   2. Installing and configuration a database and learning how to use it is more complicated that just reading and writing data to a file.  What are some important reasons tha...
Read more

CST 334 Week 7

     This week, we covered topics including I/O devices, disk drives, files and directories, file systems, and RAIDs. RAID is a storage technology that combines multiple physical disks into one logical unit to enhance performance, data redundancy, or both. RAID 1, also known as mirroring, duplicates data across two or more disks, ensuring that if one disk fails, the data remains intact on the other. This provides high data reliability but requires twice the storage capacity. RAID 4, on the other hand, uses a dedicated disk for parity, with parity information calculated using XOR, and distributed across the array. This parity allows for data recovery in the event of a disk failure. While RAID 4 offers better storage efficiency than RAID 1, it may suffer from performance bottlenecks, as the parity calculations are handled by a single disk.
Read more