Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
New case study in MSDN Flash - part 3
Message
De
29/12/2003 13:12:37
 
 
À
Tous
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
New case study in MSDN Flash - part 3
Divers
Thread ID:
00862569
Message ID:
00862569
Vues:
49
We've now been advised that the standard to get a case study published on microsoft.com is extremely high. I suppose that http://www.microsoft.com/resources/casestudies/casestudy.asp?CaseStudyID=14755 could be used as the yardstick for the height of the bar < s >.

Being the holiday season I've taken the liberty to re-write the "case study" (its salient points at least) deviod of political correctness and MS-speak to supply a chuckle or two...
Preamble

Faced with the need to update their stand-alone Membership Management system (because sales were saturated and existing users are no longer paying annual maintenance because it runs so reliably) to a state-of-the-art web service (hopefully this will compel users to upgrade, as well as allow us many new capabilities for on-going revenue by charging for services/transactions) XYZ Inc. is using Microsoft Visual studio .NET development system to migrate over 600 users in under 18 months.


Situation

Our user base is extremely satisfied with our present implementation. Unfortunately for us, there is no revenue stream of substance and we have been laying people off just to keep afloat!


We have been searching for ways to leverage the product to generate additional revenue and it struck us that we could piggy-back on Microsoft's heavy spending on .NET promotion to benefit ourselves. Microsoft has succeeded easily in convincing our few remaining dated-technology developers that .NET was "the wave of the future" and since our management team couldn't come up with anything sensible to increase revenue we opted to listen to them. The developers tell us that using the .NET framework we can charge per transaction, and that we can break existing transactions into multiple transactions to generate even more revenue. We sure are counting on those fine aspects of the framework!!!


Solution

XYZ wanted to web-enable their existing application (there's $$$ in them there transactions) by combining it with the power and flexibility of Microsoft ASP.NET (not that they knew ASP.NET had any such 'power', but advertising made it clear that it did).


Our client base runs Windows® operating systems and we figured that Microsoft would offer (additional) 'help' when we told them that a few have been talking Linux recently and we were right. We got several back-channel contacts to assist us with whatever we needed, all free of charge.


Fast Facts
  • Number of developers to rebuild application: 4
  • Total number of man-months to rebuild it: 72 (est.)

Benefits

XYZ company expects to finish the application in 9 MORE months. But we have already started the development of marketing material and our sales force is being expanded (well, actually, we're hiring sales people, since we had to let our others go some time ago) and is presently practising its script night and day to work out the kinks. Microsoft back-channel folks have been extremely helpful in these areas in particular! We are totally confident that our valued client base will be only too pleased to start paying us much more money than they are paying now for all of the new (well, not really new (no time for that), but repackaged) features that .NET allows us to offer them! And our development staff is real happy to actually be writing code again! They were very grateful when management bought their plan and were all sent off on 3 months of basic .NET training before we started the project.


Side-bar... Benefits
  • Faster time to market... Only 12 man-months of extensive training and 72 man-months developing, testing and implementing. How can it get any better than that!!!?
  • Better integration capabilities through Web Services... not that we needed any of that, but it seems to be the easiest way to justify charging more for the new product and charging per transaction so that we can have a reliable revenue stream in the future. And let's face it - THIS IS ALL ABOUT THE FUTURE!
  • Performance... We have no idea because we've only written half of the new system yet, but we are confident that Microsoft's marketing literature wouldn't lie (and we have our back-channel folks who can fix whatever we screw-up).
  • Scalability... well we only process 4 million transactions per year now and our present service had plenty of room to grow to triple that, but we are expecting to gain several more clients (there are 9 more out there that we can get) and our breaking up (existing) transactions into multiples will also increase the number significantly. We've never had 'scalability' problems before but Microsoft tells us it has got to be one of our key objectives, so here it is.
  • Reliability... we do know that our existing system never fails and that our users are very pleased with that state of affairs. But Microsoft assures us that our new system will be even better, when it's finally implemented.
  • Full Windows/Office integration...well we don't use any office components in our application because a few of our clients do not use office. But we fully expect to be able to convince them to install Office so that they can make full use of the new mail-merge letter that we are adding to the system.


Cheers
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform