Study guide Analyzing requirements and defining Microsoft .NET solution architectures

70 - 300

www.testking.com

- 1 -

70-300

Study Guide:

Analyzing Requirements and Defining

Microsoft .NET Solution

Architectures

Version 1.1

70 - 300

www.testking.com

- 2 -

TABLE OF CONTENTS

List of Tables

Introduction

1. Introduction to Designing Business Solutions

1.1 Overview of Microsoft Solutions Framework

1.1.1 Process Models

1.1.1.1 The Waterfall Model

1.1.1.2 The Spiral Model

1.1.2 The MSF Process Model

1.1.3 The MSF Team Model

1.1.3.1 MSF Team Model Roles

1.1.3.2 Combining MSF Team Model Roles

1.1.3.3 Additional Project Team Members

1.2 MSF Disciplines

1.2.1 Risk Management

1.2.2 Readiness Management

1.2.3 Project Management

1.3 Managing Tradeoffs

1.3.1 The Tradeoff Triangle

1.3.2 The Tradeoff Matrix

1.4 Iteration in Projects

1.4.1 Versioned Releases

1.4.2 Living Documents

1.4.3 Periodic Builds

1.5 The Phases of the MSF Process Model

1.5.1 The Envisioning Phase

1.5.1.1 The Envisioning Phase Milestones

1.5.1.2 The Envisioning Phase Deliverables

1.5.1.3 Defining the Scope of the Project

1.5.1.4 Creating the Solution Concept

1.5.1.5 Identifying Project Goals

1.5.1.6 Creating the Risk Assessment Document

1.5.2 The Planning Phase

1.5.2.1 The Planning Phase Milestones

1.5.2.2 The Planning Phase Deliverables

1.5.2.3 Planning for Future Phases

1.5.2.3.1 Planning for the Developing Phase

1.5.2.3.2 Planning for the Stabilizing Phase

1.5.2.3.3 Planning for the Deploying Phase

70 - 300

www.testking.com

- 3 -

1.5.3 The Developing Phase

1.5.3.1 The Developing Phase Milestones

1.5.3.2 The Developing Phase Deliverables

1.5.4 The Stabilizing Phase

1.5.4.1 The Testing Process

1.5.4.2 The Pilot Process

1.5.4.3 The Stabilizing Phase Milestones

1.5.4.4 The Stabilizing Phase Deliverables

1.5.4.5 Project Team Responsibilities

1.5.5 The Deploying Phase

1.5.5.1 The Deploying Phase Milestones

1.5.5.2 The Deploying Phase Deliverables

1.5.5.3 Project Team Role Responsibilities

2. Gathering and Analyzing Information

2.1 Gathering Information

2.1.1 Categories of Information

2.1.2 Techniques of Information Gathering

2.1.3 Sources of Information

2.1.4 Defining the Information Gathering Strategy

2.2 Analyzing Information

2.2.1 Developing Use Cases and Usage Scenarios

2.2.2 Draft Requirements Document

2.2.3 Internal Documents

2.3 Using Modeling Notations

2.3.1 The Unified Modeling Language

2.3.2 The Object Role Modeling

2.3.3 The ORM Conceptual Schema Design Procedure

2.4 Creating Use Cases and Usage Scenarios

2.4.1 Use Cases

2.4.2 Usage Scenarios

2.4.3 Creating a Usage Scenario

2.4.4 Refining the Requirements

3. The Conceptual Design

3.1 Conceptual Design Steps

3.1.1 The Research Step

3.1.2 The Analysis Step

3.1.2.1 Refining the Requirements

3.1.2.2 Refining Use Cases Diagrams

3.1.2.3 Solution Services and Application Architecture

3.1.3 The Optimization Step

70 - 300

www.testking.com

- 4 -

3.2 Validating the Conceptual Design Model

4. The Logical Design

4.1 Team Role Responsibilities

4.2 Logical Design Steps

4.2.1 The Analysis Step

4.2.2 Identifying Candidate Business Objects

4.2.3 Identifying Services for an Object

