Items related to The nimble software develops:Principle, mode and fulfillment...
The nimble software develops:Principle, mode and fulfillment(C#version ，revise a version) (Chinese edidion) Pinyin: min jie ruan jian kai fa : yuan ze 、 mo shi yu shi jian (C# ban ， xiu ding ban ) - Softcover
Synopsis
. Posts and Telecommunications Pub Date :2012-12-01 538 in People's Posts and Telecommunications Press Agile Software Development - Principles mode and real - (C # version. Revision) List 79 yuan Robert C. Martin Micah Martin Publ...
"synopsis" may belong to another edition of this title.
Search results for The nimble software develops:Principle, mode and fulfillment...
Stock Image
Software development methodology Featured Series: Agile Software Development principle. patterns and practices (C # Edition Revision)(Chinese Edition)
ISBN 10: 7115294682
ISBN 13: 9787115294685
New
paperback
Seller: liu xing, Nanjing, JS, China
Seller rating 5 out of 5 stars
paperback. Condition: New. Ship out in 2 business day, And Fast shipping, Free Tracking number will be provided after the shipment.Paperback. Pub Date: 2013 Pages: 538 in Publisher: People's Posts and Telecommunications Press software development methods to learn COLLECTION: Agile Software Development principle. depth and vivid patterns and practices (C #. revision) use The real case to explain the basic principles of object-oriented design. design patterns. UML and agile methods. Software Development Methodology Selection Series: Agile Software Development principles. patterns and practices (C #. revision) Java version was awarded the 2003 13th Jolt Award. is recognized as the typical writings. This book is an excellent tutorial for C # programmers to enhance skill. and can also be used as a textbook or reference book of university computer software engineering undergraduate. graduate. Contents: Part Agile Agile Alliance 1.1 of Chapter 1 of agile practices 1.1.1 and interact more important than comprehensive documentation of processes and tools 1.1.2 software can work more important than 1.1.3 client cooperation is more important than contract negotiations at any time 1.1.4 1.2 Principle 1.3 Conclusions 1.4 References Chapter 2 Overview of Extreme Programming follow a plan to cope with change is more important than a complete team of 2.1 Extreme Programming practices 2.1.1 2.1.2 User story 2.1.3 short delivery cycle 2.1.4 Acceptance Test 2.1.5 Pair Programming 2.1 0.6 Test Driven Development 2.1.7 collective work space 2.1.11 2.1.8 2.1.9 sustainable development speed continuous integration 2.1.10 open plan games 2.1.12 Simple Design 2.1.13 reconstructed 2.1.14 metaphor 2.2 Conclusions 2.3 References Chapter 3 3.1 3.3 iteration plan initial exploration 3.2 release plan 3.4 definition of completed 3.5 Task Scheduler 3.6 iteration 3.7 track 3.8 Conclusion 3.9 References Chapter 4 Test 4.1 Test Driven Development 4.1.1 priority designed to test the the example 4.1.2 Test prompted isolation between modules 4.1.3 unexpectedly decoupling unexpectedly 4.2 Acceptance Test 4.3 framework 4.4 Conclusion 4.5 References Chapter 5 reconstructed 5.1 prime number generator: a simple refactoring example 5.1.1 unit test 5.1.2 refactoring of 5.1.3 final look at the 5.2 Conclusion 5.3 References Chapter 6 the second part of the programming practice 6.1 Bowling game 6.2 Conclusion Agile Design Chapter 7 What is Agile Design 7.1 Design the odor 7.1.1 Design odor - Why would corrupt the smell of corruption Software 7.1.2 ossified 7.1.3 vulnerability 7.1.4 intractable 7.1.5 viscous 7.1.6 unnecessary complexity 7.1.7 unnecessary repetition 7.1.8 obscure 7.2 software 7.3 Copy procedures 7.3.1 familiar scene Agile 7.3.2 Copy program design 7.4 Conclusion 7.5 References Chapter 8 SRP: Single Responsibility Principle 8.1 defined responsibilities 8.2 coupled with separation of duties 8.3 8.4 Conclusion 8.5 References Chapter 9 OCP persistence : 9.2 Shape application open - closed principle 9.1 OCP Overview 9.2.1 to violate OCP9.2.2 follow OCP9.2.3 forecast changes and appropriate structures 9.2.4 placed hook 9.2.5 use abstract explicit closed 9.2.6 Public extracted data-driven method to get closed 9.3 Conclusion 9.4 References Chapter 10 LSP: Liskov Substitution Principle 10.1 violate the simple example of the LSP case 10.1.1 10.1.2 more subtle violation 10.1.3 practical examples 10.2 part of the method instead of to inherit 10.3 heuristic rules and idioms 10.4 Conclusions 10.5 References Chapter 11 DIP: Dependency Inversion Principle the 11.1 level 11.1.1 inverted interface ownership 11.1.2 rely on the simple example of the DIP abstract 11.2 11.3 furnace example 11.4 Conclusion 11.5 References Chapter 12 the ISP: Interface Segregation Principle 12.5 Conclusion 12.1 Interface pollution 12.2 separation example is the separation of interface to 12.3 class interface and object interfaces 12.3.1 use commissioned separation interface 12.3.2 use multiple inheritance separation interface 1. Seller Inventory # NE043709
Buy New
US$ 107.42
US$ 18.00 shipping
Ships from China to U.S.A.
Ships from China to U.S.A.
Quantity: 1 available