Week three involved downloading and installing a program called Visual Paradigm, which is a tool that helps developers create UML class diagrams. A UML (Unified Modeling Language) diagram is a visual representation of the classes in a program and the relationship between those classes. We read more about UML class diagrams, then we formed smaller groups from last week’s large group and began working as a group to create a UML class diagram for our game.
I’m learning to appreciate the object-oriented part of object-oriented programming. After defining the requirements and user stories in our group projects last week, it’s comforting on a certain level to realize that the major elements of our program are actually modeled after physical objects or even ideas. The class diagrams we did this week helped to drive that concept home, and I’m looking forward to see how we actually implement these objects on a programming level in Java code.
It was a challenge for me to envision and verbalize the objects and relationships that we’ll need in our group’s game. I think this is a skill that becomes easier with practice, and I’ve started to get the hang of it, but it was quite difficult initially. I depended a lot on my team and on referring back to the readings to get a better grasp on how everything was supposed to go together on our diagram.
Although the diagram had to be the most frustrating part of this week’s work, it was also the most interesting part to me. It was like seeing a puzzle come together with all the pieces fitting as they should. Although work to improve it based on feedback from the instructor, my team members were heroes in getting it put together, and I really appreciated their hard work.