Designing a Microsoft SharePoint 2010 Infrastructure Vol 1 part 7. 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-30 Designing a Microsoft SharePoint 2010 Infrastructure Hardware and IT costs. Each environment which is sometimes referred to as a property requires unique configuration and thus hardware and management resources. Self-management. Users can manage their own environments rather than have a central department provision all services. Financial resource management. Multi-tenancy which is designed primarily for hosting companies is easy to define for the purpose of internal cross-charging. MCT USE ONLY. STUDENT USE PROHIBITED Designing a Logical Architecture 1-31 Lesson 3 Documenting Your SharePoint 2010 Environment Documentation is a key element of design. Commonly documentation follows the development of a solution whereby developers document the technical aspects of a design. This lesson discusses documentation of your SharePoint 2010 deployment. Documentation is an essential tool for support and ongoing solution development so you must understand what you should document in a SharePoint 2010 environment. Objectives After completing this lesson you will be able to Explain why you should document your SharePoint 2010 environment. Describe the areas of your SharePoint 2010 environment that you should document. MCT USE ONLY. STUDENT USE PROHIBITED 1-32 Designing a Microsoft SharePoint 2010 Infrastructure Why Document Your SharePoint 2010 Environment Create a readily consumable map of the solution business requirements in a SharePoint 2010 logical architecture The documentation should meet the needs of several roles Stakeholders and business users Solution architects System administrators Developers The logical architecture should be a living document Update amendments Update new functionality Generate a blueprint for administration and support __J Key Points Your documentation has several uses and you must direct it to a range of consumers. This means that you will have several layers of documentation that build on each other to describe overarching .
