The document discusses software project scheduling and how to respond when management demands an impossible deadline. It describes how to create a macroscopic schedule that identifies major software engineering activities, allocates estimated effort across the planned duration, and defines responsibilities, outcomes, and milestones. It also provides an example of how adding people to a team can decrease overall productivity due to increased communication paths, and an equation for calculating effort expended based on lines of code, people, and time.

1. Software Engineering

2. What should we do when management
demands that we make a deadline that is
impossible?

3. Software project scheduling is an activity
that distributes estimated effort across the
planned project duration by allocating the
effort to specific software engineering tasks.
Macroscopic schedule- identifies all major
software engineering activities and the
product functions to which they are applied.

4.  Compartmentalization
 Interdependency
 Time allocation
 Effort validation
 Defined responsibilities
 Defined outcomes
 Defined milestones

5. Example:
four software engineers – 5000 LOC/year
…but when placed in a team
6 potential communication paths
…assume the team productivity
250 LOC/year
Therefore,
team productivity is…
20,000-(250*6)=18,500 LOC/year– 7.5%

6. …in 2 months remaining, 2 additional people
are added in team in which the
communication paths escalates to 14.
…productivity input of the new staff
840*2=1680 LOC
Team productivity…
20,000+1680-(250*14)=18,180 LOC/year

7. E = L3/( P3t4 )
where E =effort expended(person-years)
t = time duration in years

8. Consider:
A real-time software project estimated at
33,000 LOC, 12 person-years of effort.
// ~ 3.8 person-years.