book

Righting Software

by Juval Lowy

December 2019

Intermediate to advanced

480 pages

12h 41m

English

Addison-Wesley Professional

Read now

Unlock full access

How This Book Is OrganizedSome Assumptions About the ReaderWhat You Need to Use This BookConventions Used in This BookAdditional Online ResourcesAcknowledgments
What Is The Method?What The Method Is Not

Avoid Functional DecompositionVolatility-Based DecompositionIdentifying Volatility
Use Cases and RequirementsLayered ApproachTypical LayersClassification GuidelinesSubsystems and ServicesOpen and Closed Architectures
Requirements and ChangesComposable DesignThere Is No FeatureHandling Change
System OverviewThe Anti-Design EffortBusiness AlignmentThe ArchitectureDesign ValidationWhat’s Next?
Why Project Design?
Defining SuccessProject Initial StaffingEducated DecisionsServices and DevelopersEffort EstimationsCritical Path AnalysisScheduling ActivitiesProject CostEarned Value PlanningRoles and Responsibilities
The Network DiagramFloatsFloats-Based Scheduling
Accelerating Software ProjectsSchedule CompressionTime–Cost CurveAvoiding Classic MistakesProject Cost ElementsNetwork Compression
Choosing OptionsTime–Risk CurveRisk ModelingCompression and RiskRisk DecompressionRisk Metrics
The MissionFinding the Normal SolutionNetwork CompressionEfficiency AnalysisTime–Cost CurvePlanning and RiskSDP Review
God ActivitiesRisk Crossover PointFinding the Decompression TargetGeometric RiskExecution ComplexityVery Large ProjectsSmall ProjectsDesign by Layers
EstimationsDependencies and Project NetworkThe Normal SolutionCompressed SolutionDesign by LayersSubcritical SolutionComparing the OptionsPlanning and RiskPreparing for the SDP Review
When to Design a ProjectGeneral GuidelinesDesign of Project DesignIn PerspectiveThe Hand-OffIn PracticeDebriefing Project DesignAbout Quality
Activity Life Cycle and StatusProject StatusTracking Progress and EffortProjectionsProjections and Corrective ActionsMore on Projections
Is This a Good Design?Modularity and CostServices and ContractsFactoring ContractsContract Design MetricsThe Contract Design Challenge
The Prime DirectiveDirectivesSystem Design GuidelinesProject Design GuidelinesProject Tracking GuidelinesService Contract Design Guidelines

Content preview from Righting Software

4. Composition

Your software system’s reason for being is to service the business by addressing its customers’ requirements and needs. The previous two chapters discussed how to decompose the system into its components to create its architecture. The decomposition into components is inherently a static layout of the system, like a blueprint. During execution, the system is dynamic, and the various components interact with each other. But how do you know the composition of these components at run-time adequately satisfies all the requirements? Validating your design has to do with requirements analysis, system design, and your added value as the architect. Design validation and composition, as you will see, are intimately related. You can and ...