- 浏览: 79798 次
文章分类
- 全部博客 (89)
- web service (9)
- subversion (1)
- JBOSS (3)
- interview (23)
- jQery (2)
- ExtJs (0)
- Axis (0)
- Design pattern (3)
- Agile (2)
- mutithread (0)
- Core Java (24)
- programming methods (1)
- SSH (7)
- jee design (1)
- OO (4)
- books (8)
- other (1)
- JSF (7)
- seam (2)
- Weblogic (4)
- JPA (1)
- ADF (1)
- Spring (5)
- Tomcat (1)
- DWR (2)
- JEE (3)
- Servlet (1)
- EJB (1)
- JDBC (3)
最新评论
-
iloveflower:
呵呵。好好学习。。。。。。。。。。。。
java 读书 -
Eric.Yan:
看了一点,不过是电子版的……你这一说到提醒我了,还要继续学习哈 ...
java 读书
Below listed books are highly recommended by readers and project managers working on Agile Development projects as they help get a 360 degree view of the techniques, tools and procedures used in Agile Development. To know some of the best practices in Agile Development, you must read these books whose synopsis is given below:
1.Agile Project Management with Scrum
(By: Ken Schwaber ) The book provides a clear explanation about Scrum, starting from the basic tools and methodologies and it helps to provide accurate methods to fulfill customer requirements and for the translation of requirements into the software functions. The information is backed by a number of examples, case studies of real life projects about how to implement the information. The book also provides tips to solve a number of situational problems of Scrum implementation. The project management approach helps to reduce the overall time needed for implementation of Agile projects, to meet customer requirements satisfactorily and to reduce the overall error rate.
2.Agile Estimating and Planning
(By: Mike Cohn ) The book provides pragmatic approach to explain Agile Development, bringing the multiple planning approaches at several levels for measuring the software feature implementation, completion and acceptance. The book corrects a number of misunderstood attributes of Agile Development and explains the drawbacks of task based prediction models such as Gantt Charts, Work Breakdown Structures and PERT charts. The book provides general information but does not explain in-deep information. Part I explains the set-ups, Part II the details of estimating size, techniques and tools while Part III discusses value add planning. The book offers information about financial project analysis. Additionally, the first three parts of the book explain the concept of time, motivation, monitoring and communication.
3.User Stories Applied: For Agile Software Development
(By: Mike Cohn ) Every chapter contains a set of questions which are answered in the stories given and the explanation is highly sensible and carefully explained. The techniques are easy to apply and provide great value to the reader. The chapters explain the ways to handle requirements, qualitative aspects, performance and many elicit ways to monitor the progress of Agile projects. The writer explains cases, techniques and scenarios to find difference between stories. What’s more, the ideas in the book can be applied directly for productive use.
4.The Art of Agile Development
(By: James Shore ) There are 37 Agile Development practices explained in the book which are categorized mainly in five - thinking, releasing, collaboration, planning and development. Examples are given related to ubiquitous language, energized work, vision and architecture; and some of the practices and concepts have been repeated across the book. Each article in the book explains a practice or a component of Agile Development. Thus, the book provides practical value to businesses, customers, testers, analysts and developers.
5.Agile Project Management: Creating Innovative Products
(By: Jim Highsmith ) The book provides an overview on Agile Project Management and it also compares the Agile Development methodologies to traditional methods of Development. It explains the six principles of Agile Project Management by keeping the customer at the centre. It is based on dialogue between two project managers - one in Agile Development and other in the traditional management. The book provides a complete guidance for managing the Development of new products and explains concepts such as technical debt, exploration factors, anticipation, feasible deployment and opportunities refactoring.
6.Succeeding with Agile: Software Development Using Scrum
(By: Mike Cohn ) It provides an insight into Agile Development and compares some of the real ideas with stories, also offers examples of Agile Development which will appeal to a number of readers. Moreover, it provides tips to adopt new improved Agile Development procedures. The book is valuable for architects, programmers, testers, project managers and everyone who wants to integrate improved methods for developing software. The book is backed by a number of real world practices and has a great layout which ensures ideas and solutions are easy to understand, thus enabling successful adoption of Agile methods.
In the 90s, Agile Development methodologies became popular which was mainly based on iterative Development where the solutions evolved through the process of collaboration between the cross functional teams. There are many different types of Agile Development methodologies. The four main phases of traditional software Development are designing architecture, testing, delivery and feedback. Today, Agile Development is mostly seen as the process which is suitable in certain environment types which involves many small teams.
*****************************************************
Are you looking for the best software architecture books? Take a look at the following books which I found really valuable in understanding and effectively applying software architecture principles in real life. I would recommend these books as a must read for any software architect or developer regardless of language or background. (In addition to the 5 Best Design Pattern Books)
1.Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives (By: Nick Rozanski,E. Woods)
This book can be a good companion and reference for a beginner through intermediate level. It gives an excellent overview of what a system architect has to go through day in and day out to achieve success. The book contains a wealth of advice on what to pay and not pay attention to in any particular stage of the architectural development. The authors clearly speak from personal experience.
Even if you are not an architect it is a great book to buy so you understand what to expect out of one. More details about this book can be found at - http://www.viewpoints-and-perspectives.info/
2.Agile Software Development, Principles, Patterns, and Practices(By: Robert C. Martin)
This book has dozens of practical but concise examples illustrating everything from relatively simple object-oriented design concepts such as Meyer's Open/Closed Principle to subtle and complex issues with class and package dependencies.
The patterns discussion in this book is down-to-earth and easily understood. Robert does a wonderful job of explaining each design pattern, demonstrating their use through code, and placing them within the context of his design principles. The examples are numerous and, with a few exceptions, well written. I would also recommend this book to an Object Oriented Design newbie/student.
3.Working Effectively with Legacy Code (By: Michael Feathers)
This book does an excellent job of articulating the problems and scenarios, using clear examples from C, C++, Java, and C#. Many of the code examples look a lot like real examples we come across all the time (they don't appear to be fabricated).
The author defines "legacy code" as "code without tests." It doesn't matter whether the code was written last week or ten years ago. There is more emphasis on old code that nobody understands, mainly because it is messier and harder to work with. Working with legacy code isn't fun, but this book helps make it as painless as possible.
4.
Beyond Software Architecture: Creating and Sustaining Winning Solutions(By: Luke Hohmann)
This book delivers on its promise to discuss the larger business realities of creating software products. If you're a software architect, or dream of being one, this is a must read book.
The book is nicely segmented into logical chapters, making it an excellent reference. Although it covers classic architecture issues such as portability, usability, performance, layering, API design, and security, the truly valuable material is on the business and product management side of the fence, which often get ignored, or left till late in the process.
5.
Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions
(By: Gregor Hohpe, Bobby Woolf)
The book is organized into 65 patterns. Each pattern shows one typical problem in integrating applications, and how it is solved. Each pattern gives enough implementation details so it is clear how it would work, and an example or two so it is clear how it works in practice.
This book also contains in-depth coverage on software architecture using asynchronous communication. It's worth reading and re-reading if you're working with systems integration projects or writing integration software yourself.
1.Agile Project Management with Scrum
(By: Ken Schwaber ) The book provides a clear explanation about Scrum, starting from the basic tools and methodologies and it helps to provide accurate methods to fulfill customer requirements and for the translation of requirements into the software functions. The information is backed by a number of examples, case studies of real life projects about how to implement the information. The book also provides tips to solve a number of situational problems of Scrum implementation. The project management approach helps to reduce the overall time needed for implementation of Agile projects, to meet customer requirements satisfactorily and to reduce the overall error rate.
2.Agile Estimating and Planning
(By: Mike Cohn ) The book provides pragmatic approach to explain Agile Development, bringing the multiple planning approaches at several levels for measuring the software feature implementation, completion and acceptance. The book corrects a number of misunderstood attributes of Agile Development and explains the drawbacks of task based prediction models such as Gantt Charts, Work Breakdown Structures and PERT charts. The book provides general information but does not explain in-deep information. Part I explains the set-ups, Part II the details of estimating size, techniques and tools while Part III discusses value add planning. The book offers information about financial project analysis. Additionally, the first three parts of the book explain the concept of time, motivation, monitoring and communication.
3.User Stories Applied: For Agile Software Development
(By: Mike Cohn ) Every chapter contains a set of questions which are answered in the stories given and the explanation is highly sensible and carefully explained. The techniques are easy to apply and provide great value to the reader. The chapters explain the ways to handle requirements, qualitative aspects, performance and many elicit ways to monitor the progress of Agile projects. The writer explains cases, techniques and scenarios to find difference between stories. What’s more, the ideas in the book can be applied directly for productive use.
4.The Art of Agile Development
(By: James Shore ) There are 37 Agile Development practices explained in the book which are categorized mainly in five - thinking, releasing, collaboration, planning and development. Examples are given related to ubiquitous language, energized work, vision and architecture; and some of the practices and concepts have been repeated across the book. Each article in the book explains a practice or a component of Agile Development. Thus, the book provides practical value to businesses, customers, testers, analysts and developers.
5.Agile Project Management: Creating Innovative Products
(By: Jim Highsmith ) The book provides an overview on Agile Project Management and it also compares the Agile Development methodologies to traditional methods of Development. It explains the six principles of Agile Project Management by keeping the customer at the centre. It is based on dialogue between two project managers - one in Agile Development and other in the traditional management. The book provides a complete guidance for managing the Development of new products and explains concepts such as technical debt, exploration factors, anticipation, feasible deployment and opportunities refactoring.
6.Succeeding with Agile: Software Development Using Scrum
(By: Mike Cohn ) It provides an insight into Agile Development and compares some of the real ideas with stories, also offers examples of Agile Development which will appeal to a number of readers. Moreover, it provides tips to adopt new improved Agile Development procedures. The book is valuable for architects, programmers, testers, project managers and everyone who wants to integrate improved methods for developing software. The book is backed by a number of real world practices and has a great layout which ensures ideas and solutions are easy to understand, thus enabling successful adoption of Agile methods.
In the 90s, Agile Development methodologies became popular which was mainly based on iterative Development where the solutions evolved through the process of collaboration between the cross functional teams. There are many different types of Agile Development methodologies. The four main phases of traditional software Development are designing architecture, testing, delivery and feedback. Today, Agile Development is mostly seen as the process which is suitable in certain environment types which involves many small teams.
*****************************************************
Are you looking for the best software architecture books? Take a look at the following books which I found really valuable in understanding and effectively applying software architecture principles in real life. I would recommend these books as a must read for any software architect or developer regardless of language or background. (In addition to the 5 Best Design Pattern Books)
1.Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives (By: Nick Rozanski,E. Woods)
This book can be a good companion and reference for a beginner through intermediate level. It gives an excellent overview of what a system architect has to go through day in and day out to achieve success. The book contains a wealth of advice on what to pay and not pay attention to in any particular stage of the architectural development. The authors clearly speak from personal experience.
Even if you are not an architect it is a great book to buy so you understand what to expect out of one. More details about this book can be found at - http://www.viewpoints-and-perspectives.info/
2.Agile Software Development, Principles, Patterns, and Practices(By: Robert C. Martin)
This book has dozens of practical but concise examples illustrating everything from relatively simple object-oriented design concepts such as Meyer's Open/Closed Principle to subtle and complex issues with class and package dependencies.
The patterns discussion in this book is down-to-earth and easily understood. Robert does a wonderful job of explaining each design pattern, demonstrating their use through code, and placing them within the context of his design principles. The examples are numerous and, with a few exceptions, well written. I would also recommend this book to an Object Oriented Design newbie/student.
3.Working Effectively with Legacy Code (By: Michael Feathers)
This book does an excellent job of articulating the problems and scenarios, using clear examples from C, C++, Java, and C#. Many of the code examples look a lot like real examples we come across all the time (they don't appear to be fabricated).
The author defines "legacy code" as "code without tests." It doesn't matter whether the code was written last week or ten years ago. There is more emphasis on old code that nobody understands, mainly because it is messier and harder to work with. Working with legacy code isn't fun, but this book helps make it as painless as possible.
4.
Beyond Software Architecture: Creating and Sustaining Winning Solutions(By: Luke Hohmann)
This book delivers on its promise to discuss the larger business realities of creating software products. If you're a software architect, or dream of being one, this is a must read book.
The book is nicely segmented into logical chapters, making it an excellent reference. Although it covers classic architecture issues such as portability, usability, performance, layering, API design, and security, the truly valuable material is on the business and product management side of the fence, which often get ignored, or left till late in the process.
5.
Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions
(By: Gregor Hohpe, Bobby Woolf)
The book is organized into 65 patterns. Each pattern shows one typical problem in integrating applications, and how it is solved. Each pattern gives enough implementation details so it is clear how it would work, and an example or two so it is clear how it works in practice.
This book also contains in-depth coverage on software architecture using asynchronous communication. It's worth reading and re-reading if you're working with systems integration projects or writing integration software yourself.
发表评论
-
OO Design books -good website
2012-06-07 03:13 691I’m always on the search on goo ... -
Differences Between Scrum and Extreme Programming
2012-04-05 22:52 850http://blog.mountaingoatsoftwar ... -
Jolt Awards books
2012-04-05 22:01 12341990 Annotated C++ Reference M ... -
Refactoring
2012-04-03 11:00 0Replace Method with Method Obje ... -
OO Design principles
2012-04-02 22:26 870What are Software Design Princi ... -
java 读书
2012-03-29 23:57 938Thinking in java Java Algorith ... -
11 Most influential Books Every Programmer/Developer must read
2012-03-14 03:49 727Every programmer needs to learn ... -
5 Best Core java books you must read as a developer
2012-03-14 03:43 893If you want success in JAVA, yo ... -
5 Best Design Pattern Books you must read as a Software Developer
2012-03-14 03:12 904By - Sachin | 6/07/2010 | Label ...
相关推荐
Software Architecture for Developers is a practical and pragmatic guide to modern software architecture, specifically aimed at software developers. You'll learn: The essence of software ...
本文档基于《敏捷世界中的软件架构文档》(Documenting Software Architectures in an Agile World)一文的核心思想,深入探讨了在敏捷项目管理方法论下如何有效地进行软件架构的文档化工作。本文旨在为软件工程师、...
The Agile Architecture Revolution
Don’t hire a software developer until you read this book By 作者: K.N. Kukoyi ISBN-10 书号: 1539188191 ISBN-13 书号: 9781539188193 Edition 版本: 1 出版日期: 2017-05-26 pages 页数: 422 Use the ...
### 敏捷软件开发最佳实践在大型项目中的应用 #### 引言 本书《敏捷软件开发:大型软件项目的最佳实践》由Thomas Stober与Uwe Hansmann共同编写,旨在分享他们在IBM WebSphere Portal产品开发过程中引入敏捷软件...
PDF, 高清,英文原版。 Lean Architecture: for Agile Software Development http://www.amazon.com/Lean-Architecture-Agile-Software-Development/dp/0470684208
User Stories Applied: For Agile Software Development <br>by Mike Cohn <br>Publisher: Addison-Wesley Professional (March 11, 2004) <br> Agile requirements: discovering what your users...
《Agile Software Architecture: Aligning Agile Processes and Software Architectures》一书由Muhammad Ali Babar、Alan W. Brown和Ivan Mistrik编辑,旨在探讨如何将敏捷方法论与软件架构实践相结合,以提高软件...
Agile&Teamcetner项目管理对比资料搜集,供个人备案
敏捷软件开发(Agile Software Development)是一种以人为核心、迭代、逐步交付的软件开发方法论。这种方法强调灵活性、快速响应变化以及高效的团队协作,旨在在不断变化的需求环境中提供高质量的软件产品。 标题中...
Clean Code A Handbook of Agile Software Craftsmanship 英文无水印pdf pdf所有页面使用FoxitReader和PDF-XChangeViewer测试都可以打开 本资源转载自网络,如有侵权,请联系上传者或csdn删除 本资源转载自...
**敏捷软件开发**(Agile Software Development)是一种以人为本、迭代增量的现代软件工程方法论,它强调快速响应变化,通过持续反馈来提高软件项目的灵活性和效率。在《敏捷软件开发》这本书中,作者Alan S. Koch为...
Embedded Systems Architecture for Agile Development 英文epub 本资源转载自网络,如有侵权,请联系上传者或csdn删除 本资源转载自网络,如有侵权,请联系上传者或csdn删除
江苏软件架构师培训讲义共包括七天的讲义,这是第一天的讲义。...06 2Agile Software Development.pdf 06 3IsDesignDead.pdf 07 Architecture.pdf 07 Responsibilities of a Software Architect.pdf