Downloaded 17 times
![*Robot Tests
Setting Value
Library MonopolyLibrary
Post Condition: Post
Test IN: IN: Post Condition: Post Condition:
Action All Pieces Condition:
Case rounds Players Actual Rounds Output Trace
Current Square game Stop
Run The Game And
Test1 ${2} ${2} ${2} NOT goSquare TRUE NOT NULL
Check Post Conditions
Run The Game And
Test2 ${17} ${2} ${17} TRUE NOT NULL
Check Post Conditions
Keyword Action Argument Argument Argument Argument Argument Argument
Run The Game ${all pieces
${actual ${game ${output
And Check Post [Arguments] ${rounds} ${players} current
rounds} stop} trace}
Conditions square}
Init The Game ${rounds} ${players}
Run The Game
Get Actual
${testReturn}
Rounds
Should Be Equal ${actualRounds} ${testReturn}](https://image.slidesharecdn.com/2011-13488415614888-phpapp02-120928091330-phpapp02/85/2011-39-320.jpg)
Uploaded byYi Xu
速度——敏捷开发的丹田之气（2011敏捷中国大会）
The document discusses speed and agility in development. It introduces the author Xu Yi and provides contact information. It then discusses topics like modeling, test-driven development, coding practices, and skills needed for agile development like learning, practice and continuous improvement.
速度——敏捷开发的丹田之气（2011敏捷中国大会）
- 1. 速度 ——敏捷开发的丹田之气 徐毅 转载必须注明出处和作者。 本作品采用知识共享署名-非商业性使用-禁止演绎 2.5 中国大陆许可协议进行许可
- 2. *关于我 曾任职诺基亚西门子网络公司全球精益 及敏捷转型部门担任精益及敏捷顾问。 专长于大型组织(>500人)的敏捷迁徙转 变。精通各种风格、类型的黑盒测试， 包括验收性测试驱动开发、探索性测试、 测试自动化等等。在辅助一个400人的大 型组织搭建、规范化测试自动化系统及 实践之后，选择传授敏捷/Scrum以及精 益的要义，辅导其他组织进行转变。兴 趣广泛，包括但不限于各种类型测试、 敏捷/Scrum及精益。 国内敏捷会议的常客，近期的有敏捷中 国2009、2010 、2011 ，2010及2011的 ScrumGathering Shanghai，以及2009、 2010、2011年的敏捷全球之旅中国站。 更多信息请看LinkedIn主页： http://cn.linkedin.com/in/kaveri
- 3.
- 4.
- 8.
- 9. 实现 交流 确认 *
- 10.
- 11. * Elisabeth Hendrickson
- 12. 产品列表 没法管… 用户故事 到底要 怎么用啊 用工具画 UML图挺 快的呀？ * 结对编程？ 太浪费了！
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19. 业务人员和开发人员必须相互合作， 项目中的每一天都不例外。 不论团队内外，传递信息效果最好效率 也最高的方式是面对面的交谈。 *
- 23. * Monopoly（大富翁/强手棋/地产大享） Monopoly，国内又称大富翁、强手棋，号称全 世界卖得最多的桌上游戏Monopoly游戏的发明， 要追溯到1934年，当时一个叫Charles B. Darrow的美国人把自己发明的Monopoly游戏拿 去给出版商Parker Brothers，希望可以批量生产， 但当场就被Parker Brothers以52个设计错误拒之 门外。但Darrow并没放弃，他自己联系了一个 相熟的出版商，印刷了一批Monopoly游戏投放 市场，收到的反应却出奇的好。当他第二次踏 上Parker Brothers的门槛后，Monopoly得以大 批上市，并在出版的第一年----1935年就成为美 国最热卖游戏，并在接下来的七十几年时间售 出超过2亿套（只是官方统计数字，算是中国里 面的盗版大富翁，绝对远超这个数字）。 。 *
- 24.
- 25. First, find outuse cases by drawing use case diagram. Use case is a description of a system's behaviour as it responds to a request that originates from outside that system. The use case technique is used to capture a system's behavioural requirements by detailing scenario-driven threads through the functional requirements. Then, start from one specific use case, identify top level user stories, which follows the "As a <role>, I want <feature>, so that <motivation>.". Top level user story is too big to implement, we need to split it into smaller user stories. User story is a software system requirement formulated as one or two sentences in the everyday or business language of the user.
- 28. System Sequence Diagram illustrates external I/O events for system scenarios.
- 29. Then we made: *Cockburn-style Play Monopoly Main Success Scenario Use Case Text 10 Player wants to StartNewGame? 20 Player MakeMove? 30 Player PerformsAction? 40 Player EndsTurn? (repeat steps 20-40 until game ends) EXTENSIONS------------------ 30a Player buys property This is only legal if the property is available and player has enough money 1. Player gives money to the bank 2. Board is updated to reflect the change in property 30b Player pays rent This is only legal if the property is owned by another player 1. System identifies who is the owner of the field 2. Cash is transfered to the owner 30c Player is using a community card This is happening in case the player has landed on a field requireging usage of a community card 40a Active Player receives rent 1. System identifies who is the owner of the land 2. Cash is transfered to the owner * Player sells a property
- 30. domain model, orDomain Object Model (DOM) in problem solving and software engineering can be thought of as a conceptual model of a system which describes the various entities involved in that system and their relationships.
- 31. Acceptance Tests (inAgile Software Development) are usually created by business customers and expressed in a business domain language. These are high level tests to test the completeness of a user story or stories 'played' during any sprint/iteration.
- 32. Activity Diagram is a loosely defined diagram technique for showing workflows of stepwise activities and actions, with support for choise, iteration and concurrency.
- 33. Communication Diagram modelsthe interactions between objects or parts in terms of sequenced messages.
- 34. Class Diagram isa type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, and the relationships between the classes.
- 35.
- 36.
- 37. * Having pseudo-acceptance-testson the wall, it's time to realize them now. The test automation framework we used was www.robotframework.org. which is a keyword-driven framework for acceptance tests in tabular format. * Acceptance Test Driven Development (ATDD) practice drives development from automated acceptance tests, those executable acceptance tests. After written those pseudo tests into Robot format, we got a red FAIL of execution, since there was no keywords nor production code. *
- 38.
- 39. *Robot Tests Setting Value Library MonopolyLibrary Post Condition: Post Test IN: IN: Post Condition: Post Condition: Action All Pieces Condition: Case rounds Players Actual Rounds Output Trace Current Square game Stop Run The Game And Test1 ${2} ${2} ${2} NOT goSquare TRUE NOT NULL Check Post Conditions Run The Game And Test2 ${17} ${2} ${17} TRUE NOT NULL Check Post Conditions Keyword Action Argument Argument Argument Argument Argument Argument Run The Game ${all pieces ${actual ${game ${output And Check Post [Arguments] ${rounds} ${players} current rounds} stop} trace} Conditions square} Init The Game ${rounds} ${players} Run The Game Get Actual ${testReturn} Rounds Should Be Equal ${actualRounds} ${testReturn}
- 41. 坚持不懈地追求技术卓越和良好设计， 敏捷能力由此增强。 以简洁为本， 它是极力减少不必要工作量的艺术。 *
- 42. CI + ATDD+ TDD + PP + CODING DOJO
- 43. 1. Information Expert 2.Creator 3. Controller 4. Low Coupling 5. High Cohesion 6. Polymorphism 7. Pure Fabrication 8. Indirection 9. Protected Variations * General Responsibility Assignment Software Pattern http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29
- 44.
- 45. * duplicate codeor data * long method * unclear names * magic constants * high coupling (e.g., “data envy”) * low cohesion * case logic rather than polymorphism * data object (record object) * * comments that explain what code does http://en.wikipedia.org/wiki/Code_smell
- 46.
- 47.
- 48. 敏捷过程倡导可持续开发。 责任人、开发人员和用户要能够共同维 持其步调稳定延续。 团队定期地反思如何能提高成效， 并依此调整自身的举止表现。 *
- 49. 调整 检验 透明
- 50.
- 51.
- 52.
- 54.
- 55.
- 56.
- 57. * 自组织团队
- 58.
- 59.
- 60.
- 61. * • 可视化管理 • 团队身边可视化、触手可及的信息 • 相关信息全部位于一个平面
- 62.
- 63. Code Kata Coding Dojo
- 64.
- 65.
- 66.
- 67. *速度 领悟 练习 * 领悟 练习 爱迪生
- 68.
- 69. mailto:KAVERJODY@GMAIL.com mailto:KAVERJODY@MSN.com Skype : KAVERJODY 新浪微博: 徐毅-Kaveri 腾讯QQ : 17376122 http://blog.sina.com.cn/kaverjody http://cn.linkedin.com/in/kaveri http://kaverjody.wordpress.com *
- 70. * This workis licensed under the Creative Commons Attribution-NonCommercial-NoDerivs 2.5 China Mainland License. * To view a copy of this license, visit http://creativecommons.org/licenses/by-nc- nd/2.5/cn/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. 转载必须注明出处及作者。 本作品采用知识共享署名-非商业性使用-禁止演绎 2.5 中国大陆许可协议进行许可
- 71. *Agile Modeling andTDD Workshop —— Craig Larman *第一部分 *第二部分 *第三部分 *