Week 12 - Another Step, Another Discovery

 

This week, my SoCal Software group and I keep discussing part three of our first project. Different than last week, part three is more complex which involves other data class, the Book (from part two). As the project keeps growing, it is best to document it down and have a strategy for development. Therefore, my team shared how we personally approach part three of the project. Here is my strategy:

            First, I will read through the document and other related materials. After that, I add all the variables and methods' header. I then evaluate to see if a method is basic, intermediate or intense. After working on basic methods, I start evaluating the algorithms and plans to complete the rest. I stick with my plan while coding, but ready to make any change if necessary.

            After working on part FOUR of the project, which is even more complex than the three previous parts combined, I realized a flaw that I can improve in the future. Even though there is document on the project, it is best to have my own interpreted document, which is how I understand the project, the requirements and the algorithms. Moreover, I found out that it is inconvenient to scroll up and down to see other methods. With hand-written document (or in Word), I can easily find the method or variable I’m looking for, saving time and effort.