Jason's profile路随人茫茫PhotosBlogLists Tools Help

路随人茫茫

摇曳的风-婀娜的树

Jason

Occupation
Location
Interests
Jason, a graduated from Chinese Academic of Science student. From BJ to Sh, now is his second year in ShangHai.

BI & QA

在学习bw的时候, 忽然间发现BI和QA的共同之处, 整理如下:
1. QA目的在于保证产品质量, BI是为保证流程质量.
2. 为达到目的, QA和BI的architecture亦有神似之处:
    - 先分析BI和普通数据库系统的建模手段,一个使用denomalize,一个却nomalize。BI中的data warehouse, 为满足reporting, managing, 数据建模一般采用星型模型,将数据denomalized,数据冗余,但更有条理。而不像传统软件系统中的数据设计规范,(第1/2/3范式),主要考虑的是数据的添加/删除/更新操作,数据模型灵活但相对复杂。
    - 再看产品构建过程,dev和qa协同开发,开发人员会采用多种设计模式将code设计得更加灵活但分散,例如为了重用,代码组织的粒度更小,其中联系错综复杂。而QA虽然不会去整理代码, 但其test plan便会偏向条理性, case by case地去罗列, 易懂易管理.
3. bi服务于公司高层,非技术人员,qa类似。例如,bi的数据组织形式,基本上平民都可以理解。qa的交流方式类似,不会特别技术化。
 
另外关于bi人才和qa人才的构想:
作bi的同仁,也应该具有qa精神和习惯。
 
待续.

ZZ - 谷歌的用户体验准则

http://www.yeeyan.com/articles/view/86190/42448
谷歌的用户体验准则 

简介
伟大企业必有伟大之处。用户就是上帝,且看谷歌是如何对待上帝的。

ZZ - Short history of SAP BW

Short history of SAP BW

First version of SAP introduced Business Warehouse Information Systems (BIW later name was changed to BW and afterward in world of NetWeaver to BI) in the first half of year 1997. I was not able to find number of first version of BIW. Most likely it was version BIW 1.2A which went live for first six customers. Release 1.2B is based on the SAP R/3 4.5x version of course without business application modules. Let see to the history what was evaluation of it.

In year 1997 SAP started an initiative to extend the reporting and analysis capabilities of their flagship ERP software - R/3 based on OLTP environment. SAP was listening a customer's voice begging for standalone data warehousing software. Customers were annoyed for a long time of information processing in OLTP software like R/3 is. At that time they started to call this software “Reporting Server” and it rose to the largest development project in the history of SAP after the SAP R/3 development was done. This initiative was led by SAP cofounder Hasso Plattner who mandated that SAP created a reporting server.

In 1998, SAP launched a so called Early Customer Program (ECP, today’s Early Adoption Program (EAP)) with six customers to gather requirements and to do a proof of concept at customer sites. Thusly the SAP BIW was created.

Release 1.2A of BW was made available to the public in September 1998. Five years later, the 3.0B release of the SAP BW software not only provides a mature, end-to-end data warehouse technology, it also serves as a cornerstone of the formerly called mySAP Business Intelligence solution which is now NetWeaver BI.

When SAP BW was designed, it may never have been a consideration to use a third-party OLAP engine. More than likely it was a very quick decision to port the concepts from SAP R/3 to SAP BW and leverage its past development experience. Two examples of tools developed years ago as a core part of SAP R/3 that have found their way into SAP BW (not the code but the concepts) are the Early Warning System and the Report-to-Report Interface (RRI). In highlighting the reuse of R/3 tools, we are not saying that specific code was ported from one product to the next, only that SAP has had many years of experience in business intelligence and OLAP.

Based on the Microsoft multidimensional database access standard OLE DB for OLAP (ODBO) BW was first implemented on Microsoft Windows NT 4.0. There were two main reasons for developing SAP BW on Windows NT 4.0: first, to support SAP BW on the Microsoft platform using MS SQL Server 7; and second, to support Oracle Data Base Management Systems (DBMS) prior to implementing on a UNIX platform. At that time-early to mid-1998-Microsoft SQL Server 7 was still a beta product; therefore, SAP focused most BW development work on Oracle8 under Windows NT 4.0. However, toward midsummer 1998, SAP customers pressed SAP to implement SAP BW 1.2A on the UNIX platform as well. BW 1.2A supported the first UNIX implementation.

There are some common misunderstandings about SAP BW being just another application module comparable to FI, CO, or SD, or about being able to install SAPBW as an add-on to SAP R/3 or SAP R/3-based systems like CRM. While SAP BW may be installed on the same physical server, it always has to be installed as a separate SAP instance and will always use its own separate database and its own separate application servers. SAP started developing the SAP Business Information Warehouse in late 1996 based on an SAP system with just the basis and cross-application components installed and with a completely separate architecture, optimized for reporting and analysis purposes, in mind.

SAP was among the first software development companies to fully adopt a multi-tier client/server model (see Figure 3.16) and move away from traditional host-based solutions for business software. This was the beginning of the SAP R/3 success story back in the early 1990s.

Like all software releases, the BW faced the classic time-to-market, scope-of functionality, quality-of-software dilemma. Despite that it play now central role in SAP NetWeaver technology platform; a lot of customers is using it for strategic analyzing of its information; for optimizing of business operations etc. What is future of SAP BI? After acquisition of Business Objects in Oct 2007 there is a new SAP BI roadmap as of 02.2008. Some of tools originally developed by SAP will be replaced by BOBJ tools.

