From the blog mrogers4836 by mrogers4836 and used with permission of the author. All other rights reserved by the author.
From the blog mrogers4836 by mrogers4836 and used with permission of the author. All other rights reserved by the author.
http://creately.com/blog/diagrams/class-diagram-relationships/
I thought class diagrams were complex when first introduced, but this blog post breaks it down into simple concepts that are easier to understand. This article has helped me a lot in learning the current course materials on class diagrams. It has helped me to determining and distinguishing the different components in class diagrams and their relationships, which are applicable in object-oriented modeling.
As stated in the article class diagrams are the main building blocks in object-oriented modeling. Their main function is to show the relationship between different objects in the system. This includes their attributes, operations, and relationships among them. Classes in a class diagram are represented as boxes partitioned in three. An example of a class is the loan account with three partitions. The first is the class name, which in this case is loan account. The middle is the class attributes which are the type, accountName, dateReleased, and loanAmount. The last is the method or possible operations associated with the class. The example shows all of the relevant data of a particular object in a systematic and clear way. A class diagram is simply a collection of classes.
Relationships between classes are interrelated through different types of logical connections. The following are the different types:
Association – encompasses just about any logical connection or relationships between classes.
Directed Association – shows directionality with an arrowhead, arrowhead depicts a container-contained directional flow
Reflexive Association – occurs when classes may have multiple functions or responsibilities.
Multiplicity – active logical connection when cardinality of class in relation to another is depicted.
Aggregation – formation of particular class as result of one class being aggregated or built as a connection, directionality is a diamond shape near the parent class to the child class.
Composition – similar to aggregation, difference being emphasizing dependence of contained class to life cycle of container class, directionality line is a diamond shape adjacent to the container class and directionality arrow to the contained class.
Inheritance/Generalization one associated class is a child of another by virtue of assuming same functionality, to show relation a solid single arrowhead is drawn from the child class to the parent class, with the arrowhead unfilled
Realization – shows implementation of functionality defined in one class by another class, relationship is indicated by broken lines.
This article was a overview of class diagrams. I chose it for its simplicity in explaining design concepts. It is worth reading for someone looking for a review and it has helped me a lot in understanding the course materials.
From the blog CS@Worcester – Site Title by myxuanonline and used with permission of the author. All other rights reserved by the author.
Blog entry for CS443
From the blog Rick W Phillips - CS@Worcester by rickwphillips and used with permission of the author. All other rights reserved by the author.
Blog entry for CS443
From the blog Rick W Phillips - CS@Worcester by rickwphillips and used with permission of the author. All other rights reserved by the author.
Effective Code Reviews
On my way of finding a podcast for my first assignment, I passed by this podcast about Code Review. I decided to choose it for my first blog entry because it had some interesting opinions about code reviews. By listening to this, I learned about other benefits of code reviews, beside bugs detection and code improvement. Below was the link of the podcast:
https://talkpython.fm/episodes/show/102/effective-code-reviews.
In this podcast hosted by Michael Kennedy, Dougal Matthews shared his thoughts and experience about the benefits of code reviews and the elements effective code reviews should have. Dougal gave an interesting scenario that code reviews could save the day. For example, there were two persons, one knew more about C++, one knew more about Python. Even though they might not understand deeply what the other person is doing, they should have a code review with lighter level in case that one of them was ill or left the company. He also brought up one of the reason he thought that many people did not like doing code reviews. They expected bugs detection for their codes, but they usually received code improvement more than bugs for their valid codes. Michael and Dougal also had some interesting ideas for an effective code reviews.
To be honest, I haven’t thought that code reviews could be used as a tool to back-up basic information of a project like Dougal mentioned. Usually, the first thing that came to my mind when hearing code reviews would be bugs detection. But his scenario pointed out a special case, which some small groups might have, that code reviews could help fixing it.
About one of the reasons many people did not like doing code reviews, I understood their feelings when they just wanted to test if their codes had bugs or not, not to re-do the whole project again just because they received a better solution to solve their problems. But I thought that we should be more flexible about that. If we had another solution, which was better than our original one in one or many ways, then we should choose that solution. Beside improving the code, we also gained experience from it. The next time we countered something that was similar, we could jump directly to the better solution and reduce the time we might spend for the worse solutions that we had used before.
I thought that the code review checklist which was mentioned by Michael and Dougal would be very helpful. Like they said, it kept the reviewers and the developers on the same page. This certainly reduced the time everyone spending to ask around the same question about the progress. I also agreed with their idea about having more than one people doing code review for a same project. Different people had different points of view, and people might make mistakes. By having more people involved in the reviewing process, we could increase the quality of the review, and share our knowledge to each other.
From the blog CS@Worcester – Learn More Everyday by ziyuan1582 and used with permission of the author. All other rights reserved by the author.
http://creately.com/blog/diagrams/uml-diagram-types-examples/
This blog entry teaches us a great deal about the proper uses of UML Diagramming. It has a large number of concise examples that users can learn about.
I am using Create.ly for my UML app and this is about this application. I chose this blog because it provided tutorials regarding the same types of diagrams we are learning it class. The methods used in the article vary slightly from the marterial in our class and I appreciate the different approaches to the same problems.
From the blog Rick W Phillips - CS@Worcester by rickwphillips and used with permission of the author. All other rights reserved by the author.
This podcast is about the field of Data Science but also talked about team building. I chose this podcast because I saw that she(Angela Bassa) was the Director of Data Science at iRobot and because I am using iRobot’s Create on my robotics class. There was a part in the podcast that I thought was funny but is important when it comes to team building. Angela said that “you cannot have a team full of unicorns(programming gods basically)”. That was a pretty bold statement. She said that it will take time to get a team full of unicorns and a lot of resources. Then she referenced the “super chickens” who were a group of only the best chicken, but what ends up happening is they killed each other. I learned that balance is important in everything that we do.
Data Science with Angela Bassa
From the blog cs-wsu – Site Title by csrenz and used with permission of the author. All other rights reserved by the author.
http://urosv.blogspot.com/2008/03/boundary-value-analysis-bva.html
Staying current with the current course topic and keeping things as simple as possible, this blog post gives some interesting examples of boundary value testing that I believe are helpful for understanding the course material on boundary value testing.
Boundary value testing is a simple concept of error checking range functions at the boundary. As stated in the article, it is one of the most important techniques for test case designs that every software developer will come across. It is basically a black box testing technique where knowledge of the source code is not required.
Boundary value testing checks for off-by-one error, a common mistake in computer programming. The most common off-by-one error are the following:
misplacing < with with >=.
Under indexing or exceeding the limit of the storage space of an array
incrementing and decrementing variables that are not needed or failing to do so when needed.
loop conditionals
The simplest example given is that of N apples assembled in a straight line. Each apple is a assigned a number corresponding to its position. Taking all apple from p to q, including the two variables, q-p apples will be off by one, whereas q-p+1 will include all of the apples needed in counting.
Another example given is a function which colors rectangles with coordinates of the upper left and bottom right points. The code given are as follows:
if (points > 90) grade = ‘A’;
if (points > 80 && points 70 && points 60 && points 50 && points < 60) grade = 'E';
if (points < 50) grade = 'F';
This a a typical off-by-one error. The error that needs correction is the < sign which has to be <=. The error is that the last column and row of the rectangle is not colored in.
The final example are simply boundary ranges, say from 1-10. Some good test cases are 1 and 10 or 0 and 11, or perhaps 2 and 9. This is a typical example that is much like the exercises done in class or on the hw assignments.
This blog post gives a variety of interesting examples of a simple concept in boundary value testing that is off-by one error that was not shown in the examples in class or on the hw assignment that I think are worth noting for any entry level programmer. It gives a brief overview of different test cases that any programmer should try to avoid. It gives a decent overview of boundary value testing which is a simple concept of testing boundary values of functions that takes in ranges of independent variables. Those are the reasons why I choose this post for last week’s blog post assignments.
From the blog CS@Worcester – Site Title by myxuanonline and used with permission of the author. All other rights reserved by the author.
After being exposed to agile development last semester, more specifically Scrum, I thought it would be interesting to continue my learning in the topic. Seeing as I am now studying software design principles, agile modeling seems like a great place to start.
This is why I chose an article titled “An Introduction to Agile Modeling” which gives a breakdown on what Agile Modeling (AM) really is and how to apply it to software development using the best practices. Basically AM is a collection of values, principles, and practices which can be applied to any development project in an effective and lightweight manner. It is meant to be applied to base processes like Rational Unified Process or Extreme Programming and frameworks like Scrum. The idea is that AM can be tailored to any developer’s needs.
The values AM is based on:
Communication: All project stakeholders need to be able to openly converse throughout a projects life-cycle.
Simplicity: Always focus and aim for the simplest solution that meets all requirements and solves all problems.
Feedback: Get feedback often and early on the work that is done to course correct and create project transparency.
Courage: Make and stick to your decisions.
Humility: You won’t know everything, others can add value to the project.
The principles AM is based on:
The importance of assuming simplicity. The simplest solution is always best.
Embrace change when working because requirements WILL change.
Strive for rapid feedback to enable the agility of incremental changes.
Model with purpose, if you don’t why then you shouldn’t be doing it.
There’s more than one way to model and be correct. Content > Representation
Open communication is crucial for teamwork.
Always focus on the quality of work. The product owners should be proud and refactoring down the road should be easy.
After reading this article I think the above values and principles make a solid foundation when it comes to software modeling. While I sometimes think these things are obvious, it’s important to conduct yourself in accordance with a set of guidelines and code of conduct. Most of the ideas behind Agile Modeling are similar to the books I’ve read by Robert Martin aka Uncle Bob. I think the most important part of AM is the constant communication between all stakeholders. Requirements are always bound to shift and change priority so feedback and iterative changes are crucial for AM to be effective. The only thing I did not agree with in the article was that content is more important than representation. I think you could have great content but if you are not effective at representing it then what’s the point? In my opinion they are equals.
In conclusion I plan to read more into Agile Modeling and how I can apply it to my own projects. Moving forward I am going to tailor my software modeling to follow the best practices of AM as I believe it will create a strong foundation of design principles.
The following figure gives an idea of Agile Model Driven Development (AMDD).

