Microsoft 认证专业开发人员/考试 70-547

设想和设计应用程序

评估应用程序设计概念的技术可行性。

 Evaluate the proof of concept.
 Recommend the best technologies for the features and goals of the application.
 Weigh implementation considerations.
 Investigate existing solutions for similar business problems.

创建概念验证原型。

 Evaluate the risks associated with ASP.NET 2.0 technology or implementation.
 Validate that the proposed technology can be used in the application.
 Demonstrate to stakeholders that the proposed solution will address their needs.

评估应用程序的技术规格，以确保满足业务需求。

 Translate the functional specification into developer terminology, such as pseudo code and UML diagrams.
 Suggest component type and layer.

评估数据库的设计。

 Recommend a database schema.
 Identify the stored procedures that are required for an application.

评估应用程序的逻辑设计。

 Evaluate the logical design for performance.
 Evaluate the logical design for maintainability.
 Evaluate the logical design for extensibility.
 Evaluate the logical design for scalability.
 Evaluate the logical design for availability.
 Evaluate the logical design for security.
 Evaluate the logical design against use cases.
 Evaluate the logical design for recoverability.
 Evaluate the logical design for data integrity.

评估应用程序的物理设计。 考虑因素包括项目结构的设计、文件数量、程序集数量以及这些资源在服务器上的位置。

 Evaluate the physical design for performance.
 Evaluate the physical design for maintainability.
 Evaluate how the physical location of files affects the extensibility of the application.
 Evaluate the physical design for scalability.
 Evaluate the physical design for availability.
 Evaluate the physical design for security.
 Evaluate the physical design for recoverability.
 Evaluate the physical design for data integrity.

链接

面向 .NET 的应用程序架构：设计应用程序和服务 ASP.NET Web 应用程序安全 第 14 章 — 提高 SQL Server 性能 创建存储过程（数据库引擎） ADO.NET 中的数据并发简介

设计和开发用户界面

选择适合视觉界面的布局。

 Decide the content flow across pages.
 Evaluate user navigation needs.
 Identify the goal of the page.
 Ensure the congruency and consistency of the user experience throughout the application.

评估在整个 UI 中实施通用布局的策略。

 Suggest when to use style sheets, master pages, Web parts, custom controls, scripting, and user controls.
 Suggest an applicable UI standard based on the intended client environment. Considerations include chosen operating systems, technologies, and browser types.

根据设计规格选择合适的控件。

 Evaluate the type of data that must be captured or displayed.
 Evaluate available controls. Considerations include standard .NET Framework controls and custom, internally developed, and third-party controls.
 Evaluate how available controls are implemented in previous and ongoing projects or applications.
 Evaluate the user demographic. Considerations include localization concerns.
 Evaluate the user environment. Considerations include screen size and browser type and version.

根据设计规范选择合适的控件。

 Choose a validation method based on the data type provided.
 Decide how to report the feedback. Considerations include callbacks, exceptions, and writing to an event log.
 Identify the source of invalid data.
 Identify the cause of an invalid entry.
 Evaluate whether invalid data can be prevented.
 Evaluate whether an exception must be thrown.
 Evaluate whether an exception must be logged.
 Evaluate whether visual feedback, such as a message box or color, is required.

在 UI 层选择合适的数据验证方法。

 Design a user assistance mechanism.
 Choose an appropriate application status feedback technique based on available control types.
 Choose an appropriate application status feedback technique to support accessibility.
 Design an application status feedback mechanism.

选择合适的用户帮助和应用程序状态反馈技术。

 Evaluate available multimedia delivery mechanisms. Considerations include bandwidth problems, file formats, frames per second, and streaming types.
 Design a multimedia delivery mechanism.

链接

[edit | edit source]

ASP.NET 主页概述 使用 Web 标准构建 ASP.NET 2.0 网站 比较 GridView 和 DataGrid Web 服务器控件 DataList Web 服务器控件 何时使用 DataGrid、DataList 或 Repeater 如何定义 ASP.NET 主题 向导 Web 服务器控件概述 XmlDataSource 控件概述

[edit | edit source]

 Decide when to create a single component or multiple components.
 Decide which tier of the application a component should be located.
 Decide which type of object to build.

