1 / 15

Art for Chapter 3, Project Communication

Art for Chapter 3, Project Communication. 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.

emoore
Download Presentation

Art for Chapter 3, Project Communication

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Art for Chapter 3,Project Communication

  2. Figure 3-1. Model of a project. Project Work Product Schedule Task Participant

  3. 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

  4. Figure 3-3, A team-based organization consists of organizational units called teams, which consists of participants or other teams. * * Organization Team Participant

  5. 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

  6. Management :Team Figure 3-5, Example of reporting structure in a hierarchical organization. communicateDecision() communicateDecision() communicateStatus() communicateStatus() UserInterface Control Database :Team :Team :Team

  7. 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

  8. 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

  9. 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

  10. 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

  11. Figure 3-10, An example of schedule for the database subsystem.

  12. Figure 3-11, Schedule for the database subsystem (PERT chart).

  13. 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

  14. Figure 3-19. An example of an issue base.

  15. 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

More Related