locked
WSS 3.0 or MOSS 2007 or MOSS 2010 RRS feed

  • Question

  • Hi Guys,

    I have below set of requirements given by my client. Please suggest whether WSS 3.0 or MOSS 2007 or MOSS 2010 can suffice all of the requirements mentioned below. Also kindly suggest any official microsoft website where the below features can be found so that i can send it to my client too.

    Requirements:

    1. Large no. of users that are located in different geographical locations. Approx no .of users in thousands (may be sometimes concurrent access). Huge data to support. May be in terra bytes.

    2. Provides a ticketing support i.e. enhancements & bugs. The end users enters a bug, the intermediary party evaluates and then assigns to the development team. All the 3 parties are in different geographical locations. Only single ID (generated from Sharepoint for either Bug or enhancement) should flow between the three parties.

    3. The UI for work item and workflow can be customized i.e. Customization of fields of work item in User Interface and also the flow of bugs/enhancements from one state to another. In short totally customizable bug/enhancement tracker is required.

    4. Supports a Knowledge base system

    5. Facilitates chat feature between users who logs into sharepoint website and chat gets logged too automatically.

    6. Download centers where releases and user guides can be hosted.

    7. Maintain clarifications for enhancements & bugs i.e posting of notes/comments etc w.r.t a bug or enhancement.

    8. Track the current stage of enhancement or bug.

    9. Integration with Microsoft Excel/Microsoft Office. Import/Export of bugs/enhancements etc from Office products to Sharepoint is required and vice versa.

    10. Alert/Communication System. A Notification Mail should be sent out when a new bug/enhancement is filed OR when the status is changed OR a clarification is raised against an incident.

    11. An inbuilt features of outlook where mail can be sent. Dont need an outlook instance. A form inside sharepoint which support posts, forward etc and email goes to recipient. This should auto log against the bug/enhancement in database.

    12. Can i migrate the existing data of my bug tracker to the sql server database that sharepoint uses?

    Thanks

    Nitin

    Tuesday, August 3, 2010 5:36 AM

