Software Engineering

7.3
  Step 3: Task definition and scheduling .............................................................. 132
7.4
  Step 4: Resource identification, estimation, and allocation ................................. 133
7.5
  Step 5: Establish organizational work packages ................................................. 133
7.6
  Step 6: Technical planning ............................................................................... 133
7.7
  Step 7: Project planning ................................................................................... 134
7.8
  Exploring stakeholder needs ............................................................................. 135
Software development projects are confronted with the challenge of satisfying mul-
tiple stakeholders, each of whom assert a biased perspective affecting the design 
of the software product. Each stakeholder represents an important aspect or role 
associated with the software product, such as product performance, testing, appre-
ciation for software implementation, product support, and user training. Each class 
of stakeholder views their concerns and expectations associated with the software 
product as significant features or characteristics that must be incorporated into the 
software requirements.
Each stakeholder champions different and often competing objectives, opin-
ions, and expectations that must be addressed by the software engineering inte-
grated product team (SWE-IPT) during the definition of software requirements. 
This diverse set of interests creates design challenges that necessitate the conduct 

---