. Jeffries00 .st Ron Jeffries (ed Larry Constantine) Card Magic for Managers Software Development Magazine V8n12(Dec 2000)pp61-62+64 =ADVERT CARDs for THINKING XP PLANNING Cards force you to be concise and modular and allow rapid reorganization. Good for planning. .cs . Adolf00? .st Steve Adolph Geting Out of the Softwae Mud Pit Software Development Magazine V8n12(Dec 2000)pp41-44 =HOWTO =HISTORY REFACTOR MAINTENANCE TECHNICAL QUALITY Big balls of mud are messy but systematic refactoring can help. refactor::=apply behavior-preserving transformations that improve code quality. Refers to William Opdyke's 1992 Doctoral thesis "Refactoring Object-oriented Frameworks" U of Illinois at Urbana-Champaign Example: Fixing Feature Envy. A pice of code in method in class A refers to several class B methods only. Therefore Replace-Code-Segment-With-Function-Call AKA Extract Method(110) an then Move-Member-Function AKA Move Method(142) .cs . Fowler00? .st Martin Fowler Put Your Procss on a Diet Software Development Magazine V8n12(Dec 2000)pp32-36 =SURVEY LITE METHODS p34: sidebar -- resources -- Crystal, Oen source, AD, Scrum, FDD( Feature Driven Develoment). New methods tend to be adaptive and people-oriented, and minimize the production of untested artefacts. Iterative development handles changing and unknown requirements. New methods may not apply tolarger teams. .cs . Minnick00 .st Chris Minnick Visualising Sicky Web Pages Software Development Magazine V8n12(Dec 2000)pp29-31 =REVIEW TOOL GRAPHIC WWW PERFORMANCE USER WebFeedback1.2 .cs Add to "Tales of Terror": Letters V8n12(Dec 2000)p11 . Holmes00a .st Neville Holmes Some Comments on the Coding of Programs IEEE Computer Magazine V33n11(Nov 2000)pp128+126+127 =IDEA TECHNICAL CODE STYLE abbreviation punctuation layout Code is not literature, even if comments should be! Can systematically abbreviate later uses of identifiers. Can line up parentheses and punctuation vertically. See p127 fig 5, .cs . BoehmPortAl-Said00 .st Barry Boehm & Dan Port & Mohammed Al-Said Avooding the Software Model-Clash Spiderweb IEEE Computer Magazine V33n11(Nov 2000)pp120-122 =IDEA SUCCESS MODELS PQRST Mbase stakeholders MasterNet Stakeholder := user | acquirer | developer | maintainer | ... | public. Each stakeholder has a different model of what is needed. Each model is a set of assumptions. Classified as process, product, property, and success. `Could use purpose, qualities, techniques, team, etc .` Clashes can occur between and wiithin different stakeholder models. Has been used two diagnose problems quickly in large and small projects. interesting spider-web diagram on p121. Mbase ::= http://sunset.usc.edu/research/MBASE. .cs . BloomBEtal00 .st Bard Bloom & Jim Russell & John Vlissides & Mark Wegman High-level Program Development Dr. Dobbs Special Report (Dec 2000)pp17-2 =ADVERT TOOLs IBM DOMAIN MODEL WORKFLOW vs PERFORMANCE Enterprise Builder, Hyper/J, Dynamic Application Partitioning (DAP) .cs . ShullLanubileBasili00 .st Forrest Shull & Filipo Lanubile & Victor R Basili Investigating Reading Techniques for Object-Oriented Framework IEEE Trans Software Engineering V26n11(Nov 2000)pp1101-1118 =EXPERIMENT TECHNICAL OBJECT-ORIENTED CODE READING C++ ET++ GRAPHICS OMT PATTERNS Using a framework is closer to maintenance than developing a new prgrm from scratch. white-box frameworks := programmer supplies specifics by deriving from abstract classes and overriding methods. 43 students ( ugrad + grad), 15 teams, 2 kinds of training, observe how 1 semester assignments (draw OMT diagrams ) was done. training := HB | EB, HB:=hierarchy based, EB := example based. observed := 5 EB + 5 EB/HB + 4 adhoc EB + 1 EB/scratch. EB better for beginners on a tight schedule but can limit the solutions. Maintaining an object model was important but caused problems when it didn't fit the framework. .cs