BlogJava-西津渡日志 软件架构,saas-随笔分类-software engineeringhttp://www.blogjava.net/stephen80/category/5509.html软件架构,saas,战略管理zh-cnFri, 20 Nov 2009 04:23:59 GMTFri, 20 Nov 2009 04:23:59 GMT60整理软件架构相关的知识http://www.blogjava.net/stephen80/archive/2009/10/16/architecture.html西津渡西津渡Fri, 16 Oct 2009 05:13:00 GMThttp://www.blogjava.net/stephen80/archive/2009/10/16/architecture.htmlhttp://www.blogjava.net/stephen80/comments/298553.htmlhttp://www.blogjava.net/stephen80/archive/2009/10/16/architecture.html#Feedback0http://www.blogjava.net/stephen80/comments/commentRss/298553.htmlhttp://www.blogjava.net/stephen80/services/trackbacks/298553.html
Platform
Kernel
Framework
二.    Philosophy and discipline
Be aware of context
Extreme maintenance
Be pragmatic
Extreme abstract: Program to an interface (abstraction), not an implementation
  
Extreme separation of concerns
Extreme readability
Testability
No side effect
Do not repeat yourself
三.    Principle
DIP ，dependency inversion of control
OCP , open close
LSP , liskov substitute
ISP , interface segregation
SRP , single responsibility
LKP, Lease knowledge principle
四.    design pattern
Construction
Behavior
Structure

五.    anti-pattern、bad smell
Long method
Diverse change
    Repeated code
    Talk to stranger
    Pre optimize
六.    algorithms
 nLongN
 Divided and conqueror
 

七.    architecture
Hierarchal
Pipes and filter
Micro kernel
Broker
Black Board
    Interpreter
   
八.    Distributed & concurrent
What to concurrent

Scalability
    Stretch key dimensions to see what breaks
九.    languages
Ruby
Erlang
assemble
C
C++
Java
Python
Scala

Be ware of different program paradigms.
十.    Performance
 Minimize remote calls and other I/O
 Speed-up data conversion
 release resource as soon as possible 

十一.    architectures' future
软件设计思想的发展逻辑，大致是提高抽象程度 ，separation of concern 程度。
    fn(design )=  fn1(abstraction )+ fn2(separation of concern).

由于大规模数据处理时代的来临，下一代设计范式的重点：
1.    将是如何提高distributed(--concurrent) programing 的抽象程度 和 separation of concern 程度。
2.    dsl ，按照以上的公式，也确实是一个好的方向。
十二.    Reference
<art agile software development>
<prerefactor>
<design patterns>
<beautiful architecture>
<refactor>
<pattern oriented software architecture>
<extreme software development>
<beautiful code>
<patterns for parallel programming>
<java concurrent programming in practice>
<java performance tuning>
<the definite guide to hadoop>
<greenplum>
<DryadLINQ>
<software architecture in practice>
<97 things architecture should known>
http://en.wikipedia.org/wiki/Programming_paradigm





西津渡 2009-10-16 13:13 发表评论
]]>software architecture's futurehttp://www.blogjava.net/stephen80/archive/2009/07/13/286540.html西津渡西津渡Mon, 13 Jul 2009 04:33:00 GMThttp://www.blogjava.net/stephen80/archive/2009/07/13/286540.htmlhttp://www.blogjava.net/stephen80/comments/286540.htmlhttp://www.blogjava.net/stephen80/archive/2009/07/13/286540.html#Feedback1http://www.blogjava.net/stephen80/comments/commentRss/286540.htmlhttp://www.blogjava.net/stephen80/services/trackbacks/286540.html 大致上是：过程式、面向对象、组件、面向服务。
未来呢？我忘记了，抑或是 dsl ？

我以往也没有自己的认识，不过，最近我有自己的看法

软件设计思想的发展逻辑，大致是提高抽象程度 ，seperation of concern 程度。
    fn(design )=  fn1(abstraction )+ fn2(seperation of concern).


由于大规模数据处理时代的来临，下一代设计范式的重点：

  1. 将是如何提高concurrent programing 的抽象程度 和 seperation of concern 程度。
  2. 至于dsl ，我研究不多，不过，按照以上的公式，也确实是一个好的方向。

对于英文词语的使用，是因为，我想更能表达我的意思，不至于误解。见谅。
欢迎批评指正！

