1. Alcatel-Lucent CDC Workshop, Coaching & Knowledge Transfer Architecture

2. Layered Architecture

3.  Multi layered application  Logical separation

4. Layered Architecture  Multi tiered application  Physical separation

5. Presentation Layer  ASP.NET 3.5 with AjaxToolkit  Model – View – Controller  Model:  System data  Business logic (through the service layer)  View:  Displays data to the user  Asks for input  Controller:  Client side logic  Generates requests, and handles responses using the Dispatcher

6. Service Layer  Distributable  Reusable  Exposes business logic to clients  Using Windows Communication Foundation  Other communication frameworks are possible as well

7. Service Layer Components  Request Processor  Processes all requests, calls specific handlers and returns results  Request Handler  Handles requests, calls actions and/or validators in the business layer and returns a response

8. Business Layer  Business Action  Perform some specific business logic  Validator  Validates input  Calls the repositories to get / persist data  Converts the full blown entities to flat Data Transfer Objects

9. Data Access Layer  Repositories  Single access point to the database  Entity Framework for Object Relational Mapping  Tables are mapped  Difficult database interaction using mapping Stored Procedures  Returns full blown entities

10. Entity Framework  ORM from Microsoft  Layer on top of ADO.NET  Generated model  Full blow entity model  Easy extendable:  Partial classes  Extension methods

11. Technology

12. ASP.NET  ASP.NET used for front end  Ajax used for interactive web pages  Only default ASP.NET controls and custom controls  No 3rd party

13. C#  All code written in C# 3.5 SP1  Project done with Visual Studio 2008

14. WCF  Windows Communication Foundation for service communication  Used HTTP binding

15. Core Ideas

16. Level Of Abstraction  Enables Loosely Coupled code  Communicating through interfaces or base classes makes it possible to modify behavior without changing client code.  Increases testability  Enables Dynamic Aspect Oriented Programming

17. Separation Of Concerns  Each class does one thing, and only one thing  A class should have only one reason to change  Behavior should overlap as little as possible

18. Hands On!

19. Contact Item Solutions Plantin en Moretuslei 155 2140 Borgerhout  +32 3 236 64 03  info@itemsolutions.com Speaker Kristof Rennen  kristof.rennen@itemsolutions.com