From the blog CS@Worcester – Software Development Blog by dcafferky and used with permission of the author. All other rights reserved by the author.
Edit: 1,117 words in this post, 6 minute read time
Hello reader,
So, this post doesn’t really have anything to do with my classes at WSU. Rather, I just wanted to kind of talk openly about some of the reasons or things that drove me to become a student at Worcester State, specifically one in Computer Science.
Why did I choose to go to this school in particular? And what are my favorite things when it comes to computers? I hope to cover questions like that over the span of this post.
I’ll have to warn you, most posts I don’t worry about length, but this one may be a little bit of a long read. I’ll post the word count at the top of this update so you can get a gauge at how long it may be for a read to you.
So, lets start with this question: Why did I choose Worcester State? Well, I had applied to two colleges first and then planned to do a few others in case I couldn’t make it in. The two I picked — Framingham State (the first one that came to my mind initially) and then Worcester. I got a response back from Worcester State and from Framingham, a little later after WSU’s. I was accepted at WSU!
And I was denied from Framingham! I felt it was very funny. I ended up very glad that I was denied there — not to say I by any means dislike Framingham State, I just love the open feel to WSU. The variety of the people you see there is astonishing, and beautiful, the architecture and professors all very kindly and informative. The only complaint I truly have is with the God Awful parking!
Haha. Besides that one gripe, I very much enjoy spending time at Worcester State.
This leads me to my next question to answer: Why did I pick Computer Science, specifically a degree focused in Programming? There is a lot I can say in response to that inquiry.
First off, I have ALWAYS loved computers and technology. I remember as a child once having a flip phone and then having a phone with a pull out keyboard — these devices fascinated me to no end, and all they could do was very poorly connect to some internet related features and write texts/very short memos! I loved the N64 and the PS1 and 2. I hadn’t had my first laptop until I was about 10-13? I can’t recall for sure, but I got a great look at the different kinds of technology over the years.
Now I have a custom built desktop computer (most parts are aging by now but I can still run my massive library of games with no issue) and a good laptop (with a pretty cruddy screen). I remember when I used to dream of such powerful machines. I remember my first laptop and how poorly it ran Minecraft and how I could only run a few games at the lowest settings.
We are all so spoiled! Compared to not even 10 years ago, technology has grown to become so strong and immersive that, sometimes we can even find ourselves disconnected from others due to it.
I remember spending days on end playing games as a teen, escaping my own emotional and mental hell in another landscape that, to an onlooker, would appear hellish itself. But gaming and technology helped aid me through some really horrible times.
I know, I know — “Sean, answer the question you put out there.” I chose to go for a Computer Science degree because this will allow me to work in a field that I love and because through PC gaming, I was able to get into other things such as Programming and Writing and computer aided artwork. Me being a nerd for games led to me adoring technology and the times it brings me closer to others and closer to becoming the person I want to be.
Honestly, say what you will about us all sometimes not being able to interact socially as easily as people in the past may have, at least in person, but we can become so interconnected through our Technology and I think it will lead to many great things in the future, despite the negativity going on in the world today. We should use advancements in all kinds of sciences to better and to help longevity and health even if we have already used it for very terrible things as well.
*Sigh* That all is a long block of text. I won’t carry on for too much longer, but there is oooone final question I would like to state and answer: What are some of my favorite things about computers and technology as a whole? Well, there are many things. The fact that I can wear a watch that keeps track of my heartbeat and steps taken. The fact I can now message my friends nearly anywhere and at nearly any time. The fact that there is so much information and content here that History written about these times will be incredibly accurate. The fact that we all can keep our personal history so much easier than we could in the past, through the use of social media and storage devices.
The memories I’ve gotten to create with friends, the new friends I’ve been able to make, the opportunities that have come my way since all those years ago… I am so much different now than I used to be, when I was a horribly depressed kid/teen and didn’t care if I lived or died. I feel like I have a purpose, to put good positive vibes and information out there, and I feel like I can do that so much easier using technology. I can fix computers, hardware and software. I can program in a multitude of languages. Technology today allows us the ability to learn so much more and to become a much better person too, its all about how you use it.
Thank you so so very much for reading this post! I appreciate you reading this very much. Leave a comment answering some of those past questions if you want to as well! (If applicable, at least XD )
I’m down to responding or reading a nice or informative, thought out comment. I enjoy hearing other peoples opinions on these kinds of things. But besides that, I will let you go — this post is getting past a thousand words, so I feel like I’ve written enough!
I hope what I wrote was enjoyable to read, and maybe you can relate to some things. In the mean time, have a wonderful day, afternoon or night, and I will see you again with my next post!
From the blog CS@Worcester – Sean Raleigh's CS Blog by sraleigh62 and used with permission of the author. All other rights reserved by the author.