西津渡 2009-07-13 12:33 发表评论
]]>hudson 配置备忘http://www.blogjava.net/stephen80/archive/2009/05/11/270090.html西津渡西津渡Mon, 11 May 2009 10:48:00 GMThttp://www.blogjava.net/stephen80/archive/2009/05/11/270090.htmlhttp://www.blogjava.net/stephen80/comments/270090.htmlhttp://www.blogjava.net/stephen80/archive/2009/05/11/270090.html#Feedback0http://www.blogjava.net/stephen80/comments/commentRss/270090.htmlhttp://www.blogjava.net/stephen80/services/trackbacks/270090.html
    * 英文指南
    * 配置tomcat
          o 修改 server.xml ,在connector 加 URIEncoding="UTF-8"
          o 修改 catalina.sh ,加一行 CATALINA_OPTS="-DHUDSON_HOME=~/apprun/hudsonhome/ -Xms512m -Xmx512m"
                + 其中 HUDSON_HOME 是 hudson 的配置和运行文件所在地
          o 修改 tomcat-users.xml
                + <role rolename="admin"/>
                + <user username="hudson" password="hudson" roles="admin"/>
    * 把下载的hudson.war 放在 tomcat 的webapps 下，hudson 会自动启动起来，部署就完成了
          o 可以访问，比如 http://****:18080/hudson/
    * 安装 jdk
    * 安装 ant
    * 配置hudson
          o 配置和管理需要登陆 ，login
          o 打开管理页面，比如 http://****:18080/hudson/configure
          o 配置安全 ，Enable security ，两个选项：Delegate to servlet container --〉Legacy mode
          o 配置 jdk 路径， 比如 /home/**/tools/jdk1.6.0_13/
          o 配置 ant 路径， 比如 /home/**/apprun/ant171
          o 配置 System Admin E-mail Address ，//写一个很多项目公用的email
          o 记得 save
    * 新建一个job
          o 配置和管理需要登陆 ，login
          o new job ,选项 ：Build a free-style software project
          o 配置 ，比如 ：**:18080/hudson/job/icontent/configure
                + 填写svn 路径 ，比如 ：http://svn.****
                + Build Triggers，选Poll SCM ，schedule 符合 cron 规则
                + Build ，invoke ant ,填写 ant target
                + Post-build Actions ,选 E-mail Notification , Recipients 填写邮件地址
    * 配置linux 的环境变量
          o vi .bash_profile
          o JAVA_HOME=$HOME/tools/jdk1.6.0_13
          o PATH=$JAVA_HOME/bin:$PATH:$HOME/bin:$HOME/apprun/ant171/bin
          o LANG=zh_CN.GB2312 //encoding 与.java 源代码文件的编码一致 ，这样javadoc 不会有警告
          o LC_CTYPE=zh_CN.GB2312

easy！
great tool!


西津渡 2009-05-11 18:48 发表评论
]]>从应用级转到系统级开发http://www.blogjava.net/stephen80/archive/2009/02/15/254790.html西津渡西津渡Sun, 15 Feb 2009 11:36:00 GMThttp://www.blogjava.net/stephen80/archive/2009/02/15/254790.htmlhttp://www.blogjava.net/stephen80/comments/254790.htmlhttp://www.blogjava.net/stephen80/archive/2009/02/15/254790.html#Feedback0http://www.blogjava.net/stephen80/comments/commentRss/254790.htmlhttp://www.blogjava.net/stephen80/services/trackbacks/254790.html 2. 数据库不够用了,bdb
3. bdb 不够用了， 自己写b+ tree
4. java 不行了，得用 c++

看来，这个转变是个革命。搞不好得丢饭碗。

从想做一个创业者，到想做一个proferssional 。



西津渡 2009-02-15 19:36 发表评论
]]>今天修订了西津渡图解软件项目管理http://www.blogjava.net/stephen80/archive/2009/02/02/252938.html西津渡西津渡Mon, 02 Feb 2009 04:54:00 GMThttp://www.blogjava.net/stephen80/archive/2009/02/02/252938.htmlhttp://www.blogjava.net/stephen80/comments/252938.htmlhttp://www.blogjava.net/stephen80/archive/2009/02/02/252938.html#Feedback1http://www.blogjava.net/stephen80/comments/commentRss/252938.htmlhttp://www.blogjava.net/stephen80/services/trackbacks/252938.html<西津渡图解软件项目管理 〉从1年半之前，每当有新的感受，就修订一些。为自己的成长作个备注吧。


