Archives
-
Publikation: "Trends: Industrialisierung der Softwareentwicklung" in OBJEKTspektrum 3/05
"Softwareentwicklung geschieht zunehmend in einem Spannungsfeld zwischen Zeitdruck und Technologieflut. Um unter diesen Umständen verlässlich höhere Qualität zu produzieren, müssen sich Menschen und Prozesse verändern."
-
Software Cells #9: Applications as Holons - Becoming a little more systematic
Software Cells started out in the concrete and tried to make small to medium scale software architecture more tangible. Software Cells thus were a bottom-up approach.
-
Publikationen in dotnetpro 6/05
"Am Anfang war der Vertrag: Contract First Design und Microkernel-Frameworks", dotnetpro 6/05
-
Publikation: "Spezialiserung tut Not" in IT-Freelancer Magazin Mai/2005
"Spezialisierung tut Not", S. 34 in IT-Freelancer Mai 2005: Zur Notwendigkeit der Spezialisierung der Kenntnisse und Fertigkeiten für Softwareentwickler. Ein Artikel in der Linie meiner Argumentation von "On the Future of Software Development".
-
Previous Publications / Bisherige Publikationen
A (yet incomplete) list of my publications until April/May 2005. All other publications will be listet as individual posting.
Contract First and Microkernel applied - Report from a recent workshop
Finally I find time to blog about a recent workshop I did with 12 developers in Austria and where I applied Microkernels in a training.
Software Cells #8: Of Customer Problem Domain and Infrastructure - Mind the Dimension
After I put Software Cells into perspective with other architectural models, several people approached me with the question "Now, then, what are Software Cells for?" followed with some problem scenario. And I can tell you, those scenarios made me sweat for a while ;-) But I want to spare you the details and focus on my findings while trying to put Software Cells to good use on those problems.
Software Cells #7: Putting Software Layers et al. into Perspective
In my previous posting I added the missing pieces to the Software Cell puzzle: communication technologies like .NET Remoting, MSMQ, but also ADO.NET. Now you know all the basic structures of any software:
Software Cells #6: Connecting Applications
In my last posting I tried to put Software Cells into perspective. And as it turned out, they prefectly fill a gap that existed between COP/OOP and SOA. With Software Cells we can seamlessly stack levels of abstraction onto each other from single statement to groups of Solutions which I call Software Societies.
First Impression: Meeting Google´s Craig Silverstein
Lately there has been some discussion on if and how Google might be a threat to Microsoft. Bill Gates even said "[they] kicked our butts". Right now I´m not interested in the details of where exactly Microsoft feels hurt and if Google can do substantial damage to Microsoft´s position. Rather, what now surprises me is the surprise everybody felt when Google came out with desktop search functionality and Google maps etc. I´m surprised about this, because I just met with Craig Silverstein, Google´s director of technology and first employee of Google - or Google´s man behind the curtain (as some call him).
Software Cells #5: A journey through the software universe from single statement to Software Societies
So, where are we with Software Cells? In my last posting I talked about Contract First design, and I guess, we now need to tie together the various bits and pieces.
We need to talk about how to connect Software Cells. For that it´s beneficial, to put Software Cells into perspective. So let´s first vary the scale of our software map. Let´s get on a journey thru the "software universe"! What can we see, if we look thru a microsope? What can we see, if you look thru a telescope?