One of the biggest challenges I feel that we (Microsoft) face in showcasing the "value" of architecting/developing Office Business Applications is providing what I'll call "solid reference implementations" along the lines of Duwamish Books, Fitch and Mather, Global Bank, LitwareHR, other many other solutions we've released. Sure, we have the OBA Reference Architecture Packs (OBA RAPs), but, by definition, they are meant to serve as simple examples of how to leverage the OBA pattern to address a given business scenario. However, where I think they are lacking is in providing sound guidance and implementation practices around many of the architectural and implementation challenges many organizations face today in trying to deliver business value to their users. Many organizations today are asking questions like:
and tons more. So my question to you, dear reader, is what would you like to see in an OBA reference implementation? Is something like Duwamish too much? Are the OBA RAPs a step in the right direction? This is an opportunity for you to be heard.
Related posts:
1:57 am
I certainly liked the idea of Duwamish and Fitch & Mather where I could look at a full blown application and build my application by borrowing ideas from the same. Obviously with OBA there are lots of dependencies and I don’t know how they will play with packaging and deploying. There is still some reluctance on part of adopting Office as a platform for developing intranet apps. More sample apps, better to convince the management. Just my 2c…