1. Handling Large Projects  Project Decomposition  Stepwise Refinement Functional Decomposition Design Decomposition  Work Breakdown Structures (WBS)

2. Why to Project Decomposition  Project Decomposition F(xyz) q = F(x) q + (y) q + (z) q A complex project can be divided into simpler components. Each component is easier to handle. System development projects are decomposed into smaller components in order to provide better estimates of the amount of the amount of work involved and to monitor the and manage the various activities of the development team.

3. Stepwise Refinement  Stepwise Refinement Stepwise refinement are iterative methods because each iteration decomposes the system further. Systems Component 1Component 2Component 3 2.12.22.3 2.1.12.2.12.1.22.3.12.2.22.3.2

4. Functional Decomposition  Functional Decomposition Functional decomposition of a software project is a division of the system into its operational components as they are seen by the user. The objective is to describe is to define all the characteristics of the system from the user’s perspective.

5. Functional Decomposition

6. Design Decomposition  Design Decomposition Is a division of the system into lower level components that coincide with the actual software components of the systems. In a full design decomposition of a software system, the lowest components correspond to programming modules (e.g. procedures, subroutines, or program functions) Requirement Functional decomposition Design Decomposition.

7. Design Decomposition The best design would strive to produce independent software components or modules. Good design will strive for low coupling, high cohesion and information hiding.

8. Work Breakdown structure  WBS This is the division of the IT project into basic work components The sum total of these work components covers all the tasks that need to be performed in order to complete the project successfully. Materials Functions People

9. WBS  Project Decomposition Development tasks Managerial tasks Support tasks Administrative tasks

10. WBS

11. Task IDDescriptionStatusAssigned toComments 1.Management and Administration 2.Software development 2.1Software requirement analysis 2.2Software design 2.2.1Control logic 2.2.2Command interface …… 2.3.3.1Display formatterCompletedJoe Smith … 2.3Software coding 2.4Software integration … 3Procurement and development support See table 6.2

12. Principles of managing Software projects  OLD  Delegation  Supervision  Authority  Responsibility  NEW  Delegation  Leadership  Authority  Responsibility

13. Managing Large Projects

14. Project Reporting Techniques  Period written status report  Verbal reports  Status meetings  Product demonstrations (demo)

15. Status Reports  Status Reports Format Red flags Problems that require the immediate attention of the PM. Activities during the report period (2 weeks). This should be linked to WBS Planned activities for the next report period Major activity planned for the next report period Problems and general issues Issues not yet resolved from the last period Holidays, Vacation, New project members, etc. Date, report period, Name of report, Who is submitting the report.