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

2. Decomposition

Software architecture is the high-level design and structure of the software system. While designing the system is quick and inexpensive compared with building the system, it is critical to get the architecture right. Once the system is built, if the architecture is defective, wrong, or just inadequate for your needs, it is extremely expensive to maintain or extend the system.

The essence of the architecture of any system is the breakdown of the concept of the system as a whole into its comprising components, be it a car, a house, a laptop, or a software system. A good architecture also prescribes how these components interact at run-time. The act of identifying the constituent components of a system is called system decomposition ...