SoftwareDesign

SoftwareDesign - • Metaphor –shared story •...

Info iconThis preview shows pages 1–13. Sign up to view the full content.

View Full Document Right Arrow Icon
Design
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Software Life Cycle Analysis Design Implementation Testing Deployment
Background image of page 2
Software Life Cycle Analysis Design Implementation Testing Deployment
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Software Life Cycle Analysis what requirements document Design how description of classes and relationships Implementation completed program Testing test report Deployment installation
Background image of page 4
Spiral/Iterative
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Extreme / Agile Programming Strive for simplicity by removing formal structure and focusing on best practices
Background image of page 6
Extreme/Agile Programming Ken Beck Extreme Programming Explained
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Best Practices Realistic planning Small releases
Background image of page 8
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 10
Background image of page 11

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 12
Background image of page 13
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: • Metaphor –shared story • Simplicity • Testing – customers write test cases, too. • Refactoring (Martin Fowler) Best Practices • Pair programming • Collective ownership • Continuous integration • 40 hour week • On-site customer • Coding standards self-documenting code OOD • Discover classes • Determine responsibilities of classes • Describe relationships between classes CRC • Class • Responsibilities • Collaborations Relationships • Uses • Has-a • Is-a Design eBay...
View Full Document

Page1 / 13

SoftwareDesign - • Metaphor –shared story •...

This preview shows document pages 1 - 13. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online