23.2. Software project complexity influences estimation accuracy. Develop a list of software characteristics (e.g., concurrent operation, graphical output) that affect the complexity of a project. Prioritize the list.
23.3. Performance is an important consideration during planning. Discuss how performance can be interpreted differently depending upon the software application area.
23.5. Use the COCOMO II model to estimate the effort required to build software for a simple ATM that produces 12 screens, 10 reports, and will require approximately 80 software components. Assume average complexity and average developer/environment maturity. Use the application composition model with object points.
23.11. It seems odd that cost and schedule estimates are developed during software project planning--before detailed software requirements analysis or design has been conducted. Why do you think this is done? Are there circumstances when it should not be done?
23.12. Recompute the expected values noted for the decision tree in Figure 23.8 assuming that every branch has a 50-50 probability. Would this change your final decision?
E-mail me your answers at: cpersiko@ccsf.edu