1. Using UML, Patterns, and Java Object-Oriented Software Engineering Art for Chapter 3, Project Communication

2. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 2 Figure 3-1. Model of a project. Project Work ProductScheduleTaskParticipant

3. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 3 Figure 3-2, States of a software project. Definition Start Termination Steady State do/Define Scope do/Assign Tasks do/Deliver System do/Develop System Scope Defined Tasks System Done Assigned

4. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 4 Figure 3-3, A team-based organization consists of organizational units called teams, which consists of participants or other teams. TeamParticipantOrganization **

5. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 5 Figure 3-4, Example of a simple project organization. Reporting, deciding, and communicating are all made via the aggregation association of the organization. UserInterface :Team Database :Team Control :Team Management :Team Simple Project :Organization

6. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 6 Figure 3-5, Example of reporting structure in a hierarchical organization. UserInterface :Team Database :Team Control :Team communicateDecision() communicateStatus() communicateDecision() communicateStatus() Management :Team

7. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 7 Figure 3-6, Example of a organization with a liaison- based communication structure. UserInterface :Team Architecture: Team Documentation: Team Alice :Developer John :Developer Mary :Developer Chris :Developer Management: Team Sam :Developer team leader API engineer documentation liaison implementor communicates Testing: Team communicates

8. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 8 Figure 3-7, Types of roles found in a software engineering project. Configuration Document Editor Tester Application Solution End User API Engineer Client Liaison Consultant Manager Team Leader Project Manager Role Developer Manager Domain Specialist

9. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 9 Figure 3-8, Work products for the a database subsystem team. design objects:Class Model source:Source Code inspection defects:Document testing defects:Document test plan:Document persistent objects:Class Model Database Subsystem Work Products

10. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 10 Figure 3-9, Associations among tasks, activities, roles, work products, and work packages. 1 * TaskActivity Unit Of Work Work PackageWork Product describes results in Role assigned to * 1

11. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 11 Figure 3-10, An example of schedule for the database subsystem.

12. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 12 Figure 3-11, Schedule for the database subsystem (PERT chart).

13. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 13 Figure 3-12, Relationships among organizational and communication concepts. Review Request for Planned Communication Event Issue ResolutionRelease Unplanned Communication Event Problem Definition Request for Change Clarification Work ProductTask Participant produces * Role Schedule Team * * mapped to 1 responsible f or * 1 assigned to * * concern * * * 1 1 appear in Organization Communication

14. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 14 Figure 3-19. An example of an issue base.

15. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 15 Figure 3-20, Examples of mechanisms. Problem Reporting :Unplanned Communication Client Review :Planned Communication Smoke Signals :Synchronous Mechanism Fax: Asynchronous Mechanism is supported by