Peer Inspections: A Pragmatic ViewSoftware Peer Inspection: A formal review of a work product by peers. A standard process is followed with the aim of detecting defects early in the development life cycle. Aims to detect and eliminate software development defects efficiently and early, while defects are less costly to fix. Appears to be an effective approach to improving software quality. But it’s not PANACEA! Inspections for: Checking consistency, feasibility and understandability of artifacts at different stages Checking key use cases against measurable parameters - milestone demonstrations Checking compliance with requirements Studying metrics related to changes Inspections using automated tools Benefits and disadvantages of peer inspections: important components are reviewed by key stakeholders Not all artifacts can be inspected at once and cost factor Major issues related to performance, concurrency found through modeling, experimentation .The return on investment for meetings and inspections is questionable. Everyone is responsible for quality assurance. two hours Requires advance preparation The critical component merits inspection by several people, preferably those who have an interest in its quality, performance, or functionality. Random human inspections tend to degenerate into comments on first-order style and semantic issues. The old way and the new old have given way again to meet changing needs, driven by the insatiable demand for more software features produced faster under more competitive pressure to reduce costs.Davis' Top 30 Principles - Principles conventionalMaking quality #1High quality software is p...... middle of paper. .....Ed development environments, round trip engineeringTechnology insertion requiredComponent based, architecture first approachScope CreepUse case approach, iterative approach, demonstration based reviewRisks in conventional processes overcome by modern process : integrated risk managementToo focused on artifactsQuality control - MetricsAnalysis ParalysisUse case approachInsufficient functionEarly prototypingInsufficient performanceEarly feedback on architecture, demonstration-based evaluationTransition to a modern processSome characteristics of the modern process: Have an initial version developed early. Treat high risk areas early in the life cycle. Several iterations are developed (called spirals, increments, generations, versions). ) Focus on domain experience Process flexibility and change management Synergy and team cohesion Software process maturity