Software Development Books

This book provides excellent insight into the story driven process, with immediately actionable advice. Cohn clearly describes the advantages of stories, and explains how to develop quality systems that deliver value to the user. Anyone operating in, or hoping to adopt an iterative and incremental methodology will benefit from reading this piece.

This book is one of the better collections of how-to's and practical applications I've read on Agile user stories. It mixes in just enough of the theory to understand the importance and distinctions of epics, stories, tasks, and spikes without overly focusing on them. Then, it uses real-world examples in common language to walk you through some of the messier implementations of Agile, and provides specific guidance on how to make things work in less than ideal situations. I found this book particularly helpful for me personally, as well as for one of our less experienced Scrum Master's at work.

I have seen other presentations and publications from this author and he really seems to know his stuff, plus it's really easy to read. I'm a consultant and trainer and find this to be an excellent reference. There are lots of examples and the book is very easy to read. You also don't have to be involved in Agile development to find this useful, as I also use the concepts for developing user roles and focusing on user goals as a primary function even in a Waterfall development world.

I'm pretty much allergic to any form of requirements documentation. Change control makes my skin itch, and big up front planning makes me vomit. But I also am not totally comfortable with winging it all the time. As a project manager, I need to get a sense of how big the project is, what are the pieces and parts, and how will the product be used. And I need it fast, flexible, and without much overhead. Oh yeah, don't forget I have to also be able to use it to plan iterations, drive development and testing, and report status. All without making comprehensive documentation more important than working software or processes and tools more important than individuals and interactions.

That's why I'm glad I discovered User Stories Applied: For Agile Software Development by Mike Cohn. It is a short, practical explanation of how to plan, estimate, and execute an agile project with user stories. These lightweight requirements never get in the way or replace conversations with users and customers. Instead, they help you keep track of what you're going to build and serve as a reminder to talk to SME's about what they mean. You can use them to report status, to plan iterations, and to get an overview of the product's feature set.

I wholeheartedly endorse this book for all project or product managers.

As you'll read in other reviews this book does a great job of laying the foundation on how to implement XP as a development process using user stories, iterations, and other concepts used in XP.

Where the book goes a little overboard is with some drawn out stories and examples that could be cut down. In reality I think this book could almost have 1/3 less long and been a 5 star book.

I have used these books since Access 97. Absolutely invaluable to learn how to do anything you want. Don't expect it to cover what's in help, they go where help doesn't.

Is there going to be a 2007 version?

This book has everything you will need to creat Access based applications. A ton of great advice and clean coding. The index is very useful and well written.

I purchased this 2 book set in hopes of advancing my knowledge of Access and VBA. I could not find any useful information on functions such as DateAdd, DatePart, Nz, DLookup, DSum, DCount, etc. These are major parts of Access and are very useful once you learn them, but the Developers Handbook does not even cover these functions and how to use them. Or if it does, you can't find out where by searching the index. I've yet to find any information I'm looking for in these books.

It has already been said, Simply the best! I'm finding more and more Web sites/threaded discussions using or pointing to the code found in the Access Developer's Handbook and VBA Developer's Handbook.

The ShellBrowse functions alone to be extremely helpful.

Thanks to Ken, Paul, and Mike

I am a software developer and have been in business since 1982. I have never gotten more bank for my buck than with these books. I didn't think Access was worth a flip for program development until I bought these books. I have since developed a vertical market package for the seafood industry that sells itself by demo. Thanks Ken, Paul and Mike.

This man makes a promise of a written format that can be followed. The writtng is NOT CLEAR and leaves much to the readers imagination of to what exactly the format should be. There is no CD so that you can see how the step by step process works. He names his files but does not show the real differences between how he is set up and how you can set up to fit your needs. I waisted my money. He claims in the book there is support which at best is terrible.

The worst book I have ever bought on coding. If I were you try another writter.

This is a good book. It teaches many useful techniques and how lots of "how to" ideas. However, the faux site that is created isn't goal oriented which left me feeling like the book was just a collection of random things to do. It seemed disorganized at times when you would or wouldn't create another page from scratch vs. revamping one you had already made. It was not always clear why you would be better to take one approach vs. the other. Setting up the localhost environment was somewhat confusing, though not too bad.

I will definitely use it frequently. Good information, good book, good deal.

