In this tutorial, I cover GRASP, or General Responsibility Assignment Software Patterns. GRASP defines rules you can use to decide which objects should have which responsibilities in your Object design.
Here I cover the following rules: Creator, Expert, Coupling, Controller and High Cohesion. The tutorial includes a presentation, code examples, sequence diagrams and class diagrams to make everything understandable and interesting. The code used follows the video.
Welcome to part 9 of my Object Oriented Design tutorial! This all started back in part 3 in my UML Use Case Tutorial.
Here I’ll finish turning sequence diagrams into code. If you get good at this process you’ll be able to make any program no matter how complicated it may be.
All of the code from this and the last tutorial can be found below to help you learn. In the tutorials that follow I’ll answer all of the design pattern tutorials I’ve been receiving. Continue reading Object Oriented Design 9
In this video I’ll show you how to install Torchlight II for Mac. I’ve received many requests on how to play PC games on a Mac. I reached out to those people that made the requests and asked them what game they want to play most. They said they wanted to play Torchlight 2.
So, in this video I’ll show you how to install Windows Steam on Mac. Also I’ll cover how to play PC games on Mac without installing Windows. This works for numerous PC games. JUST TEST THE DEMO VERSION BEFORE YOU BUY!
The only program you’ll need is PlayOnMac. It will install everything else for you. Find other PC games you can play on Mac here. Continue reading Torchlight II for Mac
I showed you how to turn your program idea into a Use Case. Then we turned the Use Case into a Domain Model. Then I showed you how to turn the Use Case into a Sequence Diagram. Then we made the Sequence Diagram into a Class Diagram. Now I’m going to show you how to convert the Sequence Diagram into working code.
I make part of the code in this video. The rest will be made in part 9 of my Object Oriented Design Tutorial. All of the code follows the video to help you learn. To get the other diagrams, just click the associated links above.
Unified Modeling Language (UML) is a graphical way of describing software systems. In this tutorial series, I cover Use Case, Activity, Class, Object, Sequence and many more UML Diagrams.
I can’t think of anything more important for a good programmer to understand than UML. With it you’ll be able to create first class Object Oriented Designs. Those designs will allow you to create anything you can imagine. But, without UML none of these things are possible. Every video and links to all of the code can be found below.
In previous tutorials I showed you how to make a sequence diagram. In this video, I’ll show you how to convert a Sequence Diagram into a Class Diagram. Here are the tutorials on making sequence diagrams if you missed them OOD Sequence Diagrams & Sequence Diagrams 2.
In this tutorial, I wanted to show step-by-step how sequence diagrams are turned into class diagrams. Then in the next video, I’ll turn them both into working code in about 10 minutes. The class diagrams used can be found below.
In the last tutorial, I showed you how to create a complicated sequence diagram for our ATM software. In this tutorial, I’m going to simulate the process of creating a sequence diagram in a group atmosphere.
I’ll improve the last design, while explaining what I’m thinking. I’m also trying to teach how to think through a programming problem while creating the sequence diagram.
Both new sequence diagrams follow the video to help you learn. Continue reading Object Oriented Design 6
In this video I continue building my ATM software using Object Oriented Design principles. If you missed the beginning of this tutorial, the previous videos are here.
If you want to learn everything about Sequence Diagrams, I have you covered as well. I take you through the creation of a sequence diagram using all of the diagrams I made before it. The sequence diagram made in the video follows the video to help you learn. Continue reading Object Oriented Design 5
Welcome to the 4th part of my Object Oriented Design tutorial. I show you how to plan your first iteration. I explain all of the parts of the Elaboration phase of Object Oriented Design.
Then I take the Usage Case I made in part 3 of this tutorial, and convert it into a Domain Model. I cover all of the following: conceptual classes, how to build domain models, turning nouns into classes, associations and how to tell an attribute from a class.
This is a big tutorial, but the diagram that follows the video will help you learn this stuff.
Welcome to my 3rd tutorial on Object Oriented Design. In this part of the tutorial, I’ll cover Iterative Development, The Unified Process and Usage Cases.
Unlike the waterfall process for object design, with the iterative process programming starts before all of the requirements are expected. The Unified Process is a popular IDP which focuses on high risk / value parts first before creating full requirements for the program.
A large Usage Case follows the video to help you.
In the previous part of my Object Oriented Design Tutorial, I showed you how to build a Use Case, Object Model, Sequence Diagram and Class Diagram from scratch.
In this tutorial, I show you how to turn those diagrams into code and a working program. This is the process a person goes through to create excellent Object Oriented Designs. The code follows the video along with the digrams from last time.
Welcome to my Object Oriented Design Tutorial! I cover a ton of things in the video below.
The goal of this tutorial is to teach you how to create excellent OO designs. In this tutorial, I start off with a programming idea and walk you through the process of creating a Use Case, Object Model, Sequence Diagram and Class Diagram.
If you need help understanding sequence diagrams look here. The diagrams that follow the video should help you along though.