B Fn As
Download as PPT, PDF3 likes678 views
- The document discusses challenges in building application frameworks and applications simultaneously. It argues that the framework must be built in parallel with the applications that will use it. - It presents patterns for developing frameworks and applications together, including starting with pilot applications to help define the framework's abstractions, and evolving the framework based on feedback from application developers. - Metrics like the "Rule of Three" and "Budget Factor 2.5" are introduced to help scope the framework and schedule its development.
![[email_address] http://funkcode.tistory.com - Thank you for your attention](https://image.slidesharecdn.com/bfnas-1228213336699019-8/85/B-Fn-As-47-320.jpg)
B Fn As
- 1. Applications Simultaneously - 프레임웍과 어플리케이션 동시에 구축하기 Ko sang won funkcode@gmail.com / funkcode.tistory.com High Performance Computing and Object Technology Lab. Hanyang University
- 2. http://hillside.net/conferences/plop.htm : Pattern Languages of Programs “ Building Frameworks and Applications Simultaneously” - Andreas Ruping ’’
- 3. Why make the Framework ? App App App Framework
- 4. TEAM B Application TEAM A Application TEAM C Application Framework ? Framework ? Framework ?
- 5. Application Framework I’m sorry I am late … roblem The Framework must be built in parallel to applications that are going to use it
- 6. Overview of the Pattern Language A Pattern Language helps the framework developer uggestion
- 7. unning Example A German insurance company A large number of old legacy applications To build
- 9. The interface to the application program To manage the versioning of logical entities To store and retrieve objects in database
- 12. Application don’t yet exist - Competing interests ‘ Rule of Three’ A first version of the framework
- 13. A framelet is a small framework that defines an abstract architecture To keep the framework simple, focus on a small number of core concepts. Avoid too much abstraction. Three expected uses is a must, even for a small framework
- 14. Requirement Requirement Requirement Restrict the mapping of logical entities onto physical tables Only simple mappings are possible
- 15. “ THREE EXAMPLES” - Evolving frameworks “ TWO PILOT APPLICATIONS” “ BUDGET FACTOR 2.5”
- 18. Finding the right abstractions isn’t easy The framework team offer coaching
- 19. = 30 person months 12 person months x 2.5 5 people (2 people - full time) Maintaining the just released version Preparing a new version coaching delay
- 20. “ SIZE THE ORGANISATION” “ SIZE THE SCHEDULE” - A Generative Development-Process Pattern Language “ RULE OF THREE” and “BUDGET FACTOR 2.5” framework development = 2.5 * application development 3 * application development = framework development + 3 * framework instantiation framework instantiation = 1/6 * application development
- 22. Some functionality, but use it in different ways . There is a common abstraction None of these applications have been built so far Have to find the right abstractions for your framework
- 23. The pilot applications must be fairly typical should be rather important must be applications that being built early
- 24. The health insurance system is a very typical one “ Two-dimensional versioning”
- 25. “ USER INVOLVEMENT” Collaborating with the pilot users The importance of feedback from users “ ENGAGE CUSTOMERS” - A Generative Development-Process Pattern Language “ IT’S A RELATIONSHIP NOT A SALE” - Customer Interaction Patterns “ TESTS BASED ON PILOT APPLICATIONS”
- 27. A Framework with a relatively is more easily understood A smaller number of more powerful functions A larger number of less powerful functions ?
- 28. The functions the framework offers will be better understood Smaller functions have a better chance of meeting the user’s needs A larger number of smaller, somewhat atomic, functions allow for more combinations
- 29. The data access layer keeps track of which objects have been changed A session applications can commit all or some of changes to the database Two functions : Lists all changed objects Saves individual object to the database
- 30. “ FINE-GRAINED OBJECTS” - Evolving frameworks The risk of architectural mismatch
- 32. Application Developer ? Framework
- 33. Run common workshops Provide tools and demonstrate how to use these tools Offer tests of how an application and your framework collaborate Show the users how to optimize the applications Make tutorials and documentation
- 34. A two-week workshop together with the health insurance system team Learned that the commission system had special efficiency requirement Provided a script that generates a concrete access layer from application’s meta information
- 35. “ TWO PILOT APPLICATIONS” “ BUILD TRUST” - Customer Interaction Patterns “ BUDGET FACTOR 2.5”
- 37. Your framework is a framelet , - cannot be tested alone Test case coverage is much harder to achieve Can be difficult to find realistic test scenarios Framework Need applications that use the framework to act as test drivers
- 38. Indentify core components from the pilot applications, and use these components as test drivers Find typical use cases from pilot applications and maintain them as a test suite Shape these test cases into regression tests Have to include some exotic scenarios Need test cases that test the time performance and stability
- 39. The health insurance system The party system Two pilot systems
- 40. “ TWO PILOT APPLICATIONS” “ USER INVOLVEMENT”
- 42. Application Development Teams Framework Development Team “ I have to keep the framework simple ”
- 43. Be active Allow users of the framework to add application-specific functions
- 44. The printing system The workflow system An additional function Several requests for extending the two-dimensional
- 45. “ FRAMELETS FOR MULTIPLE USE” ..at least three times
- 47. [email_address] http://funkcode.tistory.com - Thank you for your attention