Chapter 3, Project Organization and Communication. A Communication Example. "Two missile electrical boxes manufactured by different contractors were joined together by a pair of wires. . Box 1. Box 2. Pair of Wires. A Communication Example (continued).
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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
"Two missile electrical boxes manufactured by different contractors were joined together by a pair of wires.
Pair of Wires
Thanks to a particular thorough preflight check, it was discovered that the wires had been reversed."
"The postflight analysis revealed that the contractors had indeed corrected the reversed wires as instructed."
In large system development efforts, you will spend more time communicating than coding
A software engineer needs to learn the so-called soft skills: technical writing, reading documentation, communication, collaboration, management, presentations.
Skills to learn
3. How the system was designed.
5. What the user really wanted.
2. How the analyst saw it.
4. As the programmer wrote it.
6. How it actually works.
Project Review: Focus on system model
Client Review: Focus on requirements
Request for clarification
Request for change
Date: Thu, 10 Oct 23:12:48 -0400
Message-ID: <[email protected]>
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.
Report number: 1291
Synopsis: The STARS client crashes when empty forms are submitted.
Subsystem: User interface
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>>
Hallway conversation (face-to-face)
Meeting (face-to-face, telephone, video conference)
World Wide Web