This book is written very clearly and is really easy to follow. I've learned a lot of other really useful stuff than just the PHP content, things that I now realise I should have been taught by the official Dreamweaver 8 book, but weren't. The PHP content for which I bought this book is fantastic - much better than another generic PHP/MySQL I have read, as this is tailored to the Dreamweaver 8 environment which takes a lot of the guessing out of the equation. This book is written by and for people who use Dreamweaver 8 in a practical situation. I'm still less than half way through my book and already feel like I've learned much more than I expected. Highly recommended. I'll be checking out Mr Powers' other books when I finish this one. Thanks David Powers, you're a genius!

This is a very good book for learning PHP, and surprisingly, most of the examples work right out of the book as he's written them, which seems rare for a programming book these days. The projects that he has you complete are highly relevant to what you'd actually be doing with PHP, and that makes it even better.

The only trouble I had with this book was that he sure packed a lot of information into each chapter, and he didn't use the sidebars as much as I would have hoped. It's easy enough to follow along with the examples the first time, but if you want to go back again and figure out how he programmed a small detail, you'll never find it unless you reread the whole chapter again. All it would have taken was a few little bullets here and there in the margins to point out some of the off-topic stuff that was going on in the examples, and the book would be much more functional as a reference. As it stands, I probably will have to get a whole new book for that purpose.

Also, the support on this book is phenomenal. I missed a small detail in Chapter 6 that caused my script to fail, and when I posted on the book's message board, I had a reply from the author in less than a day. That's a really cool added bonus.

I am a frontpage user that has set up static pages in a web site. I needed to move from static pages to dynamic pages using a database. I couldn't use PHP with FrontPage so I switched to Dreamweaver and needed a book that covered both dynamic pages and Dreamwaver. This book walked me through setting up the environment to have Dreamweaver work with Apache, PHP, MySQL and phpMyAdmin. I am completely non-technical so these areas were beyond my comfort zone but the book walked me through it very successfully. It then took me through CSS styles, setting up an online feedback form, setting up my first database and tying it into Dreamweaver. It also showed how to insert, delete and maintain records in order to keep the database up to date. This was an excellent book for a non-techie as it didn't take any knowledge for granted.

This books covers pre 93 Korn shell.

However this actually makes learning the shell more simple. At work we have a pre-93 version so the instructions are sure to work.

The author's "93" version of the book is also good, but a bit harder to understand for a beginner.

I am programming with korn shell for 12 yr. already. And I started with this book. It is an excellent book for beginner and even intermediate programmer. It took me about 2 days to go through all book. i still looking inside once in a while. Few times i was loosing this book, bought another one and after short time i dumped it and bought this one again.
Examples and explanation in this book are so usefull, short and easy to understand, that you can't find better book. Your learning efficency really depends on it. Buy it, by all means you will be glad you did it.

This book is *the* way to begin working with the Korn shell. I needed to get up to speed with a shell scripting language in order to do Oracle DBA tasks. I bought this based on the strength of it's Amazon ratings and was completely delighted.

The author has a great style, easy to understand and very clear. I found the procession of topics to be very logical; a nice gradual build up from the simple to the more complex. There is plenty of 'depth' in each chapter and good highlighting of potential problem areas and difficult concepts. These have additional coverage to help steer clear of the hassles and come to a clear understanding of the more challenging ideas.

The examples are well thought out, they present each topic of interest clearly and in a meaningful way, without clutter. I have coded almost every single one and found only a few errors. Within a chapter the examples are presented with increasing complexity, but are never the page after page monsters that leave you lost. It is amazing how well the author illustrates the content with short (20 - 30 line) samples.

When I was puzzled with something I had read here, I turned to two of my friends who 'live' in shell scripting up to their necks. Both have learned useful techniques from this book through my questions.

My copy is literally starting to come apart from constant use for reference. It is that good.

I found this to be an excellent hands-on tutorial in KornShell. Wish there were a book-2 and book-3 with advanced training.

I love the Korn shell. This book is a fine intro to Korn Shell programming. For users who want more than just an intro, you may want to consider "Korn Shell: Essential Programs for Your Survival at Work" by Larry L. Smith. Examples in Randal K. Michael's "Mastering UNIX Shell Scripting" are also helpful.

This book gives the right approach to programming with J2EE tools. It explains when to use J2EE and when not to.
It's not only useful for J2EE programming but also for non-J2EE enterprise projects as well. I STRONGLY recommend it. I have learnt so much from this book.

