book

Incremental Software Architecture

by Michael Bell

February 2016

Intermediate to advanced

272 pages

8h 49m

English

Wiley

Read now

Unlock full access

End-State Enterprise Architecture: A Risky PropositionFocus on Incremental Software ArchitectureCan Modeling and Simulation Substitute for Incremental Software Architecture?Platform for ChangeIncremental Software Architecture ProcessFinally, What Is a System?Notes
Can We Learn from Other Failures?Characterization of System FailuresNotes
Notes

Discover and Analyze System Fabric PatternsNotes
Application Discovery InstancesContinuous Application DiscoveryWhat Can Be Revealed with Application Discovery Tools?Application Identity DiscoveryApplication Architecture DiscoveryDiscovery of Application Performance and Resource UtilizationNetwork Infrastructure Discovery: Is an Application Production Ready?Asset Management DiscoveryNotes
Application Logical and Physical Topology MappingMapping Application DependencyApplication and Supporting Environment CatalogingNotes
Identifying Architecture PerspectivesKeystone Architecture Structure Classification and Decomposition DiagramDiscovering and Classifying Sub-ArchitecturesNote
Pursuing Business Analysis to Discover Sub-ArchitecturesGroup Business Services to Discover Candidate Sub-ArchitecturesEmploy Business Analysis to Discover Sub-ArchitecturesPursue Business Analysis to Classify Sub-ArchitecturesGrand-Scale Architecture Structure Classification and Decomposition: A Unified Business PerspectiveCapturing End-State Architecture Generations
A Quick Guide to Discovering Sub-ArchitecturesEnterprise End-State Architecture Technical Case StudyCarry Out Technical Profiling to Discover Architecture CapabilitiesGrouping Architecture Capabilities to Discover Sub-ArchitecturesGrand-Scale Architecture Structure Classification and Decomposition: A Unified Technical PerspectiveNotes
End-State Architecture Decomposition Driven by Business FormationsDecomposing End-State Architecture into Volatile Business SegmentsNote
End-State Architecture Environment Behavior DecompositionEnd-State Architecture Environment Behavior LevelsComponent-Level Behavior DecompositionApplication-Level Behavior DecompositionSystem-Level Behavior DecompositionEnvironment Behavior Drives End-State Architecture DecompositionFinally, End-State Architecture Decomposition: A Segmentation Process
A Shift from Software Development to Design SubstantiationPursuing Architecture Substantiation by Cross-Functional ContractsRACI ChartNotes
Scales of Environment PressuresArchitecture Structural PressuresBehavioral PressuresInduced Pressures by Volatile Architecture Areas
The Justification for Inserting Pressure PointsInserting Pressure Points in an End-State ArchitectureMethods of End-State Architecture Stress Testing
End-State Architecture Artifact StudiesData CollectionData AnalysisEnterprise Capacity Planning ModelingAn Enterprise Capacity Plan for an End-State ArchitectureNotes

Content preview from Incremental Software Architecture

Acknowledgments

Nothing could be more inspiring than a chat with a friend or a colleague who not only ponders about the world that we live in, but also bestows upon others knowledge and wisdom. Special thanks to the individuals who inspired and offered great perspectives for the completion of this book: Isabella Tugman, Lisa Nathan, Monica Roman Gagnier, Edward Kelly, David Zaffery, John Beaufait, Carlos Melendez, Sandy Tugman, and Michael Julian.