This is the final post in this series, and for a complete reference, here are the previous parts:

• Part 1 was a general introduction
• Part 2 outlined the architecture (tiers, etc)
• Part 3 showed the benefit of loosely coupled tiers (distribution, cloud, etc)
• Part 4 started the implementation by creating the entity data model (using ADO.NET Entity Framework)
• Part 5 published the entity data model as a data service (using ADO.NET Data Services)
• Part 6 implemented the business domain (using the data service)
• Part 7 created the service (using WCF)
• Part 8 started the implementation of the mobile client (using WCF)
• Part 9 added offline support to the mobile client (using SQL Server Compact, etc)

The implemented architecture is published on CodePlex in a project called KISS Architecture, and this means that you can access the full source code as well as discuss it, come with suggested improvements, etc.

On the upper right you see the UX of the sample client included in the architecture sample, and the functionality is that a part of a city name can be entered in the text box, and when the "Get" menu item is selected, the grid is filled with the matching customers.

Even if this series is complete, I will continue to build further on this architecture blueprint, and any suggestions on things to add are most welcome. Any other feedback, for that matter, is also welcome!