CS 446 QUESTIONS AND CORRECT
ANSWERS
HowA2toA2chooseA2differentA2design?(4)A2-A2Ans--1.A2fitnessA2forA2purpose
2.A2costA2ofA2production
3.A2costA2ofA2operation
4.A2fitnessA2forA2future
RoleA2ofA2DesignerA2-A2Ans--takeA2radicalA2problemsA2andA2turnA2intoA2normalA2problems
DesignA2&A2SoftwareA2ArchitectureA2-A2Ans--
AllA2architectureA2isA2designA2butA2notA2allA2designA2isA2architecture
architectureA2is:(3)A2-A2Ans--1.A2allA2aboutA2communication
2.A2whatA2'parts'A2areA2there
3.A2howA2doA2theA2'parts'A2fitA2together
architectureA2isA2not:(3)A2-A2Ans--1.A2aboutA2developmentA2(implementation)
2.A2aboutA2algorithm
3.A2aboutA2dataA2structure
SoftwareA2DifficultyA2(4)A2-A2Ans--1.A2complexity:
2.A2conformity:A2systemA2isA2dependentA2onA2itsA2environment
3.A2changeability
4.A2intangibility:A2notA2constrainedA2byA2physicalA2law
incidentalA2difficultyA2-A2Ans--problemsA2thatA2canA2beA2overcome
essentialA2difficultyA2-A2Ans--problemsA2thatA2cannotA2beA2easilyA2overcome
SoftwareA2ArchitectureA2-A2Ans--
setA2ofA2principleA2designA2decisionsA2aboutA2theA2system
DesignA2Decision:(4)A2-A2Ans--1.A2structure
2.A2behavior
3.A2interaction
4.A2non-functionalA2property
StakeholdersA2ofA2systemA2architecture:(7)A2-A2Ans--1.A2architects
2.A2developers
3.A2testers
4.A2managers
5.A2customers
6.A2users
, 7.A2vendors
PrescriptiveA2Architecture:A2-A2Ans--
capturesA2designA2decisionsA2madeA2priorA2toA2theA2system'sA2construction
(thisA2needA2toA2modifiedA2first)
DescriptiveA2Architecture:A2-A2Ans--describesA2howA2theA2systemA2hasA2beenA2built
WhyA2DescriptiveA2ArchitectureA2EasilyA2GetsA2modified?(5)A2-A2Ans--
1.A2DeveloperA2sloppiness
2.A2PerceptionA2ofA2shortA2deadlinesA2whichA2preventA2thinkingA2throughA2andA2document
ing
3.A2LackA2ofA2documentedA2prescriptiveA2architecture
4.A2NeedA2orA2desireA2forA2codeA2optimization
5.A2InadequateA2techniquesA2orA2toolA2support
ArchitecturalA2Drift:A2-A2Ans--
System'sA2descriptiveA2architectureA2thatA2notA2includedA2inA2prescriptiveA2architectureA2b
utA2notA2violateA2itsA2prescriptiveA2architecture
ArchitecturalA2Erosion:A2-A2Ans--
System'sA2descriptiveA2architectureA2thatA2violatesA2itsA2prescriptiveA2architecture
ArchitecturalA2Recovery:A2-A2Ans--(DesignA2Recovery)
ProcessA2ofA2determiningA2aA2softwareA2system'sA2architectureA2fromA2itsA2implementatio
nA2levelA2artifacts
ArchitecturalA2ConfigurationA2(Topology)A2-A2Ans--
setA2ofA2specificA2associationA2betweenA2theA2componentsA2andA2connectorsA2ofA2aA2soft
wareA2system'sA2architecture
MinimizeA2CouplingA2-A2Ans--
theA2lessA2componentsA2knowA2aboutA2eachA2otherA2theA2better
MaximizeA2CohesionA2-A2Ans--ComponentsA2shouldA2responsibleA2forA2aA2singleA2service
DeploymentA2-A2Ans--
ExecutableA2modulesA2areA2physicallyA2placedA2onA2theA2hardwareA2devicesA2onA2whichA
2theyA2areA2supposedA2toA2run
DeploymentA2ViewA2-A2Ans--
assessingA2ifA2theA2systemA2willA2beA2ableA2toA2satisfyA2itsA2requirements
DecompositionA2(Top-DownA2Abstraction)A2-A2Ans--
breakA2problemA2intoA2independentA2components
ANSWERS
HowA2toA2chooseA2differentA2design?(4)A2-A2Ans--1.A2fitnessA2forA2purpose
2.A2costA2ofA2production
3.A2costA2ofA2operation
4.A2fitnessA2forA2future
RoleA2ofA2DesignerA2-A2Ans--takeA2radicalA2problemsA2andA2turnA2intoA2normalA2problems
DesignA2&A2SoftwareA2ArchitectureA2-A2Ans--
AllA2architectureA2isA2designA2butA2notA2allA2designA2isA2architecture
architectureA2is:(3)A2-A2Ans--1.A2allA2aboutA2communication
2.A2whatA2'parts'A2areA2there
3.A2howA2doA2theA2'parts'A2fitA2together
architectureA2isA2not:(3)A2-A2Ans--1.A2aboutA2developmentA2(implementation)
2.A2aboutA2algorithm
3.A2aboutA2dataA2structure
SoftwareA2DifficultyA2(4)A2-A2Ans--1.A2complexity:
2.A2conformity:A2systemA2isA2dependentA2onA2itsA2environment
3.A2changeability
4.A2intangibility:A2notA2constrainedA2byA2physicalA2law
incidentalA2difficultyA2-A2Ans--problemsA2thatA2canA2beA2overcome
essentialA2difficultyA2-A2Ans--problemsA2thatA2cannotA2beA2easilyA2overcome
SoftwareA2ArchitectureA2-A2Ans--
setA2ofA2principleA2designA2decisionsA2aboutA2theA2system
DesignA2Decision:(4)A2-A2Ans--1.A2structure
2.A2behavior
3.A2interaction
4.A2non-functionalA2property
StakeholdersA2ofA2systemA2architecture:(7)A2-A2Ans--1.A2architects
2.A2developers
3.A2testers
4.A2managers
5.A2customers
6.A2users
, 7.A2vendors
PrescriptiveA2Architecture:A2-A2Ans--
capturesA2designA2decisionsA2madeA2priorA2toA2theA2system'sA2construction
(thisA2needA2toA2modifiedA2first)
DescriptiveA2Architecture:A2-A2Ans--describesA2howA2theA2systemA2hasA2beenA2built
WhyA2DescriptiveA2ArchitectureA2EasilyA2GetsA2modified?(5)A2-A2Ans--
1.A2DeveloperA2sloppiness
2.A2PerceptionA2ofA2shortA2deadlinesA2whichA2preventA2thinkingA2throughA2andA2document
ing
3.A2LackA2ofA2documentedA2prescriptiveA2architecture
4.A2NeedA2orA2desireA2forA2codeA2optimization
5.A2InadequateA2techniquesA2orA2toolA2support
ArchitecturalA2Drift:A2-A2Ans--
System'sA2descriptiveA2architectureA2thatA2notA2includedA2inA2prescriptiveA2architectureA2b
utA2notA2violateA2itsA2prescriptiveA2architecture
ArchitecturalA2Erosion:A2-A2Ans--
System'sA2descriptiveA2architectureA2thatA2violatesA2itsA2prescriptiveA2architecture
ArchitecturalA2Recovery:A2-A2Ans--(DesignA2Recovery)
ProcessA2ofA2determiningA2aA2softwareA2system'sA2architectureA2fromA2itsA2implementatio
nA2levelA2artifacts
ArchitecturalA2ConfigurationA2(Topology)A2-A2Ans--
setA2ofA2specificA2associationA2betweenA2theA2componentsA2andA2connectorsA2ofA2aA2soft
wareA2system'sA2architecture
MinimizeA2CouplingA2-A2Ans--
theA2lessA2componentsA2knowA2aboutA2eachA2otherA2theA2better
MaximizeA2CohesionA2-A2Ans--ComponentsA2shouldA2responsibleA2forA2aA2singleA2service
DeploymentA2-A2Ans--
ExecutableA2modulesA2areA2physicallyA2placedA2onA2theA2hardwareA2devicesA2onA2whichA
2theyA2areA2supposedA2toA2run
DeploymentA2ViewA2-A2Ans--
assessingA2ifA2theA2systemA2willA2beA2ableA2toA2satisfyA2itsA2requirements
DecompositionA2(Top-DownA2Abstraction)A2-A2Ans--
breakA2problemA2intoA2independentA2components
