Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống
1
/ 22 trang
THÔNG TIN TÀI LIỆU
Thông tin cơ bản
Định dạng
Số trang
22
Dung lượng
919,19 KB
Nội dung
Contents
Overview 1
The MSF Enterprise Architecture Model 2
The MSF Design Process Model 7
The MSF Application Model 10
Review 15
Module 5:Overviewof
Other MSFModels
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.
1999 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, MS, Windows, and Windows NT are either registered trademarks or
trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
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.
Other product and company names mentioned herein may be the trademarks of their respective
owners.
MOC Project Advisor: Janet Wilson
MOC Project Lead: Sharon Salavaria
Program Manager/MSF Project Manager: Sharon Limbocker
Program Manager/Technical Consultant: Dolph Santello
Instructional Designer: Marilyn McCune (Independent)
Product Manager: Jim Wilson
Product Manager: Jerry Dyer
Graphic Artist: Andrea Heuston (Artitudes Layout & Design)
Editing Manger: Lynette Skinner
Editors: Marilyn McCune (Independent) and Wendy Cleary (S&T Onsite)
Production Support: Ed Casper (S&T Consulting)
Manufacturing Manager: Bo Galford
Lead Product Manager: Development Services: Elaine Nuerenberg
Lead Product Manager: Mary Larson
Group Product Manager: Robert Stewart
Module5:OverviewofOtherMSFModels iii
Instructor Notes Module5:OverviewofOtherMSFModels
This module provides students with an overviewofother Microsoft Solutions
Framework (MSF) models, including the MSF Enterprise Architecture Model,
the MSF Design Process Model, and the MSF Application Model.
At the end of this module, students will be able to:
Describe the four perspectives of the MSF Enterprise Architecture Model.
Describe the three phases of the MSF Design Process Model and explain
how each phase relates to the planning phase of the MSF Process Model.
Describe the MSF Application Model.
Materials and Preparation
This section provides you with the materials and preparation needed to teach
this module.
Materials
To teach this module, you need the following materials:
Microsoft® PowerPoint® file 1639a_05.ppt
Module 5, “Overview ofOtherMSF Models”
Preparation
To prepare for this module, you should:
• Read all of the materials for this module.
Presentation:
30 Minutes
Activity:
0 Minutes
iv Module5:OverviewofOtherMSFModels
Module Strategy
Use the following strategy to present this module:
The MSF Enterprise Architecture Model
This section introduces the MSF Enterprise Architecture Model.
Topics in this section include:
• MSF Definition of Enterprise Architecture
This section presents the MSF definition of Enterprise Architecture
(EA), including the organization business activities and the application,
information, and technologies that support those business activities.
• Four Perspectives: One Architecture
Tell students that in the past, information technology (IT) professionals
have not been encouraged to examine enterprise areas other than
technology. Neither have professionals in other enterprise areas been
asked to relate their activities to other groups, least of all to the IT
domain. When asked about activities in another department, the typical
reaction is, “That is not my group.” This insularity is not very useful to
the enterprise quest for self-knowledge. Each perspective, whether it is
business, application, information, or technology, has value, but a viable
EA arises out of the way that these perspectives interrelate.
The MSF Design Process Model
This section introduces the MSF Design Process continuum and describes
the application of the design process to the MSF Process Model.
Topics in this section include:
• The MSF Design Process Continuum
This section defines conceptual design, logical design, and physical
design, and describes the MSF Design Process continuum as an iterative
process.
• Design Process Relationship to the Process Model
This section discusses the relationship between design activities during
the planning phase of the Process Model.
The MSF Application Model
This section describes the key function of the MSF Application Model,
which uses a services-based component design approach to build
applications.
Topics in this section include:
• Function of the MSF Application Model
This section describes the definitions, rules, and relationships, and
services-based component design approach used by the MSF
Application Model.
Module5:OverviewofOtherMSFModels v
• The MSF Services-based Application Model
The MSF Application Model uses a three-tier, logical model for
designing multi-tier, distributed applications that include three broad
categories of service: user, business, and data. The benefit of the model
is that it establishes definitions, rules, and relationships that form the
structure of an application.
• Breaking the Traditional View
This section compares the traditional, stove-piped services view to the
three-tier, logical approach of the MSF Application Model.
The module concludes with review questions that reinforce the module learning
objectives.
There is no activity for this module.
Module5:OverviewofOtherMSFModels 1
Overview
The MSF Enterprise Architecture Model
The MSF Design Process Model
The MSF Application Model
At the end of this module, you will be able to:
Describe the four perspectives of the Microsoft Solutions Framework (MSF)
Enterprise Architecture Model.
Describe the three phases of the MSF Design Process Model and explain
how each phase relates to the planning phase of the MSF Process Model.
Describe the MSF Application Model.
Slide Objective
To provide an overviewof
the module topics and
objectives.
Lead-in
In this module, you will learn
about some of the other
MSF models and where
additional information is
available for the models.
2 Module5:OverviewofOtherMSFModels
The MSF Enterprise Architecture Model
MSF Definition of Enterprise Architecture
Four Perspectives: One Architecture
The four perspectives of the MSF Enterprise Architecture Model relate to one
another in a way that comprises one architecture for the enterprise.
Slide Objective
To introduce the topics
presented in this section.
Lead-in
In this section, you will learn
about the MSF Enterprise
Architecture Model,
including the architecture
and benefits of the model.
Module5:OverviewofOtherMSFModels 3
MSF Definition of Enterprise Architecture
Describes the Organization’s Business Activities
Describes the Applications and Information That
Support those Business Activities
Describes the Technologies That Enable the
Applications and Information
Represents a Dynamic Environment at a Single Moment
in Time
The MSF version of enterprise architecture (EA):
Describes the organization’s business activities, including:
• How products or services are delivered.
• How the business interacts with its customers and suppliers.
• The organizational structure.
• Business processes.
Describes the applications and information that support those business
activities.
Describes the technologies that enable the applications and information.
Represents a dynamic environment at a single moment in time.
Slide Objective
To present the MSF
definition of enterprise
architecture.
Lead-in
There are many definitions
of enterprise architecture,
but few cover the scope of
what it really means.
4 Module5:OverviewofOtherMSFModels
Four Perspectives: One Architecture
There Is One Architecture
for the Enterprise
The Value of the EA Is Not in an
Individual Perspective,
But in the Relationships
Between the Perspectives
Enterprise
Architecture
Business
Business
Application
Application
Technology
Technology
Information
Information
There is one, singular architecture for the enterprise. Each perspective has
value; however, the value of the EA resides in how those perspectives relate to
one another.
The acronym BAIT is an easy way to remember the four-in-one concept of EA.
Business is at the top because it drives the enterprise. Applications and
information are the means to achieve the business goals and objectives of the
enterprise. Technology is at the base because it is the foundation.
The key to successful EA is the ability to see business activities through all four
perspectives. Mature enterprise organizations that still experience problems can
usually trace difficulties to a lack of understanding of business aspects that lie
outside of one’s activity domain.
The MSF model is significantly different from othermodels in that MSF deals
with applications before information.
Planners analyze applications first so that information technology (IT) can
be analyzed after the application perspective is tied to business goals and
objectives.
Another important characteristic is that business is the driver of the EA, and
technology is the base.
There are four perspectives to EA: the business perspective, the application
perspective, the information perspective, and the technology perspective.
Slide Objective
To present the four
perspectives of the
Enterprise Architecture
Model.
Lead-in
This slide shows the four
perspectives through which
to view an enterprise
organization, each different,
but all related.
Key Points
Tell students that B-A-I-T is
an easy way to remember
the four perspectives.
Referring to the illustration,
the pyramid symbolizes the
four-in-one concept of the
MSF version of EA.
[...]... happens, much of the sought-after flexibility, scalability, and maintainability of a multi-tiered design would be preempted Module 5:OverviewofOtherMSFModels 15 Review Slide Objective To reinforce module objectives by reviewing key points Lead-in The review questions cover some of the key concepts taught in the module The MSF Enterprise Architecture Model The MSF Design Process Model The MSF Application... perspective of the technology that the user will employ 4 What are the three type of services described by the MSF Application Model? The three types of services described by the MSF Application Model are user services, business services, and data services 16 Module5: Overview ofOtherMSFModels 5 What does the phrase “three-tier logical over n tier physical” mean? The phrase refers to the network of three-tier... design 8 Module5: Overview ofOtherMSFModels The MSF Design Process Continuum Slide Objective To introduce conceptual design, logical design, and physical design Three Perspectives of Design Three Perspectives of Design Conceptual User Perspective User Perspective Artist Rendering Artist Rendering Lead-in Conceptual, logical, and physical design provide a continuum of project activities in the MSF Design... understanding of the application and defines a working vocabulary for describing application designs Uses services-based component design An organization may use more than one application model to accommodate the different types of applications that it is developing The MSF Application Model uses services-based component design to build applications 12 Module5: Overview ofOtherMSFModels The MSF Services-based... Reusability of Services The services-based MSF Application Model enables applications to share services so that there is less rework being done and a more consistent implementation of business rules Maintainability Maintainability is the ability to evolve the product The MSF services-based component design makes it easy to find and fix smaller units 14 Module5: Overview ofOtherMSFModels Breaking... of a structure—wiring, plumbing, heating, and ventilation The contractor’s plans add detail to the architect’s plans and reflect real-world construction constraints Module 5: Overview ofOtherMSFModels 9 Design Process Relationship to the Process Model Slide Objective To illustrate the relationship between design process activities during the planning phase of the MSF Process Model Lead-in The MSF. .. network with reusable services, such that overlapping networks simply means that applications share reusable services Module 5:OverviewofOtherMSFModels 11 Function of the MSF Application Model Slide Objective To define the MSF Application Model Lead-in The key function provided by the MSF Application Model is that it expresses an approach to building applications by using services-based component... application logic that control the sequencing and enforcing of business rules For example, a business service may: Ensure transactional integrity Transform data into information by applying business rules Module 5:OverviewofOtherMSFModels 13 Data Services Data services refer to units of application logic that provide the lowest visible level of detail used to manipulate data For example, a data service... deployment of workstation and server tools and base applications, infrastructure services, network connectivity components, and platforms Technology perspective also determines the standard interfaces, services, and application models used as development resources for project teams (for example, component code libraries, standards documents, and design guidelines) Module 5:OverviewofOtherMSF Models. . .Module 5:OverviewofOtherMSFModels Business Perspective The business side of the enterprise typically addresses some issues that the IT team rarely discusses For example, from the business perspective, the following considerations are primary: Goals and objectives What is the business of the organization? Organization Who is responsible? Business .
Module 5: Overview of Other MSF Models iii
Instructor Notes Module 5: Overview of Other MSF Models
This module provides students with an overview. this module.
Module 5: Overview of Other MSF Models 1
Overview
The MSF Enterprise Architecture Model
The MSF Design Process Model
The MSF