Landing : Athabascau University
  • Blogs
  • COMP361 - Assignment 2 Reflections

COMP361 - Assignment 2 Reflections

I found assignment 2 a little easier than assignment 1, probably because assignment 1 prepares you for assignment 2. I often referred to assignment 1 to get my use cases, actors, and problem domain classes. I found a few mistakes in my assignment 1 which I wished I would have seen before submission, but I guess this is a good example of the iterative process. Each assignment is an iteration for the same project and as we learn more and more about the requirements and needs of the assignments, we can further refine our system design and planning. Unfortunately, we cannot retroactively refine our previous assignment for a better grade.

The biggest problem or challenge for me was the sheer amount of use cases and scenarios, it is very difficult for one person to think of all of them by themselves. Realistically, you are never fully isolated when working on a project as most have stakeholders. Frequent communication with stakeholders and feedback will help to find the majority use cases and scenarios possible, usually more than you can find on your own.

Keeping this in mind, I plugged away as much as I can realizing I may miss something, and well, my stakeholder, the assignment grader, will point out what I have missed and hopefully I can use this feedback to make assignment 3 better, kind of like a client or stakeholder in real life scenarios. Feedback and communication are a very important part of system design and it is becoming more and more apparent as this course continues.

My best advice for this assignment is, if you don’t know where to start, start anywhere that makes sense to you, and it will eventually all go together. After 2 assignments, I’ve already found tools that are useful, and I am starting to utilize them in my current job. Models will help me communicate with my clients and provide a better understanding on both sides of the development process to better meet their actual requirements and increase development efficiencies, hopefully fewer iterations for fixing problems due to poor communication or understanding.