Joe Saur

Book review: Mathematical Modeling and Simulation: Introduction for Scientists and Engineers by Kai Velten, and published by Wiley-VCH, 2009, paperback, ISBN 978-3-527-40758-3, 348 pp.

“Everyone models and simulates”, and the author points out that engineers and scientists especially use modeling and simulation (M&S) on a day-to-day basis. This book is intended to be an introduction to the subject for engineers, scientists and undergraduates. Some calculus and linear algebra are required; all other concepts and ideas are developed in the book. Opensource software is introduced, and pointers to sources are included. Software covered includes CAELinux, Calc, CodeSaturne, Maxima, R and Salome-Meca.

Book review: C Programming: A Modern Approach (2nd Edit.) written by K. N. King, and published by W. W. Norton & Company, paperback, ISBN 978-0-393-97950-3, 832 pp.

As Dr. King points out, all languages have both strengths and weaknesses; the important thing is to be aware of both, to use the former where they are useful, and avoid the latter wherever possible. This book aids one in doing just that. The book is intended to be a comprehensive guide to the language as it currently exists (both C99 and C89 are covered; the former is emphasized), and as an introductory textbook at the college level. As such, it is divided into four parts: • Basic features (Chapters 1-10): covers the creation of single-file programs using arrays and functions. There is also a brief history of the language, and the ongoing evolution from K&R C, through C89, and finally to C99: what drove the changes, and how the approach to using the language has differed over the years.

Review of "Just Enough Requirements Management: Where Software Development Meets Marketing by Alan M. Davis", Dorset House Publishing, 2005, ISBN 0-932633-64-1.

teams, and the test team. Based on this, his book has two main foci: the process of establishing a clear contract between the test team and the rest of the organization, and the steps the test team needs to take to fulfill its end of the bargain. Given this approach, the book is naturally divided into two halves. Part I (System-Testing Issues) covers: • A 12-question true/false test intended to clarify the reader’s understanding of his/her preconceptions about testing • SDLCs • Exhaustive vs. thorough vs. practical testing • The respective roles of the developer and tester in testing • Users, and their dislike of unpleasant surprises • System-test oracles: the user documentation • Change management issues • Implementation mistakes vs. symptoms of systemic problems Part II (System-Testing Solutions) deals with: • Mapping issues (from Part I) to solutions • Solution section A: Establishing a methodology, techniques and tools for system testing. • Solution section B: Executing systems tests while influencing project behavior • Solution section C: Organizing, sizing and building a test team • Solution section D: Changing project attitudes through roleawareness seminars As a former test manager, I would have found this book very useful in helping me to understand both my role within the organization, and the issues inherent in that role. I would also recommend it for development managers and project managers; the basic premise (clearly defined roles, agreed to by all parties) makes too much sense to be ignored. And the basic test approaches outlined in Section B could be applied at multiple levels. For whatever reason, users (and some developers) continue to believe, in the face of all sorts of evidence to the contrary, that exhaustive testing of the average system is not only possible, and that anything less is somehow unacceptable. Until that reality changes, testers need all the help they can get, and this book at least helps them to be understood within the development team. Reviewed by Joe Saur, Sr. Research Scientist, Georgia Tech Research Institute, <joseph.saur@gtri.gatech.edu>.

Review of "IEEE Computer Society Real-World Software Engineering Problems: A Self-Study Guide for Today's Software Professional by J. Fernando Naveda and Stephen B. Seidman", Prentice Hall, 2006, ISBN 0-471-71051-2

It is unlikely that a single analysis model will be able to analyze the requirements for the complete system. For capturing and analyzing the overall requirement separate models and analyst experts are needed. It is necessary to model at different level of abstraction so that both domain experts and developers can get an idea of the overall system behavior or focus on a particular part of the system in detail if required. This paper proposes a methodology, which is an improved process for requirements gathering and analysis. The proposed methodology is based on modelbased techniques to provide a specific model for the type of requirements to be gathered. This methodology also provides domain-based technique, for providing a domain specific goal model for domain experts. The domain specific technique also provides multiple level of analysis and refinement process of goal in all domains by specific domain experts.

Review of "Software Development for Small Teams: a RUP-Centric Approach by Gary Pollice, Liz Augustine, Chris Lowe, and Jas Madhur". Addison-Wesley, 2004, paperback, ISBN 0-321-19950-2.

The development of software is much like the preparation of a gourmet meal: one must concentrate on everything, as skimping on any one part can bring disaster. For example, when cooking paella, worrying about the cooking temperature and spices would be meaningless if the ingredients were not fresh (bad requirements), or if the presentation were poor (inadequate testing). Approaches, then, which emphasize all aspects of the development process are to be encouraged, and this is one of them.

Review of "Software Reliability Engineering: More Reliable Software Faster and Cheaper - 2nd Edition by John Musa". AuthorHouse, Inc., 2004, Hardback, ISBN 1-4184-9388-0, Paperback, ISBN 1-4184-9387-2.

The development of software is much like the preparation of a gourmet meal: one must concentrate on everything, as skimping on any one part can bring disaster. For example, when cooking paella, worrying about the cooking temperature and spices would be meaningless if the ingredients were not fresh (bad requirements), or if the presentation were poor (inadequate testing). Approaches, then, which emphasize all aspects of the development process are to be encouraged, and this is one of them.

Review of "Find the Bug: A Book of Incorrect Programs by Adam Barr"; Pearson Education, 2004, ISBN 0321223918

Now, this is a real geeks book! Most of us would rather write code than read code, but all of us have had to spend hours (or days!) hunting for the elusive bug thats driving us crazy, and this book offers the opportunity to develop and refine our bug-finding skills. What a concept!

Review of "SASÒ for monte carlo studies: a guide for quantitative researchers by Xitao Fan, Ákos Felsvlyi, Stephen A. Sivo, and Sean C. Keenan." SAS Institute, Inc. 2002

This book is excellent for young analysts and managers. I have doubts if those with several years of experience will have need for much of the detail in the entire book. Older people (like me) usually prefer to read only summary information (which the author was smart enough to include) or to go directly to find something immediately applicable. Again, the book makes book these tasks simple and straightforward. The book really is “a guide to planning, analysis and application.” If the need is for a great deal of guidance, then this book may not be sufficient by itself. It will, however, be an excellent choice to begin. Sites with a metric programme in place will find several uses for the book – both to bring “lesser mortals” up to date and as a training guide for those who are beginning.

Review of "Visualizing categorical data by Michael Friendly." SAS Institute, Inc. 2000

This book is excellent for young analysts and managers. I have doubts if those with several years of experience will have need for much of the detail in the entire book. Older people (like me) usually prefer to read only summary information (which the author was smart enough to include) or to go directly to find something immediately applicable. Again, the book makes book these tasks simple and straightforward. The book really is “a guide to planning, analysis and application.” If the need is for a great deal of guidance, then this book may not be sufficient by itself. It will, however, be an excellent choice to begin. Sites with a metric programme in place will find several uses for the book – both to bring “lesser mortals” up to date and as a training guide for those who are beginning.

Review of "The people capability maturity model: guidelines for improving the workforce by Bill Curtis, William E. Hefley, and Sally Miller." Addison-Wesley 2002.

Part I focuses on information. It begins by introducing data management, and briefly presenting data warehousing, object-oriented models, and directories as the integration technologies of the 1990s. A few 2-page case studies illustrate data warehousing, directories, and Web-based data management. Next it lays the groundwork for introducing metadata as the solution. Unfortunately, although some chapters mention packaged vendor solutions and “tools, tools, and more tools” (chapter 6), the lack of concrete examples keeps the discussion abstract.