SharePoint 中的应用程序（传统意义上的）由什么组成？ [不要与Web应用程序混淆]
[注意：我没有使用“应用程序”一词来表示 SharePoint 术语中所谓的“Web 应用程序”。 “应用程序”一词是一般意义上使用的。]
在主流应用程序开发平台（如 ASP.NET、Java EE）中，有明确的应用程序概念和应用程序边界。
SharePoint 应用程序由什么组成？网站？清单？特征？图书馆？
SharePoint 解决方案可以包含多个功能。一组相关的功能可以称为应用程序吗？有没有办法定义哪些功能是相关的或相互依赖的？
这不仅仅是一个理论问题。需要围绕应用程序进行边界来测量资源利用率、控制访问、确保 SLA（性能、可用性等）、变更控制、应用程序所有权、应用程序生命周期管理等。
[NOTE: I am not using word 'Application' to mean what is called a 'Web Application' in SharePoint terminology. Word 'Application' is used in general sense.]
In mainstream application development platforms (like ASP.NET, Java EE) there is clear concept of an application and application boundaries.
What a SharePoint application is made up of? Sites? Lists? Features? Libraries?
A SharePoint solution can include more than one Features. Can a set of related Features be called an application? Is there a way to define what Features are related or inter-dependent?
This is not just a theoretical question. Boundary around application are needed for measuring resource utilization, controlling access, assuring SLAs (performance, availability etc.), change control, application ownership, application life-cycle management and more.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
一种定义可以基于托管位置。它托管在 SharePoint Server 上吗？服务器端，它可以是基于 SharePoint 对象模型构建的解决方案；客户端可以基于客户端对象模型、SOAP Web 服务或 WCF 服务。此外，基于这些范例构建的应用程序可以是 Web、Windows 或控制台应用程序或 Web 服务。性能和可用性也取决于主机变量。
在 SharePoint 中，有一个明确的边界概念，具体取决于您的分类和定义。您的困惑源于将技术与产品进行比较。 ASP.NET、J2EE 都是技术。 SharePoint 是一个基于技术堆栈构建的产品。任何基于许多底层技术构建的大型产品都与 SharePoint 没有什么不同。
从开发人员的角度来看，边界可能围绕数据表示或内容管理或两者 - 解决方案范围的直接派生。功能、定制的相互依赖性并不单独构成一个应用程序的一部分。扩展 SharePoint 可能涉及依赖现有功能或构建新功能。设计人员有权根据范围以及是否重用现有功能来定义边界。我对应用程序的定义是一个业务案例和一个技术解决方案。
您没有明确要测量哪种资源利用率，是仪器仪表还是项目管理？变更管理是开发工作项目管理的一部分。我什至不是在这里谈论服务。从这个意义上说，任何旨在修改 SharePoint 的默认或当前自定义部署的自定义解决方案都将具有由其引入的更改定义的边界。
One definition can be based on hosting location. Is it hosted on SharePoint Server? Server side, it could be a solution build on SharePoint object model; client side could be based on client object model, SOAP web srevices or WCF services. Further, an application build on these paradigms could be a web, windows or console application or a web service. Performance and availability depends on host variable too.
In SharePoint there is a clear concept of boundaries, depending on your classifications and definitions. Your confusion stems from compairing technologies with product. ASP.NET, J2EE are technologies. SharePoint is a product built on a stack of technologies. Any large scale product built on many underlying technologies is no different from SharePoint.
From dev point of view boundaries could be around representation of data or management of content or both - a direct derivative of scope of your solution. Inter-dependency of features, customisations does not constitute part of one application alone. Extending SharePoint could involve dependency on existing feautures or building new ones. It is designers prerogative to define boundaries based on scope and whether to reuse existing functionality. My definition of an application would be a business case and a technical solution.
You didn't clariy what kind of resource utilisation you want to measure, it is instrumentation or project management? Change management is part of project management for development efforts. I am not even talking about Services here. In this sense any custom solution that aims to modify the default or current customised deployment of SharePoint will have a boundry defined by the changes it is bringing in.