) What kind of system thinking should we use to understand SharePoint and its value?

What kind of system thinking should we use to understand SharePoint and Its Value glossary?

SharePoint refers to Microsoft's SharePoint service, Sharepoint Foundation, and Sharepoint Server. This is a series of technologies, products, and solutions launched by Microsoft for interconnection and collaborative sharing. The latest version is 2010, which is divided into two products: SharePoint Foundation 2010 (free of charge) and Sharepoint Server 2010 (paid)

The official SharePoint homepage is on

Http://sharepoint.microsoft.com/zh-cn/Pages/default.aspx

 

Introduction

A lot of things may take time to understand before they can be evaluated more appropriately. This statement is applicable in many places, such as Sharepoint. Because of my work relationship, I have reached many customers and spent a lot of time helping these customers understand, evaluate, and implement Sharepoint. You know, sometimes this process is not very easy, and of course there are many experiences here. I have organized some materials and shared them today. My central idea (which is also the most emphasized by the Decision-Making layer of many clients) is:What we need is a systematic thinking with a general picture..

 

I. Summarize the core values of SharePoint in one sentence

The most concise sentence I have summarized is: Sharepoint is an idea about sharing and collaboration --Share is point. As a set of services and software, it has a relatively short history, but if you really understand its changes, you will find that the topic within it has not changed.

Expand it. Take SharePoint 2010 as an example to define SharePoint as follows:It is an information collaboration platform that can be used internally or externally..

 

2. Understanding SharePoint with System Thinking

I generally look at SharePoint from four perspectives and talk about the six major features of SharePoint and its integration with other external systems.

 

First, we should lookBasic Technical ArchitectureThis is to makeCTO (Technical Director)Evaluate the maturity and reliability of the technology platform, the relationship with other infrastructure products, the ability to continue expansion in the future, and the overall cost of ownership (TCO ).

Then, I will expandO & M and ManagementThe main differenceIt O & M DepartmentDiscuss and understand SharePoint deployment models, three-tier architecture, service architecture, and the possibility of Server Load balancer.

 

From the third point of viewDeveloper perspectiveI will talk about the development model and three different development methods. It is very important to select an appropriate development strategy.

Finally, I will talk aboutUser perspectiveWhat SharePoint means. Such as the concept of web pages and content, page personalization, use of lists and documents and other functions.

 

The above four view of SharePoint, then you can better understand the functionality, refer

 

In addition, Sharepoint can be combined with many other products, such

 

I have prepared a handout from me. If you need it, you can download it at the address below.

Use System thinking tool sharepoint2010.pdf

 

Iii. Some suggestions for enterprises when introducing SharePoint

The following points are emphasized and discussed in detail.

1. The introduction of Sharepoint is a system project. It is not simply a matter of installing software. It is not a matter of IT departments, but should be upgraded to the informatization level.
2. SharePoint and Lotus are not comparable. I am not very familiar with the specific functions of Lotus and its development in recent years, but I know that SharePoint has been recognized by more and more customers and users since version 2007.
3. You must have a full-time and professional SharePoint administrator and a small enterprise. You can set up one person. For medium and large enterprises, you also need to set up multiple users.
4. Usage habits may change. When Sharepoint is used, the general habit should be to collect and publish information centered on SharePoint, this may be slightly different from the traditional method of using client software or dedicated business systems.
5. Custom development should be evaluated in a proper manner, and Development should be conducted only if necessary on the premise of understanding the existing functions.
6. Integration with external application systems should be implemented through the BCS (Business connectivity Service) + SSS (secure Store service) service architecture as much as possible
7. Workflow support. By default, some templates are available in Sharepoint, which has been greatly improved in 2010. However, there is still room for improvement for complicated workflows or workflow systems. However, I think the default template (or some design with SharePoint designer) can meet the requirements of a department-level workflow.
8. Currently, the support for mobile devices is relatively simple.
9. The permission may not be very fine-grained. I know that many enterprises also have some special permission control policies. here we need to evaluate the problem of degree. Because Sharepoint is designed for sharing and collaboration.

4. Some questions about SharePoint for individuals

In addition to the topics discussed above, I often receive consultations from some personal netizens, mainly including the following questions:

