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

6. Motivation

Much as you design the software system, you must design the project to build the system. This includes accurately calculating the planned duration and cost, devising several good execution options, scheduling resources, and even validating your plan to ensure it is sensible and feasible. Project design requires understanding the dependencies between services and activities, the critical path of integration, the staff distribution, and the risks involved. All of these challenges stem from your system design, and addressing them properly is an engineering task. As such, it is up to you, the software architect, as the engineer in charge, to design the project.

You should think of project design as a continuation of the system design ...