Using UML, Patterns, and Java Object-Oriented Software Engineering Art for Chapter 14, Project Management

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 2 Figure 14-1, Phases of a Software Project Conception Definition Start Steady State do/FormulateIdea do/Problem Statement do/Project Kickoff do/Develop System GoAhead ScopeDefined && Teams System Done New Technology do/Cost-BenefitAnalysis do/FeasibilityStudy do/Review Assembled do/Infrastructure Setup Infrastructure Setup Completed do/Software Architecture do/Software Plan do/Skill Identification do/Team Formation do/Controlling do/Risk Management do/Replanning Termination do/Client Acceptance do/Delivery do/Post Mortem New Need

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 3 Figure 14-2, Management activities in a software project (continued on next slide). Initial Software Definition Project Management Plan Initial Software Architecture Start Skill Identification Conception Formulate Idea Cost-Benefit Analysis Feasibility Study Problem Statement Definition Infrastructure setupTeam assemblyProject AgreementProject Kick-off

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 4 Figure 14-2, Management activities in a software project (continued). Scope agreementProject replanning ControllingRisk management Installation Steady state Termination Client acceptance testPostmortem

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 5 Figure 14-3, Tasks, Activities and Project Functions. Task * Work Activity Project Function «invariant» duration = project.duration

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 6 Figure 14-4, Relationship between Outcome, Work, and Work Packages. produced-by * Task * Work Activity Project FunctionProject DeliverableInternal Work Product Work ProductSet of Work Products Outcome * Work Package describes

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 7 Figure 14-5, The Work Breakdown Structure is the aggregation of all the work to be performed in a project. * Task * Work Activity Work Breakdown Structure

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 8 Figure 14-6, Partial work breakdown structure for a house. Build Foundation Build Walls Build Roof Install Heating Build Structure Install PlumbingBuild House:WBS Install Sewer Pipes Install Cold & Hot Water Pipes Install Tubs & Sinks Install Electric

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 9 Figure An example of a task model with precedence dependencies Database subsystem req. elicitation Database subsystem design Database subsystem implementation Database subsystem inspection Database subsystem test plan Database subsystem test

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 10 Figure 14-8, An organization consists of organizational units, which consists of participants or groups of participants. Participant * Staff OrganizationOrganizational Unit Project * Company TeamDepartmentDivision

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 11 Figure 14-9, Types of organizations. Project-Based Organization Matrix Organization Line (Functional) Organization

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 12 Figure 14-10, Example of a organization chart for a team-based organization with three subsystem teams and two cross-functional teams. UserInterface :SubsystemTeam reports to Management :Team Documentation: CrossFunctionalTeam Architecture: CrossFunctionalTeam communicates with Database :SubsystemTeam Control :SubsystemTeam

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 13 Figure 14-11, Visualization of the organization structure from Figure with an organization chart. The reporting and communication structure are not shown explicitly.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 14 Figure 14-12, Model of a Project from a project manager’s point of view. This is a refinement of the model used in Chapter 3. * Resource Participant Fund Equipment Schedule Task * Activity con- Facility * Staff DepartmentTeam produces Work Set of Work * ProductProducts * Internal Project Work respon- sumes Package Role * des- * cribes Deliverable sible plays for Organi- zation Structure * * depends Work Product Project Function Project Outcome Work Organizational Unit Work Breakdown

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 15 Figure 14-14, Work products generated during project planning and their relationship with typical project deliverables. Problem StatementTop-level Design Organization Task Model Schedule Requirements Analysis Document (RAD) System Design Document (SDD) Software Project Management Plan (SPMP) Project Agreement Project Planning Products Deliverables

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 16 Figure 14-17, An example of an object-oriented work breakdown structure where the subsystem decomposition is used to identify high-level activities/tasks. Develop UserInterface Control Database Develop Database Subsystem Develop Control Subsystem decompositionWork Breakdown Structure UserInterface Subsystem Develop System

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 17 Figure 14-18, Assessing the financial status of a project using earned value. Current Actual cost Earned value Planned cost time Time