I bought this book because I've read very good reviews. I found this book amazing. This books shows you how to make good designs and develop in J2EE, all the chapters with full of comments from Rod's experience. Many of the concepts of this book were later applied in Spring framework. I strongly recommend read this book for advanced Java developers.

Frankly, this book has gotten a little long in the tooth. One might say that, from the products it mentions and evaluates, it is out of date. But never mind!

Rod applies principles that never go out of date - only the examples do - or seem to. A product is stuck with its basic design forever. Thus a critique of the 2002 version of Struts is as valid as a critique of the 2007 version.

Pros: Readable. Insightful. It will make you a better architect.

Cons: Typos (how do chapters get mis-numbered in the ToC?!?) It really should be in a high-quality hard binding (though the binding is quite good for paper).

Summary: 'J2EE Design...' is worth much more than its weight in gold. Buy it. READ IT!

I thoroughly enjoyed reading this book, particularly well-thought out design guidelines for developing J2EE application with or without EJB. The author introduced several best practices particularly the concepts and usage of Spring and Hibernate based j2ee development is quite helpful. In addition to this book, I find patterns and bestpractices from "Core J2EE Patterns /Deepak Alur", "Core Security Patterns /Christopher Steel" and "Enterprise Integration Patterns /Gregor Hohpe" would be helpful - especially if you are building a enterprise-class j2ee applications.
Now the downside, the book needs a complete revision to include changes with J2EE 1.4. The CODE SAMPLES explained in this book does'nt work now - please update.

It is a great book. But I give it only 4 stars is because it is hard to read. English is my 2nd language. I cannot read this book quickly. I even need check dictionary at least 2 times per page. I do not have the same problem when read other tech books.
"What is WebSphere" is another book I like. Also help me to learn system level stuff. It is much easier to read. Though it does not have so many stuff like Johnson's book.
I would like to suggest the auther to consider many tech readers are not very good at English.

This is a wonderful book! The instructions are easy to follow and all of the games are fun. I liked the fact that the finished games are on the CD so you could see what they are like while you are working on them.

As a special education teacher, I would like to think that I have a keen eye for books that can hold my student's interests while meeting their diverse needs. The Game Maker Apprentice does that and more. The only negative comment I have heard about this book from a student is that it does not cover modern three dimensional game programming. My response, you have to learn how to crawl and walk before you can run.
Game Maker Apprentice achieves its goals masterfully, and I will continue to use it to teach game programming with my students.

I have started using the Game Maker's Apprentice book and it is well written and has easy to follow directions. I am sure I will enjoy creating games with it.

This book, and the accompanying software, provide a FUN way to create some games. I used this book with four teenagers (ages 12-17) and they had a blast! I would recommend this book for anyone who wants to learn more about how games work, while having fun at the same time.

I downloaded Game Maker 7.0 and read its manual prior to purchasing this book.

My hope was that it would fill in the "holes" not explained by the program manual.

First, the good.

The book gives an excellent explanation of program logic and keeps things simple and effective for any experience level.

I also liked the fact that you could read the book and see examples without actually completing the tutorials.

I especially liked the way the book would demonstrate a particular game tutorial with an easy-to-read flow chart.

So if you didn't understand the Game Maker's manual this book IS for you.

Here is where my 3.5 star rating comes in.

I paid about $25 for the book to go beyond the program manual.

The book had a couple of the tutorials that were listed on Yo-Yo games web site. I don't like the idea of paying for something that is provided for free. However, it gave a better explanation of Game Maker's interface.

Although you can make a fully functioning game without programming, I was hoping for more guidance on Game Maker Language (GML), which you will need in fine tuning games created with Game Maker.

I was also hoping for more variety in the tutorials. Not everyone may want to make an action oriented game. For example, I wanted to make a little board game, but that isn't discussed in the book. Hopefully, it will be covered in the next edition or another book.

I still recommend the book, but make sure you are getting it for the right reasons. Review the PDF file and sample text carefully looking at the table of contents and index. You might be able to accomplish your goals by reading Game Maker's manual and looking through the forums.

This is an excellent introduction to the Agile Software Development concept for anyone who learns best from examples. Mr. Martin's book is essentially a collection of introductory concepts and principles he has spoken or written about elsewhere. Much of it may be available on the web with some searching but here it is organized logically into 3 major approaches to learning: concepts, principles, and case studies. In the first chapters Mr. Martin takes us on a high flyover of Agile Software concepts such as extreme programming and test-driven development practices. Next he takes us through Java and C++ examples to demonstrate programming with key principles in mind such as "The Single-Responsibility Principle" and "The Interface-Segregation Principle." Finally he sums up the concepts and principles by examples using several real world case studies.

