Using UML, Patterns, and Java
Object-Oriented Software Engineering
Art for Chapter 3,
Project Communication
Figure 3-1. Model of a project.
Project
Work Product
Bernd Bruegge & Allen H. Dutoit
Schedule
Task
Object-Oriented Software Engineering: Using UML, Patterns, and Java
Participant
2
Figure 3-2, States of a software project.
Scope Defined
Definition
Start
do/Define Scope
do/Assign Tasks
Tasks
Assigned
Termination
do/Deliver System
Steady State
do/Develop System
System Done
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
3
Figure 3-3, A team-based organization consists of
organizational units called teams, which consists of
participants or other teams.
Organization
Bernd Bruegge & Allen H. Dutoit
*
Team
*
Object-Oriented Software Engineering: Using UML, Patterns, and Java
Participant
4
Figure 3-4, Example of a simple project organization.
Reporting, deciding, and communicating are all made
via the aggregation association of the organization.
Simple Project
:Organization
Management
:Team
Bernd Bruegge & Allen H. Dutoit
UserInterface
:Team
Database
:Team
Object-Oriented Software Engineering: Using UML, Patterns, and Java
Control
:Team
5
Figure 3-5, Example of reporting structure in a
hierarchical organization.
Management
:Team
communicateDecision()
communicateDecision()
communicateStatus()
UserInterface
:Team
Bernd Bruegge & Allen H. Dutoit
communicateStatus()
Database
:Team
Object-Oriented Software Engineering: Using UML, Patterns, and Java
Control
:Team
6
Figure 3-6, Example of a organization with a liaisonbased communication structure.
UserInterface
:Team
communicates
team leader
Alice
:Developer
Management:
Team
communicates
API engineer
John
:Developer
Architecture:
Team
communicates
documentation liaison
Mary
:Developer
Documentation:
Team
communicates
implementor
Chris
:Developer
Testing:
Team
implementor
Sam
:Developer
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
7
Figure 3-7, Types of roles found in a software
engineering project.
Developer
API Engineer
Document Editor
Liaison
Configuration
Manager
Tester
Role
Project Manager
Manager
Team Leader
Application
Domain Specialist
Consultant
Solution
Domain Specialist
Client
End User
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
8
Figure 3-8, Work products for the a database
subsystem team.
Database Subsystem
Work Products
persistent objects:Class Model
source:Source Code
design objects:Class Model
inspection defects:Document
test plan:Document
testing defects:Document
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
9
Figure 3-9, Associations among tasks, activities, roles,
work products, and work packages.
describes
Work Package
*
results in
Work Product
Unit Of Work
1
Activity
Task
*
1
assigned to
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
Role
10
Figure 3-10, An example of schedule for the database
subsystem.
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
11
Figure 3-11, Schedule for the database subsystem
(PERT chart).
Sto rage sub syst em
sys tem anal ysis
1
5d
Nov 13
Nov 19
Bernd Bruegge & Allen H. Dutoit
Sto rage sub syst em
obj ect desi gn
2
5d
Nov 20
Nov 26
Object-Oriented Software Engineering: Using UML, Patterns, and Java
Sto rage sub syst em
tes t pl an
5
10d
Nov 27
Dec 10
Sto rage sub syst em
imp leme ntat ion
3
15d
Nov 27
Dec 17
12
Figure 3-12, Relationships among organizational and
communication concepts.
Organization
assigned to
*
*
responsible for
Participant
1
*
Team
Role
*
produces
Task
1
*
1
mapped to
*
Work Product
*
Schedule
1
Communication
appear in
Planned
Communication Event *
Bernd Bruegge & Allen H. Dutoit
Unplanned
Communication Event
concern
*
Problem Definition
Request for
Clarification
Review
Request for Change
Release
Issue Resolution
Object-Oriented Software Engineering: Using UML, Patterns, and Java
13
Figure 3-19. An example of an issue base.
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
14
Figure 3-20, Examples of mechanisms.
Client Review
:Planned Communication
is supported by
Smoke Signals
:Synchronous Mechanism
is supported by
Problem Reporting
:Unplanned Communication
Bernd Bruegge & Allen H. Dutoit
is supported by
Fax: Asynchronous
Mechanism
Object-Oriented Software Engineering: Using UML, Patterns, and Java
15