Answers

  • Nitin Hi again - I hope you are cleared with wss 3.0 and moss now sharepoint foundation is the equivalent to wss 3.0 and sharepoint to moss. If you ask experts they would recommend 2010 over 2007!!!!

    services offered in sharepoint 2010, for this check the link below of one of my blogpost:

    http://geekdeck.com/services-offered-by-microsoft-sharepoint-2010/

    hardware and software requirements of SP 2010

    http://geekdeck.com/sharepoint-2010-hardware-software-requirements/  reminding you everything is x64, literally everything when it comes to sharepoint 2010.

    Compare 2010 to 2007
    http://www.rharbridge.com/?page_id=103

    Now the question is what's new in SharePoint 2010?
    http://technet.microsoft.com/en-us/sharepoint/ee518662.aspx
    http://creese.typepad.com/pattern_finder/2009/10/whats-new-in-sharepoint-2010.html
    http://www.salfordsoftware.co.uk/content/sharepoint-2007-and-sharepoint-2010-whats-new

    MS has released all the products of 2010 like office, sharepoint, sql r2, server r2 etc etc, all of them integrate with each other and they require each others latest version to work seamlessly and to help users to take full advantage of all latest features. sharepoint 2010 goes really well with office 2010 and sql 2008 r2.


    Jibran Jamshad, Technology Consultant, Microsoft Innovation Center - Pakistan. MCT, MCPD, MS - S/W Eng Melbourne Uni. Blog - www.geekdeck.com
    Tuesday, August 3, 2010 5:44 PM
  • Office and communication server integration is better with SP 2010 (2007 I would not recommend because well.. they'll have to upgrade eventually)

    Can i migrate the existing data of my bug tracker to the sql server database that sharepoint uses --> Yes, but that will take custom development (either way). Because you need to do it with the SharePoint 2010 API. That is unless you plan to use BCS (SharePoint Server) to connect to these --> In which you - again - won't suffice with SharePoint Foundation (WSS3.0 I would not recommend, take SharePoint foundation > newer version > no more upgrade (for now))

    11. An inbuilt features of outlook where mail can be sent. Dont need an outlook instance. A form inside sharepoint which support posts, forward etc and email goes to recipient. This should auto log against the bug/enhancement in database. --> Again.. will need custom development, but is possible

    Regards,

    Jeroen


    My blog on WSS / MOSS development is found at http://jebass.blogspot.com
    • Proposed as answer by Sarbjit Singh Gill Wednesday, August 4, 2010 11:30 AM
    • Marked as answer by GuYuming Monday, August 16, 2010 1:41 AM
    Wednesday, August 4, 2010 8:06 AM

All replies

  • Nitin Hi again - I hope you are cleared with wss 3.0 and moss now sharepoint foundation is the equivalent to wss 3.0 and sharepoint to moss. If you ask experts they would recommend 2010 over 2007!!!!

    services offered in sharepoint 2010, for this check the link below of one of my blogpost:

    http://geekdeck.com/services-offered-by-microsoft-sharepoint-2010/

    hardware and software requirements of SP 2010

    http://geekdeck.com/sharepoint-2010-hardware-software-requirements/  reminding you everything is x64, literally everything when it comes to sharepoint 2010.

    Compare 2010 to 2007
    http://www.rharbridge.com/?page_id=103

    Now the question is what's new in SharePoint 2010?
    http://technet.microsoft.com/en-us/sharepoint/ee518662.aspx
    http://creese.typepad.com/pattern_finder/2009/10/whats-new-in-sharepoint-2010.html
    http://www.salfordsoftware.co.uk/content/sharepoint-2007-and-sharepoint-2010-whats-new

    MS has released all the products of 2010 like office, sharepoint, sql r2, server r2 etc etc, all of them integrate with each other and they require each others latest version to work seamlessly and to help users to take full advantage of all latest features. sharepoint 2010 goes really well with office 2010 and sql 2008 r2.


    Jibran Jamshad, Technology Consultant, Microsoft Innovation Center - Pakistan. MCT, MCPD, MS - S/W Eng Melbourne Uni. Blog - www.geekdeck.com
    Tuesday, August 3, 2010 5:44 PM
  • Thanks jibran for the information.

    Well, i have one straight questions in front of me:

    1. The 12 features that i have listed in my first post are possible to implement if i use WSS 3.0 ? I am asking this because if all my 12 requirements can be fulfilled with free component, then i may not look forward to tell my client to invest in sharepoint server. 

    Wednesday, August 4, 2010 6:02 AM
  • Office and communication server integration is better with SP 2010 (2007 I would not recommend because well.. they'll have to upgrade eventually)

    Can i migrate the existing data of my bug tracker to the sql server database that sharepoint uses --> Yes, but that will take custom development (either way). Because you need to do it with the SharePoint 2010 API. That is unless you plan to use BCS (SharePoint Server) to connect to these --> In which you - again - won't suffice with SharePoint Foundation (WSS3.0 I would not recommend, take SharePoint foundation > newer version > no more upgrade (for now))

    11. An inbuilt features of outlook where mail can be sent. Dont need an outlook instance. A form inside sharepoint which support posts, forward etc and email goes to recipient. This should auto log against the bug/enhancement in database. --> Again.. will need custom development, but is possible

    Regards,

    Jeroen


    My blog on WSS / MOSS development is found at http://jebass.blogspot.com
    • Proposed as answer by Sarbjit Singh Gill Wednesday, August 4, 2010 11:30 AM
    • Marked as answer by GuYuming Monday, August 16, 2010 1:41 AM
    Wednesday, August 4, 2010 8:06 AM
  • I think you are talking about a Bugs Lifecycle Management Portal we have implemented it some time back with SharePoint 2007, the only feature out of those 12 was the chat one which was not the part of that portal however other features were. We did it through MOSS but later i realized that 90% of that work would have been easliy done with WSS. Considering the fact that WSS is free and MOSS has a huge cost or now in 2010 Foundation is free and SharePoint has a cost its worth it to have it developed using the free version and yes there can come a few places like the chat one where things are easy to be done in the product rather than the foundation but at that time one can consider asking developers to write few lines and go an extra mile as you are already saving a lot of $$$ even the customization usually comes incase of the full product soo than its $$$$ + $$, you have to spent twice :).

    I would certainly say that WSS or Foundation is strong enough to cater your functionality and when one is stuck than customization can be done easily or one can buy any 3rd party component. 


    Jibran Jamshad, Technology Consultant, Microsoft Innovation Center - Pakistan. MCT, MCPD, MS - S/W Eng Melbourne Uni. Blog - http://geekdeck.com
    Wednesday, August 4, 2010 2:19 PM
  • Thanks Jibram.

    But two thing to considers in this are

    1. how can external users (not sitting in domain/network) can access WSS web interface? i.e WSS will be installed on my windows server where we develop and external users are not in my network. they may be in china, japan etc.

    2. what is the requirement of CALs for question 1 above? I know that WSS is free but a windows CAL is required to access WSS from client PCs

     

    Thursday, August 5, 2010 12:44 PM
  • Accessing WSS from outside the netowork is technically not an issue and can be easily accessed just like anyother web portal.

    Secondly for the licensing WSS is free but its an addon on top of Windows Server so for extranet users it would be depending upon the Windows Server CALS,  you definitely would be needing CALS for outsiders but it wont be a WSS CAL but rather Windows Server CALs.

    Now at this point you need to get engage with MSFT Account Managers to as they will suggest you best licensing solution.


    Jibran Jamshad, Technology Consultant, Microsoft Innovation Center - Pakistan. MCT, MCPD, MS - S/W Eng Melbourne Uni. Blog - http://geekdeck.com
    Friday, August 6, 2010 7:57 AM