After reading the (glowing) reviews for this book, I purchased a copy. I would say that this book is pretty weak. He presents a lot of shallow arguments, but doesn't go into the details that one would expect. His coverage of the Internet protocols is not at all in depth. I had hoped to get a more detailed analysis of the protocols of the Internet. I also find his presentation for describing the "Abstract Protocol" language as vague and confusing, and the syntax is needlessly convoluted. Why does he need to use a 'box' symbol to separate different actions? Perhaps another symbol which actually appears on most keyboards would have been a better choice.

Not only did I have the pleasure of reading this book for my Networks class, Professor Gouda also the instructor for the course. The book is excellent -- and though it is not entirely applicable -- for networking theory it is outstanding. The book is very clear and though technical in nature --- it is not long winded and difficult to understand. I completely recommend this book for anyone who would like to learn the basics of networking.

This is SUCH a good book. I took an intro to Networks class and this was the book we used. It was my senior year and I was SO sick of reading textbooks that made no sense. This book made me decide to get my masters in networks. It is very clearly written, very easy to read, the explenations of the algorithms are easy to understand. This book deserves 6 stars, not 5.

Mahmoud Mohamed Taha is one of the most original and daring of modern Islamic thinkers. This book of his, undeservedly ignored in the so-called liberated West, is a proclamation of reform and tolerance, against the oppression and despotisms that currently enmesh the Muslim world. He was a man who refused to recant, regardless of the hostility of public opinion during the dictatorial regime of Ja'ffar Nimerei, and chose instead to suffer the martyrdom of the hangman's rope. Nowadays, his followers dare not declare themselves, nor breathe a word of his teachings publicly, for fear of being persecuted and stigmatised. Admittedly, his doctrine may seem unrealistic today, in the world of multinational companies and mass consumerism. Much of it is riddled by logical contradictions. For example, it is nonsensical to talk of reforming Islam, a religion which is doctrinally irreformable. But even if one doesn't agree with him, one is still moved to admire his courage...

Mahmoud Taha had issued this book at earlier days and it seems that as if he was knowing what the world will be after a short period of time.
He was killed because he call for peace [peace with yourself, with others and with God].
But those who do not want to listen made the consipiracy and killed him.

Today's situation is what he told[If we left them they will destroy the image of Islam].
Terror has com out because right understanding of Islam is not welcomed by most of Muslims.

This is by far the best book for non-Arabic readers. While Ustazh Taha had written over 30 books detailing his thought about Islam and proposing solutions for mankind problems, only two of these books were ever translated to foreign languages. The fact that the translator, Dr. Abdullahi An-Na'em was himself a follower of the teachings of Ustadh Taha, and a renowned international law professor and human rights actvisit, makes this work readable to westerners, while sticking to the original meaning of the Arabic text. No man has been so misunderstood and his thoughts and deeds unappreciated as Ustadh Taha, both at the local and global levels...

The power of the written word to convey emotional intensity in a pleasing visual form, particularly when dealing with sacred subject matter, has been a constant them in Islamic culture. The demanding discipline of Islamic calligraphy, transmitted from master to pupil throughout the ages, has been the source of one of the humanity's richest artistic traditions. The Nasser D Khalili Collection holds examples of the Islamic calligraphy that span six centuries and demonstrate the continuity of this central art form into the modern era. The holdings - nearly 300 in total - include exceptional items that feature the work of many of the most famous master calligraphers: Yaqut, Seyh Hamdullah, Hafiz Osman, Mahmud Calaluddin, Mehmed Rasim and Yusuf 'Hafiz al-Qur'an'. This book is intended for islamicists, collectors and curators of Islamic art, specialist art trade, some students, and general readers. With a contribution by: Zakariya, Mohamed;

This a well written factual study of African civil wars. It clearly addresses the crisis without taking sides or introducing any ideological or other agendas. The chapters on Somalia, Sudan, Uganda, Mozamique and Rwanda are outstanding. Moreover, the conclouding chapter brings in an outstanding and fresh perspective. In short this is an excellent book.

Having a strong interest in the culture of the African Horn I read this book on Somalia for further insight into one of the African continent's most interesting and remote countries. Somalia has a fascinating culture making it unqiue in Africa for being a transition zone from the Muslim north to the Christain/Animist South. The Somali culture long based on clans is also unique to the Sub-Saharan African realm in that the Somali population is relatively homogenous. Ninety nine percent of the Somali population speak the same language and share the same culture despite being fractured by ruling clans.
This book gives a wonderful introduction and detailed description of the country's culture, history and political-economic situation. The only problem is that more quality pictures should of been added to give the reader a more acurate picture of Somalia rather than being a desolate desert land with starving people. Other than that this book is gold.

