Advance Software Engineering CEN5011 Project Organization and Communication

Advance Software Engineering (CEN-5011) Project Organization and Communication Fall 2004 Instructor: Masoud Sadjadi http: //www. cs. fiu. edu/~sadjadi/Classes/CEN-5011/ CEN 5011 Third Lecture (first part) September 15, 2004

Acknowledgements Overview: Motivation Dr. Bernd Bruegge Dr. Allen Dutoit Events & Mech. Planned Commu. Unplanned Com. Summary CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 2

Agenda Overview: Motivation Comm. Events & Mechanisms Planned Communication Unplanned Communication Summary Events & Mech. Planned Commu. Unplanned Com. Summary CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 3

Motivating Example Overview: Motivation Events & Mech. Planned Commu. Unplanned Com. Summary A Communication Example – Two missile electrical boxes manufactured by different contractors were joined together by a pair of wires. – Thanks to a particular thorough preflight check, it was discovered that the wires had been reversed. – After the Crash – The postflight analysis revealed that the contractors had indeed corrected the reversed wires as instructed. – In fact, both of them had. Box 1 Pair of Wires CEN 5011: Advanced Software Engineering Box 2 Third Lecture (first part) on Sept. 15, 2004 4

Communication is important Overview: Motivation In large system development efforts, you will spend more time communicating than coding A software engineer needs to learn the socalled soft skills: Events & Mech. Planned Commu. Unplanned Com. Summary – – – technical writing reading documentation communication collaboration management presentations CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 5

Term Project Objectives Overview: Motivation Events & Mech. Planned Commu. Unplanned Com. In this course, I ask each of you to (acquire and) demonstrate the following skills: Management – Run a team meeting Summary Presentation – Present your contribution to the project during its development phase. Collaboration – Negotiate requirements with the client and/or with members from your team and other teams. Technical writing – Write part of the documentation of your project. CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 6

Agenda Overview: Motivation Comm. Events & Mechanisms Planned Communication Unplanned Communication Summary Events & Mech. Planned Commu. Unplanned Com. Summary CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 7

Communication Event Overview: Motivation Events & Mech. Type of information exchange that has defined objectives and scope Planned Commu. Unplanned Com. Summary Scheduled – Planned communication – For example, review, meeting Unscheduled – Event-driven communication – For example, request for change, issue clarification, problem report CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 8

Communication mechanism Overview: Motivation Events & Mech. Tool or procedure that can be used to transmit information Planned Commu. Unplanned Com. Summary Synchronous – Sender and receiver are available at the same time. Asynchronous – Sender and Receiver are not communicating at the same time. CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 9

Classification of Communication Overview: Motivation is supported by Communication Event * Events & Mech. Communication Mechanism * Planned Commu. Unplanned Com. Planned Event Summary Unplanned Event Synchronous – Smoke signals – Hallway conversation – Meeting CEN 5011: Advanced Software Engineering Synchronous Mechanism Asynchronous – – E-Mail Newsgroups World Wide Web Lotus Notes Third Lecture (first part) on Sept. 15, 2004 10

Agenda Overview: Motivation Comm. Events & Mechanisms Planned Communication Unplanned Communication Summary Events & Mech. Planned Commu. Unplanned Com. Summary CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 11

Planned Communication Events 1 Overview: Motivation Problem Definition – Objective: Present goals, requirements and constraints. – Example: Client Presentation. – Usually scheduled at the beginning of a project. Events & Mech. Planned Commu. Unplanned Com. Summary Project Review: Focus on system model – Objective: Assess status and review system model, system decomposition, and subsystem interfaces. – Examples: Analysis Review, System Design Review. – Scheduled around project milestones and deliverables. Client Review: Focus on requirements – Objective: Brief client, agree on requirements changes. – Examples: Client Review. – Usually scheduled after analysis phase. CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 12

Planned Communication Events 2 Overview: Motivation Walkthrough (Informal) – Objective: Increase quality of subsystem. – Example: Developer presents subsystem to team members, informal, peer-to-peer. – To be scheduled by each team. Events & Mech. Planned Commu. Unplanned Com. Summary Inspection (Formal) – Objective: Compliance with requirements. – Example: Client acceptance test (Demonstration of final system to customer). – To be scheduled by project management. CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 13

Planned Communication Events 3 Overview: Motivation Status Review – Objective: Find deviations from schedule and correct them or identify new issues. – Example: Status section in regular weekly team meeting. – Scheduled every week. Events & Mech. Planned Commu. Unplanned Com. Summary Brainstorming – Objective: Generate and evaluate large number of solutions for a problem. – Example: Discussion section in regular weekly team meeting. – Scheduled every week. CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 14

Planned Communication Events 4 Overview: Motivation Release – Objective: Baseline the result of each software development activity. – Software Project Management Plan (SPMP) – Requirements Analysis Document (RAD) – System Design Document (SDD) – Object Design Document (ODD) – Test Manual (TM) – User Manual (UM) – Usually scheduled after each phase Events & Mech. Planned Commu. Unplanned Com. Summary Postmortem Review – Objective: Describe Lessons Learned. – Scheduled at the end of the project. CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 15

Agenda Overview: Motivation Comm. Events & Mechanisms Planned Communication Unplanned Communication Summary Events & Mech. Planned Commu. Unplanned Com. Summary CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 16

Unplanned Communication Events Overview: Motivation Request for clarification – The bulk of communication among developers, clients and users. – Example: A developer may request a clarification about an ambiguous sentence in the problem statement. Events & Mech. Planned Commu. Unplanned Com. Summary Request for change – A participant reports a problem and proposes a solution – Change requests are often formalized when the project size is substantial. – Example: A participant reports of a problem the air conditioner in the lecture room and suggests a change. Issue resolution – Selects a single solution to a problem for which several solutions have been proposed. – Uses issue base to collect problems and proposals CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 17

Example of Request for Clarification Overview: Motivation Events & Mech. Planned Commu. Unplanned Com. Summary From: Alice Newsgroups: cs 413. architecture. discuss Subject: SDD Date: Thu, 10 Oct 23: 12: 48 -0400 Message-ID: <325 DBB 30. 4380@andrew. cmu. edu> Mime. Version: 1. 0 Content-Type: text/plain; charset=us-ascii When exactly would you like the System Design Document? There is some confusion over the actual deadline: the schedule claims it to be October 22, while the template says we have until November 7. Thanks, Alice CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 18

Example of a Change Request Overview: Motivation Events & Mech. Planned Commu. Unplanned Com. Summary Report number: 1291 Date: 5/3 Author: Dave Synopsis: The STARS client crashes when empty forms are submitted. Subsystem: User interface Version: 3. 4. 1 Classification: missing/incorrect functionality, convention violation, bug, documentation error Severity: severe, moderate, annoying Description: <<Description of the problem>> Rationale: <<Why the change should be done>> Proposed solution: <<Description of desired change>> CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 19

Example of Issue Base Overview: Motivation Events & Mech. Planned Commu. Unplanned Com. Summary CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 20

Agenda Overview: Motivation Comm. Events & Mechanisms Planned Communication Unplanned Communication Summary Events & Mech. Planned Commu. Unplanned Com. Summary CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 21

Summary Overview: Motivation Communication Events – Planned – Unplanned Events & Mech. Planned Commu. Unplanned Com. Summary Communication Mechanisms – Asynchronous – Synchronous Important events and mechanisms – Weekly meeting – Project reviews – Online communication (discussion forum, email, web) CEN 5011: Advanced Software Engineering Third Lecture (first part) on Sept. 15, 2004 22