M70-519 Pro Designing and Developing Web Applications Using ...

M70-519: Pro: Designing and Developing Web Applications Using Microsoft .NET Framework 4 Miles cursusprijs: Miles Cursusduur: Doorlooptijd:

€ 1.495,00 3 klassikale lesdagen, cursus is zelf ontwikkeld door @The Academy 3 weken; een klassikale lesdag per week

Samenvatting Voor deze training bestaat geen officieel Microsoft cursusmateriaal. De training is door @The Academy zelf ontwikkeld. Voor de basis is gebruik gemaakt van materiaal van de 5-daagse cursus Analysing Requirements and defining Microsoft .NET Solution Architectures aangevuld met materiaal uit de Microsoft Application Architecture Guide 2nd Edition. M70-519 is een "Blended" cursus van in totaal 3 dagen klassikale training en zelfstudie. De klassikale lesdagen worden gescheiden gegeven. In de eerste, tweede en derde week is er een klassikale lesdag en in de tussenliggende tijd bestudeert de cursist een gedeelte van de stof aan de hand van de studieplanner. De cursist krijgt de beschikking over MOC cursusmateriaal, een naslagwerk, een proefexamen en een studieplanner. Voorts is aan de cursus een casus toegevoegd. In de klassikale dagen worden de complexere onderwerpen behandeld en ligt de nadruk op oefeningen. M70-519 leidt op voor het Microsoft MCPD Exam 70–519: Pro: Designing and Developing Web Applications Using Microsoft .NET Framework 4

Short Description Audience Profile Candidates are typically Job Role Professionals who design and develop Web applications by using Microsoft Visual Studio 2010 and .NET Framework 4. These professional developers should have a minimum of three years of experience using Microsoft ASP.NET technologies to develop compelling user experiences. Candidates should be able to demonstrate the following by using .NET Framework:  Experience designing and developing modern Web user experiences by using such technologies as AJAX and jQuery  Experience consuming business and data services such as REST, WS-*, Windows Communications Foundation (WCF), and Microsoft ADO.NET Data Services  Experience with the full software development life cycle  In addition, candidates should have a solid understanding of:  Web application architectures such as ASP.NET MVC and Web Form  State management for Web applications by using ASP.NET Inclusief extra studiemateriaal      

MOC workbook Naslagwerk Exampreparation: proefexamen en vaag/antwoord syllabus (Royal Pack) Klassikale Casus Studieplanner Coaching (alleen mogelijk indien examen bij @The Academy wordt afgenomen en/of geadministreerd)

www.the-academy.nl

Doelgroep Candidates are typically Job Role Professionals who design and develop Web applications by using Microsoft Visual Studio 2010 and .NET Framework 4. These professional developers should have a minimum of three years of experience using Microsoft ASP.NET technologies to develop compelling user experiences. Candidates should be able to demonstrate the following by using .NET Framework:  Experience designing and developing modern Web user experiences by using such technologies as AJAX and jQuery  Experience consuming business and data services such as REST, WS-*, Windows Communications Foundation (WCF), and Microsoft ADO.NET Data Services  Experience with the full software development life cycle  In addition, candidates should have a solid understanding of:  Web application architectures such as ASP.NET MVC and Web Form  State management for Web applications by using ASP.NET Voorkennis         

M70-513: TS: Developing Windows Communication Foundation Solutions with Microsoft Visual Studio 2010 M70-515: TS: Developing Web Applications with Microsoft Visual Studio 2010 M70-516: TS: Developing Data Access Solutions with Microsoft Visual Studio 2010 Experience designing and developing modern Web user experiences by using such technologies as AJAX and jQuery Experience consuming business and data services such as REST, WS-*, Windows Communications Foundation (WCF), and Microsoft ADO.NET Data Services Experience with the full software development life cycle In addition, candidates should have a solid understanding of: Web application architectures such as ASP.NET MVC and Web Form State management for Web applications by using ASP.NET

