I posted yesterday that we had shipped our Enterprise Collateral Management solution based on our new architecture. As I said, we still have a lot more to do. Several people have asked and many have been interested in the continuing blog posts that I have had on our 14 month development cycle. This post is an attempt to organize several threads in continuing the conversation.

Architecture

• Logical Three-Layered Services Application architecture
• Physical deployment to 1 to N Tiers depending on load, failover, customer needs, etc.
• Service-Oriented Architecture with all functionality designed and exposed as a Business Autonomous Services

Presentation Layer

• Windows Composable SmartClient implemented with CAB, SCBAT, Infragistics and Windows Forms 2.0 (see here for much, much more!)
• Dependency Injection of WCF and other Service instances via CAB
• Model-View-Presenter pattern

Service Layer

• Organized into Entity, Business Process and Infrastructure Services
• Designed as much as possible in SOA Business Process manner and Contract First
• .NET 3.0 Windows Communication Foundation with our custom behaviors
• Mostly wsHttpBinding with WS-Security, WS-ReliableMessaging, and Sessions turned on, some netTcp
• MSMQ
• Workflow based on .NET 3 Windows Workflow currently in architecture design

Domain Layer

• True Evans DDD Layer reflecting our Collateral Management domain withRepositories and Factories, Entitities, etc
• Domain Mapper Pattern implementation

Resource Layer

• Object-Relational Mapper via Wilson ORM
• Query and Criteria API makes our database access strongly-typed and allows expression of queries in C# 3.0 like syntax consistent with how we query other objects like In-Memory Repositories
• SQL Server 2005 and Oracle 10.2g support

Process

• Full and pure Extreme Programming (not "Agile")
• Information Radiator White Board with User Stories + Bugs
• TDD with NUnit GUI and TestDriven.NET
• Refactoring, Collective Code Ownership
• FIT Tests
• 1 Week Iterations, originally 3-weeks, See this also
• A Week in our Life and Process
• Team - 7 Developers + Agile Architect who codes! + Three On Site Customers + 1 External Bank Customer
• 1500+ NUnit Tests run as part of CruiseControl.NET Build run on every check-in and regression tests
• 2 Full QA resources as true members of the Whole Team with testing every Iteration
• Visual Studio 2005 Team Client + CodeRush + Refactor Pro
• All C#
• Subversion Source Control
• Wiki for design discussions and documentation
• Whiteboard Lightweight Modeling
• Process change last September to have Sam focus on Architecture "outside" and "ahead" of Iterations to layout technology infrastructure choices (like which reporting engine) and design "big ticket" items like Workflow
• Windows XP SP2 development desktops

Infrastructure

1. Deployed on Windows Server 2003 R2
2. Click-Once Deployment of Smart Client
3. SQL Server 2005 Failover Clustering & Hot Mirroring, Oracle RACs
4. Single Sign-On Security Authentication with Windows Auth, Kerberos Brokered, AD/ADAM and WCF
5. AzMan Roles as Indigo Behavior
6. PAG Exception Management & Logging Blocks
7. PAG Caching Block
8. AD/ADAM
9. X.509 PKI
10. CardSpace, SAML, and WS-Federation in design

Whew! That's 14 months in one post! -)

Technorati Tags: .NET, Windows Communication Foundation, , WCF, WF, Windows Workflow, Extreme Programming, Agile, Agile Development, Software Architecture, Microsoft