资产管理是源代码控制的超集吗? [英] Is asset management a superset of source control

查看:248
本文介绍了资产管理是源代码控制的超集吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在计划源代码管理解决方案时,您是否考虑了整个资产管理.例如:图像,外部链接,内容,规格和数据?我知道有足够的努力可以使源代码控制有效地工作,但是我经常看到可以进行源代码管理,但是可以手动操纵其他相关资产.

Do you take the entire asset management into consideration when planning your source control solution. For instance: images, external links, content, specs and data? I know there enough to wrestle with in getting source control to work effectively, but I often see okay source management, but manual manipulation of the other related assets.

(已添加) 这个问题的灵感来自StackOverflow播客#36 http://blog.stackoverflow.com/2009/01/podcast -36/

(Added) This question was inspired by the StackOverflow podcast #36 http://blog.stackoverflow.com/2009/01/podcast-36/

推荐答案

内容管理,配置管理,源代码控制和普通企业控件(即SAS-70,SOX控件)之间存在一些界限.

There's are some lines between Content Management, Configuration Management, Source Code Control and ordinary enterprise controls (i.e. SAS-70, SOX controls).

两者是截然不同的,没有超集/子集的关系.

The two are distinct, there's no superset/subset relationship.

您拥有一些企业信息,并且拥有处理该信息的基础结构.

You have some enterprise information and you have the infrastructure to process that information.

企业信息是数据(未处理);这通常在内容管理器和关系数据库之间分配.

Enterprise Information is data (not processing); this is often split between Content Managers and Relational Databases.

  • 内容管理是您购买(或扩展)的应用程序.它处理半结构化"和非结构化"信息.例如,图像,链接和内容".有些人称之为资产管理".

  • Content Management is an application you buy (or extend). It handles "semi-structured" and "unstructured" information. For example, images, links, and "content". Some folks call this "Asset Management".

RDBMS是您购买的应用程序.它包含结构化信息.

RDBMS is an application you buy. It contains structured information.

普通企业控件应涵盖所有这些生产"数据-内容和RDBMS.如果没有,内容管理或RDBMS软件将无济于事.

Ordinary Enterprise controls should cover all of this "production" data -- content and RDBMS. If they don't, no amount of content management or RDBMS software will help.

基础架构正在很大程度上处理(而非数据).您必须将配置管理作为一门学科.配置管理包括所有运行时配置参数,设置,文件和诸如此类的内容以及源代码.

Infrastucture is largely processing (not data). You must apply configuration management as a discipline. Configuration management includes all of the run-time configuration parameters, settings, files and what-not as well as source code.

您的源代码控制和您的配置是企业信息资产处理的一部分.

Your source code control and your configuration is part of the processing of the enterprise information asset.

我建议您专注于配置管理-源代码,设置,参数,补丁程序等.

I suggest you focus on configuration management -- source code, settings, parameters, patches, etc.

内容(如数据库管理中的数据)是用户而非开发人员的责任.技术人员提供RDBMS或内容管理工具.但是技术人员对信息的使用不承担任何责任-最终用户拥有信息-他们可以随心所欲地使用信息.

Content, like the data in a database management, is the responsibility of the users, not the developers. Technical folks provide the RDBMS or content management tools. But technical folks do not take responsibility for the use of the information -- end users own the information -- they can do with it as they please.

内容管理(或资产管理")将是手动的.您可以购买它们的工具,但是用户需要开发自己的使用这些工具的过程.它将永远看起来像是手动的.

Content Management (or "asset management") will be manual. You can buy them tools, but the users need to develop their own processes for using those tools. And it will always seem manual.

这篇关于资产管理是源代码控制的超集吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