西津渡 2009-02-02 12:54 发表评论
]]>对设计的检查单http://www.blogjava.net/stephen80/archive/2008/07/06/212881.html西津渡西津渡Sun, 06 Jul 2008 08:44:00 GMThttp://www.blogjava.net/stephen80/archive/2008/07/06/212881.htmlhttp://www.blogjava.net/stephen80/comments/212881.htmlhttp://www.blogjava.net/stephen80/archive/2008/07/06/212881.html#Feedback1http://www.blogjava.net/stephen80/comments/commentRss/212881.htmlhttp://www.blogjava.net/stephen80/services/trackbacks/212881.html
      The design model resides at the core of the software engineering process. It is the place where quality is built into the software (and the place where quality is assessed. For this checklist, the more questions that elicit a negative response, the higher the risk that the analysis model will adequately serve its purpose. . For this checklist, the more questions that elicit a negative response, the higher the risk that the design model will not adequately serve its purpose.

      General issues:

          o Does the overall design implement all explicit requirements? Has a traceability table been developed?

      设计对需求的匹配？



          o Does the overall design achieve all implicit requirements?

          
    
          o Is the design represented in a form that is easily understood by outsiders?

        易理解？

          o Is design notation standardized? Consistent?

        

          o Does the overall design provide sufficient information for test case design?

        可测试。

          o Is the design created using recognizable architectural and procedural patterns?

        常用的架构 和模式？
        

          o Does the design strive to incorporate reusable components?

        重用组件？

          o Is the design modular?

        模块化

          o Has the design defined both procedural and data abstractions that can be reused?
        重用的过程 / 数据 抽象？
        

          o Has the design been defined and represented in a stepwise fashion?
        逐渐细化的表述？    

          o Has the resultant software architecture been partitioned for ease of implementation? Maintenance?
        可部署性？ 可维护性？


          o Have the concepts of information hiding and functional independence been followed throughout the design?

           封装性？

          o Has a Design Specification been developed for the software?

        文档？


      For data design:

          o Have data objected defined in the analysis model been properly translated into required data structured?

        数据映射with analysis？        

          o Do the data structures contain all attributes defined in the analysis model?
        数据属性？

          o Have any new data structures and/or attributes been defined at design time?

        新的数据结构？

          o How do any new data structures and/or attributes related to the analysis model and to overall user requirements?

        用户需求与数据结构匹配吗？

          o Have the simplest data structures required to do the job been chosen?

        数据结构简单吗？

          o Can the data structures be implemented directly in the programming language of choice?

        编程语言适合数据结构？

          o How are data communicated between software components?
        软件组件之间的数据交换？

          o Do explicit data components (e.g., a database) exist? If so, what is their role?

        数据库？

      For architectural design:

          o Has a library of architectural styles been considered prior to the definition of the resultant software architecture?
        
        架构模式？

          o Has architectural tradeoff analysis been performed?
        架构分析的tradeoff？

          o Is the resultant software architecture a recognizable architectural style?

        认可的架构风格？

          o Has the architecture been exercised against existing usage scenarios?
        架构有应用示例吗？    

          o Has an appropriate mapping been used to translate the analysis model into the architectural model?
        
        分析和架构之间的mapping？

          o Can quality characteristics associated with the resultant architecture (e.g., a factored call-and-return architecture) be readily identified from information provided in the design model?
        架构的质量特点？


      For user interface design:

          o Have the results of task analysis been documented?
          o Have goals for each user task been identified?
          o Has an action sequence been defined for each user task?
          o Have various states of the interface been documented?
          o Have objects and actions that appear within the context of the interface been defined?
          o Have the three "golden rules" (SEPA, 5/e, p. 402) been maintained throughout the GUI design?
          o Has flexible interaction been defined as a design criterion throughout the interface?
          o Have expert and novice modes of interaction been defined?
          o Have technical internals been hidden from the causal user?
          o Is the on-screen metaphor (if any) consistent with the overall applications?
          o Are icons clear and understandable?
          o Is interaction intuitive?
          o Is system response time consistent across all tasks?
          o Has an integrated help facility been implemented?
          o Are all error message displayed by the interface easy to understand? Do they help the user resolve the problem quickly?
          o Is color being used effectively?
          o Has a prototype for the interface been developed?
          o Have user's impressions of the prototype been collected in an organized manner?

      For component-level design:

    * Have proof of correctness techniques (SEPA, 5/e, Chapter 26) been applied to all algorithms?

    算法正确性？

    * Has each algorithm been "desk-tested" to uncover errors? Is each algorithm correct?

    算法？

    * Is the design of the algorithm consistent with the data structured that the component manipulates?

    算法？
    * Have algorithmic design alternatives been considered? If yes, why was this design chosen?

    替代算法考虑了吗？

    * Has the complexity of each algorithm been computed?
    
    每个算法的复杂性考虑了吗？

    * Have structured programming constructs been used throughout?
    
    结构好吗？



西津渡 2008-07-06 16:44 发表评论
]]>西津渡图解软件项目管理http://www.blogjava.net/stephen80/archive/2007/11/02/157704.html西津渡西津渡Fri, 02 Nov 2007 03:17:00 GMThttp://www.blogjava.net/stephen80/archive/2007/11/02/157704.htmlhttp://www.blogjava.net/stephen80/comments/157704.htmlhttp://www.blogjava.net/stephen80/archive/2007/11/02/157704.html#Feedback0http://www.blogjava.net/stephen80/comments/commentRss/157704.htmlhttp://www.blogjava.net/stephen80/services/trackbacks/157704.html99街购物搜索引擎，www.99jie.com
根据体会，修订了图解软件项目管理一文。这是今年以来的第三次较大修订。
有需要者请下载。西津渡图解软件项目管理
下边是目录。
第一章 项目管理的目标
一、    产品，周期，成本的约束。
二、    关键路径管理
三、    可行性分析很重要
四、    人际技巧
五、    谈判技巧
第二章 项目过程
一、    计划阶段
二、    架构阶段和技术攻关
三、    迭代阶段
四、    结束阶段
第三章 分析,形成specification
一、    最重要的是specification 发挥作用
二、    重要的创造性工作
三、    选择适合的表达方式
四、    数据以及数据的key 和约束
五、    测试脚本
六、    Review ,评审
第四章 设计系统UI
一、    一幅图胜过千句话
第五章 设计,code ,build ,test
第六章 部署和重构
第七章 风险
一、    分析风险
二、    技术风险
三、    所有的风险是人的风险，trust and capable
四、    记住50%以上的软件项目以失败告终
五、    所有的风险是管理的风险，遵循一套项目管理哲学
第八章 保持项目的进展
一、    对项目负责，做出决定
二、    让进展可见，持续集成
三、执行，并检查
四、    解决冲突，大家都是兄弟姐妹
五、    能担当者是项目经理
六、    关键路径的变更
第九章 总结经验
第十章 一些效率关键指标
第十一章 项目管理工具
第十二章 参考
第十三章 口诀


