Anatomy Of An Agile .Net Project
Download as PPTX, PDF0 likes611 views
The document outlines the anatomy of an Agile .NET project, emphasizing modern design principles such as solid architecture and onion architecture, alongside the development process that incorporates test-driven design and continuous integration. It discusses various layers of architecture, dependency management, and emphasizes the importance of project structure and continuous deployment. The author, Fredrik Kalseth, also highlights tools and methods used throughout the project lifecycle, concluding with the significance of monitoring and constant improvement.
Anatomy Of An Agile .Net Project
- 1. ANATOMY OF ANAGILE .NET PROJECTBy Fredrik Kalseth,Senior Consultant at Capgemini in StavangerTHIS IS NOT A BIOLOGY LESSON.
- 2. CASE STUDYDevin Exposé, a Content Managment System
- 4. ONION ARCHITECTUREA modern approach to n-tier architecture.
- 5. ClientUser interface LayerORMTest FixtureDTO / ViewModelMessage/EventASP.NET, ASP.NET MVC, WPF...Anti Corruption LayerApplication ServicesDomain ServicesDomain ModelDirection of Flow (DIP)nHibernate, LLBLGEN, Linq To Sql, XPO... Application CoreDatabaseContinous Integration ServerTestsInfrastructureMessage BusExternal SystemsTFS, Team City, Cruise Control... NServiceBus, MassTransit, proprietary...
- 6. MediaItemVMUploadMediaItemViewUser interface LayerMediaItemControllerMediaItemUploaderApplication ServicesDomain ServicesIRepository<T>Domain ModelMediaItemIUnitOfWorkMediaItemTagIMediaStorageApplication CoreMediaStorageLinqToSqlRepository<T>DataContextTestsInfrastructureWhen_uploading_MediaItem
- 7. DEPENDENCY MANAGEMENTFollow the Dependency Inversion Principle.Manage dependencies using an IoC framework.
- 8. OBJECT/RELATIONAL MAPPINGRows in a database are just data. Objects are data (state) + behavior.
- 10. TEST DRIVEN DESIGNDrive the implementation of important/complex use cases through unit and integration tests.
- 11. PROJECT STRUCTUREFew projects = faster builds.Separate assemblies != loose coupling!
- 12. BRANCH BY FEATURESeparate concerns. Merge continously.
- 13. F14 BranchF12 BranchTrunkF13 BranchF15 BranchFeature branchMerge from trunkMerge from other branch
- 14. CONTINUOUS INTEGRATIONMerge frequently. Build merged code frequently. Test built code frequently.
- 16. DEMONSTRATIONFixing a bug the agile way.
- 18. DISTRIBUTED SOURCE CONTROLSource control everywhere.
- 19. AUTOTESTINGContinously running tests in the background.
- 20. CONTINOUS DEPLOYMENT“On average we deploy new code fifty times a day.” - Timothy Fitz, IMVU
- 21. PROJECT MONITORINGSmeedee, an open source project monitor.
- 22. Read my bloghttp://iridescence.noFollow me on Twitterhttp://twitter.com/fkalsethTHANK YOUSTUNNED SILENCE. APPLAUSE?FOR STAYING AWAKE!Fredrik Kalseth,Senior Consultant at Capgemini in Stavanger
Editor's Notes
- #6: Emphasizes use of interfaces for behavior contractsExternalization of infrastructureDomain model – state and behaviorDomain services – typically interfaces for repositories etc.Application services – orchestrate the finer grained domain services. Concerns such as transactionality and persistence are typically dealt with by application services. ”Task services”Outer layer reserved for things that change often. UI, implementations of infrastructure stuff (Repository) etc.
- #14: http://www.lostechies.com/blogs/derickbailey/archive/2009/07/21/branch-per-feature-source-control-part-2-how-theory.aspx
- #21: http://timothyfitz.wordpress.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/
- #22: Capgemini’s Smeedee Open source project monitor: http://www.smeedee.org