by Gerrit Muller Buskerud University College e-mail: gaudisite@gmail.com www.gaudisite.nl Abstract Products and enterprises evolve over time. This presentation explores the impact of these changes on the and on the business by making (small and simple) models of life cycle aspects. Distribution This article or presentation is written as part of the Gaudí project. The Gaudí project philosophy is to improve by obtaining frequent feedback. Frequent feedback is pursued by an open creation process. This document is published as intermediate or nearly mature version to get feedback. Further distribution is allowed as long as the document remains complete and unchanged. status: preliminary draft legend automated data inputs interoperability human inputs error prone! ~3% error rate change request problem report usage context other s requirements other s life cycle context design realization
Product Related Life Cycles individual s service production sales upgrades and options production upgrades and options sales disposal creation upgrades and options creation 2 Gerrit Muller MALCproductLifeCycle
System Life Cycle order ordering components manufacturing shipping installation using local changes, e.g. accounts procedures add option maintenance upgrade using sales shipping refurbishing shipping installation secondary use maintenance dispose 3 Gerrit Muller MALCLifeCycle
Approach to Life Cycle Modeling Identify potential life cycle changes and sources Characterize time aspect of changes Determine required effort Determine impact of change on and context Analyse risks how often how fast amount type performance reliability business see reasoning 4 Gerrit Muller MALCapproach
What May Change During the Life Cycle? www.homes4sale.com business volume www.apple.com/itunes/ product mix www.amazon.com product portfolio www.ebay.com product attributes (e.g. price) www.shell.com customers www.stevens.edu personnel www.nokia.com suppliers stock market application, business processes insurance company et cetera local Dutch cheese shop 5 Gerrit Muller MALCchanges
Simple Model of Data Sources of Changes usage context other s requirements design realization legend automated data inputs interoperability human inputs error prone! ~3% error rate other s life cycle context change request problem report 6 Gerrit Muller MALCsources
Data Sources of Web Server client content preparation content web server data quality? content content content provider provider provider shop configuration e.g., staff, roles configuration e.g. resource allocation 7 Gerrit Muller MALCwebServerChanges
Example Product Portfolio Change Books sales info product portfolio characteristics O'Reilly Addison Wesley Springer publisher selection selection depends on business life cycle changes determined by business characteristics new books per year source: http://en.wikipedia.org/wiki/long_tail UK (1) USA(2) China(3) 206k (2005) 172k (2005) 107k (1996) 68k (1996) 101k (1994) sales WH Smith Amazon "long tail" India(21) 12k (1996) source: http://en.wikipedia.org/wiki/books_published_per_country_per_year item 8 Gerrit Muller MALCbookExample
Example Customer Change internet: broadband penetration growth in Q1 '04 Q2 '04 Q2 '04 Asia Pacific total 48M 54M 12.8% China 15M 19M 26.1% India 87k 189k 116.8% http://www.apira.org/download/world_broadband_statistics_q2_2004.pdf What is the expected growth of # customers? What is the impact on and infrastructure? What is the impact on CRM (Customer Relation Management)? What is the impact on customer, sales support staff? 9 Gerrit Muller MALCcustomerExample
Web Shop Content Update screen screen How much time/effort is needed for content updates? client client How much staff is needed? What is the impact of errors in content updates? network How many errors can be expected? What is the impact of content updates on server loads? web server network publication new content and updates content definition data base server product descriptions logistics ERP financial customer relations 10 Gerrit Muller MALCwebShopContentUpdate
Web Shop Content Change Effort prepare change 1 review input select info layout&cosmetics check-in prepare change 2 prepare change n effort changes = n changes *(t prepare + t verify )+t commit verify change 1 inspect source inspect result verify change n commit changes #fte = effort changes / hours per day n changes per day 10 100 effort changes 1 uur 10 uur 1000 100 uur #fte 0.1 1 12 with t prepare t verify t commit = 4 min = 2 min = 1 min hours per day = 8 hours 11 Gerrit Muller MALCeffortContentChanges
Example of Client Level Changes main access through search personalization catalogue entries Up-to-date information: Bestsellers What Other Customers Are Looking At Right Now other advertizements styling: frequently updated, fashion! standard boilerplate snapshot of www.amazon.com 12 Gerrit Muller MALCmoreChanges
Example of Time Scale Model for Changes problem response workstation useful life MR scanner useful life clinical prototype procedural change legislation change 3 months 1 year 10 years commodity hardware and software new generation of magnets gradients detectors minor SW release major SW release 13 Gerrit Muller HMPAlifecycles
Web Shop Security and Changes public internet protected production area web server screen client network screen client What is the security model? What is the impact on server loads? What is the impact on staffing? What is the impact of changes in staff? What is the impact of changes on security? data base server very secure intranet network product descriptions logistics ERP financial content definition customer relations 14 Gerrit Muller MALCwebShopSecurity
Web Shop Reliability and Changes new faults = average fault density * #changes severity hit probability detection probability #errors = faults f( severity, hit probability, detection probability) Jansen iso Janssen operator iso sales repr low high high high low medium 15 Gerrit Muller MALCreliability