Ch03lect1 ud
Download as PPT, PDF0 likes405 views
The document discusses the importance of communication in software engineering projects. It describes an example where two missile electrical boxes were joined with reversed wires, which could have caused a crash. Effective communication is needed to organize large projects and avoid such issues. Project organization involves defining work products, schedules, participants, tasks, and using tools like project management software. Roles can include management, development, cross-functional, and consultants. Tasks produce work products and schedules map tasks over time using techniques like Gantt and PERT charts.
Ch03lect1 ud
- 1. UsingUML,Patterns,andJava Object-OrientedSoftwareEngineering Chapter 3, Project Organization and Communication
- 2. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 2 Pair of WiresBox 1 Box 2 A Communication Example "Two missile electrical boxes manufactured by different contractors were joined together by a pair of wires.
- 3. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 3 Box 1 Box 2 A Communication Example (continued) Thanks to a particular thorough preflight check, it was discovered that the wires had been reversed."
- 4. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 4 After the Crash... ... "The postflight analysis revealed that the contractors had indeed corrected the reversed wires as instructed."
- 5. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 5 “In fact, both of them had.” Box 1 Box 2
- 6. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 6 Communication is important 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. It’d be nice for each of you to (acquire and) demonstrate the following skills: ♦ Management: Run a team meeting ♦ Presentation: Present a major aspect of your project during its development phase. ♦ Collaboration: Negotiate requirements with the client and with members from your team and other teams. ♦ Technical writing: Write part of the documentation of your software
- 7. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 7 Have to organize well for effective communication...
- 8. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 8 Project components (developer’s perspective) ♦ Work product Piece of code, a UC model, a design document, deliverables (to the client) ... ♦ Schedule Intermediate (internal) deadlines Alpha, beta, public release dates Project management software ♦ Participant / project member Developer, tester, technical writer, product manager ... ♦ Task Design a component, test a component, fix a bug, write User’s Guide ... Issue tracking software
- 9. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 9 Project organizations ♦ Team based ♦ Interaction via reporting, decision, and communication ♦ Example organization Management team User Interface team Database team Control team
- 10. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 10 Roles ♦ Each member may assume multiple roles ♦ Role types Management roles Project manager, team leader ... Development roles System architect, object designer, implementor, tester ... Cross-functional roles API engineer, document editor, configuration manager, tester ... Consultant roles Client, end-user, application domain specialist, solution domain specialist ...
- 11. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 11 Tasks and work products ♦ Task: well-defined work assignment for a role Design a component, test a component, fix a bug, write User’s Guide ... ♦ Work product: tangible item resulting from a task Piece of code, a UC model, a design document, deliverables (to the client) ...
- 12. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 12 Schedule ♦ Mapping of tasks onto time with dependencies specified
- 13. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 13 Schedule – Gannt chart
- 14. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 14 Schedule – PERT chart Storage subsystem system analysis 1 Nov 13 5d Nov 19 Storage subsystem object design 2 Nov 20 5d Nov 26 Storage subsystem test plan 5 Nov 27 10d Dec 10 Storage subsystem implementation 3 Nov 27 15d Dec 17