Here are my arguments to support this evaluation. The first one is from the point of view of system integration, and the last two ones are from software architecting and development perspectives.
- MOSS is a truely integrated collaboration environment. It brings into one place Enterprise Content Management (ECM), rich features for business management through built-in workflows and dashboards, and easy access to a variety of data sources with Business Data Catalog (BDC). Excel Services and InfoPath make MOSS environment even more tightly integrated with other products in Office 2007.
Before MOSS the enterprise world is full of many ECM systems, both proprietary and open sources. With MOSS now including ECM and taking into account the large number of SharePoint users (up to 85 million licenses sold as Tom Rizzo said in his Foreword to the book "Essential SharePoint 2007", Addison-Wesley, 2007), it can be foreseen that ECM providers now face a strong competitor.
- MOSS is built on matured and new Microsoft technologies such as ASP.NET 2.0, web part frameworks and .NET 3.0. Customzing MOSS is now much easier than customizing SharePoint 2003. Everyone who worked with SharePoint 2003 knows how painful it is to introduce a custom branding to SharePoint 2003 deployment, or to make a SP2003 site internet-facing.
It is easy to change the look-and-feel of MOSS portals with ASP.NET master pages. MOSS architecture also supports Internet-facing sites with non-Active Directory authentication mechanisms. Hawaiian Airlines and Glu Mobile’s Website are great real world success stories of MOSS sites presence on the internet.
- MOSS should not be approached like a shrinked-wrapped product. It fact, it has become a full-scale environment for enterprise computing. This environment comes with very strong out-of-box capabilities, such as the ones mentioned in section 1. above.
However, MOSS also provides lots of support for third-party development within the environment. Imagine what we can achieve if we consider MOSS as a delivery channel where end-users can access their digital resources within a rich, customizable, web-based environment, with version control, BI elements. These digital resources can be processed outputs from other line-of-business applications. Full stand-alone packages or independent software applications may be built or re-architected to take into account MOSS capabiltities. For example, they can output their reports to MOSS document libraries or dashboards and let end users consume these outputs from there. MOSS can also be used to host the productivity-layer components as proposed by Microsoft in realizing composite applications by OBAs.
With these enhancements, MOSS bring more opportunities to system integrators and ISVs. They can offer services and products with MOSS in one of the following areas:
- Deployment and integration of MOSS into existing IT infrastructure.
- Development of MOSS web parts for rich business working contexts, or components to relialize the concepts of composite applications. Microsoft has already actively promoted Office Businesss Applications (OBA) in this direction.
- Re-architecting existing products with WSS or MOSS as the delivery channel. Again, Microsoft has spent lots of effort in this direction. Many serious products such as Microsoft Visual Studio Team System/Team Foundation Server and Microsoft Project 2007 already rely on WSS as an output environment. The latest release of Microsoft BI products (PerformancePoint Server 2007) also includes WSS 3.0 and MOSS components. While observing these products are gaining more popularity, many other software vendors may follow this approach.
1 comments: