150 likes | 164 Views
Learn the key communication models, team structures, and work products to enhance project collaboration for successful outcomes. Explore various organizational and communication concepts, roles, and scheduling techniques to streamline project progress and management. Identify communication mechanisms and issue resolution methods to ensure smooth project execution.
E N D
Figure 3-1. Model of a project. Project Work Product Schedule Task Participant
Figure 3-2, States of a software project. Scope Defined Start Definition do/Assign Tasks do/Define Scope Tasks Assigned Termination Steady State do/Deliver System do/Develop System System Done
Figure 3-3, A team-based organization consists of organizational units called teams, which consists of participants or other teams. * * Organization Team Participant
Simple Project :Organization Figure 3-4, Example of a simple project organization. Reporting, deciding, and communicating are all made via the aggregation association of the organization. Management UserInterface Database Control :Team :Team :Team :Team
Management :Team Figure 3-5, Example of reporting structure in a hierarchical organization. communicateDecision() communicateDecision() communicateStatus() communicateStatus() UserInterface Control Database :Team :Team :Team
Figure 3-6, Example of a organization with a liaison-based communication structure. UserInterface :Team communicates Alice Management: :Developer Team team leader communicates John Architecture: :Developer Team API engineer communicates Mary Documentation: :Developer Team documentation liaison communicates Chris Testing: :Developer Team implementor Sam :Developer implementor
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 Solution Domain Specialist Consultant Client End User
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
Figure 3-9, Associations among tasks, activities, roles, work products, and work packages. describes results in Work Package Work Product * Unit Of Work 1 Activity Task * 1 Role assigned to
Figure 3-10, An example of schedule for the database subsystem.
Figure 3-11, Schedule for the database subsystem (PERT chart).
Figure 3-12, Relationships among organizational and communication concepts. Organization assigned to Team * * responsible f or Participant 1 * Role * produces Task Work Product 1 * * * 1 Schedule mapped to 1 Communication concern appear in Planned Unplanned Communication Event Communication Event * * Request for Problem Definition Clarification Review Request for Change Release Issue Resolution
Figure 3-20, Examples of mechanisms. is supported by Client Review Smoke Signals :Planned Communication :Synchronous Mechanism is supported by Problem Reporting Fax: Asynchronous :Unplanned Communication Mechanism is supported by