Contents Overview 1 Microsoft Enterprise Strategy 2 Microsoft Solutions Framework 4 Unified Modeling Language 11 Practice: Using Visio 2000 to Create UML Diagrams 16 Design Patterns 20 Market Purchasing 30 Practice: Using Market Purchasing 35 Lab 1: Reviewing the Market Purchasing Conceptual Design 43 Review 47 Module 1: Designing Distributed Applications for Windows ® 2000 Information in this document is subject to change without notice. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Complying with all applicable copyright laws is the responsibility of the user. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation. If, however, your only means of access is electronic, permission to print one copy is hereby granted. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.  2000 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, ActiveX, BackOffice, FrontPage, Microsoft Press, MSDN, MS-DOS, PowerPoint, Visio, Visual Basic, Visual C++, Visual InterDev, Visual J++, Visual Studio, Win32, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. Program Managers: Rhy Mednick, Susie Parrent Instructional Designer: Susie Parrent Subject Matter Experts: David Chesnut, Sam Gill (TechnoWiz), Michel Pahud Media Management: David Mahlmann Editing Manager: Lynette Skinner Editor: Mick Alberts, Jennifer Linn Production Manager: Miracle Davis Print Coordinators: Linda Lu Cannon (Write Stuff), Marlene Lambert (Online Training Solutions, Inc.) Build Coordinator: Eric Wagoner Graphic Artist: Scott Serna Test Lead: Eric Myers Manufacturing Manager: John Williams Group Product Manager: Juan Fernando Rivera Lead Product Manager, System Services and Infrastructure: Edward Dudenhoefer Manufacturing Manager: Rick Terek Operations Coordinator: John Williams Manufacturing Support: Laura King; Kathy Hershey Lead Product Manager, Release Management: Bo Galford Group Manager, Courseware Infrastructure: David Bramble General Manager: Robert Stewart Module 1: Designing Distributed Applications for Windows® 2000 iii Instructor Notes This module provides students with an overview of the design methodologies and the technology infrastructure that facilitates distributed application development. In particular, this module presents an overview of the Microsoft ® Enterprise Strategy, Microsoft Windows ® 2000 technologies, the Microsoft Solutions Framework (MSF), the Unified Modeling Language (UML), and design patterns. This module also introduces students to the sample application, Market Purchasing, that is used in the labs throughout the course. After completing this module, students will be able to: ! Describe Microsoft Enterprise Strategy and identify the Windows 2000 technologies and the types of applications they can build. ! Identify the technologies and application types that this course will focus on. ! Describe design patterns and how they apply to architecture and logical design. ! Describe the MSF application model and UML. ! Describe the attributes of the Market Purchasing application that will be used in this course. Materials and Preparation This section provides the materials and preparation tasks that you need to teach this module. Required Materials To teach this module, you need the following materials: ! Microsoft PowerPoint ® file 1910A_01.ppt ! Module 1: Designing Distributed Applications for Windows 2000 ! Lab 1: Reviewing the Market Purchasing Conceptual Design Preparation Tasks To prepare for this module, you should: ! Read all of the materials for this module. ! Complete the lab. Presentation: 60 Minutes Lab: 45 Minutes iv Module 1: Designing Distributed Applications for Windows® 2000 Other Activities This section provides procedures for implementing interactive activities to present or review information, such as games or role paying exercises. Practice: Using Visio 2000 to Create UML Diagrams ! To prepare for this practice 1. Review the instructions in the student notes. 2. Complete the practice. Practice: Using Market Purchasing ! To prepare for this practice 1. Review the instructions in the student notes. 2. Complete the practice. Module 1: Designing Distributed Applications for Windows® 2000 v Module Strategy Use the following strategy to present this module: ! Microsoft Enterprise Strategy The purpose of this topic is to introduce students to the Microsoft Enterprise strategy. Focus on defining the three service layers (user, business, and data) and the technologies that are available for each. This is only an introduction. Avoid presenting the details that will be provided in subsequent modules. ! Microsoft Solutions Framework The purpose of this section is to introduce students to the Microsoft Solutions Framework. In the “MSF Motivation” topic, discuss why a successful approach to application development is needed. The statistics are grim. In the “Enterprise Services Framework” topic, present MSF in the context of the Enterprise Services Framework (ESF). It is important to emphasize the two other frameworks: Microsoft Readiness Framework (MRF) and Microsoft Operations Framework (MOF). You can refer students to the MRF URL: http://www.microsoft.com/DirectAccess/training/mrf.asp. In the “MSF Team Model” topic, discuss how different roles in the MSF Team model can benefit from this course. ! Unified Modeling Language The purpose of this section is to introduce students to UML. The introduction includes all of the elements they will need to know to complete the labs. Focus on the two diagrams―use case and class―and the notations that are used in these diagrams. Avoid providing the details of the Automated Teller Machine (ATM) sample, which will be covered in detail in Module 3. ! Practice: Using Visio 2000 to Create UML Diagrams The purpose of this practice is to familiarize students with using Microsoft Visio ® for UML. Visio is used for design work in the labs in this course. Most of the tasks in this practice are tasks that students will use in the labs. ! Design Patterns The purpose of this section is to introduce students to design patterns. The concepts involved with design patterns are introduced by describing a scenario that is complex (without a facade) and by describing how a facade provides an elegant solution to a recurring design problem. ! Market Purchasing The purpose of this section is to introduce students to the Market Purchasing sample application. • Introduction to Market Purchasing The purpose of this topic is to review with the students the business problem, the vision, and the description. • Market Purchasing Conceptual Design The purpose of this topic is to review with the students the conceptual design of Market Purchasing. The conceptual design is given to the students as a starting point for the labs in this course. vi Module 1: Designing Distributed Applications for Windows® 2000 ! Practice: Using Market Purchasing This practice is an excellent way to familiarize students with the key concepts of the Market Purchasing application. After completing this practice, students should be more familiar with what a requisition is and with how to create one. They should also be familiar with the lifecycle of a requisition and how it flows through Market Purchasing. Because this is the first time students have seen Market Purchasing, consider demonstrating the practice first. Demonstrate all of the steps in the practice, explaining what is happening during each step. After completing the practice, let the students experiment with Market Purchasing to try creating and processing requisitions. Familiarize yourself with how Market Purchasing works before presenting this module. Be sure to read all pertinent information about Market Purchasing, and spend some time running Market Purchasing before you teach this course. Also, read the Readme.txt file in the root folder of the Trainer CD to find descriptions of any minor bugs in Market Purchasing that students may encounter. • Market Purchasing Logical Design The purpose of this topic is to describe the process of logical design— that is, to map the conceptual design to classes by using design patterns as a mechanism for solving recurring logical design problems. • Market Purchasing Physical Design The purpose of this topic is to describe the process of physical design— that is, to map the logical classes to physical classes, making the correct technological choices. Lab Strategy ! Lab 1: Reviewing the Market Purchasing Conceptual Design The purpose of this lab is for students to become familiar with the actors and use cases of the Market Purchasing application. These are important for creating the logical and physical designs in later labs. Students need to do a lot of reading to complete this lab. To make the lab more interesting, you could provide a discussion that leads students through the conceptual design. Discuss each actor and use case with the students. Ask them questions about the use cases to test their understanding. It is not necessary for students to memorize every detail and business rule of Market Purchasing. The main goal of the lab is for students to understand the larger issues. Students might ask questions for which there aren’t answers in the conceptual design. Rather than trying to find an answer in the conceptual design, consider making these types of questions discussion points to provide a further understanding of the design process and maybe Market Purchasing. The conceptual design represents a hypothetical interaction between designers, managers, administrators, and users for an unspecified company. It probably does not answer every possible question for the solution to that company’s needs. If you do not provide a detailed discussion of the conceptual design, be sure to discuss with students their answers to the questions in Lab 1. Module 1: Designing Distributed Applications for Windows® 2000 1 # ## # Overview ! Microsoft Enterprise Strategy ! Microsoft Solutions Framework ! Unified Modeling Language ! Design Patterns ! Market Purchasing In this module, you will learn about the Microsoft ® Enterprise strategy. You will also learn about the Microsoft Solutions Framework (MSF) and how it serves as the basis for design work in this course. You will then learn about the Unified Modeling Language (UML), which serves as the notation in this course. You will also learn about the background of design patterns and how they will be applied in this course. Finally, you will be introduced to Market Purchasing, the sample application that is used throughout this course. After completing this module, you will be able to: ! Describe the Microsoft Enterprise strategy, identify the Microsoft Windows ® 2000 technologies, and identify the types of applications that you can build. ! Identify the technologies and application types that this course will focus on. ! Describe design patterns and how they apply to architecture and logical design. ! Describe the MSF application model and UML. ! Describe the attributes of the Market Purchasing application that will be used in this course. Topic Objective To provide an overview of the module topics and objectives. Lead-in In this module, you will learn about the key elements in designing distributed applications for Windows 2000. 2 Module 1: Designing Distributed Applications for Windows® 2000 Microsoft Enterprise Strategy User Services Business Services Data Services SQL Server ADO IIS ASP COM+ Components HTML DHTML ActiveX Win32® Application DCOM HTTP The Microsoft Enterprise strategy is based on the n-tier design and uses Microsoft tools and services to build scalable, distributed applications. User Services User services can be implemented in 32-bit Windows applications (often referred to as rich clients) and developed by using Microsoft development tools such as Microsoft Visual Basic ® , Microsoft Visual C++ ® , and Microsoft Office. Alternatively, lighter-weight HTML front ends (often referred to as thin clients) can be developed by using Microsoft FrontPage ® or Microsoft Visual InterDev ® and hosted on Internet Information Server (IIS). These HTML-based applications allow greater reach to clients in intranet and Internet solutions by using technologies such as Active Server Pages (ASP). Dynamic HTML (DHTML) and ActiveX ® controls can be used to provide varying degrees of functionality. Business Services Business services are implemented in Component Object Model (COM) components. As a result, business functionality can be encapsulated and reused. COM components can be developed in any COM-aware language, such as Visual Basic, Visual C++, or Microsoft Visual J++ ® , and they can be distributed over multiple computers running different operating systems. The COM+ services in the Windows 2000 operating system provide declarative transaction management, asynchronous operations, a distributed event mechanism, security, and ease of deployment. Other infrastructure services such as ActiveX Data Objects (ADO) can be used to access the data services. Topic Objective To provide an overview of Microsoft Enterprise strategy. Lead-in In this topic, you will be introduced to the key technologies used by the Microsoft Enterprise strategy. Module 1: Designing Distributed Applications for Windows® 2000 3 Data Services Data services are usually provided by relational databases stored in a database management system such as Microsoft SQL Server ™ . These databases contain the application data in normalized tables linked by common fields. In some applications, data may be stored in a nonrelational form; for example, in the Windows 2000 Directory or Microsoft Exchange Server. 4 Module 1: Designing Distributed Applications for Windows® 2000 # ## # Microsoft Solutions Framework ! MSF Motivation ! Enterprise Services Framework ! MSF Team Model ! MSF Process Model ! MSF Application Model MSF is a guide for planning, building, and managing distributed computing systems. Like a compass, MSF guides product developers and consultants in a consistent direction without providing the details of how to get there. This allows everyone to agree on the higher-level aspects of the project, including vision, architecture, responsibilities, and many other factors that determine the success of a distributed computing application. Once you establish a shared vision, you can use detailed methodologies, if necessary, to achieve your goals. MSF also serves as a useful tool for measuring progress against the original goals for the project. MSF models help provide the foundation for effective distributed computing by addressing the areas identified as key requirements for next-generation systems throughout the planning, building, and managing life cycle. In this section, the following topics will be covered: ! MSF Motivation ! Enterprise Services Framework (ESF) ! MSF Team Model ! MSF Process Model ! MSF Application Model Topic Objective To provide an overview of the section topics and objectives. Lead-in In this section, you will learn about the Microsoft Solutions Framework. [...]... technology when building applications with Microsoft products and technologies 10 Module 1: Designing Distributed Applications for Windows® 2000 The MSF Application Model defines three categories of services: user, business, and data These services promote a three-tiered logical model for distributed applications The MSF Application Model is the recommended approach for designing such applications The Application.. .Module 1: Designing Distributed Applications for Windows® 2000 MSF Motivation Topic Objective To provide the reason for MSF Lead-in In this topic, you will learn about the outcomes of projects Failed 28% 46% Succeeded Challenged 26% Application Development Projects This slide highlights the need for a solution framework—a set of models that will guide application development efforts toward... notational elements than are listed here For more information about UML, go to the OMG site at http://www.omg.org/uml or refer to the book UML Distilled 14 Module 1: Designing Distributed Applications for Windows® 2000 UML – Use Case Diagrams Topic Objective To provide an introduction to use cases Lead-in Authentication In this topic, you will be introduced to notation for use case diagrams Deposit ATM ATM... physical model of the application Module 1: Designing Distributed Applications for Windows® 2000 13 A standard notation provides a number of benefits to the developer and systems architect It allows the creation of a formal description of the envisioned system from many points of view at the conceptual, logical, and physical phases of its design It also makes it easier for external analysts or consultants... Module 1: Designing Distributed Applications for Windows® 2000 # Unified Modeling Language Topic Objective To provide an overview of the section topics and objectives ! What is UML? Lead-in ! UML – Use Case Diagrams ! UML – Class Diagrams In this section, you will learn about UML This section provides a brief introduction to the Unified Modeling Language (UML) and its nomenclature For detailed information... An attribute is information about a class It is similar to an association In the preceding slide, the ATM User class has two attributes: Card ID and PIN An operation is a process that a class needs to carry out In the preceding slide, the ATM User class has one operation (method): Authenticate 16 Module 1: Designing Distributed Applications for Windows® 2000 Practice: Using Visio 2000 to Create UML... in more detail in Module 3, “Logical Design and Behavioral Design Patterns.” 28 Module 1: Designing Distributed Applications for Windows® 2000 Design Pattern Benefits Topic Objective To describe the benefits of design patterns Lead-in In this topic, you will be introduced to the benefits of design patterns ! Provide Solutions to Common Design Problems ! Provide a Common Vocabulary for Design Teams Design... design, Logical design, and Physical design You will be provided with the Conceptual design for Market Purchasing You will also be provided with some of the Logical and Physical design, and will create the rest of the Logical and Physical design in lab exercises Module 1: Designing Distributed Applications for Windows® 2000 9 MSF Application Model Topic Objective To provide an introduction to the application... completed but overextended their budgets, took longer than originally scheduled, or delivered less functionality than originally promised 5 6 Module 1: Designing Distributed Applications for Windows® 2000 Enterprise Services Framework Topic Objective To provide the context for MSF Lead-in In this topic, you will learn about the Enterprise Services Framework and its components: MRF, MSF, and MOF Building MRF... be human users or other objects A single actor can perform many use cases In the use case diagram in the slide above, one actor is the ATM User, the other actor is the Automated Teller Machine (ATM) ! Use cases (represented as an ellipse) Use cases are narrative descriptions of processes Module 1: Designing Distributed Applications for Windows® 2000 15 UML – Class Diagrams Topic Objective To provide . materials for this module. ! Complete the lab. Presentation: 60 Minutes Lab: 45 Minutes iv Module 1: Designing Distributed Applications for Windows® 2000 Other. the practice. Module 1: Designing Distributed Applications for Windows® 2000 v Module Strategy Use the following strategy to present this module: ! Microsoft