Mr. Martin is a master at this sort of approach to teaching software design. Those familiar with his work will immediately recognize his hand. Some (perhaps most) learn well from this approach and the organization of the book lends itself well to a classroom study or self-directed learning. This is an excellent introduction to an important and timely topic.

Reader,

This book addresses some of the key reasons software continues to fail. It firmly ends the discussion that was never relevant of 'Agile means you do not have to REALLY known OO design'.

Indeed to be 'Agile' and not create iteratively 'crap', the only real way is via your mastery of OO Design. Long term systems that withstand change do not happen via accidential discovery with a lack of vision and core design at the core.

You can work in software with a lot of gaps, but the content here defines what is mandatory for even moderate levels of interesting work.

Do you agree in the following as a common value of `good' for software?

FROM: http://articles.techrepublic.com.com/5100-10878_11-1050347.html

Good design

Well-designed applications offer software components that are more robust, more maintainable, and more reusable. Such applications should be able to adapt changing business needs without affecting design. For example, a banking application should be able to support new types of accounts without a change in the existing design.

Three key points of good design are:

Maintainability, which is the ease with which a software system or component can be modified to adapt to changing environments, improve performance, correct faults, or other attributes. Well-designed applications require fewer resources for maintenance and changes.

Reusability, which is the degree to which a software module or components can be used in more than one computing program or software system. Reusability of software components helps ensure faster development of software applications.

Robustness, which is the stability of software applications in extreme situations (e.g., maximum load conditions, erroneous user inputs). Robust applications have less downtime and can reduce maintenance costs.

Bad design
Nobody plans to create ill-designed applications. It often happens because of a lack of experience or because the app was designed quickly to meet an extremely tight deadline. Poorly designed applications usually have these problems in common:

They're rigid. A design is rigid if it cannot be easily changed. For example, a single change to heavily interdependent, rigid software could begin a cascade of changes in dependent packages. When such a program grows in size, the designers or maintainers cannot predict the extent of that cascade of change, and the impact of the change cannot be estimated. This makes the cost of the change impossible to estimate.
They're fragile. Poorly created programs have a tendency to break in many places when a single change is made. Simple changes to one part of the application can lead to failures in other parts that appear to be completely unrelated. Fixing those problems leads to even more issues, and the maintenance process begins to resemble a dog chasing its tail. Such fragility greatly decreases the credibility of the design and maintenance organization, which leaves users and managers unable to predict the future quality of the product.


They're not reusable. A design is difficult to reuse when its desirable parts are highly dependent upon other details, which aren't desired. If the design is highly interdependent, other designers will also be daunted by the amount of work necessary to separate the desirable portion of the design from the parts that aren't reusable. In most such cases, the cost of the separation is deemed to be higher than the cost of redevelopment of the design.

Still with me? Ok..


.NET developers historically have lacked (as compared to other OFA (one framework only) developers) at the very, very least) acceptable OO Design skills. I mean even remotely `predictably' acceptable. Sure I worked with many teams who were exceptions but they were all from other (Java/Smalltalk) environments. Even C++ developers can slant to a master of C, deep internals, and Fragile Base Class disaster (grin). So Microsoft would have been nuts as they have always know this to put multiple-inheritance into C#. I digress... This is relevant to the book I swear....

Uncle Bob Martin created a masterpiece here that is still just as (more?) relevant. It is utterly transformative for anyone who wants to be even remotely productive on a team of best-practice types.

FYI this is the book used when I teach 'Core Object Oriented Design for the C# Developer' around the country.

NOTE: Do not let the word 'Agile' fool you. This is a book about best practices in software design and development. Agile just assumes you already know this material, yet most I work with do not.

He provides definitive coverage of the most critical reasons for failure if you skip then. For example, inheritance in OO is wrong for most cases used today in .NET.

Liskov substitution principle
Read this (covered in detail in this book):


Kind Regards,
Damon Wilder Carr
http://blog.domaindotnet.com

It's a great book. As a senior developer with more than 5 year's experieces of Object-Oriented Design, I think this is a valuable pragmatic book about how to do in a practical project.

