o far, you and I have journeyed through the realm of class diagrams. Classes are a good start for understanding how an application is hooked together, and while they describe
lthough AOP and MDA were developed from very different viewpoints: programming vs. modeling; weaving many inputs into one output vs. creating many outputs from one input, there is a great
hen Gerald Weinberg began working in the information technology industry, he wasn’t hired as a software developer or a programmer?not because he wasn’t qualified for these positions, but because they
he concept of time travel has been a staple of science fiction since the entertainment genre was invented. Whether it’s H.G. Wells’ “The Time Machine,” Doc Brown’s DeLorean in “Back
n Part 2 we looked at associations, which are nothing more than references, but they can be directional and represent multiplicity. If we were restricted to our ability to generate
ave you ever needed to populate a database with realistic, but generated (as opposed to actual) data, in volumes that demand automation? Such a need arises in many circumstances, such
any companies devote a sizeable portion of their IT infrastructure to converting traditional EDI data to and from the data formats their back office systems use. Typically, they handle this
lasses are only the first step to understanding UML. In my last article I discussed classes in UML and how they are coded using C#. In this article I will
nce upon a not-long-ago, Web services were the future killer application that you just had to have a grasp on. While they are a very important part of most architectures