-


 CST 338 – Software Design –Wk07/08 Learning Journal Summary

When I look back at Jotto now, it still seems like a challenge. I would definitely change my approach and make sure I understand the prompt before I begin. I would make a list of the methods and write down how to implement them in my own words to show that I understand what is being asked. As I begin coding, I will use that list as a checklist to track my progress and return to methods I might have set aside for later implementation.

I really enjoyed the coding bat exercises. They were challenging for me because Java was one of the first classes I took when I started my programming journey. Although it took me a while, I was able to complete the required tasks. It was a fantastic way to get back into using java.

After a couple of setbacks with Jotto and Markov, I was able to complete Legally Distinct Pocket Monsters aka LDPM aka Project 1. Project 1 was the first time we were required to use object-oriented programming. The prompt also seemed to give you less detailed information which made it difficult to implement. With the help of our awesome TA, Polina Mejia, I was able to finally pass all tests on an assignment for the first time.

One area where I believe I have improved is understanding UML diagrams. The assignments assigned in this course all came with UML diagrams that helped to lead you through the required fields, constructors, and methods as well as the types of classes and their relationships.

Lastly, the other area where I improved is in extending classes. Although I am not an expert, I am more comfortable with the concept. It indicates that a child class (subclass) extends a parent class (super class). Creating an object of the child class will allow you to use methods and fields from both the child and the parent class.


Comments

Post a Comment

Popular posts from this blog

-
Image
  Week 2- CST-300 Module 2 OLI – Module 2 This week’s module focused on collective intelligence, reading the mind in the eyes, behavior of good teams, and why team skills will help after graduation. Collective intelligence illustrated how teams that have better collaboration skills were more successful. Meaning that everyone participated and contributed to complete the task or project. Some key features of successful teams were equal participation, higher number of women, and social sensitivity. I enjoyed the reading the mind in the eyes activity. It is difficult to tell a person’s emotions by examining just their eyes and not the entire face or body language. I scored about average. I will continue to participate and share my thoughts and ideas on topics being discussed in my team. Behaviors of good teams was a research article done at google looking for the perfect team. They found that teams promote better job satisfaction, better problem solutions and faster innovation.
Read more
-
Image
  Week 1- CST-300 Module 0 & 1 Team Resume Hello and welcome to my first post. This is a screen shot of our team resume. Although we ran into issues with some members missing, we eventually joined with another group and managed to collaborate on this assignment. Our team did an excellent job with their bios and completed the assignment on time. Module 1 Lecture   The readings from module 1 taught me about CSUMB's history and vision statement. It also covered the Degree programs from the School of Computing and Design and its faculty. The lecture also included a video titled "Study Tips to Succeed as an Online Student." The video taught me that I will need to read the syllabus, plan weekly study times, connect with classmates, check canvas frequently, and ask questions to be successful in this class.   Module 1 Lab   The lab for this week explains the American Psychological Association (APA) writing style. APA is the style used by the Computer Science departmen
Read more
-
  Week 3- CST-300 Module 3   OLI – Module 3 This week’s module is titled “What do You Bring to the Team?” and it is made up of six sections. The first section was Processing Styles and Diversity Communication. It explains approaches that would help an internal processor in your team. Some examples were to think silently for a minutes before discussing for answers, ask if members need more time before responding, and use email to communicate. The second section was Work Styles. Here we learned about work styles Get it Right – Task oriented, Get it Done – Task oriented, Get Along – people oriented, and Get Appreciation – People oriented. Each style had its strengths and weaknesses and we had to figure out how to balance them or how to help others with a different style. The third section was Your Booth Team Members. Here we watched a video of each booth member. We were then tasked with ways to support each member’s work style. The fourth section was Conflict Styles. It focuse
Read more