[edit | edit source]

 Establish the life cycle of a component.
 Decide whether to use established design patterns for the component.
 Decide whether to create a prototype for the component.
 Document the design of a component by using pseudo code, class diagrams, sequence diagrams, activity diagrams, and state diagrams.
 Evaluate tradeoff decisions. Considerations include security vs. performance, performance vs. maintainability, and so on.

[edit | edit source]

 Decide the types of clients that can consume a component.
 Establish the required component interfaces.
 Decide whether to require constructor input.

[edit | edit source]

 Decide whether existing functionality can be implemented or inherited.
 Decide how to handle unmanaged and managed resources.
 Decide which extensibility features are required.
 Decide whether a component must be stateful or stateless.
 Decide whether a component must be multithreaded.
 Decide which functions to implement in the base class, abstract class, or sealed class.

[edit | edit source]

 Decide when it is appropriate to raise an exception.
 Decide how a component will handle exceptions. Considerations include catching and throwing a new exception; catching, wrapping, and throwing the wrapped exception; catching and terminating, and so on.

[edit | edit source]

 Analyze data relationships.
 Analyze the data handling requirements of a component.

[edit | edit source]

 Identify potential issues, such as resource leaks and performance gaps, by profiling a component.
 Decide when to stop profiling on a component.
 Decide whether to redesign a component after analyzing the profiling results.

[edit | edit source]

[edit | edit source]

 Identify a reusable software component from available components to meet the requirements.
 Identify whether the reusable software component needs to be extended.
 Identify whether the reusable software component needs to be wrapped.
 Identify whether any existing functionality needs to be hidden.
 Test the identified component that is based on the requirements.

[edit | edit source]

 Evaluate the current exception handling mechanism.
 Design a new exception handling technique.

[edit | edit source]

 Choose an appropriate data storage mechanism.
 Choose an appropriate data flow structure.
 Choose an appropriate decision flow structure.

[edit | edit source]

 Decide whether to log data. Considerations include policies, security, requirements, and debugging.
 Choose a storage mechanism for logged events. For example, database, flat file, event log, or XML file.
 Choose a systemwide event logging method. For example, centralized logging, distributed logging, and so on.
 Decide logging levels based on severity and priority.

[edit | edit source]

 Decide whether to monitor data. Considerations include administration, auditing, and application support.
 Decide which characteristics to monitor. For example, application performance, memory consumption, security auditing, usability metrics, and possible bugs.
 Choose event monitoring mechanisms, such as System Monitor and logs.
 Decide monitoring levels based on requirements.
 Choose a systemwide monitoring method from the available monitoring mechanisms.

[edit | edit source]

 Decide which configuration attributes to store.
 Choose the physical storage location for the configuration attributes.
 Decide in which format to store the configuration attributes.
 Choose when to use ASP.NET Administrative tools.

[edit | edit source]

[edit | edit source]

 Create the unit testing strategy.
 Evaluate the integration testing strategy.
 Evaluate the stress testing strategy.
 Evaluate the performance testing strategy.
 Evaluate the test environment specification.

[edit | edit source]

 Describe the testing scenarios.
 Decide coverage requirements.
 Evaluate when to use boundary condition testing.
 Decide the type of assertion tests to conduct.

执行集成测试。

 Determine if the component works as intended in the target environment.
 Identify component interactions and dependencies.
 Verify results.

解决一个错误。

 Investigate a reported bug.
 Reproduce a bug.
 Evaluate the affect of the bug and the associated cost and timeline for fixing the bug.
 Fix a bug.

部署和支持应用程序

根据性能分析策略评估应用程序的性能。

 Identify performance spikes.
 Analyze performance trends.
 Track page response times.
 Track logon times.

分析监控应用程序时收到的数据。

 Monitor and analyze resource usage.
 Monitor and analyze security aspects.
 Track bugs that result from customer activity.
 Choose when to use ASP.NET 2.0 Health Monitoring APIs.

评估部署计划。

 Identify component-level deployment dependencies.
 Identify scripting requirements for deployment.

创建应用程序流程逻辑图。

 Evaluate the complexity of components.
 Evaluate the complexity of interactions with other components.

验证生产配置环境。考虑因素包括负载平衡、Web 场和 Web 花园。

 Verify networking settings.
 Verify the deployment environment. 

来源：http://www.microsoft.com/learning/exams/70-547.mspx

外部链接

• 考试 70-528 的课程总结和建议