西津渡 2007-11-02 11:17 发表评论
]]>图解软件项目管理http://www.blogjava.net/stephen80/archive/2007/08/10/135781.html西津渡西津渡Fri, 10 Aug 2007 05:16:00 GMThttp://www.blogjava.net/stephen80/archive/2007/08/10/135781.htmlhttp://www.blogjava.net/stephen80/comments/135781.htmlhttp://www.blogjava.net/stephen80/archive/2007/08/10/135781.html#Feedback3http://www.blogjava.net/stephen80/comments/commentRss/135781.htmlhttp://www.blogjava.net/stephen80/services/trackbacks/135781.html图解软件项目管理
加强的部分：
   软件项目的商业背景， 项目的平衡术， 关键路径的管理。
  




西津渡 2007-08-10 13:16 发表评论
]]>scjp 的一些古怪的问题http://www.blogjava.net/stephen80/archive/2007/07/20/131503.html西津渡西津渡Fri, 20 Jul 2007 07:48:00 GMThttp://www.blogjava.net/stephen80/archive/2007/07/20/131503.htmlswing 也要学习。


西津渡 2007-07-20 15:48 发表评论
]]>pair programming 的体会http://www.blogjava.net/stephen80/archive/2007/03/28/106872.html西津渡西津渡Wed, 28 Mar 2007 02:03:00 GMThttp://www.blogjava.net/stephen80/archive/2007/03/28/106872.htmlhttp://www.blogjava.net/stephen80/comments/106872.htmlhttp://www.blogjava.net/stephen80/archive/2007/03/28/106872.html#Feedback0http://www.blogjava.net/stephen80/comments/commentRss/106872.htmlhttp://www.blogjava.net/stephen80/services/trackbacks/106872.html
这个小项目只有我们两个人，通过3天的pair programming ，我把自己的编程习惯，风格，设计理念全部共享给同事。
我们一起思考业务，设计，项目进展非常好。进度提高一倍以上。
多年来，我几乎不肯把自己的经验分享给别人，如今念佛悔改，几乎没有一点保留。

pair programming 的好处在交流，在于知识的共享。
今后做项目也多了一个非常得力的帮手。
我自己考虑，今后我带的所有项目成员，都要经常交叉进行pair programming.充分的交流。






