SharePoint Solution Architecture (having ALM in mind)

1. SharePoint Solution Architecture(having ALM in mind) Adis Jugo managing consultant

2. Corporate Profile • 60+ highly skilled, Microsoft certified experts • Microsoft Gold Partner: • Information Worker Solutions • Business Intelligence • Data Management Solutions, • Advanced Infrastructure Solutions • Premier MCS partner • Locations: Aalen, Munich, Cologne, Sofia

3. Perception of SharePoint applications

4. Impact BUILD TO CHANGE, INSTEAD OF BUILDING TO LAST

5. Requirements

6. Time and Costs estimation

7. Time and Costs estimation

8. The development curve • Initial platform • Security and permissions • Administration interface • Scaling and clustering

9. Architecture

10. Architecting SharePoint solutions

11. What is wrong with this web part?

12. A SharePoint Solution

13. 4 questionsforarchitects • How will the users be using the application? • How will the application be deployed into production and managed? • What are the quality attribute requirements for the application (security, performance, concurrency, localization, and configuration) • How can the application be designed to be flexible and maintainable over time?

15. Demo 1: Practical architecture

16. Solution Architecture: InPage / MVP Model

17. Localization / Internationalization

18. Other architecture considerations Architecture documentation Standard Design Patterns Avoid 3rd Party libraries Solution Technical Documentation

19. Development

20. 5 golden rules in development Follow the architecture Coding conventions (Microsoft) Define standard core libraries – own or SPG Use standard VS 2010 templates Follow the SharePoint rules of game

21. Testing & QA

22. Unit Testing – The First Line of defense No Unit Testing is Possible with SharePoint…?

23. Unit Testing – The First Line of defense …or maybe it is. nUnit Framework Microsoft Patterns and Practices: Pex & Moles

24. Demo 2: Testing with nUnit Framework

25. Deployment

26. 4 Deployment considerations to keep in mind What is to be deployed When is to be deployed Where do we deploy How is the configuration performed

27. Requirements (Change!)

28. Demo 3: New Frontiers

29. And finally

30. ShareDove Architecture Project http://sharedove.codeplex.com

31. Resources • Time and Costs estimation templatehttp://adis.jugo.ba/download/blogimg/2011/1sug_juli2011/TimeCostsEstimation_Example.xlsx • MS P&P: SharePoint Guidehttp://spg.codeplex.com • MVP pattern in SharePoint InPage elements (WebParts, ASPX)http://msdn.microsoft.com/en-us/library/ee413740.aspx • Coding Conventions Examplehttp://blogs.msdn.com/b/brada/archive/2005/01/26/361363.aspx • SharePoint best practiceshttp://msdn.microsoft.com/en-US/sharepoint/ff660756.aspx • Pex and Moles Frameworkhttp://research.microsoft.com/en-us/projects/pex/downloads.aspx • Asterixand Cleopatrahttp://www.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Daps&field-keywords=asterix+and+cleopatra&x=0&y=0 http://www.plan-b-gmbh.com

32. http://www.plan-b-gmbh.com http://www.adisjugo.com @adisjugo