I bought this for my brother. Got for a good deal on Amazon. Very happy with the fast delivery by Amazon.

After reading this text, I feel it deserves the attention of other great texts such as Design patterns and Refactoring, even though much of it's content expounds upon the ideas of these two classics. It's my opinion that this text has two strong points: it explains the ideas and details of agile development very clearly, and it does an excellent job of explaining the most popular patterns originated by GOF, plus a few more. The authors style was very good, with most of the examples in Java. Being a C++ programmer, I would have liked to see more examples in that language, but this is not any fault of the author.

A good reference to the PERL language.

As opposed to the O'Reilly publications, this book does not assume as much reading between the lines as what is written at times in those.

So, this may be useful for people to clarify what is being talked about in entries there, or just as a more clear starting point to begin with for the areas of PERL programming that it covers.

This book is a great reference if you just want to quickly look up a syntax. The index is very good and makes it easy to find answers to problems quickly, and it almost always beats trolling through google search results! While it would not be useful as the only text for beginners, I think it would make a good supplemental text. It also might be a good choice for people who already have experience in other languages, and are switching to perl, or intermediate perl programmers who cannot remember where every comma and semicolon should go!

I am extremely impressed by this merchant. The shipping was on time and the book was in great condition

This is a great reference book for perl. It doesn't try to teach the reader perl, which after you already know it is really nice. This is more like a collection of all the perlmod/man pages put together in an organized manner. I reference this book all the time for different syntax structures and many other reasons.

As a new programmer and new Perl programmer this is an invaluable reference. For the ambitious newbie this book can serve as a great starter guide to the Perl language. As a reference and supplement to another beginner book, this book really soars.

I was able to quickly expand my understanding of Perl and started writing real perl programs (albeit very simple ones as a beginning perl programmer) by using this book. You'll become well versed in Perl using this as your constant guide.

When a programming reference can be distilled is such a highly useful and pragmatic way, you've got to add it to your library. Brilliant job on this one.

I highly recommend this work and I'm confident you won't leave home without it. Or perhaps you'll buy one for home and work. I also highly recommend 'Perl Power' by John Flynt and 'Beginning Perl, Second Edition' by James Lee (Apress) as companion beginner books to this one.

It's now over 6 years since this book came out and it still has a tremendous amount of relevance. I am rereading it again and stop by every now and then in hopes that a new edition will come out. I have all the other Zeldman books and they are all useful, but nothing approaches how much I learned from this book. It amazes me how much of the content is still applicable. Anyone who's been doing this since the book came out can make mental notes about what has changed. A proponent of CSS before it was practical (really), Jeffrey seems to have planned a long shelf life for this book.

If you're a graphic designer who is entering web development (which is a large segment), it's still a must read, but beware the 4.x browser version suggestions, and don't bother to try and support tables any more. It's not necessary, and it's bad form for oh, so many reasons. Everything else in the book is absolutely essential for the transition. Your best bet would be to read it and ask questions from someone who's been developing websites for a long time (and is open to web standards).

And if you've been building these things for a long time, it's still a great book to revisit at least yearly.

You can't really go wrong with a Zeldman book, imho, at least so far. If he writes something on knitting, I can't guarantee it...

This book gives a good overview of Web Design till 2001.
People who are interested in where the web is coming from will like this book. If your are looking for how web design is done today anno 2005 I would like to recommend Jeffrey Zeldman book "Designing with web standards".

Even though some of the content in this book is outdated (such is the nature of a book based on the internet, which evolves daily), it is still a mainstay in my collection. I would recommend this book to anyone even remotely interested in web design.

Jefferey Zeldman teaches basic, foundation building principles that you will use almost daily during your tenure as a web designer. If your looking for a book to hold you by the hand and teach you how to perform specific actions with step by step coding, this isn't your book. Instead, it touches upon ideas and methods. Zeldman covers topics from designing good navigation to fundamental steps in working with a potential client.

I gave this book 4 out of 5 stars. It would have received a perfect score if it wasn't for some outdated material. Purchase this book, it should be a part of any collection.

A thorough, comprehensive and usable book for people trying to migrate from traditional media into the (sometimes) scary world of new media.

Jeffrey Zeldman's unique voice permeates the entire book, holds your hand, and gently guides you through the ups & downs of working with the web. His examples are concise and to the point, his writing style (as always) humorous and friendly, and, most importantly, you get the feeling that he truly loves this medium, and would like nothing more than being able to help another person discover just what the fuss is all about.