1. Is there a future for learning SharePoint?To be honest, this question is like a friend who often asked me to say, "Learn. net has a future ", you can skip this question, because my answer is basically: Yes. This is by no means perfunctory. In fact, the sub-line is that no matter what technology, you will have a future if you master it at the right time and apply it to your knowledge.
2. I feel that I have to learn a lot and I don't know how to do it. What should I do?? This is a practical problem. Many people feel this way. I think if your company attaches great importance to it, you 'd better find the nearest and professional training institution for systematic study, microsoft also has this Certification Exam (http://www.microsoft.com/learning/en/us/certification/cert-sharepoint-server.aspx#tab1), you can test your knowledge through the exam. Of course, you can also learn by yourself. You can buy some books by yourself (both in foreign countries and in China). Then Microsoft also provides some official training materials, example (http://blogs.technet.com/ B /ldusolier/archive/2011/10/18/sharepoint-training-kits.aspx)

 

Summary

In this article, I hope to help you better understand SharePoint from the perspective of the system. I have provided some materials and made some improvements to enterprise and individual concerns and problems. It is hoped that it can be a reference for the enterprise's decision-making layer, management and development personnel, users, or simply SharePoint enthusiasts.

 

Address: http://www.cnblogs.com/chenxizhang/archive/2011/11/20/2256344.html

Glossary

SharePoint refers to Microsoft's SharePoint service, Sharepoint Foundation, and Sharepoint Server. This is a series of technologies, products, and solutions launched by Microsoft for interconnection and collaborative sharing. The latest version is 2010, which is divided into two products: SharePoint Foundation 2010 (free of charge) and Sharepoint Server 2010 (paid)

The official SharePoint homepage is on

Http://sharepoint.microsoft.com/zh-cn/Pages/default.aspx

 

Introduction

A lot of things may take time to understand before they can be evaluated more appropriately. This statement is applicable in many places, such as Sharepoint. Because of my work relationship, I have reached many customers and spent a lot of time helping these customers understand, evaluate, and implement Sharepoint. You know, sometimes this process is not very easy, and of course there are many experiences here. I have organized some materials and shared them today. My central idea (which is also the most emphasized by the Decision-Making layer of many clients) is:What we need is a systematic thinking with a general picture..

 

I. Summarize the core values of SharePoint in one sentence

The most concise sentence I have summarized is: Sharepoint is an idea about sharing and collaboration --Share is point. As a set of services and software, it has a relatively short history, but if you really understand its changes, you will find that the topic within it has not changed.

Expand it. Take SharePoint 2010 as an example to define SharePoint as follows:It is an information collaboration platform that can be used internally or externally..

 

2. Understanding SharePoint with System Thinking

I generally look at SharePoint from four perspectives and talk about the six major features of SharePoint and its integration with other external systems.

 

First, we should lookBasic Technical ArchitectureThis is to makeCTO (Technical Director)Evaluate the maturity and reliability of the technology platform, the relationship with other infrastructure products, the ability to continue expansion in the future, and the overall cost of ownership (TCO ).

Then, I will expandO & M and ManagementThe main differenceIt O & M DepartmentDiscuss and understand SharePoint deployment models, three-tier architecture, service architecture, and the possibility of Server Load balancer.

 

From the third point of viewDeveloper perspectiveI will talk about the development model and three different development methods. It is very important to select an appropriate development strategy.

Finally, I will talk aboutUser perspectiveWhat SharePoint means. Such as the concept of web pages and content, page personalization, use of lists and documents and other functions.

 

The above four view of SharePoint, then you can better understand the functionality, refer

 

In addition, Sharepoint can be combined with many other products, such

 

I have prepared a handout from me. If you need it, you can download it at the address below.

Use System thinking tool sharepoint2010.pdf

 

Iii. Some suggestions for enterprises when introducing SharePoint

The following points are emphasized and discussed in detail.

1. The introduction of Sharepoint is a system project. It is not simply a matter of installing software. It is not a matter of IT departments, but should be upgraded to the informatization level.
2. SharePoint and Lotus are not comparable. I am not very familiar with the specific functions of Lotus and its development in recent years, but I know that SharePoint has been recognized by more and more customers and users since version 2007.
3. You must have a full-time and professional SharePoint administrator and a small enterprise. You can set up one person. For medium and large enterprises, you also need to set up multiple users.
4. Usage habits may change. When Sharepoint is used, the general habit should be to collect and publish information centered on SharePoint, this may be slightly different from the traditional method of using client software or dedicated business systems.
5. Custom development should be evaluated in a proper manner, and Development should be conducted only if necessary on the premise of understanding the existing functions.
6. Integration with external application systems should be implemented through the BCS (Business connectivity Service) + SSS (secure Store service) service architecture as much as possible
7. Workflow support. By default, some templates are available in Sharepoint, which has been greatly improved in 2010. However, there is still room for improvement for complicated workflows or workflow systems. However, I think the default template (or some design with SharePoint designer) can meet the requirements of a department-level workflow.
8. Currently, the support for mobile devices is relatively simple.
9. The permission may not be very fine-grained. I know that many enterprises also have some special permission control policies. here we need to evaluate the problem of degree. Because Sharepoint is designed for sharing and collaboration.

4. Some questions about SharePoint for individuals

In addition to the topics discussed above, I often receive consultations from some personal netizens, mainly including the following questions:

1. Is there a future for learning SharePoint?To be honest, this question is like a friend who often asked me to say, "Learn. net has a future ", you can skip this question, because my answer is basically: Yes. This is by no means perfunctory. In fact, the sub-line is that no matter what technology, you will have a future if you master it at the right time and apply it to your knowledge.
2. I feel that I have to learn a lot and I don't know how to do it. What should I do?? This is a practical problem. Many people feel this way. I think if your company attaches great importance to it, you 'd better find the nearest and professional training institution for systematic study, microsoft also has this Certification Exam (http://www.microsoft.com/learning/en/us/certification/cert-sharepoint-server.aspx#tab1), you can test your knowledge through the exam. Of course, you can also learn by yourself. You can buy some books by yourself (both in foreign countries and in China). Then Microsoft also provides some official training materials, example (http://blogs.technet.com/ B /ldusolier/archive/2011/10/18/sharepoint-training-kits.aspx)

 

Summary

In this article, I hope to help you better understand SharePoint from the perspective of the system. I have provided some materials and made some improvements to enterprise and individual concerns and problems. It is hoped that it can be a reference for the enterprise's decision-making layer, management and development personnel, users, or simply SharePoint enthusiasts.

 

Address: http://www.cnblogs.com/chenxizhang/archive/2011/11/20/2256344.html