My advisor recently showed me a copy of this book and I'm so glad that we have such a great and useful book in Digital Communication Theory area from someone who has spent many successful years of his reasearch life in this field. I appreciate what these peple doing to share their knowledge with studnets like me and next generation of Engineers and researchers.

Electrical Power system is one of the greatest text books I have read The only problem that I am facing in order to prepare my self for the PEO exam is the solution manual of the book which I can not find any where for purchesing, So even when I try to solve the problems at the end of each chapter I can not tell if I have solved this problem or that one correctly I wish the book came with an answer sheets

the content suit student who would like to study fluid dynamics in a more specific content. those content are important and critical in fluid. this new book has the quite new fleid like MEMS, it also has interesting historical note, and mixing. this book is useful.

The answer to the three questions raised by the title of the book are 1) Islam is the only true religion, therefore Islam will conquer all other religions 2) American power will diminish since all civilizations rise and fall (Rome, Greece, Persia, etc) 3) Allah's predictions will soon come to pass since we live in the "Last Days".

There are in the book interesting sections on Islamic religious and philosophical schools through the centuries, and the various sects of Islam; also a short section on Muhammad (not a man to cross!).

However, if you are looking to buy this book based on the title, forget it.

Even though the book is a wealth of knowledge, specially for non-muslims, it would've been better without this misleading title. If you think this book's gonna talk about terrorism or 9/11 or stuff, you're wrong and cant be blamed for that. The book is extremely informative but i deducted 1 star for that catchy stupid title (not that its a lie though) and 1 star for not providing me any info i didn't know.
There're are four chapters in this 125 paged book. The first three chapters are pretty much intro to Islam/Quran/Mohammed (pbuh) with a deeper look as you read briefly about Islam's beliefs, history, culture, philosophy, society, scholars and sects etc. Non muslims would like this info if they seek Islam's knowldege but as i'm a muslim, i skipped them as we study these topics since our childhood. Chapter 4, the only one having something to do with the title of the book, starts on page 103(outa 125 pages) and is amazingly interested to both Muslims and Non muslims. You first learn about this intricate mathematical code in Quran from God that keeps it from corruption from man. After assuming you're satisfied that Quran's word of God (you will, once you see this code open mindedly) it goes to tell that whole the content of Quran is word of God and hence true. Then in the last four pages of the book, authors quote verses from Quran about downfall of nations etc. Well, once you believe Quran is word of God, downfall of nations wont be the first thing you'll wanna know.
The bottom line is Non muslims should buy this book and disregard the title while Muslims should rather buy Ahmed Deedat's 'Quran: The ultimate Miracle' which only explains this code. About 9/11 i'd recommend David Icke's "Alice in the wonderland and the WTC disaster" and you wont ask of any other book on the topic. After getting done with this book on the first day, all i can do is tape up the last half of the title of the book (And American...) and forward to friends.

