Tài liệu Module 2: Solution Design Using the MSF docx

Module overview Module 3: A Services-based Approach to Solution Design Module 4: Business Solution Conceptual Design Module 5: Business Solution Logical Design Module 6: Beginning Physic

MSF

Module overview

Module 3: A Services-based Approach to Solution Design Module 4: Business Solution Conceptual Design Module 5: Business Solution Logical Design Module 6: Beginning Physical Design

Module 1: Course Overview Module 2: Solution Design Using the MSF

Module 7: Selecting Solution

Technologies

Module 8: Solution Design and the

Component Object Model

Module 9: Designing Solutions with

Design Overview

Activity 2.1: Identifying Design Principles

MSF Design Process

Activity 2.2: Identifying Design Phases

! Overview

" Design Overview

" Activity 2.1: Identifying Design Principles

" MSF Design Process

" Activity 2.2: Identifying Design Phases

" Benefits of the MSF Design Process

" Review

In this module

Designing solutions to today’s complex business challenges should not be left

to chance or to a haphazard approach Instead, a flexible process, or framework, can guide your solution design and avoid the issues associated with rigid methods

The Microsoft® Solutions Framework (MSF) describes a flexible and adaptable process that helps guide project teams by using several models In this course, you will learn about two of these models, the MSF Process Model for

Application Development and the MSF Application Model

In this module, you will learn about the conceptual, logical, and physical design phases and how they relate to the MSF Process Model In module 4, you will learn about the MSF Application Model

After completing this module, you will be able to:

" Describe the role of design in developing effective solutions to business challenges

" Describe the MSF Process Model for Application Development

" Explain the roles of the conceptual, logical, and physical design phases in the design process

" Explain the benefits of using the MSF Process Model for Application Development

Slide Objective

To provide an overview of

the module topics and

objectives

! Design Overview

In this section

" Business Solution Design

" A Well-Designed Solution

" Cost of Fixing a Poorly Designed Solution

" Cost of Not Fixing a Poorly Designed Solution

Slide Objective

To provide an overview of

this section

Business Solution Design

" Identifying the business challenge to be addressed

" Analyzing the challenge for possible solutions

" Determining the optimal solution for the challenge

" Describing the solution so that it can be understood by all stakeholders

" Documenting the solution design so that it can be implemented by using the appropriate technologies

Designing a solution is a process that includes several steps Although the steps are sequential, they overlap and influence each other

Before beginning design, you must first identify the challenge After identifying the challenge, you analyze the information for possible solutions From these alternative solutions, you must select the one that is optimal, based on the business requirements

After you have identified the optimal solution, you must describe it in such a way that all project stakeholders understand it

The final step of the design process is to document the solution design so that it can be developed, implemented, and deployed

Slide Objective

To provide a high-level

description of the process

that the students will be

going through for the next

five days

Lead-in

You will be learning the

details of the design process

in the remainder of this

course A high-level

overview of business

solutions design includes

the following steps

A Well-Designed Solution

" Useful

$ Solves the business problem

$ Enables delivery of information, services, and products

" Usable

$ Enables and enhances productivity

$ Is intuitive and error-free

" Desirable

$ Is cost-effective

$ Is flexible, scalable, and maintainable

Developing a successful solution requires the design to be useful, usable, and desirable If the design does not exhibit these attributes, neither will the solution And if initial deployment of a solution is not successful, it will have to

be fixed at an additional expense to the customer

Slide Objective

To provide the basis for

evaluating a solution design

Lead-in

A good design should not be

measured by its use of

technology but by whether

the solution is useful,

usable, and desirable

Cost of Fixing a Poorly Designed Solution

100 80 60 40 20

Envisioning Planning Developing Stabilizing

pressures often force development teams to take shortcuts, which runs counter

to doing the proper analysis, validation of customer requirements, and overall product design required for a successful project This perilous behavior usually results in expensive design changes that occur late in the life cycle of the project

Investment in the cost of quality can appear to be counterproductive to management goals Preventive techniques — such as ongoing design reviews, inspections, configuration management, user validation, and skill development

— might appear to add additional project overhead and slow progress All these techniques, however, when applied pragmatically, allow project teams to deal effectively with changes and help to prevent design flaws from entering the final release of the product

Abundant industry data proves that when organizations make such quality investments, they enjoy lower development costs, higher customer satisfaction, and more time and resources to focus on producing other innovative business solutions

Slide Objective

To show the exponential

costs of fixing a design

defect later rather then

earlier

Lead-in

It is much easier to fix a

design defect when it is

merely a sentence in your

specification rather than a

malfunction after the

solution has been deployed

Cost of Not Fixing a Poorly Designed Solution

a business not being competitive with other organizations that have developed well-designed applications for their business functions

A poorly designed project also has hidden costs, including the opportunity costs involved in developing the application Personnel who could have been

working on other applications or projects have been unavailable, and money that could have been used for other projects, business investments and expansion, or even employee compensation has been spent on an inadequate project Every dollar that goes into a project is a dollar that cannot be spent elsewhere

For the organization’s Information Technology (IT) department, the costs can include the wasted resources of developers, technicians, and engineers;

inefficient use of computer hardware, software licenses, and network bandwidth; and potential damage to the image of the IT department

Finally, consider the personal and political costs incurred by the participants in the failed project Whenever a large-scale project is deemed a failure within an organization, all personnel associated with that project may carry its stigma, regardless of the role they may have played in it

Removing a design flaw from an organization’s production system involves much more than shipping the organization an updated release of the system Business operations are disrupted, customers are dissatisfied, and employee morale (and effectiveness) is lowered as a consequence These expenses are insidious, and their cost to the organization is often many times higher than the initial cost of developing the system