www.the-academy.nl

Onderwerpen Architecture and Data Access Technologies  Data Access Technologies  Data Access Scenarios Designing the Application Architecture  Plan the division of application logic  Analyze requirements and recommend a system topology  Choose appropriate client-side technologies  Choose appropriate server-side technologies  Design state management LAB: Application Architecture Designing the User Experience  Design the site structure  Plan for cross-browser and/or form factors  Plan for globalization LAB: User Experience Designing Data Strategies and Structures  Design data access  Design data presentation and interaction  Plan for data validation LAB: Data Designing Security Architecture and Implementation  Plan for operational security  Design an authentication and authorization model  Plan for minimizing attack surfaces. LAB: Security Preparing For and Investigating Application Issues  Choose a testing methodology  Design an exception handling strategy  Recommend an approach to debugging  Recommend an approach to performance issues LAB: Issues Designing a Deployment Strategy  Design a deployment process  Design configuration management  Plan for scalability and reliability  Design a health monitoring strategy LAB: Deployment Casus Design Examen: Microsoft MCPD Exam 70–519: Pro: Designing and Developing Web Applications Using Microsoft .NET Framework 4 Voor verdere informatie over de mogelijkheden van @The Academy kunt u contact opnemen met één van onze opleidingsadviseurs. Wij zijn te bereiken op 040-292 47 47.

www.the-academy.nl

Inhoud Microsoft MCPD Exam 70–519: Pro: Designing and Developing Web Applications Using Microsoft .NET Framework 4 Designing the Application Architecture (19%)  Plan the division of application logic. This objective may include but is not limited to: choosing between client-side and server side processing, planning separation of concern, (for example, partitioning functionality between controllers and evaluating business and data service consumption), planning for long-running processes (for example, synchronous vs. asynchronous)  Analyze requirements and recommend a system topology. This objective may include but is not limited to: designing interaction between applications, mapping logical design to physical implementation, validating nonfunctional requirements and cross-cutting concerns (for example, communications, operations management, and security), evaluating baseline needs (for example, scale and quality of service)  Choose appropriate client-side technologies. This objective may include but is not limited to: JavaScript, ASP.NET AJAX, jQuery, Microsoft Silverlight  Choose appropriate server-side technologies. This objective may include but is not limited to: user controls, server controls, partials, custom HtmlHelper extensions, Web parts, inheriting controls, dynamic data controls  Design state management. This objective may include but is not limited to: designing an application for the proper use of application state, session state, and request state (for example, ViewState, ControlState, Cache object, cookies, and client-side persistence) Designing the User Experience (17%)  Design the site structure. This objective may include but is not limited to: designing application segmentation for manageability and security (for example, using areas, shared views, master pages, and nested master pages), appropriate use of style sheets, client-side scripting, themes, client ID generation, rendering element modes, routing engine  Plan for cross-browser and/or form factors. This objective may include but is not limited to: evaluating the impact on client side behaviors, themes, bandwidth, style sheets (including application design - task based or scaled rendering of existing page), when to apply Browsers file, structural approaches, user agents, different platforms (mobile vs. desktop)  Plan for globalization. This objective may include but is not limited to: designing to support local, regional, language, or cultural preferences, including UI vs. data localization (for example, implementing at database level or resource level), when to use CurrentCulture vs. CurrentUICulture, globalization rollout plan (for example, setting base default language, planning localization), handling Unicode data (for example, what fields to include, request encoding), rightto-left support, vertical text and non-Latin topographies, calendars, data formatting, sorting Designing Data Strategies and Structures (18%)  Design data access. This objective may include but is not limited to: choosing data access technologies such as ADO.NETData Services, Entity Framework, Windows Communications Foundation (WCF), and ASP.NET Web Services  Design data presentation and interaction. This objective may include but is not limited to: pulling data from data layer and binding into views, pages, and controls, and pulling data back to data layer by using ModelBinders, data source controls, and HtmlHelper extensions, or programmatically  Plan for data validation. This objective may include but is not limited to: contextual validation vs. data integrity, where to validate data, synchronization between UI and data layer, data annotations  Designing Security Architecture and Implementation (17%)  Plan for operational security. This objective may include but is not limited to: approaches for process- and resource-level security, including local and remote resources, Code Access Security (CAS), including trust level, process identity, application pool, and identity tag  Design an authentication and authorization model. This objective may include but is not limited to: authentication providers, including WindowsForms, and custom user identity flowthrough (for example, trusted subsystem), role management, membership providers, URL authorization (for example, AuthorizationAttribute), file authorization, Authorization Manager (AzMan)  Plan for minimizing attack surfaces. This objective may include but is not limited to: input validation, throttling inputs, request filtering, where to use Secure Sockets Layer (SSL)

