Smart Client Software Factory 2010
Download as PPTX, PDF0 likes1,465 views
This document provides an overview and guidance on the Smart Client Software Factory 2010 framework. It discusses how SCSF takes advantage of Microsoft Enterprise Library and Composite UI Application Block to generate application frameworks using a software factory model. This allows for rapid and standardized application development while focusing on business logic. The framework promotes extensible, modular, and loosely coupled architecture. It also outlines the application layering approach and common architecture patterns used. Finally, it describes the development activities and roles including architects, business analysts, developers, and designers.
More Related Content
What's hot (20)
Viewers also liked (11)
Similar to Smart Client Software Factory 2010 (20)
Smart Client Software Factory 2010
- 1. Smart Client Software Factory 2010A Brief Development Guidance -Western Digital #tomysmile – 05 Aug 2010
- 3. OverviewSCSF takes advantage of the Microsoft Enterprise Library 2.0 and Composite UI Application Block, using a software factory model to generate the application frameworkRapid and standardized application development, allowing developers to generate core application frameworks and focus on building the business logicEnd result is an extensible, extendable, modular, maintainable and loosely couple architecture application
- 5. Application Layering cont.Presentation – outer layer, exchangeableBusinessServicesRulesData AccessModulesInfrastructure
- 7. Architecture Patterns cont.Presentation PatternDependency Injection / Object BuilderObserver PatternComposite and ModularityCommanding Pattern……
- 9. Development Activities cont.Architects approachBusiness analyst approachDeveloper approachDesigner approach
- 10. Development Activities cont. – Business Analyst ApproachData Access LayerThis layer concern only for database activity (CRUD), no business validation or caching or else.Create DAL for each database activityLookupDAL, AllocationDAL, BuildRequestDALBusiness Analyst will need to work closely with database dev / admin and define the output of the result. Business Rules LayerThe main concern of this layer is to provide business specific rules and validation. Rules must be exchangeable and configurable.Create Rules as specific and clear as it can in this layer, if no rules required then just passed it on to the upper layer (DAL)DataLookupRule, AllocationRule, BuildRequestRule
- 11. Development Activities cont. – Business Analyst ApproachService LayerThe main concern of this layer is to be the application data End Point and all the data related activities must be through this layer in order to maintain the standard and maintainability.Service can be passed to the Business Rule layer or accessing a Web / WCF ServicesService must be exchangeable, testable and mock able, so always use interface based programming in this layerThis layer is perfect for caching feature because all the data will need to be retrieve or pass from this layer.Eg: DataLookupService, AllocationService
- 12. Development Activities cont. – Business Analyst ApproachPresentation LayerThis is the most outer layer that presents the data looks and feelThe SCSF use MVP and MVC for the presentation, so it can be extend and exchange either use Web-based, Windows Form-based, WPF-based even Silverlight without having to change the whole codes and project structures.Contain 3 sub layer :Model – represent the data source ( service layer )View – this is the display that user can seePresenter / Controller – the hub between data source and the viewView layer must be dumb enough so it can be replace by Windows Form, Web Form, WPF or Silverlight
- 13. Development Activities cont – Developer ApproachThe reverse of the Business analyst approach
- 14. Development Activities cont. – The FlowInterface usually prefix with char ‘I’InterfaceConcreteInterfaceConcretePresenterView
- 15. Development Activities cont. – The FlowView Interface (IMainView)View PresenterView / User ControlService InterfaceInfrastructure.InterfaceInfrastructure.ModuleCache FeatureException Handling (Opt)Service ConcreteBusiness InterfaceBusiness ConcreteDAL / RepositoryDatabase
- 16. Development Activities cont. - ConfigurationApplication Configapp.configappSettings.configappConnectionStrings.configModules ConfigProfileCatalog.xmlMessaging ConfigMessages.xml
- 17. Thank You