Slide Objective

To show that there are

potentially even greater

costs if the design defect is

not fixed

Lead-in

Not only are there costs

associated with fixing a poor

design, but there are also

costs associated with not

fixing it

Activity 2.1: Identifying Design Principles

In this activity, you will consider the design of a common item and identify the features of the item that illustrate principles of good design and the features that might be considered design flaws

After completing this activity, you will be able to:

" Demonstrate an understanding of the characteristics of good design

Slide Objective

To introduce the activity

" Relationship Among Design Phases

" Design Phases in MSF Process Model

The second phase of the MSF Process Model is composed of three design phases: conceptual design, logical design, and physical design

In this section, you will learn about the three phases of design and how they relate to each other and to the MSF Process Model

Slide Objective

To provide an overview of

this section

Three Phases of Design

" Iterative evolution from high level of detail to low level

of detail

" Each phase represents a different view of the solution

$ User’s perspective: conceptual design

$ Project team’s perspective: logical design

$ Developer’s perspective: physical design

Physical Conceptual Logical

The solution-design process is evolutionary; it evolves from a nebulous idea at

a high level of detail to a tangible entity

For example, building design starts with sketches of the proposed structure These drawings provide a view of the building for the client and might contain floor plans, cutaways, and other figures This view corresponds to conceptual design The conceptual design starts with what the business and users require and results in a set of models that communicate these requirements

The sketches of the proposed structure are followed by architectural plans, also known as blueprints This phase in the architectural process combines the client’s requirements with the architect’s knowledge Detailed drawings allow for communication with contractors and other parties

This view of the architectural process corresponds to logical design

Finally, the contractor’s plans are drawn up for the builder, adding detail to the architect’s plans to make adjustments for the physical environment of the site and materials available to build the building These plans direct the construction activities and add greater detail for individual subcontractors

This view corresponds to physical design During this phase, real-world constraints of technology are applied to the logical model, including implementation and performance considerations At this point, real resources, costs, and schedule can be estimated

Slide Objective

To introduce the concept of

the three design phases

Lead-in

The MSF Design Process

consists of three phases

Services and Objects, User Interface, and Logical Database

Scenarios

During conceptual design, you define the challenge and solution in terms of scenarios that reflect business requirements You should view the problem from the perspectives of the customer, the user, and the business — not from a technology perspective

Slide Objective

To provide an introduction to

the conceptual design

phase of the MSF Design

Process

Lead-in

The first phase, conceptual

design, is about gathering

and understanding

information about the

business and the users

Services and Objects, User Interface, and Logical Database

During logical design, you start to identify the details of the solution The logical design describes the structure of the solution, which helps manage the solution's complexity

In this phase, you take the business problem identified in the scenarios of conceptual design and develop a model of the solution The model includes business objects and services, user interface prototypes, and logical database design

You should view the challenge and the solution from the perspective of the project team This phase is crucial, as it is the transformation of the design from the conceptual to the physical

You can begin logical design as soon as the conceptual design provides a good understanding of the business and of the user

Slide Objective

To provide an introduction to

the logical design phase of

the MSF Design Process

Lead-in

The second phase, logical

design, uses the scenarios

of conceptual design as

inputs for creating the

logical models of the

solution

Components, User Interface, and Physical Database

Services and Objects, User Interface, and Logical Database

Scenarios

During physical design, you apply real-world technology constraints, including implementation and performance considerations, to the outputs of logical design

The models of logical design are used to design components, user interface specifications, and physical data store design

You should view the solution from the perspective of the developers and define the solution's services and technologies During physical design, you begin considering the best way to implement the solution and the appropriate tools to use

Physical design begins after the logical design has provided enough information for physical design decisions to be made

Slide Objective

To provide an introduction to

the physical design phase of

the MSF Design Process

Lead-in

The third phase, physical

design, uses the structures

defined in logical design to

create a description of the

solution in such a way that

the solution required can be

developed

Relationship Among Design Phases

" A phase can begin when the project team agrees that sufficient information exists

" Outputs from one phase are inputs for the next phase

" Design effort iterates across phases

" A phase baselines when the primary effort is shifted to the next phase

" Each phase is equally important

Some design process models and methodologies are rigid, prescribing precisely when and how to accomplish each step In contrast, the MSF advocates a flexible, iterative process that includes conceptual, logical, and physical design

A design phase does not have to end in order for the next design phase to start You can begin a phase as soon as enough information from the previous phase

is available In addition, each phases provides information to both the following and previous phases This is the iterative aspect of the process

When the project team is ready to shift its primary effort to the next phase, the current phase is baselined The team reaches consensus on the output of the phase and agrees that it is ready to move forward

Slide Objective

To describe how the three

phases are interrelated,

iterative, and equally valued

Lead-in

Now that we understand

that there are three phases,

let’s look at their relationship

to each other

Design Phases in MSF Process Model

Vision Approved

Vision Approved

Project Plan Approved

Project Plan Approved

Physical Design Baseline

Logical Design Baseline

Conceptual Design Baseline

Conceptual Design Logical Design Physical Design

The starting point and endpoint for each design phase are intended to be flexible It is possible to start planning the design (and possibly even developing the physical elements of the project) while still constructing the vision of the project; however, some sequencing occurs You should start conceptual design before you begin logical design Likewise, you should start logical design before moving on to physical design Similarly, the conceptual design has to baseline, or stabilize, before the logical design can be baselined, before the physical design can be baselined, and before the deliverables can be baselined

Slide Objective

To position the MSF Design

Process in the context of the

MSF project life cycle, the

MSF Process Model for

Application Development

Lead-in

As you would expect, design

is a major part of the

project-planning process