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 |
| chapter 2 |
| chapter 2 |
| 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 | |
| chapter 3 |
| chapter 3 |
| chapter 3 |
| chapter 3 |
| chapter 3 |
| chapter 3 |
| chapter 3 |
| chapter 3 |
Analyze business requirements for the solution | |
| chapter 3 |
| chapter 3 |
| chapter 3 |
| chapter 3 |
| chapter 3 |
| |
Gather and analyze user requirements | |
| chapter 3 |
| |
| chapter 3 |
| chapter 3 |
| chapter 3 |
Gather and analyze operational requirements | chapter 3 |
| chapter 3 |
| chapter 3 |
| chapter 3 |
| |
| chapter 3 |
| 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 |
| chapter 4 |
| chapter 4 |
| chapter 4 |
| chapter 4 |
| chapter 4 |
| chapter 4 |
| chapter 4 |
| chapter 4 |
Select a deployment strategy | chapter 4 |
| chapter 4 |
| chapter 4 |
| chapter 4 |
Select a security strategy | chapter 4 |
| chapter 4 |
| chapter 4 |
Select an operations strategy | |
| |
| |
| |
| chapter 4 |
| 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 |
| chapter 6 |
| chapter 6 |
| chapter 6 |
| chapter 6 |
| chapter 6 |
| chapter 6 |
| chapter 6 |
Validate the conceptual design | chapter 6 |
Creating the Logical Design | chapter 7 |
Create the logical design for the solution | chapter 7 |
| chapter 7 |
| chapter 7 |
| chapter 7 |
| chapter 7 |
| chapter 7 |
| chapter 7 |
| chapter 7 |
| chapter 7 |
| chapter 7 |
| chapter 7 |
| chapter 7 |
| chapter 7 |
| chapter 7 |
Create the logical data model | chapter 7 |
| chapter 7 |
Normalize tables | chapter 7 |
| chapter 7 |
| chapter 7 |
| chapter 7 |
Validate the proposed logical design | chapter 7 |
| chapter 7 |
| chapter 7 |
| chapter 7 |
Creating the Physical Design | |
Select the appropriate technologies for the physical design of the solution | |
Create the physical design for the solution | |
| chapter 8 |
| chapter 8 |
| chapter 8 |
| chapter 8 |
| chapter 8 |
| chapter 8 |
| chapter 8 |
| chapter 8 |
| chapter 8 |
| chapter 8 |
| chapter 8 |
Create the physical design for deployment | |
| chapter 8 |
| chapter 8 |
| chapter 8 |
| chapter 8 |
Create the physical design for maintenance | chapter 8 |
| chapter 8 |
Create the physical design for the data model | chapter 8 |
| chapter 8 |
| chapter 8 |
| chapter 8 |
Validate the physical design | chapter 8 |
| chapter 8 |
| chapter 8 |
| 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 |