Download as PDF, PPTX
![Read FileRead File
static void Main(string[] args)
{
StreamReader sr = File.OpenText("MyFile.txt");
string s = sr.ReadLine();
while (s != null)
{
s = sr.ReadLine();
Console.WriteLine(s);
}
}
D](https://image.slidesharecdn.com/framework-engineering-1231175171329646-2/85/Framework-Engineering-Revisited-77-320.jpg)
![static void Main(string[] args)
{
foreach (string s in File.ReadAllLines("MyFiles.text"))
{
Feedback (Read File)Feedback (Read File)
{
Console.WriteLine(s);
}
}
D](https://image.slidesharecdn.com/framework-engineering-1231175171329646-2/85/Framework-Engineering-Revisited-78-320.jpg)
Uploaded byYoungSu Son
Framework Engineering Revisited
Framework defines "semi-complete" applications that embody domain-specific object structures and functionality. Frameworks avoid duplication and increase productivity. They define common loops, databases, math functions and other functionality while allowing for application-specific logic. Frameworks balance stability with allowing incremental improvements through careful management of dependencies between components.
More Related Content
Similar to Framework Engineering Revisited
![[NEXT] Android Profiler μ¬μ©λ²](https://cdn.slidesharecdn.com/ss_thumbnails/day6profiler150810-150811041218-lva1-app6892-thumbnail.jpg?width=640&height=640&fit=bounds)
![[NEXT] Flask λ‘ Restful API μλ² λ§λ€κΈ°](https://cdn.slidesharecdn.com/ss_thumbnails/flask2-141209115126-conversion-gate02-thumbnail.jpg?width=640&height=640&fit=bounds)
Framework Engineering Revisited
- 1.
- 2.
- 3.
- 4. Douglas C. SchmidtSays..Douglas C. Schmidt Says.. FrameworksFrameworks definedefine βsemiβsemi--completeβ applicationcompleteβ application that embody domainthat embody domain--specific object structures and functionality.specific object structures and functionality.
- 5. App SpecificApp Specific LogicLogic EventEvent LoopLoop DATABASEDATABASEADTsADTs MATHMATH NETWORKINGNETWORKING GRAPHICSGRAPHICS GUIGUI SingletonSingleton StrategyStrategy InvocationsInvocations Application BlockApplication Block Libraries is..Libraries is.. Class LibraryClass Library ComponentComponent ArchitectureArchitecture OO DesignOO Design LoopLoop SingletonSingleton StrategyStrategy ReactorReactor AdapterAdapter StateState Active ObjectActive Object SelectionsSelections Design PatternDesign Pattern
- 6. EventEvent ReactorReactor NETWORKINGNETWORKING Active ObjectActive Object GUIGUI StateState AppSpecificApp Specific LogicLogic MATHMATH InvocationsInvocations But Framework is ..But Framework is .. DATABASEDATABASE SingletonSingleton GRAPHICSGRAPHICS AdapterAdapter EventEvent LoopLoop LogicLogic ADTsADTs CallbacksCallbacks ApplicationApplication FrameworkFramework Component ArchitectureComponent Architecture
- 7. Why Do YouNeed Framework?Why Do You Need Framework? Avoid Duplication Productivity
- 8. Welcome toWelcome to MyFrameworkMy FrameworkMy FrameworkMy Framework Journey!Journey!
- 9. βFramework Engineeringβ, TechED2007 Europe βFramework Design Guidelinesβ , Addison Wesley Krzysztof Cwalina Program Manager on .NET Framework Team
- 10.
- 11.
- 12. Project Management TriangleProjectManagement Triangle Scope Cost Time O
- 13. Organization Project Management TriangleProjectManagement Triangle Organization O
- 14. DODO understand howunderstandhow organizational structure,organizational structure, culture, and decision making processesculture, and decision making processes impaimpa ct your product.ct your product. O
- 15. Conway's lawConway's law Ifyou have 4 groups working on a compiler, youβll get a 4-pass compiler. O
- 16.
- 17. Conway's Clean StateApproachConway's Clean State Approach 1 β’ Define the business missionβ’ Define the business mission 2 β’ Learn the business process from business ownersβ’ Learn the business process from business owners 3 β’ Re-engineer these process to fit the missionβ’ Re-engineer these process to fit the mission 4 β’ Structure the IT organization to support the reengine ered business processes. β’ Structure the IT organization to support the reengine ered business processes. O
- 18. Your Company CultureIs ..Your Company Culture Is .. Voluntary ?? O
- 19. Your Company CultureIs ..Your Company Culture Is .. Familial ?? O
- 20.
- 21. Organizational InfluencesOrganizational Influences SizeofOrganizationSizeofOrganization SimpleDesign Consistency Design Small Team Consistency Design Focus on 80/20 Rules O
- 22. Organizational InfluencesOrganizational Influences SizeofOrganizationSizeofOrganization PowerfulDesign Lack Consistency Large Team Lack Consistency Remove Requirements O
- 23.
- 24.
- 25. Decision Making Processis..Decision Making Process is.. O
- 26. Give this bookyour boss..Give this book your boss..
- 27.
- 28.
- 29.
- 30. Peanut ButterPeanut ButterSkyscrapersSkyscrapers Focus: featuresFocus: features Results:Results: stability,stability, incrementalincremental improvements, notimprovements, not greatgreat endend--toto--endend scenariosscenarios Focus: scenariosFocus: scenarios Results:Results: Excitement,Excitement, breakthroughs, butbreakthroughs, but beware of leavingbeware of leaving existing customersexisting customers behindbehind P
- 31. MModeration (oderation (δΈεΊΈδΈεΊΈ)) MileStone=Scenarios+FeatureMileStone =Scenarios+Feature Planning M1 M2 Release Testing Feature completeVision statement RTM Planning M1 M2 Testing Technology Preview Beta 1 Beta 2 RC1 P
- 32.
- 33. Right Way??Right Way?? CChooseright types.hoose right types. A
- 34. Taxonomy ofTaxonomy ofTypesTypes LibrariesLibraries,Primitives,Abstractions,Primitives,Abstractions A
- 35. PrimitivesPrimitives Very little policy(behavior design decisions) Stable design Commonly appear in publicly accessible APIs Almost impossible to evolve/change design; any design changes have huge breaking change impact on other APIs Example: Int32, String A
- 36. Definition: Libraries are typesthat are not passed between com ponents Examples EventLog, Debug, LibrariesLibraries EventLog, Debug, Easy to Evolve Leave old in, add new one Beware of duplication! A
- 37. AbstractionsAbstractions Definition: Abstractions are interfacesor classes with unsealed member s that are passed between components. Examples Stream, IComponent Hard to EvolveHard to Evolve Unfortunately, pressure to evolve A
- 38. Primitive Oriented DesignPrimitiveOriented Design A.K.A. βHandle based designβ (functional) Great evolvability, poor usability (sometimes) Low level stable primitives + high level reusable components with limited dep endencies other than to the primitives E.g. Type.GetType(object) β works, but not as convenient as Object.GetType A
- 39. for primitive..for primitive.. C#3.0NewFeatureC#3.0NewFeature namespaceMyCompany.StringManipulation { public static class StringExtensions{ public static bool IsNullOrEmpty(this string s){ return String.IsNullOrEmpty(s); } }} } β¦ using MyCompany.StringManipulation; string message= βhello worldβ; if(message.IsNullOrEmpty()){ Console.WriteLine(βEMPTYβ); }
- 40. Component Oriented DesignComponentOriented Design Rich APIs with lots of features, thus with lots of dependencies Great usability, poor evolvability Good for higher level components, not for the core of a platformGood for higher level components, not for the core of a platform A
- 41. A DODO Manage Dependencies..ManageDependencies.. A
- 42. Component is .. A Lego,Plug ??
- 43. A .. a setof types that ship and evolve as a unit.
- 44.
- 45. APIDependencyAPIDependency Component A hasan API dependency on component B, if a type in B shows in the publicly accessible API surface of a type in A. This includes: Base types and implemented interfaces Generic parameter constraints Return types and parameters of members Applied attributes Nested types A
- 46. ImplemenatinDependencyImplemenatinDependency If a typein A uses a type in B in its implementation. Hard Dependencies (required to run) Soft Dependencies (optional) A
- 47. CircularDependencyCircularDependency Component A dependson component B and Component B depends on component A (even indirectly). A
- 48.
- 49. Solution is Layering..Solutionis Layering.. A
- 50. xDepend (NxDepend (NDDepend)epend) NDepend- http://www.ndepend.com
- 51.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58. Heavy Dependency.Heavy Dependency. //your API public class Tracer { MessageQueue mq = new MessageQueue(β¦); public void Trace(string message){ mq.Send(message); } } // your customerβs program that is hard to test Tracer tracer = new Tracer(); public void ProcessOrder(Order order){ tracer.Trace(order.Id); β¦ } A
- 59. Inversionof ControlInversionof Control //your better API public abstract class TraceListener { public abstract void Trace(string message); } public class Tracer { TraceListener listener; public Tracer(TraceListener listener){ this.listener = listener; } public void Trace(string message){ listener.Trace(message); } } A
- 60. Dependency InjectionDependency Injection //your customerβs program that is easier to test Tracer tracer = new Tracer(new FileListener()); public void ProcessOrder(Order order){ tracer.Trace(order.Id); β¦ } A
- 61. // customerβs programthat is even easier to test Tracer tracer = container.Resolve<Tracer>(); public void ProcessOrder(Order order){ tracer.Trace(order.Id); β¦ } Check out DI Containers (a.k.a. IoC Containers): autofac, Castle Windsor, PicoContainer.NET, Spring.NET, StructureMap, Unity, nInject and others. http://www.nInject.org A
- 62. PackagingPrinciplePackagingPrinciple Package Cohesion Principle REP(Release Reuse Equivalency) CCP (Common Closure Principle) CRP (Common Reuse Principle) Package Coupling PrinciplePackage Coupling Principle ADP (Acyclic Dependencies Principle) SDP (Stable Dependencies Principle) SAP (Stable Abstraction Principle) ARobert C. Martin, Principle of Package Architecture http://www.objectmentor.com/resources/articles/Principles_and_Patterns.pdf
- 63. DO balance advanceswith compatibility. A
- 64. Types of βCompatibilityβTypesof βCompatibilityβ BackwardBackward A CrossCross--VersionVersion ForwardForward
- 65.
- 66.
- 67. Define whatβs aβbreaking changeβ This definition depends on the objective E.g. Enable portable code between Silverlight and . NET FrameworkNET Framework E.g. Enable cross-version portability? A
- 68. AVOID duplication andoverlap. A
- 69. TeamTeam SpaceSpace Showand TellShow and Tell A PLoP β Capable, Productive and Satisfied Patterns for Productivity http://hillside.net/plop/plop98/final_submissions/P54.pdf ProblemProblem SpaceSpace
- 70. When the newtechnology is β10x betterβ Make sure you understand the impact on the ecosystem What would happen if the BCL team added a new String? Whatβs the migration path for code using the old API? Support Automatic Migration Tool. (VB -> VB.NET, .NET 1.0 -> .NET 2.0) Provide Code Based Migration Manual. COM+ -> WCF , ASP.NET Web Service -> WCF A KC1
- 71. μ¬λΌμ΄λ 70 KC1 Thisslide needs major work Krzysztof Cwalina, 2007-10-19
- 72.
- 73. Is using yourframework correctly likeβ¦Is using your framework correctly likeβ¦ Running across a desert?Running across a desert? D
- 74.
- 75. DO design APIsby first writing code samples for the main scenarios and then defining the object model to support the code samples. D
- 76.
- 77. Read FileRead File staticvoid Main(string[] args) { StreamReader sr = File.OpenText("MyFile.txt"); string s = sr.ReadLine(); while (s != null) { s = sr.ReadLine(); Console.WriteLine(s); } } D
- 78. static void Main(string[]args) { foreach (string s in File.ReadAllLines("MyFiles.text")) { Feedback (Read File)Feedback (Read File) { Console.WriteLine(s); } } D
- 79. Object Model ListingObjectModel Listing D
- 80. Framework Design StudioFrameworkDesign Studio Assembly ExploerAssembly Exploer Project -> Add -> Assembly Download here - http://code.msdn.microsoft.com/fds D
- 81. Framework Design StudioFrameworkDesign Studio Assembly ReviewCommentAssembly ReviewComment D
- 82. Framework Design StudioFrameworkDesign Studio CompareAPIVersionsCompareAPIVersions D
- 83. Framework Design StudioFrameworkDesign Studio CompareAPIVersionsCompareAPIVersions Red is removed, Green is added, Grey means inherited.Grey means inherited. D
- 84. Framework Design StudioFrameworkDesign Studio Exporting toMicrosoft WordExporting toMicrosoft Word Tools -> Export to Document D
- 85. DO treat simplicityas a feature. D
- 86. Remove Requirements (ATAM). ReuseExisting Concepts or APIs Adjust Abstraction Level Consider framework users(experience, knowledge) Three Example D
- 87. DO measure, measure,and measure! D
- 88. Specification Document: QualitiesSpecificationDocument: Qualities Performance Goals (XML Parser..) Baseline: What do is the best my API could do? Measure delta from the baseline Threat Models (Security ..) Threat: What is the worst that my component couldThreat: What is the worst that my component could do? Mitigate the threats Keep a balance between many other qualities you want your framework to have (ATAM) D
- 89. THE POWER OFSAMENESS D
- 90. When you pickup your rental carβ¦.When you pick up your rental carβ¦. Push the seat all the way back Find an NPR station Find the exit Read the manual??Read the manual?? D
- 91. Oh, down tolockβ¦Oh, down to lockβ¦ D
- 92. How to usea keyβ¦How to use a keyβ¦ D
- 93. Oh, youOh, youpushpush the PRESS buttonβ¦the PRESS buttonβ¦ D
- 94. Who actuallyWho actually needsneedsthis data?this data? D
- 95. You know howto drive your car All cars work basically the same way Your rental car is a car Therefore, you can drive your rental carTherefore, you can drive your rental car That is⦠D
- 96.
- 97.
- 98. Branches and IntegrationsBranchesand Integrations --FeatureCrewFeatureCrew MainMain PU-stagingPU-staging PU-stagingPU-staging PU-stagingPU-staging V PU-staging Branch PU-staging Branch Feature Branch Feature Branch Feature Branch Feature Branch PU-staging Branch PU-staging Branch PU-staging Branch PU-staging Branch http://www.codeplex.com/BranchingGuidance/Wiki/View.aspx?title=Feature%20Crews%3a% 20How%20Microsoft%20Does%20It
- 99. AVOID integrating unfinishedfeatures. V
- 100. Functional Specification Developer DesignSpecification Test Plan Threat Model API review Architectural ReviewArchitectural Review Dependency Management Static Analysis Code Coverage Testing (Unit and Integration Tests) 0 Bugs Performance V
- 101. DO pay yourdebt. V
- 102. Planning M1 M2 Release Testing FeaturecompleteVision statement RTM Technology Preview Beta 1 Beta 2 RC1 Milestone Quality V
- 103. Milestone Quality (MQ)MilestoneQuality (MQ) Initiatives that are hard to do in regular milestones Large productivity and efficiency improvements Infrastructure changes For example, a new source control system Refactoring of fragile subsystemsRefactoring of fragile subsystems Internal implementation documentation Bugs backlog V
- 104. DO understand howorganizational structure, culture, and decision making proc esses impact your product. AVOID peanut-butter in Scenario Based Application. DO manage your dependencies. DO balance advances with compatibility. AVOID duplication and overlap. DO design APIs by first writing code samples for the main scenarios and then dDO design APIs by first writing code samples for the main scenarios and then d efining the object model to support the code samples. DO treat simplicity as a feature. DO measure, measure, and measure! AVOID integrating unfinished features. DO pay your debt.
- 105. Krzysztof Cwalina, BradAbramsKrzysztof Cwalina, Brad Abrams Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries http://channel9.msdn.com/pdc2008/PC58/ http://www.gotdotnet.com/team/fxcop
- 106. Douglas C. Schmidt(PLoP Editor, POSA 2, 4 Writter) JAWS: An Application Framework for High Performance Web System http://citeseer.ist.psu.edu/81775.html (En) http://www.devpia.com/net2/EvaCast/Lecture/?cu=view&r=11 (Kr) Ralph Johnson (GoF , Design Patterns) Evolving Frameworks http://st-www.cs.uiuc.edu/users/droberts/evolve.html (En) http://arload.wordpress.com/2008/09/15/evolvingframeworks/ (Kr)
- 107. Robert C. Martin Principlesof Package Architecture (Design Principles and Design Patterns) http://www.objectmentor.com/resources/articles/Principles_and_Pattern s.pdf (En) http://www.devpia.com/net2/EvaCast/Lecture/?cu=view&r=108 (Kr) For Korean People.. Load to Architect http://www.arload.net EvaCast (Online Free Lecture) http://www.evacast.net
- 108. μ΄ μ μλ¬Όμ ν¬λ¦¬μμ΄ν°λΈμ»€λ¨Όμ¦ μ½λ¦¬μ μ μμνμ-λΉμ리-λμΌμ‘°κ±΄λ³κ²½νλ½ 2.0 λνλ―Όκ΅ λΌμ΄μΌμ€μ λ°λΌ μ΄μ©νμ€ μ μμ΅λλ€. This work is licensed under Creative Commons Korea Attribution 2.0 License.