Hannes's Mind Maze
Think smart!
Sign in
|
Join
|
Help
Home
Contact
About
RSS
Atom
Comments RSS
Search
Tags
.Net
.Net Framework 3.5
Analysis and Design
ASP.Net
Books
Business Analysis
Domain Driven Design
General
Humor
I.T.
New South Africa
Personal
Process
Programming
Security
Software
Software Development
Sport
System Analyst
Technology
Navigation
Home
Careers
Downloads
Support
Archives
June 2008 (1)
May 2008 (1)
January 2008 (2)
November 2007 (4)
September 2007 (3)
August 2007 (10)
July 2007 (4)
June 2007 (3)
May 2007 (5)
April 2007 (12)
March 2007 (3)
February 2007 (8)
January 2007 (14)
December 2006 (6)
November 2006 (5)
October 2006 (6)
August 2006 (1)
July 2006 (1)
June 2006 (4)
May 2006 (2)
March 2006 (4)
February 2006 (4)
January 2006 (4)
December 2005 (1)
November 2005 (10)
October 2005 (7)
September 2005 (10)
August 2005 (5)
July 2005 (6)
June 2005 (11)
May 2005 (13)
April 2005 (15)
March 2005 (5)
February 2005 (7)
January 2005 (16)
December 2004 (1)
Book List
Applying UML and Patterns
Continuous Integration
Design Patterns
Domain-Driven Design
Object-Oriented Design Heuristics
Patterns of Enterprise Application Architecture
Programming Pearls
UML Distilled
The Pragmatic Programmer*
Applying Domain-Driven Design and Patterns*
UML 2.0 in a Nutshell*
Head First Design Patterns*
Herding Cats*
Object Oriented Systems Development*
Like to read
SA Developer
SA Architect
Joel on Software
Joel Reddit
The Daily WTF
Wikipedia
ScottGu's Blog
Slash Dot
January 2006 - Posts
2
Comments
Use Cases: When to use Includes, Generalization and Extending
by
hannes
I often find unsure when I have to decide if I must use a <<include>> or <<extend>> in my UML Use Case Diagram. Here are a couple of quidelines taken from UML For Dummies by Michael Jesse Chonoles and James A. Schardt (ISBN: 0-7645-2614-6) Linking Use Cases with «include» (sometimes referred to a <<uses>>) You’ll often run into déjà vu as you document your use cases—especially when several of them show an identical sequence of events exchanged between an actor...
Filed under:
Analysis and Design
1
Comments
Evolution
by
hannes
Go here for a timeline of the evolution of programming languages, from the daddy of them all, Fortran (1954), to present. Share this post: email it! | bookmark it! | digg it! | reddit! | kick it! | live it!
Filed under:
Programming
0
Comments
First impressions SQLServer 2005
by
hannes
From the little time I spend working on SQLServer 2005 I must say that I like the new SQLServer. But there are some pains, old and new, here are two. Old pain : Why can't I still not publish an ERD from the Db Diagram to visio or a picture file. I know there is a lot of tools that allows you to do it externally but why can't SQL Server do it for me? New Pain : When executing code, i.e. creating a new store proc's, and you don't put the data base name to use on top It just goes and created that store...
Filed under:
Programming
Comments
Hi again
by
hannes
Hi all, it's been a while since my last blog entry but here I'm again. First things first, to all a prosperous 2006. Well 2005 was a hectic year with lots of high's but sofar the first month of 2006 is far less hectic. 2006 promise to bring some new challenges (home & work) for me but I think I'll concentrate on consolidations. Share this post: email it! | bookmark it! | digg it! | reddit! | kick it! | live it!
Filed under:
Personal