Upload
royfelixadekie
View
5
Download
0
Embed Size (px)
DESCRIPTION
Software Architectural Testing
Citation preview
PowerPoint Presentation
Software Architecture Testing CT059-3.5-2Architectural Evolution and Maturation
CT059-3.5-3 Software Architecture TestingArchitectural Evolution and MaturationTopic & Structure of the lessonFeatures and CapabilitiesArchitectural Care and feeding
Slide 2 (out of 11)CT059-3.5-3 Software Architecture TestingArchitectural Evolution and MaturationLearning OutcomesBy the end of this lecture, YOU should be able to :Discuss the features and capabilities of an architectureDiscuss the factors for architectural care and feeding
Slide 3 (out of 11)CT059-3.5-3 Software Architecture TestingArchitectural Evolution and MaturationKey Terms you must be able to useIf you have mastered this topic, you should be able to use the following terms correctly in your assignments and exams:FeaturesCapabilitiesMaturationEvolution
Slide 4 (out of 11)CT059-3.5-3 Software Architecture TestingArchitectural Evolution and MaturationForces Shaping Software ArchitectureSlide 5 (out of 11)
CT059-3.5-3 Software Architecture TestingArchitectural Evolution and Maturation
Features & Capabilities
FeaturesCustomer demandE.g. We want the product to or The product should ..Should prioritizedMade clear by development team
Slide 6 (out of 11)CT059-3.5-3 Software Architecture TestingArchitectural Evolution and MaturationFeatures & CapabilitiesCapabilitiesUnderlying architectures ability to support a related set of featuresShould able to implement most or all requested features in a well defined, disciplined manner.
Slide 7 (out of 11)CT059-3.5-3 Software Architecture TestingArchitectural Evolution and MaturationFeatures & CapabilitiesTo archive this phenomenon the development team should work repeatedly on one architecture.
Through this repeated process the initial architecture matures.
Slide 8 (out of 11)CT059-3.5-3 Software Architecture TestingArchitectural Evolution and MaturationMaturation & Evolutioncyclic process sometimes the cycle must be broken when redesign & rework of existing system sometimes shortcuts must be implement to archive quick win
Slide 9 (out of 11)CT059-3.5-3 Software Architecture TestingArchitectural Evolution and MaturationArchitectural Care & FeedingTechnology Currency to avoid redesign additional benefits to the users new and improved architectureTechnology debt create long term solution should deliver on promised dateFeature without underlying capabilities
Slide 10 (out of 11)CT059-3.5-3 Software Architecture TestingArchitectural Evolution and MaturationArchitectural Care & FeedingKnown Bugs fix the known bugs use stable and proven architecture cycle of positive improvementLicense Compliance review each vendors upgrade know when your must upgrade the architecture respond in kind to keep pace
Slide 11 (out of 11)CT059-3.5-3 Software Architecture TestingArchitectural Evolution and Maturation