查看完整版本: <大道至简>全而简的一本软件工程好书

<大道至简>全而简的一本软件工程好书

一个深入了解的程序员用最简单的语言表述出来的软件开发过程，如何做项目管理。

感谢楼主奉献一本好书.::em60::

过度设计，过犹不及，大道至简。

::em61:: 下了，看看哦，呵呵

设计能走到这一步，不是每个人都能掌握的。“时间+经验+个人资质”才能做到这一点的！

这书适合哪些群体看啊，我也想下载看看，但担心浪费钱了，因为我已经没钱了

软件方面的书和一些相关的精辟总结可真不少，
《大道至简》，
又多了解一本！
::em71::

机会不容错过，钱是可以再赚的，但是机会不是随时都有的。别等到有钱了，就找不到这篇文章了，或者根本就想不起来有这么一篇文章了啊::em72::

应该是本好书。。。下下来看看

刚刚接触项目管理，谢谢分享

[color=blue]贴一下这本书的目录，可能在选择要不要下载时更有方向：[/color]
[color=#0000ff][/color]


[b][size=3]1. 编程的精义
[/size][/b]
1. 编程的精义·······················································11
2. 会或者不会写程序·············································13
3. 程序 = 算法 + 结构········································14
4. 语言··································································16
5. 在没有工程的时代·············································16

[size=3][b]2. 是懒人造就了方法[/b][/size]

1. 是懒人造就了方法·············································18
2. 一百万行代码是可以写在一个文件里的············20
3. 你桌上的书是乱的吗·········································23
4. 我的第一次思考：程序=算法+结构+方法··········25

[size=3][b]3. 团队缺乏的不只是管理
[/b][/size]
1. 三个人的团队····················································29
2. 做项目 = 死亡游戏 ?·······································31
3. 做ISO质量体系的教训·····································33
4. 谁动摇了你的制度？·········································36
5. “那我们就开始开发吧”··································38
6. 组织的学问：角色·············································39
7. 跟随蚂蚁。但不要栽进蚂蚁洞里。···················42
8. “什么是增值税发票？”··································44

[b][size=3]4. 流于形式的沟通[/size][/b]

1. 客户不会用C，难道就会用UML吗？··············48
2. 项目文档真的可以用甲骨文来写·······················50
3. 最简沟通···························································53
4. 为不存在的角色留下沟通的渠道·······················57
5. 流于形式的沟通················································60

[size=3][b]5. 失败的过程也是过程
[/b][/size]
1. 做过程不是做工程·············································63
2. 做过场·······························································65
3. 实现，才是目的················································65
4. 过程不是死模型················································66
5. “刻鹄类鹜”与“画虎类狗”··························69
6. 工程不是做的，是组织的··································71

[size=3][b]6. 从编程到工程[/b][/size]

1. 语言只是工具····················································73
2. 程序··································································75
3. 方法··································································75
4. 过程··································································76
5. 工程··································································78
6. 组织··································································80
7. BOSS·································································82
8. 上帝之手···························································84

[size=3][b]7. 现实中的软件工程
[/b][/size]
1. 大公司手中的算盘·············································87
2. 回到工程的关键点·············································92
3. 思考项目成本的经理·········································94
4. 审视AOP··························································97
5. 审视MDA························································100

[size=3][b]8. 是思考还是思想[/b][/size]

1. 软件工程三个要素的价值·································103
2. 其实RUP是一个杂物箱···································104
3. UML与甲骨文之间的异同·······························105
4. 经营者离开发者很远，反之亦然······················106
5. 矛盾：实现目标与保障质量·····························107
6. 枝节与细节······················································108
7. 灵活的软件工程···············································110

[[i] 本帖最后由 scmscmscm 于 2008-6-13 22:08 编辑 [/i]]

[color=blue]再贴一段作者的话，也有助于了解这本书：[/color]



我其实是很希望这本书能放在读者的书架案头，而不是放在电脑的某一个目录中。因为它应当是一本可以阅读和品味的书，而不是在电脑中备查的技术资料。

然而，我在决定担任这家公司的软件架构师的同时，我就意识到，我没有足够的精力来运作这本书。——我的意思是如果要把他做成纸质的书的话，我没有足够的精力。

出版商是要寻求利润的。——于此，我一早就知道。但我从来不知道：到底一本书簿一点或者厚一点，哪个会让出版商更有利润。

我只想写一本“阐明软件工程的思想核心”的书。这本书要很容易就读明白，还要很容易就想通，还要很容易就知道：工程其实很简单，只是大家把它做复杂了。

然而问题是：我把它写得太简单了，以至于只写了110页，就没有必要再写下去了。

我当然可以把一本书写得很复杂，或者很厚。这很容易，就如做Coder一样：把代码写烂或者写乱都很容易，要想写得简洁却远非易事。

代码写得太简洁，老板会认为你在偷懒；书写得太薄，出版社就不愿意出。我看来是忘掉了侯捷先生说过的“买书如买纸”，以书的厚薄来论价值的故事。

忘掉了就忘掉吧。好的一面是现在书变成了电子版，大家终于可以读到它了。不好的呢？我想大概不要钱的东西很难得到珍视吧：如果下载这本书只是因为收集，而不是阅读，那会是让我感到比讨论“买书如买纸”这样的事更为难过的。

好吧。希望你能象对待纸质书籍那样来阅读这本《大道至简》。放心，我并不介意你把它打印出来放在床头。

补充声明：我保留在传统媒体(书籍、杂志)上刊载、出版本书的权利。但允许任何人在网络上非商业性地、自由地、不加修改地传播这本书的电子版本。

周爱民 2005年10月14日
[url=http://www.doany.net/]http://www.doany.net/[/url]
mailto:aim@263.net

[[i] 本帖最后由 scmscmscm 于 2008-6-13 22:01 编辑 [/i]]

[color=blue]这是开篇的故事：[/color]

基本上，这已经描述了“愚公移山”整个工程的概况。接下来，我们应该注意到愚公作为编程人员的基本素质。在与“河曲智叟”的对答中，他叙述了整个工程的实现程序：
“虽我之死，有子存焉”，这里描述了可能存在的分支结构，即“IF”条件判断。
“子又生孙，孙又生子；⋯⋯子子孙孙，无穷匮也”，这里描述了完成这个工程所必须的循环结构。
作为优秀的程序分析师，愚公论述了这个循环的可行性：由于“山不加增”，所以条件“山平”必将成立(“何苦而不平”)，所以这不会是一个死循环。

[[i] 本帖最后由 scmscmscm 于 2008-6-13 22:08 编辑 [/i]]

基于以上的内容，我觉得这本书适合想了解如何做出好的软件的人。
在虚拟货币不充分时，也推荐下载：
因为简短，因为语言很口语化，所以很容易读完，相对于不太能一下子看完的长篇论述来说，收获会更大。