Rating:  Summary: THE Book For Anybody & Everybody In Software Review: This is THE book for all the professinals belonging to Software Industry.The book gives Pragmatic understanding of SEI-CMM Model addressing all possible stages and activities of Software Project Life Cycle.Correct weightage has been given to Engineering as well as Managerial perspectives of software project execution details. All Key Process Areas (KPA's)have been explained by mapping them with day to day activities in live project scenarios. This not only authenticates the explaination but also introduces the reader with state-of-the-art Software Practices. The illustrations given by Prof. Jalote in this book give concrete proofs of seemingly abstract concepts introduced in KPA's of SW-CMM. Important fact revealed in this book in the most convincing way is that CMM is more of a common sense and not a just another stringent standard.Having read this book one acquires clear understanding of SW-CMM, Software Project Activities and their inter-relation. This book is very much free from any kind of theoritical bias.It is something like the book written by the hardcore software professinal for all software professinals. The book is equally helpful for Software Engineers, Project Managers, Business Development Executives, CMM Implementors and for CEO's as well.
Rating:  Summary: Tries to take on too much Review: This title seems to be on every CMM person's shelf, based on title alone. However, covering up to level 5 in one book means that it is not a practical reference for a journey to any particular level. It seems to gloss over just about every topic, and fails to provide the level of detail to really be a useful guide. I have stopped using it at all as a reference.
Rating:  Summary: Tries to take on too much Review: This title seems to be on every CMM person's shelf, based on title alone. However, covering up to level 5 in one book means that it is not a practical reference for a journey to any particular level. It seems to gloss over just about every topic, and fails to provide the level of detail to really be a useful guide. I have stopped using it at all as a reference.
Rating:  Summary: The best author on Software Engg Review: Though I havn't read this book, but I have taken few courses under the author as an undergrad student at IIT Kanpur. The author is the best in his field.
Rating:  Summary: The best author on Software Engg Review: Typically I seldom buy a SW Eng. book, since it's a Have-Your-Habds-Dirty engineering, there is not much formulars, recipes and tricks for you to learn. We started our SW outsourcing last year with an office set up in China. Though we gained lots of experiences through painful trial process, I think we would have saved much more time and energy on both business and technical sides in dealing with our clients, should we owned the book earlier (we did not buy that from Amazon unfortunately) Since the author was a one time insider of the well known, NASDAQ listed Indian SW outsourcing company, along with his rich academia experience, the book is full of a ciombnination of engineering praticalness and acdemia sophiscation, and is well orgnized and well written. It touches not only the state-of-the-art, like tracability, impact analysis, risk management, SW metrics and effort estimation, but also addreess pratical issues like contract/agrement drafting and negotiiation, which we found is very useful. One thing confuses me is that asides from most of start-of-the art techniques adopted by InfoSys, why they use a revised Waterfall process model instead of popular evolutionary process. Is that because they are in the SW outsoucing busienss? Another suggestion is that, the book may looks like better if it can adopt a evolutionay/iterative/incremental way on telling people the story and the theory/practice behind them. Some popular books on UML are using this Unfidied Process way, evn on writing books. Is that interesting?
Rating:  Summary: A Must-have Bible for Anyone Practicing SW Outsourcing Review: Typically I seldom buy a SW Eng. book, since it's a Have-Your-Habds-Dirty engineering, there is not much formulars, recipes and tricks for you to learn. We started our SW outsourcing last year with an office set up in China. Though we gained lots of experiences through painful trial process, I think we would have saved much more time and energy on both business and technical sides in dealing with our clients, should we owned the book earlier (we did not buy that from Amazon unfortunately) Since the author was a one time insider of the well known, NASDAQ listed Indian SW outsourcing company, along with his rich academia experience, the book is full of a ciombnination of engineering praticalness and acdemia sophiscation, and is well orgnized and well written. It touches not only the state-of-the-art, like tracability, impact analysis, risk management, SW metrics and effort estimation, but also addreess pratical issues like contract/agrement drafting and negotiiation, which we found is very useful. One thing confuses me is that asides from most of start-of-the art techniques adopted by InfoSys, why they use a revised Waterfall process model instead of popular evolutionary process. Is that because they are in the SW outsoucing busienss? Another suggestion is that, the book may looks like better if it can adopt a evolutionay/iterative/incremental way on telling people the story and the theory/practice behind them. Some popular books on UML are using this Unfidied Process way, evn on writing books. Is that interesting?
Rating:  Summary: A very good hand book for those who implement CMM Review: Very few books (rather none) are available for practitioners who wish to implement CMM-based process improvement with illustrative examples. This book is an excellent aid for directing the thinking of practitioners.
Rating:  Summary: Good book Review: Very good reading for anybody who is responsible for the software engineering and project deliverables. Clear delivery of the material is supported by practical tools - templates, worksheets, etc. Example of the WAR project is very helpfull. I would highly reccomend this book!
|