4.2.4 Identifying Attributes of an Object

4.2.5 Identifying Object Relationships

4.3 Logical Design Outputs

4.4 The Optimization Step

4.4.1 Refining Objects

4.4.2 Verifying an Existing Logical Object Model

4.4.3 Establishing Control in Logical Design

5. The Physical Design

5.1 Team Role Responsibilities

5.2 The Physical Design Deliverables

5.3 Physical Design Steps

5.3.1 The Research Step

5.3.1.1 Research Step Deliverables

5.3.1.2 Identifying Physical Requirements and Constraints

5.3.1.3 Resolving Conflicts between Requirements and Constraints

5.3.2 The Analysis Step

5.3.2.1 Refining the UML Models

5.3.2.2 Creating a Preliminary Deployment Model

5.3.3 The Rationalization Step

5.3.3.1 The Rationalization Step Deliverables

5.3.3.2 Creating Distribution and Packaging Strategies

5.3.3.3 The Components Plan

5.3.3.4 Packaging Components

5.3.3.5 Distributing Preliminary Components

5.3.3.6 Create a Deployment Model

5.3.3.7 Validating and Refining Distribution and Packaging

5.3.4 The Implementation Step

5.3.4.1 The Programming Model

5.3.4.2 Specifying Component Interfaces

6. Designing the Presentation Layer

70 - 300

www.testking.com

- 5 -

6.1 User Interface Components

6.2 User Interface Design Guidelines

6.3 Creating the Initial User Interface Design

6.4 Providing User Assistance

6.5 Selecting a User Interface Model

6.5.1 Windows-Based User Interfaces

6.5.2 Web-based user interfaces

6.5.3 Mobile device user interfaces

6.5.4 Document-based user interfaces

6.6 Selecting the Client Environment

6.7 Creating a User Interface Prototype

6.8 The User Process Components

6.9 User Process Design Guidelines

7. Designing the Data Layer

7.1 Physical Data Model Types

7.2 Identifying Entities and Attributes

7.3 Identifying Tables and Columns

7.4 Entity Relationships

7.5 Optimizing Data Access

7.5.1 Indexing

7.5.2 Partitioning

7.5.3 Normalization

7.6 Data Validation

7.7 Identifying Data Integrity Requirements

7.8 Business Rules

8. Designing Security Specifications

8.1 Common Security Vulnerabilities

8.2 Principles for Creating Security Strategies

70 - 300

www.testking.com

- 6 -

8.3 Creating a Threat Model

8.3.1 The STRIDE Threat Model

8.3.2 Incorporating Mitigation Techniques

8.4 Implementing .NET Framework Security Features

8.5 .NET Security Features

9. Deploying to a Production Environment

9.1 Core Components and Site-Specific Components

9.2 Site Deployment Phases

9.2.1 The Preparation Phase

9.2.2 The Installation Phase

9.2.3 The Training Phase

9.2.4 The Stabilization Phase

9.3 Transferring the Project to Operations and Support

9.4 Closeout Activities

Index

LIST OF TABLES

TABLE 1.1

TABLE 2.1

TABLE 7.1

TABLE 8.1:

TABLE 8.2:

Basic Testing Terms

Some Important Modeling Terms

Some Common DBMS Data Types

Principles of Security

Mitigation Techniques

70 - 300

www.testking.com

- 7 -

Analyzing Requirements and Defining

Microsoft .NET Solution Architectures

Exam Code: 070-300

Certifications:

Microsoft Certified (MCP)

Microsoft Certified Solution Developer (MCSD) Core

About This Study Guide

This Study Guide is based on the current pool of exam questions for the 070-300 - Analyzing Requirements

and Defining Microsoft .NET Solution Architectures exam. As such it provides all the information required

to pass the Microsoft 070-300 exam and is organized around the specific skills that are tested in that exam.

Thus, the information contained in this Study Guide is specific to the 070-300 exam and does not represent a

complete reference work on the subject of Analyzing Requirements and Defining Microsoft .NET Solution

