Managing Complexity and Change with Scalable Software Design

MANAGING COMPLEXITY & CHANGE WITH SCALABLE SOFTWARE DESIGN Lodewijk Bergmans

Software engineering: a 3D balancing act

Plan of this talk ,[object Object],[object Object],[object Object],[object Object]

Challenges in software development ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

experience: complexity vs project risk source: Wallace, Keil & Rai, “Understanding software project risk: a cluster analysis”, Information & Management 42 (2004)

The only constant: Change Year maintenance costs (%) Definition Reference 2000 >90% sw.cost devoted to system maintenance & evolution / total sw. costs Erlikh (2000) 1993 75% sw. maintenance / IS budget (in Fortune 1000 companies) Eastwood (1993) 1990 >90% sw. cost devoted to system maintenance & evolution / total sw. costs Moad (1990) 1990 60-70% sw. maintenance / total MIS operating budgets Huff (1990) 1988 60-70% sw. maintenance / total MIS operating budgets Port (1988) 1984 65-75% Effort spent on sw. maintenance / total available SE effort. McKee (1984) 1981 >50% Staff time spent on maintenance / total time (in 487 organizations) Lientz & Swanson (1981) 1979 67% Maintenance costs / total sw. costs Zelkowitz et al. (1979)

proportional maintenance costs source: Banker et.al., “Software Complexity and Maintenance Costs”, CACM, Nov. 1993

Solution approach: scalable design ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Scalable design approach - technology ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Scalable design approach - people ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],source: fact 28 in R. Glass., “Facts and Fallacies of Software Engineering”, Addison-Wesley 2003

Scalable design approach - value ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Software Complexity in an Industrial Case: ,[object Object],[object Object],[object Object]

Industrial case ,[object Object],[object Object],int get_kng(KNG_struct* KNG_ptr) { const char* func_name = "get_kng"; int result = OK; timing_handle timing_hdl = NULL; TIMING_IN; trace_in(mod_data.tr_handle, func_name); if (result == OK) { /* Retrieve current KNG */ *KNG_ptr = mod_data.KNG; } HE(result, "GET_KNG FAILED"); trace_out(mod_data.tr_handle, func_name, result); TIMING_OUT; return result; } primary functionality error handling

Industrial case: approach ,[object Object],[object Object],KNG_struct get_kng() { return ( mod_data.KNG); } note: ASML focused first on only one aspect

Industrial case: how to achieve this ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Improvement potential source: Walker Royce, “Improving Software Economics”: IBM white paper (2009) costs (per person year) 10-35% 5-10% <5% 200-1000% 25-100% 15-35% 5-25% impact (productivity) 25-50%

Conclusion ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],* source:a study by The Software Technology Support Center and The Mitre Corporation

questions/discussion items ,[object Object],[object Object],[object Object],[object Object],[object Object]

Applicability of scalable design ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Wat can you do? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Scalable Design Paradox ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],source: fact 28 in R. Glass., “Facts and Fallacies of Software Engineering”, Addison-Wesley 2003

Managing Complexity and Change with Scalable Software Design

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie Managing Complexity and Change with Scalable Software Design

Ähnlich wie Managing Complexity and Change with Scalable Software Design (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Managing Complexity and Change with Scalable Software Design

Hinweis der Redaktion