Appendix B: Exam 70-300 Objective Mapping Document


The following table is designed to help focus your exam preparation. Each exam objective is listed in the left column, with the corresponding chapter where that objective is addressed in the right column. These objectives were current on the Microsoft site at the time of the creation of this table. Because Microsoft reserves the right to change objectives without notice, you should check the exam site prior to finalizing your exam preparation.

Exam 70-300: Analyzing Requirements and Defining Microsoft .NET Solution Architectures

Microsoft Exam Objective

Located in Chapter

Envisioning the Solution

Develop a solution concept

chapter 2

Analyze the feasibility of the solution

chapter 2

Analyze the business feasibility of the solution

chapter 2

Analyze the technical feasibility of the solution

chapter 2

Analyze available organizational skills and resources

chapter 2

Analyze and refine the scope of the solution project

chapter 2

Identify the key risks

chapter 2

Gathering and Analyzing Business Requirements

Gather and analyze business requirements

Analyze the current business state

chapter 3

Analyze business processes

chapter 3

Analyze the organizational structure, both current and projected

chapter 3

Analyze vertical market position and industry position

chapter 3

Analyze personnel and training needs

chapter 3

Analyze the organizational political climate

chapter 3

Analyze business reach or scope

chapter 3

Analyze current and future regulatory requirements

chapter 3

Analyze business requirements for the solution

Identify business requirements

chapter 3

Identify dependencies, both inside and outside the company

chapter 3

Identify features of the solution

chapter 3

Define design goals, such as extensibility requirements

chapter 3

Define data requirements, types, and flows

chapter 3

Create data flow diagrams

Gather and analyze user requirements

Identify use cases

chapter 3

Identify usage scenarios for each use case

Identify globalization requirements

chapter 3

Identify localization requirements

chapter 3

Identify accessibility requirements

chapter 3

Gather and analyze operational requirements

chapter 3

Identify maintainability requirements

chapter 3

Identify scalability requirements

chapter 3

Identify availability requirements

chapter 3

Identify reliability requirements

Identify deployment requirements

chapter 3

Identify security requirements

chapter 3

Gather and analyze requirements for hardware, software and network infrastructure

Identify integration requirements

chapter 3

Analyze the IT environment, including current and projected applications, and current and projected hardware, software, and network infrastructure

chapter 3

Analyze the impact of the solution on the IT environment

Chapter 3

Developing Specifications

Transform requirements into functional specifications. Considerations include performance, maintainability, extensibility, scalability, availability, deployability, security, and accessibility

Chapter 4

Transform functional specifications into technical specifications. Considerations include performance, maintainability, extensibility, scalability, availability, deployability, security, and accessibility

Chapter 4

Select a development strategy

Chapter 4

Select strategies for auditing and logging

chapter 4

Select strategies for error handling

chapter 4

Select strategies for integration

chapter 4

Select strategies for globalization

chapter 4

Select strategies for localization

chapter 4

Select strategies for data storage

chapter 4

Select strategies for state management

chapter 4

Include constraints in the development plan to support business rules. Constraints include data validation

chapter 4

Select a deployment strategy

chapter 4

Select strategies for deployment, such as coexistence strategies

chapter 4

Select strategies for licensing

chapter 4

Select strategies for data migration

chapter 4

Select a security strategy

chapter 4

Select strategies to ensure data privacy, such as encryption, signing, and sealing

chapter 4

Select strategies to ensure secure access

chapter 4

Select an operations strategy

Select strategies for data archiving and data purging

Select strategies for upgrades

Create a support plan

Create a test plan

chapter 4

Create a user education plan

chapter 4

Creating the Conceptual Design

chapter 6

Create a conceptual model of business requirements or data requirements. Methods include Object Role Modeling (ORM)

chapter 6

Transform external information into elementary facts

chapter 6

Apply a population check to fact types

chapter 6

Identify primitive entity types in the conceptual model

chapter 6

Apply uniqueness constraints to the conceptual model

chapter 6

Apply mandatory role constraints to the conceptual model

chapter 6

Add value constraints, set comparison constraints, and subtype constraints to the conceptual model

chapter 6

Add ring constraints to the conceptual model

chapter 6

Validate the conceptual design

chapter 6

Creating the Logical Design

chapter 7

Create the logical design for the solution

chapter 7

Create the logical design for auditing and logging

chapter 7

Create the logical design for error handling

chapter 7

Create the logical design for exception handling

chapter 7

Create the logical design for integration

chapter 7

Create the logical design for globalization

chapter 7

Create the logical design for localization

chapter 7

Create the logical design for security

chapter 7

Create the logical design for data privacy. Options include encryption, signing, and sealing.

chapter 7

Include constraints in the logical design to support business rules

chapter 7

Create the logical design for the presentation layer, including the user interface (UI)

chapter 7

Create the logical design for services and components

chapter 7

Create the logical design for state management

chapter 7

Create the logical design for synchronous or asynchronous architecture

chapter 7

Create the logical data model

chapter 7

Define tables and columns

chapter 7

Normalize tables

chapter 7

Define relationships

chapter 7

Define primary and foreign keys

chapter 7

Define XML schema

chapter 7

Validate the proposed logical design

chapter 7

Review the effectiveness of the proposed logical design in meeting business requirements. Business requirements include performance, maintainability, extensibility, scalability, and accessibility

chapter 7

Validate the proposed logical design against usage scenarios

chapter 7

Create a proof of concept for the proposed logical design

chapter 7

Creating the Physical Design

Select the appropriate technologies for the physical design of the solution

Create the physical design for the solution

Create specifications for auditing and logging

chapter 8

Create specifications for error handling

chapter 8

Create specifications for physical integration

chapter 8

Create specifications for security

chapter 8

Specifications can apply to strategies for physical data privacy, such as encryption, signing, and sealing

chapter 8

Include constraints in the physical design to support business roles

chapter 8

Design the presentation layer, including the UI and online user assistance

chapter 8

Design services and components

chapter 8

Design the data flow between services

chapter 8

Design state management

chapter 8

Define the look-up data and the configuration data used by the application

chapter 8

Create the physical design for deployment

Create deployment specifications, which can include coexistence and distribution

chapter 8

Create licensing specifications

chapter 8

Create data migration specifications

chapter 8

Design the upgrade path

chapter 8

Create the physical design for maintenance

chapter 8

Design application monitoring

chapter 8

Create the physical design for the data model

chapter 8

Create an indexing specification

chapter 8

Partition Data

chapter 8

Denormalize tables

chapter 8

Validate the physical design

chapter 8

Review the effectiveness of the proposed physical design in meeting the business requirements. Business requirements include performance, maintainability, extensibility, scalability, availability, deployability, security, and accessibility

chapter 8

Validate use cases, scenario walkthroughs, and sequence diagrams

chapter 8

Create a proof of concept for the proposed physical design

chapter 8

Creating Standards and Processes

Establish standards. Standards can apply to development, documentation, coding, code review, UI, and testing

Chapter 9

Establish processes. Processes include reviewing development documentation, reviewing code, creating builds, tracking issues, managing source code, managing change, managing release, and establishing maintenance tasks. Methods include Microsoft Visual Studio .NET Enterprise Templates

chapter 9

Establish quality and performance metrics to evaluate project control, organizational performance, and return on investment

chapter 9




MCSD Analyzing Requirements and Defining. NET Solutions Architectures Study Guide (Exam 70-300)
MCSD Analyzing Requirements and Defining .NET Solutions Architectures Study Guide (Exam 70-300 (Certification Press)
ISBN: 0072125861
EAN: 2147483647
Year: 2003
Pages: 94

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net