software development methodology featured (4 risultati)

paperback. Condizione: New. Ship out in 2 business day, And Fast shipping, Free Tracking number will be provided after the shipment.Paperback. Pub Date: 2013 Pages: 240 Publisher: People's Posts and Telecommunications Press software development methods to learn COLLECTION: software process for software developers. raised some very difficult and sensitive issues. and controversial evolution: get inspiration from a number of years has been the prosperity of the system - technology to find the answers. Featured Series: software process for software development methods to learn with 5 parts of 19 chapters devoted to systematic exposition of the author's point of view. the software industry has been plagued by the problem of trying to answer - how we should restructure the process of software construction to enable it to effectively as we would like to run? Part 1 of 4. questioning the traditional view - software engineering is really a panacea to solve the problem of software development? Part 2 of Chapter 2. this part of the book is of the view that the perspective of the software process to look at the software development. Part 3 of Chapter 7 of space. from a different angle to show the main changes brought about by the software process theory. as well as how to practice this concept. Part 4. Chapter 3. compared to the software process and software engineering. and to redraw the boundaries for each applicable category. Part 5 of 3. expediency and long-term issues in software development are discussed. The book won the 2002 Jolt Book Award. Reading this book. to help lead the independent thinking of the reader in on the issue of software development. software development methodology Featured Series: software process software industry practitioners read reference. Chapter 1 Contents: The first part of the question of software engineering to understand software engineering software engineering paradox waiting for hardware development. software developers doing? The available hardware and software developers how to accelerate the speed of delivery? Good enough software - the common people of the contemporary interpretation of the traditional development process intrinsic software engineering software engineering software engineering for your project? The plight of Chapter 2 Software Engineering organized. measurable realities of the software development process it? Of course. we can be software development in certain parts of the automation. is not it? Good enough approach to software development can replace harmful software engineering? Chapter 3 to understand the software development software asset software development requires teamwork software development division of labor helpful? Not once and for all to find more useful metaphor than the Software Engineering Chapter 4 to find a better metaphor than software engineering software development process and comparison with the traditional process of software development process revival second part of Chapter 5 of the software process to regain software excellent software development technology dedicated to improving the software development status of technology to encourage developers to write horn sounded Chapter 6 without license technology process the private peer recognition and recommendation of the way for better software license is just an illusion license in personal software developers to. Windmill war technology not too little. but too much of the third part of the software process implied mean Chapter 7 users of technology on the impact of the software easy to copy. so the software process can effectively artisans of the problems with the user of the bulk market need a different kind of relationship. however. please remember: buyers are likely not excellent software users should sign on the name of the developer works signature make the situation changes craftsmen craftsman in charge of the works should be smaller. more robust software for the discerning user is more conducive to the process of use.

paperback. Condizione: New. Ship out in 2 business day, And Fast shipping, Free Tracking number will be provided after the shipment.Paperback. Pub Date :2013-07-01 Pages: 228 Publisher: People Post Press Software development methodology Featured Series : Agile iterative development Administrator's Guide is agile and iterative development methods authoritative guide . Famous guru Craig Larman software methods described in the book is not only what is agile iterative method. its operation mechanism. the implementation strategy and why . but also through the statistical significance of the important research data . as well a.Four Satisfaction guaranteed,or money back.

paperback. Condizione: New. Ship out in 2 business day, And Fast shipping, Free Tracking number will be provided after the shipment.Paperback. Pub Date: 2013 Pages: 300 Publisher: People's Posts and Telecommunications Press approach to software development to learn COLLECTION: Reconstruction and mode (revision) groundbreaking reveals the depth the Reconstruction and mode both software the development of links between the key technologies on reconstructed mode to improve the existing design. often better than in the early design usage patterns. Software development methodology Featured Series: Reconstruction and the mode (Revised Edition) not only shows an application mode and reconstructed innovative approaches and help readers through the real in-depth understanding of the remodeling and mode. The book tells the story of the 27 kinds of reconstruction way. Featured Series: Reconstruction and the mode (Revised Edition) software development methodology suitable for object-oriented software developers to read. as colleges and universities computer readings of professional software engineering teachers and students. Contents: Chapter 1 of this book's writing why 1.1 over-design 1.2 mode panacea 1.3 design less than 1.4 test driven development and continuous refactoring 1.5 refactoring evolutionary design mode 1.6 Chapter 2 2.3 watchful eyes reconfigurable of 2.1 What reconfigurable 2.2 reconstructed motivation 2.4 readable code 2.5 keep clear 2.6 2.7 2.11 refactoring tool design outstanding loans 2.8 evolution of the new framework 2.9 composite Reconstruction and test-driven refactoring 2.10 composite refactoring advantage of Chapter 3 mode 3.1 What mode gradual 3.2 more than one way mode obsessed 3.3 mode 3.4 through refactoring trends and removal mode 3.5 mode makes the code more complex 3.6 mode Knowledge 3.7 mode Chapter 4 code and bad taste pre-designed 4.1 Repeat code (Duplicated Code ) 4.2 is too long function (Long Method) 4.3 is too complex conditional logic (Conditional Complexity) 4.4 basic type of paranoid inappropriate exposure (Primitive Obsession) 4.5 (Indecent Exposure) 4.6 solution spread (Solution Sprawl) 4.7 similar to the class (Alternative Classes heavy class with Different Interfaces) 4.8 tautological class (Lazy Class) 4.9 is too large (Large Class) 4.10 branch statement (Switch Statement) 4.11 combinatorial explosion (Combinatorial Explosion) 4.12 weird solutions (Oddball Solution) Chapter 5 mode oriented the format 5.2 catalog referenced in the project configuration directory 5.1 refactoring 5.2.1 an XML Builder5.2.2 HTML Parser5.2.3 loan risk learning the order of the program 5.3 starting point 5.4 Chapter 6 Creating 6.1 Creation Method replace constructor 6.1.1 motive 6.1 .2 practice 6.1.3 Example 6.1.4 variant 6.2 will create the knowledge move to Factory6.2.1 motivation 6.2.2 practice 6.2.3 Example 6.3 with Factory Packaging category 6.3.1 Motivation 6.3.2 practice 6.3.3 example 6.3.4 variants of 6.4 polymorphic create 6.4.1 motive 6.4.2 Factory Method introduced the practice 6.4.3 Example 6.5 with 6.5.2 Example 6.5.3 the Builder package Composite6.5.1 practice variant the 6.6 inline Singleton6.6.1 motive 6.6.2 practice 6.6.3 example Chapter 7 simplifies 7.1 combination method 7.1.1 motive 7.1.2 practice example Strategy replace conditional logic 7.2.1 Motivation 7.2 7.1.3 7.2.2 practice 7.2.3 Example 7.3 moved into the decorative function Decorator7.3.1 motivation 7.3.2 practice 7.3.3 Example 7.4 with the State replaced state to change the conditional statement 7.4.1 motivation 7.4.2 practice 7.4.3 example 7.5 with Composite replace implicit the tree 7.5.1 motive 7.5.2 practice 7.5.3 example 7.6 generalization of Chapter 8 of the Command replace conditions Scheduler 7.6.1 motive 7.6.2 practice 7.6.3 example 8.1 form Template Method8.1.1 motive 8.1.2 practice example 8.2 8.1.3 8.2.2 practice extract Composite8.2.1 motive 8.2.3 example 8.3 motivation Composite replace more than one of the points 8.3.1 8.3.2 practice 8.3.3 Example.

paperback. Condizione: 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.