Great Content Creates Great Systems
2015-09-02 09:20
120 查看

i HAvE SEEn My FAiR SHARE of initiatives focus endlessly on requirements, design, development, security, and maintenance, but not on the actual point of the system—the data. This is especially true in content-based systems in which the data is information delivered as unstructured or semi-structured content. Great content means the difference between a system that is hollow and one that is relevant.
Content is king. Content is the network. Content is the interface. In an increas- ingly interconnected world, content quality is rapidly becoming the difference between success and failure. FaceBook versus Orkut/Google versus Cuil/ NetFlix versus BlockbusterOnline…the list is endless where battles have been won and lost on the content battlefield. One could argue that content-related aspects are not the software architect’s problem—but I think the next decade will certainly disprove that.
Part of the design process for a new system should be devoted to assessing content inventory. Designing an effective domain/object/data model is not enough.
Analyze all available content and assess its value on the following criteria:
• •
Is there enough content available? If not, how do we attain critical mass? Is the content fresh enough? If not, how do we improve delivery rates?

• Have all possible content channels been explored? RSS feeds, email, and paper forms are all channels.
• Are there effective input streams built to facilitate the continual delivery of this content into the system? It’s one thing to identify valuable content, but another thing altogether to harvest it regularly.
Make no mistake, the success of a system depends on its content. Spend a healthy part of the design process to assess the value of your content. If your findings are less than satisfactory, then that’s a red flag the stakeholders must be advised about. I have seen many systems that fulfill all contractual obliga- tions, meet every requirement, and still fail because this fairly obvious aspect was ignored. Great content creates great systems.
Zubin Wadia is CEO at RedRock IT Solutions and CTO at ImageWork Tech- nologies. He has a diverse software programming background with knowledge
of Basic, C, C++, Perl, Java, JSP, JSF, JavaScript, Erlang, Scala, Eiffel, and Ruby languages. His main focus is on enabling Fortune Global 500 companies and U.S. government agencies through business process-automation solutions.
Great Content Creates Great Systems
Zubin Wadiai HAvE SEEn My FAiR SHARE of initiatives focus endlessly on requirements, design, development, security, and maintenance, but not on the actual point of the system—the data. This is especially true in content-based systems in which the data is information delivered as unstructured or semi-structured content. Great content means the difference between a system that is hollow and one that is relevant.
Content is king. Content is the network. Content is the interface. In an increas- ingly interconnected world, content quality is rapidly becoming the difference between success and failure. FaceBook versus Orkut/Google versus Cuil/ NetFlix versus BlockbusterOnline…the list is endless where battles have been won and lost on the content battlefield. One could argue that content-related aspects are not the software architect’s problem—but I think the next decade will certainly disprove that.
Part of the design process for a new system should be devoted to assessing content inventory. Designing an effective domain/object/data model is not enough.
Analyze all available content and assess its value on the following criteria:
• •
Is there enough content available? If not, how do we attain critical mass? Is the content fresh enough? If not, how do we improve delivery rates?

• Have all possible content channels been explored? RSS feeds, email, and paper forms are all channels.
• Are there effective input streams built to facilitate the continual delivery of this content into the system? It’s one thing to identify valuable content, but another thing altogether to harvest it regularly.
Make no mistake, the success of a system depends on its content. Spend a healthy part of the design process to assess the value of your content. If your findings are less than satisfactory, then that’s a red flag the stakeholders must be advised about. I have seen many systems that fulfill all contractual obliga- tions, meet every requirement, and still fail because this fairly obvious aspect was ignored. Great content creates great systems.
Zubin Wadia is CEO at RedRock IT Solutions and CTO at ImageWork Tech- nologies. He has a diverse software programming background with knowledge
of Basic, C, C++, Perl, Java, JSP, JSF, JavaScript, Erlang, Scala, Eiffel, and Ruby languages. His main focus is on enabling Fortune Global 500 companies and U.S. government agencies through business process-automation solutions.
相关文章推荐
- inputstream获取网页信息
- java关闭流,解压缩后的清除
- jQuery实现固定在网页顶部的菜单效果代码
- FrameWork之View的绘制过程(下)
- Android 打造形形色色的进度条 实现可以如此简单
- 研究传销骗局
- Sql Server 保留几位小数的三种做法
- Avoid “Good Ideas”
- Cuckoo Filter:设计与实现
- 解决android中viewpager自动占满父控件的问题
- Windows下TexLive2015 TeXstudio 和SumatraPDF安装配置
- TQ2440 学习笔记—— 13、GPIO 接口【实验:用汇编语言实现】
- Linux常用命令大全
- 【Cocos2dx】触摸事件
- “Perfect” Is the Enemy of“Good Enough”
- CSS3 简易照片墙
- 技术文摘7 部队 项目
- Java删除文件夹和文件
- 汉诺塔问题
- 计算机中丢失 msvcr110.dll