Designing a Microsoft SharePoint 2010 Infrastructure Vol 1 part 5. This course is intended for IT Professionals who use Microsoft SharePoint 2010 in a team-based, medium-sized to large environment. While they may have implemented a SharePoint deployment, they have limited experience in designing a SharePoint infrastructure. They likely work as a senior administrator who acts as a technical lead over a team of administrators. Members of this audience should have at least 6 months experience with SharePoint 2010. | 1-10 Designing a Microsoft SharePoint 2010 Infrastructure Avoiding Technology-Based Design You should not focus your logical design on a given technology. Even if you are designing a SharePoint 2010 solution you may find that there are business-critical components that require additional solutions or integration. Failure to identify these may lead to a solution that does not meet business requirements. You should identify requirements that may be out-of-scope for this particular project. SharePoint 2010 has a range of great technical capabilities but you should ensure that your solution is based on business requirements not solution features. The SharePoint 2010 features may deliver the functionality that solves a business requirement but your design must always put the requirement before the feature. Avoiding Leading Questions When you prepare your questions do not make them match your preferred solution otherwise there is an increased chance that you will miss a requirement that does not fit with your predefined solution. Updating Documentation Design documentation is a set of living documents. As changes occur you must return and update plans so that you have an ongoing business and technical description of the project. If you fail to do so the documentation may become a description of the initial design which you cannot use for sign-off or rebuilds. Additional Reading For more information about SharePoint 2010 licensing see http fwlink LinkID 200849 clcid 0x409. MCT USE ONLY. STUDENT USE PROHIBITED Designing a Logical Architecture 1-11 Approaches to Requirements Gathering Methods of information gathering include Sponsor and stakeholder interviews Focus groups User interviews User questionnaires Existing business processes Rules of engagement include An agenda Time constraints Types of information include Qualitative Quantitative Review documentation Key Points When you need to find out about business requirements you must ask managers and staff
