EnterpriseArchitecture
ArchitectureDescription
Status:Indraft
UnderReview
SentforApproval
Approved
Rejected
Version:<>
ReleaseDate:
Note:SEARCHANDREPLACE
<>
Searchforany<>asyourinputwillbe
required.
Alsoreviewanyyellowhighlightedtext.
ArchitectureDescription
Thedocumentisnottobeconsideredanextensivestatementasitstopicshave
tobegenericenoughtosuitanyreaderforanyorganization.
However,thereaderwillcertainlyberemindedofthekeytopicsthathavetobe
considered.
ThisdocumentservesastheFOUNDATIONFORCREATINGA
CONSISTENTDESCRIPTIONOFADEVELOPINGARCHITECTURE.This
documentprovidesabasisforcompletionwithinyourownorganization.
Thisdocumentwas:
Preparedby:
On:<>
Acceptedby:
On:<>
ArchitectureDescription
Thefollowingtemplateshouldbeusedtodescribeanarchitecture.Basedonthe
principlesofEnterpriseArchitecture,everysubsequentarchitecturedeveloped
andimplementedwithintheenterpriseshouldattempttoutilizeexistingand
commonbuildingblocks.Thisdocumentdoesnotattempttoidentifyallthese
buildingblocks,butprovidesanapproachbywhichthosebuildingblockscanbe
identifiedanddocumented.
Thetemplateisformattedtoidentifytheminimuminformationcommonly
documentedforarchitecture.Sincemanyarchitecturesvaryininfluencing
factors,technologyused,andevenintent,attemptingtoidentifyeverypotential
fieldisnearlyimpossible.However,everyarchitecturedescriptionhasgeneric
characteristicswhichshouldbeidentified.Eachcharacteristicisexplainedas
theyappear,androomisprovidedtomakenotesrelevanttoyourorganization.
ExecutiveInformation
CharacteristicExplanationNotes/Comments
NameIdentifythespecificarchitecturebyname
oruniquecodingsystem.
ScopeDescribethescopeofthearchitecture,
whatitdoes,whoisinvolved,howitwill
impacttheenterprise.Thischaracteristic
definestheboundariesforusingthe
architecturewithinthebusiness
environment.
BusinessGoalsIdentifythespecificgoalswhichthe
architectureaddresses.
BusinessDriversIdentifytheinfluencingfactorsonthe
developmentandimplementationofthe
architecturefromabusinessperspective,
suchascompetitiveadvantage,cost
efficiency,etc.
ConstraintsIdentifythoseconstraintsonthespecific
architecture,suchasfunding,lackof
expertise,time,etc.
StakeholdersIdentifytheprimarystakeholdersofthe
architecture.Requirementsforthe
architecturewillbeginwiththese
individuals.
StatementofWorkIdentifytheapprovedstatementofwork
allowingthedevelopmentand
implementationofthisspecific
architecture.Thischaracteristicisused
toprovidetrackingandaccounting
capabilitiesfordecisionsacrossthe
enterprise.
ArchitecturalInformation
CharacteristicExplanationNotes/Comments
BusinessArchitecture
ArchitectureGoals
andObjectives
Definethespecificgoalsandobjectives
ofthearchitecture.Thesemustbe
alignedwiththeBusinessGoals
describedintheprevioussection.
BusinessFunctionDescribethebusinessfunctionthatthe
architecturewillprovideorsupport.
LocationsDefinethelocationswherethe
architecturewillbeimplemented.
OrganizationsDefinewhatorganizationswillbe
expectedtoutilizethearchitecture.
RolesDefinethekeyrolesinvolvedinthe
fulfillmentofarchitecturegoalsand
objectives.
Process/ProductDefinetheprocessesand/orproducts
resultingfromorimpactedbythe
implementationofthearchitecture.
BusinessServices/
Interactions
Definethebusinessservices/interactions
createdorsupportedbythearchitecture.
DependenciesDefinethedependenciesforthe
architectureforcomponentsoutsidethe
scopeofthework.
DataArchitecture
DataEntity/Data
Components
Listthespecificdataentities/data
componentsusedbythearchitecture.
BusinessFunction
Mapping
Identifywhichbusinessfunctionsare
supportedbythelisteddataentities/
components.
Applications/DataIdentifywhichapplicationsareusedto
access,manage,anddisplayeachdata
entity/component.
DataModelProvideavisualrepresentationofthe
relationshipbetweendataentities/
components,businessfunctions,and/or
applications.Therequiredinformation
maybeexternaltothedescriptionand
thelinksareprovidedhere.
DataSecurityDefinethelevelofsecurityrequiredand
howitwillbehandledwithinthis
architecture.
DataMigrationDefinehowdatamigrationwillbehandled
withinthearchitecture,eitherwiththe
initialimplementationorwithongoing
operations.
DataLifecycleDefinetherequirementsrelevantto
maintainingdata,addressingtopicsof
retention,archiving,anddisposalofdata.
ApplicationArchitecture
InterfacesDescribetheapplicationinterfaces
available,whethertheyareclient-based,
web-based,orsystem-based.
UserRolesand
Locations
Identifythevariousroleswithinthe
applicationandwherethoserolesare
geographicallylocatedwithinthe
organization.
CommunicationDescribetheintendedcommunication
flowbetweenapplications.
Use-CasesIdentifyhowtheapplicationwillbeused
byitsusers.Therequiredinformation
maybeexternaltothedescriptionand
thelinksareprovidedhere.
SoftwareEngineeringDescribetheapplicationintermsof
packages,modules,services,and
operationstoaidinitsdevelopment.The
requiredinformationmaybeexternalto
thedescriptionandthelinksareprovided
here.
SoftwareDistributionDescribehowtheapplicationsoftwareis
structuredanddistributedacrossthe
enterprise.Therequiredinformationmay
beexternaltothedescriptionandthe
linksareprovidedhere.
ApplicationMigrationDescribehowtheapplicationwillmigrate
fromitsbaselineconfigurationtoitstarget
configuration.Therequiredinformation
maybeexternaltothedescriptionand
thelinksareprovidedhere.
TechnologyArchitecture
PlatformIdentifythetechnologyplatformtobe
usedbythearchitecture.
TechnologyStandardsIdentifythetechnologystandardsthat
mustbeadheredto.
LocationCapabilitiesDefinetheconstraintsandopportunities
availablebasedonlocation,i.e.alocation
maynotsupporttherecommended
technologycomponents.
BuildsIdentifyanddescribethevarious
hardwareconfigurationbuildstobeused.
Therequiredinformationmaybeexternal
tothedescriptionandthelinksare
providedhere.
NetworkingDescribethenetworkingrequirements
associatedwiththetechnology.Theymay
includedetailedinformationabout
storageandprocessingrequirementsas
well.
LogicalComponentsListthelogicalcomponentstobe
implemented.
PhysicalComponentsListthephysicalcomponentstobe
implemented.
BlankTemplate
CharacteristicExplanationNotes/Comments
|
|
