object oriented, mvc, software factory dan lightswitch

1. object oriented, mvc, software factory dan lightswitch

2. Object Oriented VS Pemrograman Terstruktur • Kelebihan Object Oriented • Code Reuse • Mudah Perawatan & Pengembangan untuk Sistem yang besar Object oriented

3. Abstraksi Enkapsulasi Inheritance Message Polymorphisme Prinsip object oriented

4. Identifikasi Class & Object Identifikasi Struktur : gen-spec, whole-part Identifikasi Atribut Identifikasi Method/Service Langkah-langkah ooa

5. use case diagram class diagram statechart diagram activity diagram sequence diagram collaboration diagram component diagram deployment diagram Unified modelling language

6. Asosiasi Aggregasi Komposisi Generalisasi Spesialisasi Class relationship Abstract Class, Polymorphisme, dan Interface

7. Jenis MVC pada website • Server Side MVC • Mixed Client Side and Server Side MVC • Mixed MVC 1 • Mixed MVC 2 • Rich Internet Application MVC Model, view, controller

8. Mvc vs mvp ( model, view, presenter ) MVC

9. MVP

10. Loose coupling Clear separation of concerns/responsibility Individual Test Driven Code Reuse Flexibility/Adaptable Parallel Development Keuntungan model mvc & mvp

11. MVP Pattern • View is more loosely coupled to the model • Easier to unit test • Usually view to presenter map one to one • MVC Pattern • Controller are based on behaviors and can be shared across views • Can be responsible for determining which view to display (Front Controller Pattern) Perbedaan utama mvc & mvp

12. Separation of application tasks by default • An extensible and pluggable framework • also supports the use of Dependency Injection (DI) and Inversion of Control (IOC) container models • A powerful URL-mapping component • Support for existing ASP.NET features Fitur ASP.NET MVC

13. The front controller itself is usually implemented in two parts: a handler and a hierarchy of commands Front controller

14. Front controller The handler has two responsibilities : · Retrieve parameters · Select commands Representing commands as individual objects allows the controller to interact with all commands. After the command object completes the action, the command chooses which view to use to render the page • Kelebihan • - Centralize the logic to reduce the amount of code duplication • - The retrieval of data is also best handled in one location • avoid the issues of thread safety in the command classes • Only one front controller needs to be configured

15. the handler should be examined closely for performance problems Increased complexity Pertimbangan mengenai front controller

16. A software factory may include processes, templates, IDE configurations and views • Microsoft is developing four software factories: • Smart Client Software Factory, for Visual Studio 2008 (released: April 2008) • Web Service Software Factory (released: July 2006) • Mobile Client Software Factory (released: July 2006) • Web Client Software Factory (released: January 2007) Software factory

17. Two parts to the methodology, one part for factory authors and another part for factory users the methodology starts by identifying and classifying architectural styles for frequently encountered families of solutions, such as web portals, smart clients and connected systems Software factories describe processes that span part or all of the solution life cycle Software Factories supply reusable assets to help users enact the processes. Assets : documents, such as patterns, guidelines and check lists, some are tools, such as designers, wizards, and scripts, some are assets used by tools, such as templates, models and configuration files, and some are executables, such as libraries, frameworks and sample code The assets are delivered in a structured and installable package called a software factory template A key feature of the methodology is that the products of two or more factories can be composed Software factory

18. Software factory schema It describes the assets that comprise the factory, how they are packaged, and how they are installed, customized and applied

19. Software factory

20. reduction in cost and time to market significant improvements in quality greater consistency from solution to solution Reduce the Risk easier to accurately forecast budget, schedule, and resource requirements Easier to analyze the impact of new requirements Reduce the time and cost of training new developers benefits

21. Benefits • QUICKLY CREATE PROFESSIONAL-QUALITY BUSINESS APPLICATIONS • pre-configured screen templates • prewritten code • including changing themes, templates, adding custom validation, providing smart data types, and deploying to Windows Azure • an application can be designed, built, tested, and in your user's hands quickly • EASILY ACCESS EXISTING SYSTEMS AND DATA • Integrated with Ms. Office • BUILD FOR TODAY, PREPARE FOR TOMORROW • your application can grow to meet the increasing demands of popular applications using the Microsoft Windows Azure Cloud Hosting option Visual studio lightswitch

22. More Benefits • In most cases, you can even switch from a browser application to a desktop application and back again by changing a single setting and redeploying • search capabilities, the ability to sort and rearrange grids, and the ability to export data are already built in • adding, updating, saving, and deleting are also built in • You just set some validation properties or write some simple validation code based on your business rules, and its done • LightSwitch provides authentication and authorization features that let you define users and roles • You can create relationships even between entities from different data sources Visual studio lightswitch