MAY THE SOURCE BE WITH YOU…

Archive for the ‘Software Architecture’ category

Object Oriented Concepts

August 26th, 2008

Below is a short list of object oriented concepts. Object: An object is a software bundle of related state and behavior. Software objects are often used to model the real-world objects that you find in everyday life. This lesson explains how state and behavior are represented within an object, introduces the concept of data encapsulation, [...]

Solution Scope analysis

April 13th, 2008

The Commonality and Variability Analysis is a well documented analysis to help one determine how to break up classes during architecture. Another, equally as important analysis that I use, I call the Solution Scope analysis. Here we intended to make sure to differentiate the logic that solves the specific problem from the logic that solves [...]

This is a casual list of things I do personally when using EA. I use EA for sequence diagrams because sequence diagrams help me make my command classes.  I also use EA for class diagrams cause I can export Actionscript, and for database design because I can export sql to create the DB (and when its not perfect like for [...]

Command Strategy Queue

April 10th, 2008

This Implementation keeps coming up for me as I make applications for the flash player platforms. As you may or may not know, the flash player platform is full of concurrency.  We deal with this concurrency using the event model. Sometimes concurrent events need to initiate commands with interdependancies that need to be managed. These [...]

Pre-loading is something all developers contended with. Any time the user has expressed his/her desire to navigate to an application state that is not ready we turn to a pre-loader. We do this because we can not put the user in that state instantaneously, and yet we have to acknowledge the user’s request by putting [...]

Implementation Patterns

April 7th, 2008

I love Design Patterns. They are a great thing to check out when designing a solution. They don’t work so well when you need code. This is because they attempt to solve more abstract problems and lend them selves to reuse at the concept layer but do not lend themselves to reuse at the code [...]

Lets say I have 64 for files and I want to organize them in the ideal folder structure. Let’s say I have 8 pieces of content I want the application user to be able to navigate, and I want to come up with the ideal navigation. In either case I want to pose the question [...]

Interactive Building

March 20th, 2008

About 8 months ago I was tasked with creating software that would assist in the sale of units in a building that had not yet been built. As the Technical Lead, I did the following: Wrote an SDLC for the company outlining the processes to be followed for a project of this complexity Implemented SVN [...]

UML 2.0

February 8th, 2008

From time to time we have found it beneficial to diagram out certain facets of our application.  I would like to suggest learning and using the following UML 2.0 specifications. To diagram the order in which a sequence of process occur use a sequence diagram: http://en.wikipedia.org/wiki/Sequence_diagram To diagram inheritance, composition and association relationships between classes [...]

The goal of software architecture is to make life easier for those involved.  We make life easy for the developer by minimizing complexity and maximizing reusability.  We make life easy on the development manager by emphasizing task-ability and testability as we refine the encapsulations within the architecture.  I refer to the efforts made to maximize [...]

Proudly powered by WordPress. Theme developed with WordPress Theme Generator.
Copyright © MAY THE SOURCE BE WITH YOU…. All rights reserved.