<<Project Name>>

Physical Design
Customer Name
Directions for using template:
Read the Guidance (Arial blue font in brackets) to understand the information that
should be placed in each section of this template. Then delete the Guidance and
replace the placeholder within <<Begin tet here!! with "our response. There ma" be
additional Guidance in the Appendi of some documents# which should also be
deleted once it has been used.
$ome templates ha%e four le%els of headings. The" are not indented# but can be
differentiated b" font t"pe and si&e:
'eading ( ) Arial Bold (* font
'eading + ) Arial Bold ,talic (- font
'eading . ) Arial Bold (. font
'eading . ) Arial Bold ,talic (+ font
/ou ma" elect to indent sections for readabilit".
Author
Author 0osition
1ate
2ersion: (.3
3453+5+3(-
2002 Microsoft Corporation. All rights reserved.
The information contained in this document represents the current view of Microsoft Corporation on the issues
discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not
be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accurac of an
information presented after the date of publication.
This document is for informational purposes onl. MICROSOFT MA!S NO "ARRANTI!S# !$PR!SS OR
IMP%I!D# IN T&IS DOC'M!NT(
Microsoft and !isual Basic are either registered trademarks or trademarks of Microsoft in the "nited #tates and$or
other countries.
3453+5+3(-
Revision & Sign-off Sheet
6hange Record
1ate Author 2ersion 6hange Reference
Re%iewers
7ame 2ersion Appro%ed 0osition 1ate
1istribution
7ame 0osition
1ocument 0roperties
,tem 1etails
1ocument Title 0h"sical 1esign
Author
6reation 1ate
8ast 9pdated
3453+5+3(-
Table of Contents
0h"sical 1esign $ummar"..............................................................................................-
:n%ironment 6onstraints# and Assumptions...................................................................-
1ependencies..................................................................................................................-
0ro;ect 1ependencies.................................................................................................-
'ardware :n%ironment 1ependencies.......................................................................-
$oftware :n%ironment 1ependencies........................................................................<
Application 1e%elopment...............................................................................................<
9ser $er%ices (9, ) 9ser ,nterface)...........................................................................<
6omponent <<Component Name>> 1esign........................................................<
Business $er%ices (=iddle>tier Business 8ogic)........................................................?
6omponent <<Component Name>> 1esign........................................................?
1ata $er%ices Tier.......................................................................................................@
6omponent <<Component Name>> 1esign........................................................@
1atabase 1esign...................................................................................................((
,nfrastructure 1eplo"ment............................................................................................(+
$olution Topologies..................................................................................................(+
,ntranet 6ommunication...........................................................................................(+
$er%ices.................................................................................................................(+
0rotocols...............................................................................................................(+
$ecurit".................................................................................................................(.
,nternet 6ommunication...........................................................................................(.
$er%ices.................................................................................................................(.
0rotocols...............................................................................................................(.
$ecurit".................................................................................................................(.
:tranet 6ommunication..........................................................................................(.
$er%ices.................................................................................................................(-
0rotocols...............................................................................................................(-
$ecurit".................................................................................................................(-
7etwork 1iagnostics ,mpact....................................................................................(-
Authentication5Acti%e 1irector"57T 1omain $trateg"............................................(-
Addressing................................................................................................................(-
6lient Tier.............................................................................................................(<
$er%er Tier............................................................................................................(<
1'60 6onfigurations...........................................................................................(<
7ame Resolution......................................................................................................(<
A,7$ 6onfigurations...........................................................................................(<
17$ 6onfigurations.............................................................................................(<
Remote Access..........................................................................................................(<
7aming $tandards....................................................................................................(<
$er%er 0lacement......................................................................................................(<
$er%er $i&ing............................................................................................................(*
Administrati%e =odel...............................................................................................(*
,ndi%idual 0roduct5$er%ice Beatures to be ,mplemented..........................................(*
$er%ice <<Service Name>> 6onfiguration..........................................................(*
3453+5+3(-
6onfiguration of :n%ironment.................................................................................(*
$ecurit" $trateg"..........................................................................................................(*
$ecurit" 1esign ,mplications...................................................................................(?
$ecurit" ,mplementation ,ssues................................................................................(?
$ecurit" Cperational $upport 6onsiderations..........................................................(?
,nstallation and $etup...................................................................................................(?
'ardware ReDuirements...........................................................................................(?
$oftware ReDuirements............................................................................................(?
9n>,nstallation..............................................................................................................(?
1esign for 1eplo"ment................................................................................................(4
1esign for =igration....................................................................................................(4
1esign for ,ntegration...................................................................................................(4
Accessibilit" $upport....................................................................................................(4
=ulti>language $upport................................................................................................(4
1esign for $upportabilit".............................................................................................(4
8ogging5:%enting.....................................................................................................(@
:rror =essages.........................................................................................................(@
1iagnostic Tools.......................................................................................................(@
Reco%er" from 6orruption5:rror =essaging............................................................(@
,ssues............................................................................................................................(@
Appendi......................................................................................................................+3
3453+5+3(- (
%Intro)uction to the Tem*late
Descri*tion+ The &hsical 'esign is the application of real(world phsical design
constraints applied to the )ogical 'esign. This is developed b anal*ing which
pieces of the )ogical 'esign alread e+ist in components, what can be reused or
modified, and what new pieces must be created.
,usti-ication+ The &hsical 'esign is a complete implementation design or blueprint,
in the form of a technical specification that the development team will use to build the
solution.
,Team Role Primary+ Program Management is responsible for ensuring that the
phsical design document is completed. De.elo*ment will have the primar
responsibilit for creating the document-s content. Release Management will
participate both in content creation and review along with development to ensure that
operational, deploment, migration, interoperabilit, and support needs are
addressed within the design.
Team Role Secon)ary+ Pro)uct Management will review and understand the
&hsical 'esign in order to conve it to parties e+ternal to the team and to ensure
that it aligns with initial pro.ect sponsor re/uirements. 'ser !/*erience will review
the design to ensure user re/uirements are met. Test will review the &hsical 'esign
to ensure test plans are in place to validate it.01
3453+5+3(- +
Physical Design Summary
%Descri*tion+ &rovide an overall summar of the contents of this document. This
should include the criteria b which the design was established and how it was
validated.
,usti-ication+ #ome pro.ect participants ma need to know onl the document-s
highlights, and summari*ing creates that user view. 2t also enables the full reader to
know the essence of the document before the e+amine the details.1
<<Begin tet here!!
!n.ironment Constraints# an) Assum*tions
%Descri*tion+ The 3nvironment Constraints and Assumptions section identifies and
defines the conditions that impact the phsical design. These ma be associated with
the current infrastructure into which the solution will be deploed or time and cost
constraints that impact the selection of technologies. This section should also identif
all assumptions that were made in developing the phsical design that need
verification.
,usti-ication4 'ocumenting these conditions ensures that the development team
applied them to the process of creating the design. 2t also signals to stakeholders
e+ternal to the team that these conditions were considered.1
<<Begin tet here!!
De*en)encies
%Descri*tion+ The 'ependencies section identifies the pro.ect, hardware, and
software dependencies and resources re/uired to enable development to begin.1
Project Dependencies
%Descri*tion+ The &ro.ect 'ependencies section defines pro.ect(related conditions
that must be in place for the development team to be successful. This ma include
having specificall skilled people on the team, depending on an e+ternal pro.ect, or
re/uiring a deliverable from a related pro.ect team.1
<<Begin tet here!!
Hardware Environment Dependencies
%Descri*tion+ The 5ardware 3nvironment 'ependencies section lists and describes
the environmental hardware that should be in place for the development team-s work.
2temi*e all re/uired development workstations and testing environment hardware
here.1
<<Begin tet here!!
3453+5+3(- .
Software Environment Dependencies
%Descri*tion The #oftware 3nvironment 'ependencies section lists and describes
the environmental software that should be in place for the development team-s work.
2temi*e all re/uired development workstations and testing environment software
here.1
<<Begin tet here!!
A**lication De.elo*ment
0Descri*tion+ The Application 'evelopment section describes the design for an
applications that e+ist within the solution. Applications ma include custom code and
components. The sub(sections provide topic ideas that ma help build a cohesive
picture of the phsical implementation.1
User Services (UI User Interface)
%Descri*tion+ 2n n(tier development, the "ser #ervices section represents the
traditional "ser 2nterface 6"27. More than .ust presentation, the solution ma have
additional client(tier services behind the presentation laer and possibl even a client
database implementation. #eparate the client database implementation into the data
services tier, but do not include it here. This section should focus solel on "2
presentation services.
2temi*e all the components and use the following sub(sections to describe them in
detail.1
<<Begin tet here!!
Com*onent <<Component Name>> Design
%Descri*tion+ The Component 'esign section provides details for each component
within the architecture. Construct a separate section for each component that
includes the applicable sub(sections listed below 6Behavioral #ummar,
'ependencies, etc.7.1
e!aviora" S#mmar$
%Descri*tion+ The Behavioral #ummar section describes the e+pected component
behavior, including a high(level description of services and value.1
<<Begin tet here!!
Dependencies
%Descri*tion+ The 'ependencies section provides a detailed, uni/ue dependenc for
each component different from the overall environment dependencies. 'etail inter(
component dependencies, C8M9 role, securit conte+t dependencies, memor
allocation estimates, and state full dependencies.
3453+5+3(- -
,usti-ication1
<<Begin tet here!!
New %pp"ication Interfaces
%Descri*tion4 The :ew Application 2nterfaces section describes the interface names,
public$private methods, arguments and snta+ re/uired of all new interfaces.1
<<Begin tet here!!
C!an&ed %pp"ication Interfaces
%Descri*tion4 The Changed Application 2nterfaces section describes the interface
names, public$private methods, arguments and snta+ re/uired of an e+isting
interfaces that must be changed. This section is optional if this is a revision pro.ect or
!ersion ;9 pro.ect.1
<<Begin tet here!!
'emoved %pp"ication Interfaces
%Descri*tion+ The <emoved Application 2nterfaces section identifies all application
interfaces that are removed for this solution. This section is optional if this is a
revision pro.ect or !ersion ;9 pro.ect.1
<<Begin tet here!!
Scriptin& Interfaces
%Descri*tion4 The #cripting 2nterfaces section describes all interface names,
public$private methods, arguments, and snta+ re/uired.1
<<Begin tet here!!
'e&istr$ Impact Confi&#ration and Settin&s
%Descri*tion4 The <egistr 2mpact = Configuration and #ettings section describes
the registr kes created, default configuration, and values.1
<<Begin tet here!!
Error (essa&es
%Descri*tion4 The 3rror Messages section identifies all events, e+ceptions, and
errors that ma occur within a component. )ist message descriptions here as well.1
<<Begin tet here!!
Sec#rit$ Imp"ementation
%Descri*tion4 The #ecurit 2mplementation section describes the securit conte+t
strateg for the component that will be used in calling conte+t 6interactive user7 or
specific role etc. 2t should identif additional securit beond C8M9 implementation
3453+5+3(- <
as re/uired. This information should also include dependencies$assumptions made
within the conte+t of this component-s e+ecution.1
<<Begin tet here!!
Component (ana&ement Iss#es
%Descri*tion4 The Component Management 2ssues section describes an uni/ue
aspects of the component design.1
<<Begin tet here!!
#siness Services ((idd"e)tier #siness *o&ic)
%Descri*tion+ The Business #ervices section defines the application components for
the solution-s business services tier. Itemi*e all the components and use the following
sub(sections to describe them in detail.1
<<Begin tet here!!
Com*onent <<Component Name>> Design
%Descri*tion+ The Component 'esign section provides details for each component
within the architecture. There should be a separate section for each component that
includes the applicable sub(sections listed below 6Behavioral #ummar,
'ependencies, etc.7.1
e!aviora" S#mmar$
%Descri*tion+ The Behavioral #ummar section describes the e+pected component
behavior, including a high(level description of services and value.1
<<Begin tet here!!
Dependencies
%Descri*tion+ The dependencies section provides a detailed, uni/ue dependenc for
each component different from the overall environment dependencies. 'etail inter(
component dependencies, C8M9 role, securit conte+t dependencies, memor
allocation estimates, and state full dependencies.
,usti-ication1
<<Begin tet here!!
New %pp"ication Interfaces
%Descri*tion4 The :ew Application 2nterfaces section describes the interface names,
public$private methods, arguments and snta+ re/uired of all new interfaces.1
<<Begin tet here!!
3453+5+3(- *
C!an&ed %pp"ication Interfaces
%Descri*tion4 The Changed Application 2nterfaces section describes the interface
names, public$private methods, arguments and snta+ re/uired of an e+isting
interfaces that must be changed. This section is optional if this is a revision pro.ect or
!ersion ;9 pro.ect.1
<<Begin tet here!!
'emoved %pp"ication Interfaces
%Descri*tion+ The <emoved Application 2nterfaces section identifies all application
interfaces that are removed for this solution. This section is optional if this is a
revision pro.ect or !ersion ;9 pro.ect.1
<<Begin tet here!!
Scriptin& Interfaces
%Descri*tion4 The #cripting 2nterfaces section describes all interface names,
public$private methods, arguments, and snta+ re/uired.1
<<Begin tet here!!
'e&istr$ Impact Confi&#ration and Settin&s
%Descri*tion4 The <egistr 2mpact = Configuration and #ettings section describes
the registr kes created, default configuration, and values.1
<<Begin tet here!!
Error (essa&es
%Descri*tion4 The 3rror Messages section identifies all events, e+ceptions, and
errors that ma occur within a component. )ist message descriptions here as well.1
<<Begin tet here!!
Sec#rit$ Imp"ementation
%Descri*tion4 The #ecurit 2mplementation section describes the securit conte+t
strateg for the component that will be used in calling conte+t 6interactive user7 or
specific role etc. 2t should identif additional securit beond C8M9 implementation
as re/uired. This information should also include dependencies$assumptions made
within the conte+t of this component-s e+ecution.1
<<Begin tet here!!
Component (ana&ement Iss#es
%Descri*tion4 The Component Management 2ssues section describes an uni/ue
aspects of the component design.1
<<Begin tet here!!
3453+5+3(- ?
Data Services +ier
%Descri*tion+ The 'ata #ervices Tier section is used if the solution re/uires
implementing separate data tier service components in addition to the phsical
database implementation. 2f the solution re/uires implementing the design through
e+tensive data services within a database engine itself, use the >'atabase 'esign?
section to describe this.
2temi*e all the components and use the following sub(sections to describe them in
detail.1
<<Begin tet here!!
Com*onent <<Component Name>> Design
%Descri*tion+ The Component 'esign section provides details for each component
within the architecture. There should be a separate section for each component that
includes the applicable sub(sections listed below 6Behavioral #ummar,
'ependencies, etc.7.1
e!aviora" S#mmar$
%Descri*tion+ The Behavioral #ummar section describes the e+pected component
behavior, including a high(level description of services and value.1
<<Begin tet here!!
Dependencies
%Descri*tion+ The 'ependencies section provides a detailed, uni/ue dependenc for
each component different from the overall environment dependencies. 'etail inter(
component dependencies, C8M9 role, securit conte+t dependencies, memor
allocation estimates, and state full dependencies.
,usti-ication1
<<Begin tet here!!
New %pp"ication Interfaces
%Descri*tion4 The :ew Application 2nterfaces section describes the interface names,
public$private methods, arguments, and snta+ re/uired of all new interfaces.1
<<Begin tet here!!
C!an&ed %pp"ication Interfaces
%Descri*tion4 The Changed Application 2nterfaces section describes the interface
names, public$private methods, arguments, and snta+ re/uired of an e+isting
interfaces that must be changed. This section is optional if this is a revision pro.ect or
!ersion ;9 pro.ect.1
<<Begin tet here!!
3453+5+3(- 4
'emoved %pp"ication Interfaces
%Descri*tion+ The <emoved Application 2nterfaces section identifies all application
interfaces that are removed for this solution. This section is optional if this is a
revision pro.ect or !ersion ;9 pro.ect.1
<<Begin tet here!!
Scriptin& Interfaces
%Descri*tion4 The #cripting 2nterfaces section describes all interface names,
public$private methods, arguments, and snta+ re/uired.1
<<Begin tet here!!
'e&istr$ Impact Confi&#ration and Settin&s
%Descri*tion4 The <egistr 2mpact = Configuration and #ettings section describes
the registr kes created, default configuration, and values.1
<<Begin tet here!!
Error (essa&es
%Descri*tion4 The 3rror Messages section identifies all events, e+ceptions, and
errors that ma occur within a component. )ist message descriptions here as well.1
<<Begin tet here!!
Sec#rit$ Imp"ementation
%Descri*tion4 The #ecurit 2mplementation section describes the securit conte+t
strateg for the component that will be used in calling conte+t 6interactive user7 or
specific role etc. 2t should identif additional securit beond C8M9 implementation
as re/uired. This information should also include dependencies$assumptions made
within the conte+t of this component-s e+ecution.1
<<Begin tet here!!
Component (ana&ement Iss#es
%Descri*tion4 The Component Management 2ssues section describes an uni/ue
aspects of the component design.1
<<Begin tet here!!
Data1ase Design
%Descri*tion+ The 'atabase 'esign section defines the complete database
strateg.1
<<Begin tet here!!
3453+5+3(- @
Data,ase Sc!ema
%Descri*tion4 The 'atabase #chema section defines the databases, table structures,
and field$record descriptions and their structures. The database schema can be
represented using a schema(modeling tool.1
<<Begin tet here!!
Stored Proced#res
%Descri*tion4 The #tored &rocedures section describes each stored procedure
name, its functionalit, parameters$arguments, and transactional support.1
<<Begin tet here!!
Data 'ep"ication Strate&$
%Descri*tion4 The 'ata <eplication #trateg section defines the tpe of strateg
selected 6multi(tier or multi(platform, selected engine, 'T# packages, etc7 and
identifies and describes all uni/ue replication procedures.1
<<Begin tet here!!
Sec#rit$ Imp"ementation
%'escription4 The #ecurit 2mplementation section describes the data securit model.
This should include descriptions of group administration and role rights within each
database and its associated tables. @ou ma choose to consolidate specific securit
assignments within the schema section above using a visual format in a graph or
schema outla.1
<<Begin tet here!!
Data (ana&ement Strate&$
%'escription4 The 'ata Management #trateg section describes the post installation
strateg for un(interrupted performance. This should include the technical
specifications for implementing that data(management strateg. This section ma
overlap with the 8perations &lan and #upport &lan, which can be referenced here.1
<<Begin tet here!!
In-rastructure De*loyment
%Descri*tion+ The 2nfrastructure 'eploment section is applicable if the solution
includes implementing, deploing, and migrating a packaged infrastructure product or
service. The sub(sections provide topic ideas that ma help build a cohesive picture
of the phsical implementation.1
So"#tion +opo"o&ies
%Descri*tion+ The #olution Topologies section provides a general e+planation of the
solution-s topolog architecture. This should include phsical machine locations,
3453+5+3(- (3
network design topologies, and site topologies. 2nclude both central and remote site
topologies if applicable. A visual or graphic depiction of this topolog ma provide
clarit.1
<<Begin tet here!!
Intranet Comm#nication
%Descri*tion+ The 2ntranet Communication section describes the server and services
communication strateg within the firewall boundaries for the solution.1
<<Begin tet here!!
Ser.ices
%Descri*tion+ The #ervices section itemi*es all intranet communication product
services to be implemented within the solution.1
<<Begin tet here!!
Service <<Ser.ice Name>> Confi&#ration
%Descri*tion+ The #ervice Configuration section describes the installation options,
configuration issues, and options for the above(named service. <epeat this section
for each service to be implemented.1
<<Begin tet here!!
Protocols
%Descri*tion+ The &rotocols section itemi*es the network protocols supported. This
should include a list of configuration options$issues re/uired within all tiers of
solution.1
<<Begin tet here!!
Security
%Descri*tion+ The #ecurit section lists the securit configuration
options$re/uirements specific to intranet communication.1
<<Begin tet here!!
Internet Comm#nication
%Descri*tion+ The 2nternet Communication section describes how the solution will
provide for or be dependent upon 2nternet connectivit. 2t also defines the perceived
impact of the solution upon the e+isting 2nternet services, and lists an additional
services re/uired 6firewall support, encrption$secure communication strateg, etc.7.1
<<Begin tet here!!
3453+5+3(- ((
Ser.ices
%Descri*tion+ The #ervices section itemi*es all 2nternet communication product
services to be implemented within the solution.1
<<Begin tet here!!
Service <<Ser.ice Name>> Confi&#ration
%Descri*tion+ The #ervice Configuration section describes the installation options,
configuration issues, and options for the above(named service. <epeat this section
for each service to be implemented.1
<<Begin tet here!!
Protocols
%Descri*tion+ The &rotocols section itemi*es the network protocols supported. This
should include a list of configuration options$issues re/uired within all tiers of
solution.1
<<Begin tet here!!
Security
%Descri*tion+ The #ecurit section lists the securit configuration
options$re/uirements specific to 2nternet communication.1
<<Begin tet here!!
E-tranet Comm#nication
%Descri*tion+ The 3+tranet Communication section describes how the solution will
provide for or be dependent upon 3+tranet connectivit. 2t also defines the perceived
impact of the solution upon the e+isting 3+tranet services, and lists an additional
services re/uired 6!&:, private network, B2B or partner relationship, trust
environments established between partners, etc.7.1
<<Begin tet here!!
Ser.ices
%Descri*tion+ The #ervices section itemi*es all e+tranet communication product
services to be implemented within the solution.1
<<Begin tet here!!
Service <<Ser.ice Name>> Confi&#ration
%Descri*tion+ The #ervice Configuration section describes the installation options,
configuration issues, and options for the above(named service. <epeat this section
for each service to be implemented.1
<<Begin tet here!!
3453+5+3(- (+
Protocols
%Descri*tion+ The &rotocols section itemi*es the network protocols supported. This
should include a list of configuration options$issues re/uired within all tiers of
solution.1
<<Begin tet here!!
Security
%Descri*tion+ The #ecurit section lists the securit configuration
options$re/uirements specific to e+tranet communication.1
<<Begin tet here!!
Networ. Dia&nostics Impact
%Descri*tion+ The :etwork 'iagnostics 2mpact section describes the changes
needed in the phsical network, such as an needed new subnets, segments, line
speeds, hubs, routers or switching e/uipment.1
<<Begin tet here!!
%#t!entication/%ctive Director$/N+ Domain Strate&$
%Descri*tion+ The Authentication$Active 'irector$:T 'omain #trateg section-s title
should be modified for the specific solution. 2t describes the detailed model of the
Active 'irector implementation, :T #erver account domains, resource domains, and
trust relationships, )'A& or other authentication strategies. 2f our solution supports
more than one, provide details on each authentication strateg.1
<<Begin tet here!!
%ddressin&
%Descri*tion+ The Addressing section describes the method for network address
assignment and management 6'5C&$#tatic 2&, etc.7. This entire section ma not
appl to the solution or be greatl reduced in scope if the deploment is e+clusive to
an isolated environment 6i.e., a single instance on a single machine.7. 5owever, if
planning a large(scale, multi(tier deploment, this section is probabl more relevant
when each tier is defined independentl.1
Client Tier
<<Begin tet here!!
Ser.er Tier
<<Begin tet here!!
3453+5+3(- (.
D&CP Con-igurations
<<Begin tet here!!
Name 'eso"#tion
%Descri*tion+ The :ame <esolution section describes the method for resolving host
6server7 and client names on the networks 6':#$A2:#, etc.7.1
"INS Con-igurations
<<Begin tet here!!
DNS Con-igurations
<<Begin tet here!!
'emote %ccess
%Descri*tion+ The <emote Access section describes how the feature6s7 work when
connected via remote access or slow links.1
<<Begin tet here!!
Namin& Standards
%Descri*tion+ The :aming #tandards section defines all naming standards re/uired
b the new application or infrastructure environment. This should include naming
conventions for components, including server, sites, organi*ation units, workstations,
etc.1
<<Begin tet here!!
Server P"acement
%Descri*tion+ The #erver &lacement section describes the guidelines for placing
servers, both centrall or remote.1
<<Begin tet here!!
Server Si0in&
%Descri*tion+ The #erver #i*ing section describes the guidelines for configuring
servers.1
<<Begin tet here!!
3453+5+3(- (-
%dministrative (ode"
%Descri*tion+ The Administrative Model section describes how the servers and
clients will be administrated.1
<<Begin tet here!!
Individ#a" Prod#ct/Service 1eat#res to ,e Imp"emented
%Descri*tion+ The 2ndividual &roduct$#ervice Beatures to be 2mplemented section
itemi*es all products that will be deploed on behalf of the solution and the features
of each product$service to be implemented. )ist the products and use the sub(
sections below to describe them in detail.1
<<Begin tet here!!
Ser.ice <<Service Name>> Con-iguration
%Descri*tion+ The #ervice Configuration section describes for each product its
installation options, configuration settings at default, an options available, and all
issues associated with its deploment.
<epeat this section for each service to be implemented.1
<<Begin tet here!!
Confi&#ration of Environment
%Descri*tion+ The Configuration of 3nvironment section defines the overall
environment configuration that addresses the solution-s performance, scalabilit,
reliabilit, and securit. 2n an implementation$deploment$migration pro.ect, this
section is likel to be e+tensive.1
<<Begin tet here!!
Security Strategy
%Descri*tion+ The #ecurit #trateg section describes the solution(wide strateg to
ensure securit of all components. This section is coordinated with the #ecurit &lan
6a section of the Master &ro.ect &lan7. The sub(sections provide additional detail on
ke elements of the solution-s securit.1
<<Begin tet here!!
Sec#rit$ Desi&n Imp"ications
%Descri*tion+ The #ecurit 'esign 2mplications section identifies the specific aspects
of the design that satisf the solution-s securit re/uirements.1
<<Begin tet here!!
3453+5+3(- (<
Sec#rit$ Imp"ementation Iss#es
%Descri*tion+ The #ecurit 2mplementation 2ssues section identifies an issues that
arise from the solution-s design that impact securit implementation.1
<<Begin tet here!!
Sec#rit$ 2perationa" S#pport Considerations
%Descri*tion+ The #ecurit 8perational #upport Considerations section defines how
the design will influence the solution-s managerial and operational support processes.
The specific securit controls are defined in the #ecurit &lan.1
<<Begin tet here!!
Installation an) Setu*
%Descri*tion+ The 2nstallation and #etup section describes the strateg for the
solution-s installation. This information ma also be found in the 'eploment &lan.
The sub(sections specif the re/uired hardware and software.1
<<Begin tet here!!
Hardware 'e3#irements
%Descri*tion+ The 5ardware <e/uirements section identifies the hardware
components that will be re/uired for installation. The hardware installation
procedures can be found in the 'eploment &lan.1
<<Begin tet here!!
Software 'e3#irements
%Descri*tion+ The #oftware <e/uirements section identifies the software
components that will be re/uired for installation. The software installation procedures
can be found in the 'eploment &lan.1
<<Begin tet here!!
'n2Installation
%Descri*tion+ The "n(2nstallation section describes the strateg for the solution-s
removal from its deploment environment.1
<<Begin tet here!!
Design -or De*loyment
%Descri*tion+ The 'esign for 'eploment section describes the technical
specifications that will assist in e+ecuting the solution-s deploment. These are
design considerations based on the solution-s current and future environment. This
information should not describe the deploment process 6as that is the content of the
'eploment &lan7.1
3453+5+3(- (*
<<Begin tet here!!
Design -or Migration
%Descri*tion+ The 'esign for Migration section describes the technical specifications
that will assist in e+ecuting the solution-s migration. These are design considerations
based on the solution-s current and future environment. This information should not
describe the migration process 6as that is the content of the Migration &lan7.1
<<Begin tet here!!
Design -or Integration
%Descri*tion+ The 'esign for 2ntegration section describes the technical
specifications that will ensure the solution-s integration and interoperabilit with
surrounding solutions$sstems. These are design considerations based on the
solution-s current and future environment.1
<<Begin tet here!!
Accessi1ility Su**ort
%Descri*tion+ The Accessibilit #upport section describes the design elements that
meet handicap and accessibilit re/uirements.1
<<Begin tet here!!
Multi2language Su**ort
%Descri*tion+ The Multi()anguage #upport section describes the design elements
that meet multi(language re/uirements.1
<<Begin tet here!!
Design -or Su**orta1ility
%Descri*tion+ The 'esign for #upportabilit section describes the technical
specifications that will assist in the solution-s supportabilit. These are design
considerations based on the solution-s current and future environment. This
information should not describe the supportabilit process 6as that is the content of
the #upport &lan7.
,usti-ication1
<<Begin tet here!!
*o&&in&/Eventin&
%Descri*tion+ The )ogging$3venting section describes how logging will occur within
the solution.1
<<Begin tet here!!
3453+5+3(- (?
Error (essa&es
%Descri*tion+ The 3rror Messages section describes how error messages will be
created and communicated within the solution.1
<<Begin tet here!!
Dia&nostic +oo"s
%Descri*tion+ The 'iagnostic Tools section describes how diagnostic tools are
integrated into the solution and how the will function.1
<<Begin tet here!!
'ecover$ from Corr#ption/Error (essa&in&
%Descri*tion+ The <ecover from Corruption$3rror Messaging section describes how
the solution will recover from corruption events.1
<<Begin tet here!!
Issues
%Descri*tion+ The 2ssues section identifies an unresolved issues that are related to
the solution-s phsical design. This information should list the issue and its
implications to the design.1
<<Begin tet here!!
3453+5+3(- (4
A**en)i/
3453+5+3(- (@