Architectures. This Study Guide also includes the information required to answer questions related to the

developing Windows-based and Web based .NET, XML and ASP applications that may be asked during the

exam. Topics covered in this Study Guide includes: Developing a solution concept; Analyzing the business

and technical feasibility of a solution; Analyzing available organizational skills and resources; Analyzing

and refine the scope of the solution project; Identifying key project risks; Gathering and analyzing business

requirements; Analyzing the current business state; Analyzing business processes; Analyzing the current and

projected organizational structure; Analyzing vertical market position and industry position; Analyzing

personnel and training needs; Analyzing the organizational political climate; Analyzing business reach or

scope; Analyzing current and future regulatory requirements; Analyzing business requirements for the

solution; Identifying business requirements; Defining design goals; Defining data requirements, types, and

flows; Creating data flow diagrams; Gathering and analyzing user requirements; Identifying use cases and

scenarios for each use case; Identifying globalization and localization requirements; Identifying accessibility

requirements; Gathering and analyzing operational requirements; Identifying maintainability, scalability,

availability, reliability, deployment, and security requirements; Gathering and analyzing requirements for

hardware, software, and network infrastructure; Identifying integration requirements; Analyzing the IT

environment, and the impact of the solution on the IT environment; Transforming requirements into

functional specifications; Transforming functional specifications into technical specifications; Selecting a

development strategy; Selecting strategies for auditing and logging, error handling, integration, globalization,

localization, data storage, and state management; Selecting a deployment strategy; Selecting strategies for

licensing, data migration, and security; Selecting strategies to ensure data privacy, and secure access;

Selecting strategies for data archiving and data purging, upgrades, and support; Creating a test plan;

Creating a user education plan; Creating a conceptual model of business requirements or data requirements;

Transforming external information into elementary facts; Applying a population check to fact types;

Identifying primitive entity types in the conceptual model; Applying uniqueness constraints and mandatory

role constraints to the conceptual model; Adding value constraints, set-comparison constraints, and subtype

constraints to the conceptual model; Adding ring constraints to the conceptual model; Validating the

conceptual design; Creating the logical design for auditing and logging, and error handling; Creating the

logical design for integration, globalization, localization, and security; Including constraints in the logical

design to support business rules; Creating the logical design for the presentation layer, services and

70 - 300

www.testking.com

- 8 -

components, and state management; Creating the logical design for synchronous or asynchronous

architecture; Creating the logical data model; Defining tables and columns; Normalizing tables; Defining

data relationships; Defining primary and foreign keys, and the XML schema; Validating the logical design;

Selecting the appropriate technologies for the physical design of the solution; Creating the physical design

for the solution; Creating specifications for auditing and logging, error handling, physical integration, and

security; Including constraints in the physical design to support business rules; Designing the presentation

layer, services and components, and data flow between services; Designing state management; Defining the

look-up data and the configuration data used by the application; Creating the physical design for deployment;

Creating deployment, licensing, and data migration specifications; Designing the upgrade path; Creating the

physical design for maintenance; Designing application monitoring; Creating the physical design for the

data model; Validating the physical design; Creating Standards and Processes; Establishing standards;

Establishing 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; Establishing quality and

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

Intended Audience

This Study Guide is targeted specifically at people who wish to take the Microsoft MCSE exam 070-300 -

Analyzing Requirements and Defining Microsoft .NET Solution Architectures. This information in this

Study Guide is specific to the exam. It is not a complete reference work. The MCSD certificate is an

advanced certification program. Therefore it is not aimed at new comers to the world of IT. As such, the

concepts dealt with in this Study Guide are complex and require a prior understanding of programming

solutions.

How To Use This Study Guide

To benefit from this Study Guide we recommend that you:

• Study each chapter carefully until you fully understand the information. This will require regular and

disciplined work. Where possible, attempt to implement the information in a lab setup.

• Be sure that you have studied and understand the entire Study Guide before you take the exam.

Note: Remember to pay special attention to these note boxes as they contain

important additional information that is specific to the exam.

Good luck!