1. Copyright © 2012-2014 by Mark J. Sebern Software Engineering Process I SE-2800-09 Technical Practices

2. Copyright © 2012-2014 by Mark J. Sebern Definition of Done (revisited) “Done” components Repository usage Design Reviews/inspections Testing techniques & strategies Integration/build Textbook, Table 4.1

3. Copyright © 2012-2014 by Mark J. Sebern Repository Usage Repository functions Team collaboration Backup, change mgt Feature/release mgt Repository options SVN, Git, …

4. Copyright © 2012-2014 by Mark J. Sebern Design Documentation Are your designs documented well enough to have real defects? If not, do they actually contain any useful information? How do YOU document designs?

5. Copyright © 2012-2014 by Mark J. Sebern Consider: (click for full image)

6. Copyright © 2012-2014 by Mark J. Sebern Design Documentation ExternalInternal Static Class diagram with embedded descriptions Pre- & post-conditions, invariants, behavior descriptions Dynamic Use cases and UC/sequence/acti vity diagrams State charts/diagrams

7. Copyright © 2012-2014 by Mark J. Sebern Reviews & Inspections Reviews Personal Peer Inspections Larger group or entire team

8. Copyright © 2012-2014 by Mark J. Sebern Testing Testing techniques Testing strategies Testing after development Test-driven development

9. Copyright © 2012-2014 by Mark J. Sebern Continuous Integration Repository-centric development Frequent updates merged into “master” or “development” branch Often linked to automated build/testing “Don’t break the build!”

10. Copyright © 2012-2014 by Mark J. Sebern Definition of Done (revisited) “Done” components Repository usage Design Reviews/inspections Testing techniques & strategies Integration/build Textbook, Table 4.1

11. Copyright © 2012-2014 by Mark J. Sebern Design Exercise

12. Copyright © 2012-2014 by Mark J. Sebern User Stories Choose a text document Store documents Search for "near/adjacent" keyword combinations Perform textual analysis Report analysis data Character frequency Word frequency Common n-grams ??