CSUMB Learning Journal (Chris - Group 1)

1. The most challenging part of the Library assignment was managing the splitting of strings in the Library class. Reading the strings from the files proved to be simple, but splitting them up into arrays and accurately parsing through them specifically in the initReader method was a challange and took a could tries. 2. The easiest part of the project was the overall development of the Reader, Book, and Shelf classes. These classes were very straight forward from start to finish with their familiar design goals. 3. I am most proud of my management of the initReader method. A working process for how to manage adding a readers books to themselves came quickly to me, even considering the initial trouble I had with parsing their related string. 4.    The lecture session on static vs non-static items as well as the lecture on deep vs shallow copies was the most useful to me for this assignment -- mainly due to them being forefront of new material for me. Most other items utilized i...

 Some of the lecture material this week covered the proper methods for inheritance classes. This specifically covered accessing a parent class constructor or other methods and values. The project that was finished this week was the Trooper Maker assignment which was also part of the midterm. Overall it encompassed ideas of inheritance and abstract classes alongside a lot of the material that has been covered before. Its implementation was somewhat simple as the majority of the methods within it were methods that could be autogenerated and the logic for the attack method was straightforward. The only error I ran into was incorrectly spacing the output statements. 1. I worked with the rest of my team -- Jeremiah, Jake, and Ian. 2. My strategy for working on this assignment was to generally brute force it at first. I've found that when under a time limit for smaller projects, brute forcing algorithms can get you to a working product faster even if it's not very efficient at first....

 This week's lecture material covered topics such as static vs nonstatic, overrides, equals and hashcode methods, inheritance, and interfaces.  Out of these topics, static values was the one that was the most informative to me. Previously the static modifier mainly meant that I was unable to call a non-static method from a static method and vice versa -- although after the provided explanation the definition is much clearer now. A static method is a method that belongs to the class rather than an instance of the class while a non-static method belongs to the instance. This means that static items can be updated and called from anywhere just by referencing the class and non-static items must be called in context to an instance of the class. The projects for this week were the Vacuum Inheritance and the Shelf projects. The Vacuum Inheritance project went over utilizing abstract classes, interfaces, and inheritance. The shelf class handles the individual shelf objects that are in...

 So far this week's lecture material primarily covered JUnit testing and UML diagrams. JUnit allows users to create their own testing methods for any class and their methods. UML diagrams are used to display every method and variable in a class alongside their modifiers such as Public and Private -- the arguments and return values are also shown in a UML diagram. The primary language we will be using in this course is Java in both Intellij and in Android Studio. For the assignments this week we set up our development environments, practices simple java programming, and worked on a couple projects. The individual project this week was the LabReader project which covered the process of how to read information from a file and parse it into usable data. Other than these, the other projects were parts of the Library project -- the Book and the Reader class. The Book class managed the book object that took in all the important details of books such as the title, ISBN, and author. The Rea...