Should be on the shelf of every designer - no matter what your level of experience is.

This book opened my eyes to issues such as accesibilty, css and xhtml, I now have a site that is fast to load and easy to update. I found this book to be an easy read,[ I am neither a graphic designer nor a trained web designer] I really like Zeldman's writng style and will use some of his points in my classes web design for photographers. The mix of code and ideas was great and for once I just read the book rather than being tempted into turning on my computer and starting work.

This book provides meticulous details about QA for integrated software and component-based software .This particular book teaches how to approach testing and QA in a systematic manner .The book gives an organized and detailed description for the Software Quality assurance for the software components. It teaches all the way from very basic step. Beginning with Black Box testing and following White box, Regression testing, Performance, System level testing .The approach includes various different validation methods that needs to be rigorously applied and a detailed QA approach which teaches all the possible Test Cases. Overall this book provides a complete teaching of the Component Based Software. Being Professor Jerry Gao's student, have completed software quality and testing courses under him. This book has increased my knowledge for component-based software testing as it describes different testing methods, phases, issues, challenges etc. I highly recommend this book for college graduates and professionals who want to brighten their career in QA and testing areas.

This is a very unique book on QA and software testing topics because it discusses some of the testing techniques & concepts extended from research world and also covers the modern software component concepts and the applicability of these techniques on them. The book is divided into IV parts. The first part introduces the reader with software components and it's testability. The model based solution to some of the issues and challanges can be applicable to the SOA based softwares as well.
Part II of the book discusses the fundamental black box and white box techniques. A section is devoted on white box techniques for object oriented testing.
Part III of the book focuses on most important challanges of todays software. The UML based approcah to software integration testing discussed in this book uses an unique approach of content and context based relationship of objects. Regression testing for maintaining software is discussed in detail.
Part IV is entirely devoted to QA topics. They fully cover QA measuremnet and validation topics, standards and certification.
This is a must have book for software developer, Test engineer and QA professionals. The references at the end of each chapter reminds you to go deeper and dig into IEEE and ACM papers on the subject. I have already recommended this book to my fellow software developers and managers.

The book has detailed coverage of all software testing terminologies and methodologies such as black-box, white-box, test automation, integration, and performance testing.Over all, this is a very good book for learning Testing techniques for component based software.This book is extremely well organized and should be useful for both novice and experienced software testers.

I learned many new concepts about Software Testing from this book. I learned how to do the manual testing, automation testing of the component software using this book. White Box Testing, which involves Control Flow Graph is documented well in this book anyone who wants to learn about the White Box Testing can easily learn through it. This book is very user friendly in terms of doing Software Manual Testing.
Automation Testing is described well too. I recommend anyone from Software Engineering planning to go into Software Testing should read this book atleast once.

This book helped me gain good knowledge about Software testing, its objectives and various approaches for real time experience. It helped me understand the basic concepts and fundamentals of Software component testability. Through this book, I got a basic idea about the rules and methodologies that are being implemented and followed in current software testing field, as per industry standards.

Black box and White box testing techniques and their relevant issues, challenges and solutions, the various test models, everything is explained very visibly. It serves as a good guide for the beginners as well as the Software professionals of all levels. Information on testing methods like Regression, Integration, Performance and System testing are detailed in a systematic manner.
The information in this text book, taught us to follow the best ways to achieve a well defined test coverage criteria by deriving a definite plan for the project- a plan for managing the schedules, designing and testing the software based components to meet the requirements in the project within a deadline. We, in a team, worked on a Simulated ATM machine, for a practical experience, and the book helped us as a good start. Each chapter has a good introductory part, which gives a clear synopsis about the complete chapter.
The book explains the role of different testing tools, designing and handling the test cases, how to perform component testing quickly and efficiently through automation testing, without manual involvement. Manual testing is time consuming and hence to solve this issue, Automation testing has been introduced lately and this information has been illustrated by the authors very clearly in the book, with suitable examples for the readers understanding.

I personally found this book very helpful and knowledgeable. A Software component's life cycle through the testing phase has been explained well, alongside giving us information about the methodologies to improve the quality of a product, and how to derive a test case to support the functionality; everything is mentioned in this book. My only suggestion is, this book is a complete pack of information on testing of a Software component and its Quality assurance, and hence, from college students to Software professionals, everybody has to experience this book, if they are seriously looking to pick up their career in Testing.