Architecture Tutorials & Articles
-
Unit testing with .NET
by Kevin JonesMuch is said about Unit testing - but how do you actually do it? Kevin Jones explains how XP, Unit testing and .NET go together.
-
AOP: Patching in the 21st Century
by Sing LiSing Li takes a whimsical look at the latest software development craze, and gives a clear explanation that should help you get to grips with what it's all about.
-
Domain-specific modeling for generative software development
by Martijn IsegerDomain specific modeling is a hot topic at the moment, and plays a key role in Microsoft's ‘Software Factories' idea. Martijn Iseger explains how it works, and how generative software development is the next big thing.
-
SOA and persistent data requirements
by Derek HenningerDoes SOA need special consideration when it comes to data? Derek Henninger thinks that the key is persistence.
-
Change Management, Team Collaboration & Project Visibility across the Development Lifecycle
by Dominic TavassoliThe need to collaborate when during the initial stages of a project is fairly obvious but today there is a new emphasis on software lifecycle. Collaboration and change management is now an issue for the entire lifecycle.
-
Best-practice enterprise coding
by James WintersThis introduction to Microsoft's recently-released Enterprise Library - a configuration and management tool for application blocks - highlights some of its most important features, and shows you how to use the library blocks in your application code.
-
The testing quest for perfect code
by Dave WheelerInvestigating Test-driven Development with Visual Studio 2005 Team Developer.
-
Comparing SOA and Distributed Objects
by Sean BakerWhat are the differences between Service Oriented Architecture (SOA) and Distributed Objects (DO)? We define SOA - the newer and less understood technology.
-
UML Re-Applied
by Jason GormanHow the challenge of Enterprise Architecture is changing what we model, and why.
-
Avoiding the pitfalls of automated testing
by Allan McNaughtonIt is commonly thought that automated testing is the panacea for all quality assurance woes. But is that always the case?
-
Architecture and design with Visual Studio 2005 Team System
by David WheelerThe new Distributed System Designers that will be provided as part of Visual Studio 2005 Team System are an important component within Microsoft's Dynamic Systems Initiative, which is designed to help organisations manage their entire IT lifecycle.
-
The Emperor's new methodology
by Edward GarsonAgile methods? There seems to be no technology these days that doesn't have an ‘agile' approach. Is it all hype, or is there something behind the façade and the West Coast accent?
-
Refactoring - the elixir of youth for legacy VB code
by Danijel ArsenovskiDon't just convert your existing VB code into .NET - give it a new life by transmuting it into gold!
-
The .NET express, destination Longhorn
by Dan BrownIf you want to know where .NET is taking us, Dan Brown thinks that it's all about the next version of Windows.
-
Secrets of Great Architects
by Don Awalt Rick McUmberThis article presents techniques for applying levels of abstraction to IT solutions, which can allow architects to focus on a single aspect at a time, and compares this to other engineering disciplines.
-
High-level Best Practices in Software Configuration Management
by Laura Wingerd Christopher SeiwaldWhen deploying new SCM tools, implementers sometimes focus on perfecting fine-grained activities, while unwittingly carrying forward poor, large-scale practices from their previous jobs or tools.
-
Best practices for test-driven development using Nunit
by Edward GarsonDespite plenty of coverage of Test Driven Development (TDD), a largely ignored area is that of best practices. Here we introduce TDD and flesh out best practice scenarios using NUnit.
-
Be explicit!
by Ingo RammerThe advantages of explicit boundaries in distributed applications.
-
Keeping it all Together in .NET
by Mike JamesWe take a close look at Borland's Together UML design tool for .NET.
-
A tale of two architectures
by The DraughtsmanThe .NET/J2EE schism isn't simply a matter of programming languages, but how to implement large scale architectural constructs. Although the two environments are very similar, .NET programmers probably don't understand J2EE, and vice versa. This (slightly irreverent) overview aims to bridge the gap.