西津渡 2007-03-28 10:03 发表评论
]]>总监、系统分析员、软件架构师的个性特质http://www.blogjava.net/stephen80/archive/2007/03/12/103246.html西津渡西津渡Mon, 12 Mar 2007 03:07:00 GMThttp://www.blogjava.net/stephen80/archive/2007/03/12/103246.htmlhttp://www.blogjava.net/stephen80/comments/103246.htmlhttp://www.blogjava.net/stephen80/archive/2007/03/12/103246.html#Feedback0http://www.blogjava.net/stephen80/comments/commentRss/103246.htmlhttp://www.blogjava.net/stephen80/services/trackbacks/103246.html系统分析员，在于综合能力，在于灵活，在于平衡。
架构师，在于执着，在于超然物外。

小的项目，就容不了这么多人，项目经理就够了。

西津渡 2007-03-12 11:07 发表评论
]]>图解软件项目管理http://www.blogjava.net/stephen80/archive/2007/02/03/pm.html西津渡西津渡Sat, 03 Feb 2007 07:07:00 GMThttp://www.blogjava.net/stephen80/archive/2007/02/03/pm.htmlhttp://www.blogjava.net/stephen80/comments/97747.htmlhttp://www.blogjava.net/stephen80/archive/2007/02/03/pm.html#Feedback3http://www.blogjava.net/stephen80/comments/commentRss/97747.htmlhttp://www.blogjava.net/stephen80/services/trackbacks/97747.html  阅读全文

西津渡 2007-02-03 15:07 发表评论
]]>management thoughthttp://www.blogjava.net/stephen80/archive/2006/08/08/62388.html西津渡西津渡Tue, 08 Aug 2006 09:32:00 GMThttp://www.blogjava.net/stephen80/archive/2006/08/08/62388.html
 I think the management thought I have some change.
 first I think management can't chease.Just choose those can met your culture.Ond shouldn't think use employee and kick off after.
 second ,I think corporation's existence not for profit or some great idea .It's for some people who have similar pursue and ideal to make life. these is most important.
 three, If you can't layer it ,you can't manage it.real layer should take clear boardary.


西津渡 2006-08-08 17:32 发表评论
]]>log 经验http://www.blogjava.net/stephen80/archive/2006/06/30/55992.html西津渡西津渡Fri, 30 Jun 2006 09:00:00 GMThttp://www.blogjava.net/stephen80/archive/2006/06/30/55992.htmlhttp://www.blogjava.net/stephen80/comments/55992.htmlhttp://www.blogjava.net/stephen80/archive/2006/06/30/55992.html#Feedback0http://www.blogjava.net/stephen80/comments/commentRss/55992.htmlhttp://www.blogjava.net/stephen80/services/trackbacks/55992.html    warn, 程序固然可以正常运行，可是不是希望的逻辑
    info ,至少应该显示程序的执行逻辑
    debug, 显示数据

   所以info 对于发现运行时的错误很重要，要有效的撰写。


西津渡 2006-06-30 17:00 发表评论
]]>use case 设计http://www.blogjava.net/stephen80/archive/2005/12/05/22548.html西津渡西津渡Mon, 05 Dec 2005 05:37:00 GMThttp://www.blogjava.net/stephen80/archive/2005/12/05/22548.htmlhttp://www.blogjava.net/stephen80/comments/22548.htmlhttp://www.blogjava.net/stephen80/archive/2005/12/05/22548.html#Feedback0http://www.blogjava.net/stephen80/comments/commentRss/22548.htmlhttp://www.blogjava.net/stephen80/services/trackbacks/22548.htmluse case 设计的重要性不亚于架构设计。

use case 设计的经验
分层
   核心的业务，要优先考虑。
分模块
   关注核心的概念。

use case 设计的优化

提供可选的方案
    有对比，才有优化。
用户接口能否再简单
    约束住用户，用户会感觉麻烦。
    不要对架构增加太多的约束。



西津渡 2005-12-05 13:37 发表评论
]]>EA ，不错的建模工具http://www.blogjava.net/stephen80/archive/2005/12/04/22470.html西津渡西津渡Sun, 04 Dec 2005 13:35:00 GMThttp://www.blogjava.net/stephen80/archive/2005/12/04/22470.htmlhttp://www.blogjava.net/stephen80/comments/22470.htmlhttp://www.blogjava.net/stephen80/archive/2005/12/04/22470.html#Feedback0http://www.blogjava.net/stephen80/comments/commentRss/22470.htmlhttp://www.blogjava.net/stephen80/services/trackbacks/22470.html最近进行业务建模，Use case,UI 设计.综合的使用方面，比rose 方便。
enterprise architect 与 powerdesigner 一起使用。
做UI 的时候，把 Get***List，Service 方法的参数和返回值写好，产品的设计就没有什么二义性了。



西津渡 2005-12-04 21:35 发表评论
]]>