MCSD Analyzing Requirements and Defining .NET Solutions Architectures Study Guide (Exam 70-300 (Certification Press)
Chapter 1: Understanding the .NET Framework
- Figure 1-1: .NET acts as a middleware component between the application and Windows.
- Figure 1-2: A typical three-tier web application without .NET
- Figure 1-3: Web services can accept SOAP messages from almost any platform.
- Figure 1-4: The ASP.NET testing interface for web services
- Figure 1-5: Code being edited within the Visual Studio environment
- Figure 1-6: Using Visio to create the conceptual and logical designs of an application
Chapter 2: Visualizing the Solution
- Figure 2-1: A UML state diagram can be used to define a business process.
- Figure 2-2: The enterprise technical architecture consists of five architecture types.
Chapter 5: An Overview of Object Role Modeling
- Figure 5-1: Visio’s ORM Source Model template creates the ORM diagram for you.
- Figure 5-2: The updated diagram including uniqueness constraints
- Figure 5-3: The updated diagram including mandatory role constraints
- Figure 5-4: The updated diagram including new value constraints
Chapter 6: Conceptual Design
- Figure 6-1: A typical procedure diagram
- Figure 6-2: A typical data flow diagram, which documents the data interactions of a system
- Figure 6-3: A hierarchical diagram of the top-level screens of a simple data entry application
Chapter 7: Logical Design
- Figure 7-1: A sample conceptual database design model
Chapter 8: Physical Design
- Figure 8-1: The Windows Event Viewer in Windows XP
- Figure 8-2: Details of one event inside the Event Viewer
- Figure 8-3: An example of an unhandled error message
Chapter 9: Developing Standards for Your Solution
- Figure 9-1: Bug convergence
Категории