This is a very thought-provoking book for any follower of ISLAM to read and also, the title is very straight foward of the book`s contents.

I am currently working on a research project focused on the same area, The IT organizational transitioning to Object Oriented software development environment. From my experience and through my research, I found this book is a much-needed book in the area of ?transition? to object-orientation. Various authors have considered words such as adoption and diffusion to indicate the manner in which object-technology should be used. What has been missing is the discussion on how to move the existing organization to the ?new? or object-oriented way of executing software projects. This book satisfies the crucial need of discussion the transition issues.

Ch 1 of the book starts off with some basic discussion on the importance of object technology, and clarification of some commonly used but potentially confusing terms. This sets the scene for planning for transition, a crucial aspect of any process, as outlined in chapter 2. Challenges of moving to OO (page 35) provides the starting point for further brainstorming by project teams, each identifying their own challenges in addition to the ones that the authors have identified. The various types of plans, their significance and the role they will play in transition are discussed in chapter 3. However, chapter 4, according to me, forms part of the most important discussion in any transition ? that of cultural change. Change and culture are challenging topics in their own right. The authors have done an excellent job of combining the two, in the context of OO transition. The suggestion of nominating ?Change champions? (page 71) is invaluable, as such champions provide the necessary ?catalysis? for the transition process.

The authors maintain their foresight through chapters 5 and 6 ? an example being chapter 6, section 6.2, wherein they correctly suggest selection of a ?method? BEFORE selecting a CASE tool, which, in my opinion, has saved many organizations the pains and confusion resulting out of bringing the two together at the same time.

While chapters 7 through 10 do not contain anything dramatic about them, they still maintain the consistent theme of ?transition? in them. Chapter 13 emphasizes the need for documenting the development process, and steps, templates and metrics discussed there, as well as in chapter 14, are most helpful to a practitioner.

Personally, I don?t think chapter 15 brings anything new to the reader, but it is a timely reminder on the inspections aspect of testing OO products.

This book presents a thorough guidance about how to manage the difficult process of transitioning from conventional software development to object-oriented software development. Today, object orientation brings several promises and pitfalls, however, it does not eliminate the need of programming/design skills, rather, the paradigm usually demands an even stronger knowledge and experience. As the authors state, the growing tendency to use third-part components requires of suitable design structures able to support these components. Hence, objects are becoming more and more a real need in terms of cost and added value. Moreover, it places object-oriented frameworks in an important position, as a practical way to express reusable designs and capture the essence of patterns, algorithms, components and architectures. Regarding users and non-programmers, the authors argue that object-oriented technologies can make system analysis and design more accessible by reducing semantic gaps. This argument can be partially true for some projects, but it should be taken carefully because the inherent complexity of the object paradigm is far more complicated than other software development approaches. In my opinion, we can just say that objects promote better software quality, but their conceptual simplicity is more likely to be a myth.

Software development planning is seen as a critical component within the framework. Planning appears as a dynamic activity that serves as a controlling document for managing the software development project. In this context, it is important to stress the notion of business plan, to specify how the company will make money, the assumptions about the business environment, and the risk factors involved in the project. The authors refer also to the different roles in this process, and describe some standards such as ISO 9000 and the CMM model. Furthermore, the tips and practical advice included at the end of the sections result very useful to complement the theory. The book also talks about the well-known issue of dealing with culture changes, and gives a list of possible ways of selling change (with object orientation) minimizing the risks. The effects of these changes on the development team can be tough, and they should be balanced. As example of this situation, software engineers who where proficient at procedural programming may tend to spend more time on implementation issues than on object design, while developers who were familiar with data modeling may tend to develop more elaborate object models. In this line, some key responsibilities of people in the team are mentioned (for instances: a domain analyst, a prototyping expert, a distributed object applications expert, and a framework developer), in order to direct the staffing and organization of the project. Nonetheless, despite the author's suggestions, change will be a very uncomfortable activity for sure. In brief, the book outlines the basics of planning and some practices to promote change. Those readers looking for a more complete treatment of the subject should complement this information with other sources. When it comes to technical issues, the authors discuss the role of object-oriented techniques and CASE tools supporting these techniques. The selection of these techniques/tools will depend on how they simplify the decomposition of systems into manageable pieces, how they provide a consistent way of proceeding through the software development process, domain considerations, and graphical facilities, among others. As one of the most interesting contributions of this part, the authors propose a process for evaluating tools on the basis of criteria such as utility, extensibility, flexibility, usability and completeness. Then, they move to some topics about strategies for legacy systems, maintenance and reuse. In this context, the book remarks the benefits of reusability and how it affects budgeting. Several tradeoffs about initial investment and development of specific components/frameworks versus usage of third-part components/framework are covered. At the end, it is argued that the development should be oriented towards engineering adaptability. Personally, I think the technical contents included in these sections are the soundest part of the book.

Finally, the book goes through some conventional project management activities considered from the viewpoint of object orientation. In this line, activities such as project tracking and control, documentation of the development process, software metrics and inspection of software products are explored. Although there is nothing really new in this part, all these activities work together under the concept of processes as baseline for improving software quality. Processes will guide project evolution, documentation and inspection. Moreover, the definition and measuring of these processes (more important than measuring people or code) is a crucial aspect to be successful at object-oriented software development. As regards software metrics, they are useful as they can be applied to repeatable processes in order to take decision about the project. A valuable template for documenting these metrics is included. Related with this matter, the realization of inspections to remove defects early and to avoid rework is encouraged, providing some recommendations for their application. It is important to note that all these improvements are not a minor factor in the budget of the projects, rather they usually involve a significant part of the overall investment.

On the whole, the book provides a comprehensive walk trough the most important aspects that should be taken into account to move towards object-oriented development. It is mainly directed to organization leaders, software managers, and people not very familiar with object technologies, who have had some experience in conventional software development. The sections are coherently organized, and the style is very fluent with profusion of diagrams and tables illustrating the concepts presented. The inclusion of tips and practical advice fit properly in this context. I think the book is a very good introductive reading for those who want to foster the unsettling process of object-oriented software development.

This is an excellent resource for those organizations (and individuals) who are experienced in traditional software development and would like to consider the more modern object-oriented approach.

The authors clearly describe the culture, mentality, and the process. I have myself published about the subject, but this is a relatively comprehensive and complete book that describes and illustrates the transition rather elegantly.

Not only I would recommend the book as a textbook for the university teaching and students, but I also recommend it to software engineering professionals and organizations. I frequently use it for consulting and to complement my teaching and training classes.