Browse by Tags

All Tags » Analysis and Design (RSS)

Jimmy Nilsson is coming to Cape Town by hannes

In collaboration with PBT Group in Cape Town, South Africa, Jimmy Nilsson will be giving a presentation called "Is Domain-Driven Design more than Entities and Repositories?" and Niclas Nilsson will give a presentation called "Dynamic Languages for Statically Typed Minds". Read more here . Share this post: email it! | bookmark it! | digg it! | reddit! | kick it! | live it!

Non Functional Requirements Checklist / Template by hannes

1. USABILITY Usability is a measure of how well the software supports the execution of user tasks. Key factors contributing to usability are the presentation of information and the management of user interaction. Usability includes two other measures, affordance and accessibility. 1.1 Affordance is a measure of the cost of learning to be productive with a user interface [Nor]. A user interface may be highly usable once it has been learned, but difficult to learn. The well-known EMACS text editor...

Head First Object Oriented Analysis and Design book review by hannes

A while back a very nice lady at O'Reilly publishers, Kathryn Barrett, send me a book from the Head First series. Head First Object Oriented Analysis and Design is a very nice book for new analysts because it covers most of the basic's subjects. Topic's includes requirement gathering, analysis and design, architecture, design principals, iterations, testing and lifecycles. If you are used to reading Eric Evans and Martin Folwer this book maybe not be for you because it does not cover...

On Methods, Process and Models by hannes

Thoughts about Methods, Process and Models taken from the book Microsoft Object Thinking by David West. (See chapter 6) All methods are someone else’s idea about what you should do when you develop software. It may be useful, from time to time, to borrow from those ideas and integrate them into your own style. It is essential, however, to transcend any method, even your own idiosyncratic method, and “just do it.” Software development is like riding a surfboard—there is no process that will assure...

RUP Artifacts by hannes

Found this really cool site about RUP Artifacts. Go have look. Share this post: email it! | bookmark it! | digg it! | reddit! | kick it! | live it!

More on Domain Driven Design by hannes

If you want to listen to what Eric Evans has to say about Domain Driven Design go download his interview with .Net rocks here . If you want to know more about DDD go the official DDD-site here . Share this post: email it! | bookmark it! | digg it! | reddit! | kick it! | live it!

LINQ promotes DDD by hannes

I think the biggest beneficiary of LINQ will one day be Domain Driven Design. Jimmy Nilsson thinks so too. " What I'm thinking about for instance is LINQ which fast approaching, and I believe it might be a signal to lots of Microsoft-developers wanting to go for DDD. I also see LINQ as a technique that solves what I solved with NWorkspace, but without you having to write your own abstraction." Read Post ADDDP . Share this post: email it! | bookmark it! | digg it! | reddit! | kick it...

Splitting up the work by hannes

I like reading Joel’s blog on software and in his latest post he talks about Apple Safari for Windows: The world's slowest web browser and the possible reason for the lack of performance as explained by Raymond Chen in one of his post, Performance gains at the cost of other components . In the end it all comes down to splitting up the work. Currently I work on a domain driven project which shows the same symptoms, the application start up takes awfully long. I think the reason for our problems...

Why analyst should be building the Domain Layer by hannes

I had a very interesting discussion the other day with some of my fellow analysts about application development in an ideal world using Domain Driven Design. Layering according to Domain Driven Development can loosely be divided into 4 layers. These layers are the User Interface, Application, Domain and Infrastructure layers. On top we have the User Interface layer which is a dumb layer. Next is the Application layer that co-ordinates the system, in other words it controls the flow in the system...

Pattern adoption phases by hannes

Jimmy Nilsson quotes Gregg Irwin about the phases you go thru for pattern adoption in his book Applying Domain-Driven Design and Patterns (page 51) You use it without being aware that you are using it. You hear about it, read up on it, thinker a bit. You learn more and start using it explicitly, if naively. You get the fire and evangelize. Something clicks. You learn more and apply less naively and more implicitly. Time passes and you see flaws. You question the concepts. You either forget about...

OO Systems Developement using UML by hannes

An older but very nice book "Object Oriented Systems Development using the Unified Modelling Language". The Author is Ali Bahrami and it is published by McGraw-Hill. (ISBN 0-07-116090-6). The book covers topic's like OO Methodologies UML OO Analysis (Identifying Uses Cases / Classes / Relationships / Attributes / Methods) OO Design (Process & Design Axioms / Class Design / Access Layers / UI's) Software Quality (Testing / User Satisfaction) What is very nice about this book...

Applying Domain Driven Design and Patters by hannes

About two weeks ago I went to Kalahari.net to check out the prizes of the books on my wish list and to my surprise APPLYING DOMAIN-DRIVEN DESIGN AND PATTERNS: WITH EXAMPLES IN C# AND .NET was only R305.00. So I ordered it immediately. Last Friday I received my book and showed it to a friend who also wanted the book. When I showed him the link the prize went up to R580.00! Well I was glad I ordered the book the first time because it really is a very good book. So far I only read the first few pages...

Octupus by hannes

Octopus is a tool to support the use of OCL. Octopus which stands for "OCL Tool for Precise UML Specifications". Read more here... and Get it here... Share this post: email it! | bookmark it! | digg it! | reddit! | kick it! | live it!

OO Design Axioms by hannes

In his book, Object Oriented Systems Development using the UML language, Ali Bahrami has the following to say about axioms and corollaries. Axioms By definition, an axiom is a fundamental truth that is always observed to be valid and for which there are no counter exception s . T wo of the most important Object Oriented Design Axiom s are The Independence axiom The Information axiom The Independence axiom deals with the relationships between components. One component should be able to satisfy the...
Filed under:

Patterns by hannes

Characteristic of a good pattern [1] It solves a problem Patterns capture solutions, not just abstract principals or strategies. It is a proven concept Patterns capture solutions with a track record, not theories or speculations. The solution is not obvious The best patterns generate a solution to a problem indirectly - a necessary approach for the most difficult problems of design. It describes a relationship Patterns do not just describe modules, but describe deeper systems structures and mechanisms...
Filed under:
More Posts Next page »
Powered by Community Server (Commercial Edition), by Telligent Systems