According to SAP, there are more than 12,000 installations of SAP's BI solution exist these days.

SAP BIW/BW/BI major releases:


Versions in detail:



Information fro this post was gathered from several internet sources; plus following books:

BIW for SAP by Naeem Hashmi

Mastering the SAP BIW: Leveraging the BI Capabilities of SAP NetWeaver by Kevin McDonald

For further reference see:

gleez.com/sap/bw/biw_and_bw

wikipedia.org/wiki/SAP_Business_Information_Warehouse

化工污染对张江生活有影响么

5月5日下午,下午4:02:01 PM,接到公司admin通知,张江发生毒气泄漏,请大家火速逃离。
届时,在张江工作人员,依靠各大公司班车,taxi等所有可利用的交通工具,火速离开张江。逃离很久,还收到公司保安来电,多喝牛奶解毒,在此感谢公司保安。
 
现在回想这些事实,真不知道是去抱怨还是去接受。
其实,先前一段时间正要考虑在张江买房。因为觉得以后就住在张江,虽说张江有化工厂,医药等企业,污染比较大,但毕竟上班近,有不错的小学/中学,而且表面看起来植被绿油油的,也有很多小孩孕妇在附近溜达,白天空气也还不错,只是有些地段会有消毒水味道,也无多少大碍,可以方便许多。于是坐等阳光花城,和汤臣豪园3期开盘。如今,这次突发事件,请问即使市场价格跌,可以省掉一些成本,但谁会为我和我家人的健康买单?小孩呢?
 
张江真是头疼。
 

朋友的推荐

有的时候, 内心需要被震惊一下, 便会醒悟.
对销售这个角色, 由于一直是一知半解的状态, 所以总是好奇. 虽然自个儿并不是从业人员, 但今天我让自己花费了不少周折去了解销售的过程. 通过网络, 亲戚朋友多方面帮助, 自己总算有了一个大概的了解.
 
"ZZ~~客户是公司生存和发展的基石,大量、稳定和有效地获取客户是企业实现销售任务的重要保障。一般的,企业产品或方案的常见销售过程如下:
  1. 筛选和整理候选的目标客户数据库。
  2. 通过电话营销、电邮营销、函件营销、网站营销、传真营销等方式,接触目标客户,介绍企业的产品或方案,并逐步挖掘出具体的目标客户。
  3. 与目标客户进行深入地沟通、接洽和演示,将其转变成为企业的实际客户。

在上述三个过程中,第一个阶段的工作是策略性的,需要根据企业或方案的特点,策略性地确定适合的目标行业;第二个阶段的工作是事务性的,非常烦琐、耗时;第三个阶段的工作是艺术性的,需要企业的优秀销售人员与客户进行深入沟通和洽谈,为客户的特殊需求提供增值性的服务。"

不过在学习过程中, 被告诫了一把, 同是国防科大毕业, 他见我过多关注流程, 便提到了某些人性后的坏习惯, 就是'规矩'.
或许, CRM真是管理者给销售人员下的金箍子, 如果是小公司的, 怎么用合适, 怎么去变通, 是需要仔细考虑考虑的.  
ondemand的概念虽好, 但仔细一问, http://soft.mainone.com/crm/setup.html 这个也未必好用 , 还是那句话, 怎么去变通, 是需要仔细考虑考虑的.  
 
或许, 规矩不懂不行, 懂得太多了, 真不是一个好事.
 
这里有俩个推荐读物: <谈判是什么> <竞争性销售>, SINA有在线, 可以预览后再买, 比先前买的<谈判学>4版, 要合适得多.
 

昨日重现 - tuoge的三步

久别的九队兄弟tuoge, 奇迹般地在这周来到了上海. 那天我还在Labs食堂,  一抬头发现熊四和砣哥.
"这....? 难道? "   忽然间, 像是回到了九队, 同是12班的你/我/他, 又奇迹般地走在了一起.
前几天, 俩个人去湘泉整了啤酒一瓶, 后为了确保能篮球一场, 又领着他去了一趟运动超市, 买了一套装备.  
.
.
周五终于到了, tuoge虽说球技也就那样, 但当年的三步篮和软肉, 让三区队每个人记忆犹新.
现在通告, 5年了, 没变!!!
肉还是那么软
三步篮, 还是有点神奇.
 
 
现在已经很快乐了, 明天生日再祝自己生日快乐. ^^
 

生意

共勉:

温州人的生意经,说到底就是“致富经”。为了致富,他们不怕走遍“千山万水”,不惜说上“千言万语”,不惧寻找“千方百计”,不怕历经“千辛万苦”。正是凭着这本“吃苦经”、“创业经”,温州人才能够四海为家,不因小而不为之,最终赚得“盆满钵满”。

BI competitors

SAP products
     BI overview:   http://www.businessobjects.com/product/
     OLAP:           Voyager
 
 
Oracle 商务智能首页
 
Microsoft BI solution
 
IBM BI solution

BI 的搜索工具- polestar

Polestar 是一个创新的搜索和发掘工具,用户可以使用它来搜索BusinessObjects Enterprise 管理的信息空间(一个共享上下文意义的Universe 对象集合)的内容。可以使用搜索关键字来检索空间,检索到的空间按相关性顺序排名并显示在搜索结果中。
 
Photo 1 of 11