This project is read-only.

Planifier dans SharePoint 2013

Articles TechNet sur la planification de SharePoint 2013

Les articles qui suivent abordent la planification de SharePoint 2013 et peuvent être consultés en ligne. Les rédacteurs mettent régulièrement à jour les articles dès que de nouvelles informations sont disponibles et en réponse aux commentaires des utilisateurs.

Planification des solutions
Planification de l’architecture de batterie de serveurs

Vidéos sur la planification de SharePoint 2013

Les enregistrements vidéo suivants sur la planification de SharePoint 2013 sont disponibles en ligne ou au téléchargement.

Ressources supplémentaires concernant la planification de SharePoint 2013

Les ressources suivantes consacrées à la planification de SharePoint 2013 sont disponibles auprès d’autres experts aux spécialités diverses.

http://technet.microsoft.com/fr-fr/library/cc261834.aspx

 

Learn how to govern applications for SharePoint 2013 by creating a customization policy and understanding the app model, branding, and life-cycle management.

http://technet.microsoft.com/en-us/library/dn531035.aspx

How will you manage the applications that are developed for your environment? What customizations do you allow in your applications, and what are your processes for managing those applications?

For effective and manageable applications, your organization should consider the following:

  • Customization policy   SharePoint 2013 includes customizable features and capabilities that span multiple product areas, such as business intelligence, forms, workflow, and content management. Customization can introduce risks to the stability, maintenance, and security of the environment. To support customization while controlling its scope, you should develop a customization policy.

  • Life-cycle management   Follow best practices to manage applications and keep your environments in sync.

  • Branding   If you are designing an information architecture and a set of sites to use across an organization, consider including branding in your governance plan. A formal set of branding policies helps ensure that sites consistently use enterprise imagery, fonts, themes, and other design elements.

  • Solutions or apps for SharePoint?   Decide whether a solution or an app for SharePoint would be the best choice for specific customizations.

Get developer guidance about customizing and branding SharePoint 2013 on MSDN: Build sites for SharePoint 2013.

Customization policy

Determine the types of customizations you want to allow and how to manage them. Your customization policy should include:

  • Service-level descriptions   What are the parameters for supporting and managing customizations in your environments? See Service-level agreements.

  • Guidelines for updating customizations   How do you manage changes to customizations, and how do you roll out those changes to your environments? Consider ways to manage source code, such as a source control system and standards for documenting the code.

  • Processes for analyzing   How do you understand whether a particular customization is working well in your environment, or how do you decide which ones to create, change, or retire?

  • Approved tools for customization   Consider development standards, such as coding best practices and the tools that you will to use across your organization. For example, you should decide whether to allow the use of SharePoint Designer 2013 and Design Manager, and specify which site elements can be customized and by whom.

  • Process for piloting and testing customizations   How do you test and deploy customizations? How many people should be in a pilot testing group? What are your standards for testing and validating customizations?

  • Who is responsible for ongoing support   Who will be responsible for supporting customizations in your environments—individual teams or a central group?

  • Guidelines for packaging and deploying customizations   Do you have individual packages for each, or do you include several in a feature or solution? Which customizations should be apps for SharePoint instead of solutions? How do you ensure that customizations in one environment do not affect the rest of your SharePoint implementation?

  • Specific policies regarding each potential type of customization   What types of customizations do you allow?

    For more information about kinds of customizations and their potential risks, see the Customizations table later in this article. For more information about processes for managing customizations, see the white paper SharePoint Products and Technologies customization policy. Most of this content still applies to SharePoint 2013.

  • Policies around using the App Catalog and SharePoint Store Which apps for SharePoint do you want to make available to your organization? Can users purchase apps directly? See Solutions or apps for SharePoint? later in this article for more information.

Last edited Dec 2, 2013 at 7:47 PM by EROL, version 1