1. PowerPoint Presentation for IS-207 Copyright 2006 © Michael W. Schaffer. All rights reserved. Slide 1 System Analysis & Design Shrink-wrap Tools and Techniques 7/16/2015 1:52:06 PM

2. Slide 2 Shrink-wrap Tools & Techniques Configuration & Release Mgmt Three-tiered Environment Defect Tracking Operational Issues

3. Slide 3 Configuration & Release Mgmt Source Code Repository Visual Source Safe, CVS, RCS, etc. Build cycles, regression testing Reproducibility Branching & Merging code lines, point releases, etc. Release Management: controlling the launch of product

4. Slide 4 Three Tier Environment - I Separate development environment for coders. Often provided in a packaged toolset. Desktop and server-based. Insulates developers (and QA) from day-to-day turbulence in the code. Provides Unit Test environment

5. Slide 5 Three Tier Environment - II Integration/Test Environment, for formal validation. Releases of code into test are controlled from the code repository with automation & tracking. Validity of Performance testing is dependent on having comparable hardware to production systems, and the ability to simulate production load.

6. Slide 6 Three Tier Environment - III Production Environment – the hardware and networks that your end-users actual use. Code is published into production in a highly controlled and scripted fashion. Launch planning …with roll-back High performance, High-availability Highly Secure Network layer, Physical security

7. Slide 7 Defect Tracking System A database and workflow system to manage reporting, repair, and measurement of defects Track all defects & enhancements Maintain focus during “endgame” Source for real metrics to demonstrate progress (or lack thereof). Bugzilla, too many to list

8. Slide 8 DTS - Workflow Defects reported by anyone. Defects triaged by QA & Release Team: duplicate report?, reproducible (create a test case)? What priority? Assigned to development to fix Tested by development (unit test), marked as fixed.

9. Slide 9 DTS – more workflow “Fixed” bugs are re-tested by QA, marked as “validated” Management then marks bugs as “closed”. Bugs also closed by management with “not a bug” Bugs can be deferred, or the fix can be a change to documentation.

10. Slide 10 Operational Issues Monitoring & Measurements Alerting Reporting, Metrics Capacity Management & Scale

11. Slide 11 IT: “Plumbing” Network Connectivity Security Operating Systems Hardware, esp Storage & Fiber Build, Buy, Outsource