软工国外原课件06SOFABDDIntro.pptxVIP

SOFABDD;Outline;3;Identifying What’s Wrong:Smells, Metrics, SOFA(ESaaS §9.5);Beyond Correctness;Qualitative: Code Smells ;Single Level of Abstraction;Why Lots of Arguments is Bad;Program X Smells;Quantitative: ABC Complexity;Quantitative: Cyclomatic Complexity;Quantitative: Metrics;Leap Year Metrics;Revised Leap Year Metrics;15;Do One thing;17;Comments Should Describe Things That Aren’t Obvious From The Code: Why, not What (§9.4 ESaaS) (from officemate John Ousterhout);// Add one to i.i++; // Lock to protect against concurrent access.SpinLock mutex; // This function swaps the panels.void swap_panels(Panel* p1, Panel* p2) {...};Comments should be at a higher abstract level than code: # Scan the array to see if the symbol exists not # Loop through every array index, get the# third value of the list in the content to# determine if it has the symbol we are looking# for. Set the result to the symbol if we# find it.;21;Introduction to Behavior-Driven Design and User Stories(Engineering Software as a Service §7.1);Why Do SW Projects Fail?;Agile Lifecycle Review;25;Behavior-Driven Design (BDD);User Stories;Why 3x5 Cards?;Different Stakeholders May Describe Behavior Differently;Product Backlog;Related Issue;32;BDD should test app implementation;34;Points, Velocity, and Pivotal Tracker(Engineering Software as a Service §7.2);Productivity and Tools;Measuring Productivity;More on Points;More on Points;Pivotal Tracker;Pivotal Tracker;Tracker Roles;Pivotal Tracker: Features vs. Chores;Team Cyberspace Whiteboard;45;1.;47;SMART User Stories (Engineering Software as a Service §7.3);Creating User Stories;SMART Stories;Specific Measurable;Achievable;Relevant: “Business Value”;5 Whys to Find Relevance;Timeboxed;56;Rotten Potatoes should have good response time;58;Lo-Fi UI Sketches and Storyboards (Engineering Software as a Service §7.4);Building Successful UI;SaaS User Interface Design;Lo-Fi UI Example;Storyboards;Example Storyboard;Lo-Fi to HTML;66;The purpose o