www.the-academy.nl

Preparing For and Investigating Application Issues (15%)  Choose a testing methodology. This objective may include but is not limited to: black box, white box, integration, regression, coverage, API testing, performance testing, security testing This objective does not include: load testing, Web testing, unit testing  Design an exception handling strategy. This objective may include but is not limited to: HandleError attribute in MVC, common error pages, post-error processing, global vs. page level  Recommend an approach to debugging. This objective may include but is not limited to: tools and approaches for a given scenario (for example, memory dumps, Debugging Attributes, crashes vs. hangs, deadlocks, assembly binding), when to attach to process (Visual Studio Development Server vs. IIS vs. Internet Explorer), root cause analysis This objective does not include: basic breakpoints  Recommend an approach to performance issues. This objective may include but is not limited to: which instrumentation to watch or create (including performance counters and event tracing) to analyze performance issues, page and fragment caching Designing a Deployment Strategy (14%)  Design a deployment process. This objective may include but is not limited to: Windows Installer (MSI) vs. xcopy vs. Web Deployment Tool, scaling, rolling deployments  Design configuration management. This objective may include but is not limited to: using the ConfigSource attribute (for example, connection strings), staging vs. production vs. development, topologies, machine.config vs. web.config, using IIS vs. Visual Studio Development Server during development, application pools, configuration inheritance  Plan for scalability and reliability. This objective may include but is not limited to: scaling up, scaling out, at physical level and at architectural level, impact of offloading technologies on load balancing, including state, synchronizing machine and encryption keys  Design a health monitoring strategy. This objective may include but is not limited to: when to monitor application or business-related events (e.g., on UI every time clicked or in business layer), determining a strategy for using ASP.NET Health Monitoring, throttling, filtering, delivery method

www.the-academy.nl

INSCHRIJFFORMULIER Bedrijfsnaam Adres Postcode en plaats Telefoon Contactpersoon Emailadres contactpersoon Factuur adres Contactpersoon facturatie Inkoopnummer Prijs M70-519: Pro: Designing and Developing Web Applications Using Microsoft .NET Framework 4

Kruis aan indien gewenst

Omschrijving Microsoft Exam Vouchers

Startdatum

€ 1.495,=

Aantal 1

____ - ____ - ________

Prijs per stuk € 175,=

Totaal € 175,=

Naam Cursist

Emailadres Cursist

Ondergetekende is tekeningsbevoegd en verklaart zich akkoord met de cursusvoorwaarden. Naam

Handtekening

Datum ____ - ____ - ________

Betalingsvoorwaarden: Facturatie: 100% bij opdracht. Betalingstermijn: 10 werkdagen voor aanvang opleiding Alle genoemde bedragen zijn exclusief BTW. De opdracht wordt aan @The Academy B.V. verstrekt door middel van ondertekening van dit inschrijfformulier. U kunt uw ondertekende opdrachtbevestiging per fax retourneren aan @The Academy op faxnummer : 040 - 292 47 48. Wij danken u voor het in ons gestelde vertrouwen.

www.the-academy.nl