Computer Science Books

This book came at a time when I really needed it. It helped myself and my group mates get a senior project done on time with a decent grade. It had all that we needed in it about matlab and then some. I'm glad to add this to my library of books that I'm going to be using for my carreer. I would highly recomend this book.

I have just started learning MATLAB and this is the best book I have found so far. The book is full of examples, well structured and can be used as a reference as well as a textbook. Numerous facets of MATLAB are covered including but not limited to linear algebra, flow analysis, symbolic derivatives and integration, and solving systems of equations both numerically and symbolically. This book was written to be used in a classroom environment but I had no trouble getting through it on my own. I would venture to say that it goes way beyond an introduction into intermediate practical uses for MATLAB. If you only get one book on MATLAB, this is it!

I reviewed a number of books before choosing a text for an introductory class on computational techniques for sophomore engineers. I chose this book because it struck a great compromise between the "Introduction to MATLAB" materials and the MATLAB functionality engineers really use (especially chapters 11 and 12).

The examples are thorough and plentiful. Student engineers and anyone new to MATLAB would do well to get this book.

This is an awsome! It was turned into the Disney Channel Original Movie 'The Other Me'! The movie was awsome too!!! A must read or see!

I love the book "Me Two" its so exciting, adventurous, and awesome. Then I heard they were coming out with a movie on "Me Two" on disney channel called "The Other Me". I was so thrilled!

I just love this book its so good its exciting, adventurous, and you never know what happens next.Then I was so happy that they made a movie on "Me Two" called "The Other Me". I was so happy!

GIS, intelligent digital geographic information systems - are turning geography into a business science, and Measuring Up: The Business Case for GISprovides case studies about companies and government agencies which have implemented GIS solutions in their business goals and plans. Chapters show how to save money and time using GIS-based systems, how to use GIS to generate revenue and help budgets, and how to manage the resources and information bases resulting from GIS systems. The inclusion of over seventy articles from over twenty business sectors span the globe in experience and setting, creating a very specific, detailed set of insights on new GIS-driven business processes. Highly recommended.

I picked up this book at an ESRI User Group meeting. I had seen it advertised and asked the local ESRI rep about it. He gave me the book!

It is an excellent resource. It cites specific studies of GIS use to illustrate how GIS can pay for itself several times over. There are plenty of examples to cover a broad spectrum of GIS uses. There are several government examples, as well as some less known uses.

There is also a slide show / outline based on the book that can be downloaded from the ESRI website.

This is an outstanding resource for increasing the return on your GIS investment as well as to get new comers up to speed in understanding the benefits to GIS. As a GIS veteran who has trained new users as well as managers new to GIS in the public, private and non-profit sectors, this is the best book that I have come across to expose them to the importance of GIS and how it has specifically reduced costs, streamlined and improved service as well as perform analysis not feasible in the past. I gave five books to a world class City Planning, Info Tech, Neighborhood Services & Law Enforcement department managers (and kept one for me).

What I specifically enjoyed is that this is a "non-technical" book that focuses on several real world examples of how GIS technology has been used by real people, in the real world, in modern times and budgets and how they benefited as well as how much "$" it saved them. Full of color images and very easy to read. By seeing case studies of what others have done, I am now implementing some of the same uses. So even a GIS dinosaur like myself has been able to steal some wonderful ideas that make my bosses look great. Making them happy keeps me happy. A lifesaver for the new GIS person (especially management) and a resource for the GIS Veteran. Well done & highly recommended.

This book will walk you through the myriad of excel functions that can help turn your spreadsheets into robust analysis tools, rather then dreary collections of numbers. A great resource!

This reference manual describes all the "FUNCTIONS" that you can use in Excel.

If you want to learn WHAT A FUNCTION IS, this reference will tell you.

If you want to know what Families of Functions EXIST in Excel, this reference organizes the functions into families ( Database, Date/Time, DDE & External, Engineering, Financial, Information, Logical, Lookup/Reference, Match & Trig, Statistical and Text Functions), and then lists and describes the details of every one of them.

If you ALREADY KNOW WHAT that you need to use an Excel function, this reference will tell you HOW to use it.

This is the dictionary of Excel Functions which are the heart of Excel. This is one of those rare books ( like a dictionary ) that is not diminished by the lack of an index.

The table of contents lets you find everything.

Recommended for financial programmers, engineers and scientist

Programmers working, or starting to work with Java on OpenVMS (Virtual Memory System) are certain to appreciate this excellent, hands-on tome on working with this language (complete with accompanying CD)--but as author Roland Hughes makes clear, interested programmers should first read his earlier book, The Minimum You Need to Know to Be an Open VMS Application Developer, since this book builds comprehensively on that one. A sequel (Volume 2)is in the wings. Hughes begins with an introduction that frames the basic reasons programmers are having to use JAVA in these applications and candidly lays out the major pitfalls programmers will encounter when applying JAVA to VMS. He focuses in particular on problems that C and C++ programmers have with JAVA, paying special attention to the momentum of the C and C++ mindset they bring to the table and the problems that can generate. For example, he points out that in JAVA, most things are classes--and while they may look similar in C and C++, they are not. He feels that many of these problems stem from the syntax and the origin of the language. Because Java was originally created as a pure OOP language used in imbedded systems (like the system in your microwave or VCR), almost everything in it is a class. Hughes makes it clear that in order to use JAVA successfully on Open VMS, you need to develop a Free Class Library, and reveals how to create JAVA classes with the Java Native Interface (JNI). Hughes provides a plethora of useful tips for transcending these difficulties, framed in a pragmatic approach that distains expensive shortcuts, and enables programmers to descend into the bowels of the applications with a knowledgeable voice at their elbow. The text contains many hand-on practical exercises that teach programmers to build applications while simultaneously constructing infrastructures, rewriting the same application with each new tool under review. At each step there are detailed explanations, examples and illustrations that allow the reader to move back and forth between the text and the application, providing a rich learning experience in working with JAVA on OpenVMS. Part of what makes the book especially valuable is Hughes' comprehensive candor about the flaws of JAVA when it is applied to OpenVMS. In addition to discussing the problems faced by C and C++ programmers as they try to change their mindset as they learn to work with JAVA, Hughes' explores a series of other challenges they are likely to encounter, including problems relating to case sensitivity and case sensitivity inside the compiler, plus problems resulting from the fact that JAVA is only a semi-interpreted language. While conveying much useful substance, the author also engages in lively, cogent (and sometimes humorous) commentary on what is driving the increased use of JAVA on Open VMS in contemporary IT culture. As he looks at not only the "how to," but he "why" of Java in these applications, it is clear that his sympathy is clearly with veteran C and C++ programmers and not IT management. A significant part of the problem, he feels, lies in the roots of the process and the way a great deal of IT business is being conducted not just with reference to JAVA, but with software projects in general. In recent years, many software projects have had a tendency to turn into monsters, destroying schedules and budgets, and raising programming costs late in the curve--a trend that does not serve IT goals well. As software budgets rise, management is desperately seeking "silver bullets," tools to cut costs while trying to achieve ever more challenging IT goals. But as Fred Brooks observed in his IT classic, The Mythical Man-month, the root of the problem is not just rising costs, but something inherent in the evolving nature of the information revolution. As the amount of data available rises faster than the ability to process it, programming tasks become ever more challenging. As a result, even as hardware costs are dropping, many software costs continue to rise. To cut costs, many projects start cheap, and are forced to add staff later when problems emerge. Unfortunately, the addition of people to a software project late in the process actually makes things worse. In a similar vein, Hughes suggests that IT management, by looking for a silver bullet, is ignoring the roots of the problem by only seeking short-term cost-cutting solutions. Silver bullets are often advertised, but do they really exist? Hughes clearly feels that in the end, quick fixes and short term cost cutting measures are penny wise and pound foolish. In the final section of the book, "Ruminations," Hughes engages in a colorful and educational rant about the state of the IT industry and the programmers that work in it, offering useful advice and insight that will be valued by novice and veteran programmers alike. Bravo, Mr. Hughes! Any IT professional using VMS should have this book on his/her shelf, and the "prequel" and sequel as well.

Stop right there. If you haven't read Roland Hughes' first book in this series, The Minimum You Need to Know to be an OpenVMS Application Developer you'll need to do so. Think of it as the prerequisite of a college course. Now, you are ready for the second book, The Minimum You Need to Know About Java on OpenVMS. Why two books? Java wasn't covered so thoroughly in the first. Believe me; you'll be glad you have both.

The concept of this book is "how to convert your existing core business application to use Java, yet still preserve your investment in the most stable platform on earth." In other words, Hughes shows programmers how to create all the tools you need to make Java a usable language on OpenVMS. Java is an object-oriented programming language somewhat similar to C and C++ but really very different. Hughes goes into great comparison. Java has classes, but has a unique class called an Array with no defined constructor. This means values can be stored anywhere and in no specific order. You're going to learn to build the tools you need to build the tools you want. Pretty simple, right?

As in the first book, Hughes uses the same application to demonstrate each new tool, in this book, using Java with FMS and RDB. He shows how to develop a generic class that will be usable by Indexed Files, also how to use JNI to access RMS, FMS, system services, and operating system provided libraries. Programmers learn to create an infrastructure MMS Procedure and how to use the supporting classes the procedure creates. Hughes also shows how to access RDB via the JDBC driver, demonstrating the importance of SQL. An accompanying CD-ROM contains the Class source.

This isn't just flat textbook reading though. Hughes uses humor and casual language to engage his readers. He comfortably refers to things like geek books and nerd attitude. He knows that this work is on the intense side of life. The information within the book is very professionally presented, with detailed analysis and explanations, troubleshooting and error experiencing tips, and exercise quizzes that test your knowledge. You have to know these things!

The final chapter examines the future of IT and the choices you make going into it. So you want to be a computer programmer huh? Are you sure? Don't listen to your guidance counselor without reading this book (and the first) first. Triple digit hourly rates, six figure salaries...maybe not. Downsizing, layoffs, feast or famine? Maybe so. When looking for sage advice on IT, go to the guru, Roland Hughes.

Reviewed by Regan Windsor for Reader Views (8/07)

While Java has exploded in the world of the Web and high tech toys, "The Minimum You Need to Know about Java on OpenVMS," focuses on "converting existing core business applications to use Java, yet still preserving your investment on the most stable platform on earth." For maximum understanding and success, this book should be read as a companion to "The Minimum You Need to Know to be an OpenVMS Application Developer."

In true "tell it like it is" Hughes' fashion you realize early on in this book that the author is not a big fan of Java. To a seasoned C/ C++ user, the similarities and yet vast differences of Java and C++ can make it a cumbersome (if not extremely frustrating) language to work with. The good news is this is not a sugar-coated book on Java; Hughes confronts the biggest setbacks of working with Java and what you need to do to work through them.

"The Minimum You Need To Know about Java on OpenVMS" covers basic code for using RTL and SYS functions, tips and tools for accessing RMS indexed files, the why's and how's of interfacing with FMS, details (including code) on creating a sample application (Mega Zillionare, as used in "The Minimum You Need to Know to be an OpenVMS Application Developer"), as well as some additional knowledge transfer and insights from the author.

As with the first book in "The Minimum You Need to Know" series, "The Minimum You Need to Know about Java and OpenVMS" provides the reader with invaluable tips and tricks, includes a CD full of code, hands-on-programming exercises, and questions for review. The book reads as though you are being coached through the process of using Java on OpenVMS, as well as being provided with a few insights (and opinions!) along the way.

"The Minimum You Need to Know about Java on OpenVMS" is an essential tool for anyone tasked with using Java on OpenVMS.

I have just finished going through this book yesterday and realized, I
didn't have this much detailed knowledge on the subject (even being a
networking professional for over 20 years). The book is definitely lives
up to the expectations, in fact I am yet to see a better book on
cellular wireless data (though this is not a main topic here). This book
goes quite in depth on some very unique aspects of GPRS and CDMA2000
data services, while presenting fresh view on the problem and uncovering

some of the interesting industry secrets. This book is a must have for
any one who wants to master wireless data and learn what Mobile or
wireless VPN is about.
Shneyderman and Casati do a great job of writing about this fascinating
topic. This book makes a great reference for data and wireless pros as
well as a good (but not too easy) introduction for any beginner. Style
is great and fresh too. Recommend it to all.
- Enjoy

I've heard plenty about mobile VPNs, and I've been looking everywhere for some meat on it. Finally, I found this book. If you are looking for solid, useful info on this topic, this is the book for you.

This is a very good book published right on-time. Covers hot mobile communications topics with good enough detail. Introduces mobile data communication concepts at first and explains mobile VPN's for 2.5G and 3G technologies. Although concentrated on CDMA2000 in stead of W-CDMA, this book is still useful on mobile data comunications and VPNs. Warmly recommended.

An unbelievably thorough, yet concise distillate of the whole of classical biological patterning theory. The bibliography alone is priceless.

I used this book, authored by my professor, while taking developmental biology in my final semester of a Cell & Molecular Biology degree plan. The book reflects my professor's very interesting approach to learning development: skeptical examination (in the iconoclastic tradition) of the principles underlying various models, which is more important than traditional undergraduate memorization of -say -mammalian embryonic fate maps (bo-ring!). His work is the first to hold developmental mechanisms up to the light together for a discriminating view. Don't forget your mental climbing boots when you read this- there's not an ounce of fluff.

Dr. Held has done a fantastic job distilling pattern formation processes to a collection of model classes. The bibliography alone is priceless - an superb piece of scholarship. Thank you, Dr. Held.

This is a great textbook for people wanting to learn the basics of programming computers.It logically presents ML,Java and Prolog.The first sentence states,"Computer programmes are practical magic.".It absolutely is ! You will enjoy reading the historical background on programming too.The ideas really are not difficult to fathom .If you have a desire to learn the foundations of computer language design.For an advanced computer student,this book will be repetitive and frivolous.Yet,i found this basic programming book to be enjoyable and insightful.

This is one of the most clear and enjoyable Computer Science books I have ever read -- and being a CS Ph.D. student I've read quite a lot! The examples are at the right level of complexity, and the exercises at the end of each chapter are actually (gasp) fun! Alternating theoretical and practical chapters makes for a very balanced reading, where abstract concepts are explained by linking them to real language features.

The book smoothly moves the reader through Standard ML, Java and Prolog in a concise and pleasant manner. Although it doesn't go deep in any of these languages, it provides the reader with enough background to create simple programs and utilize the power of each language; the interested reader can go on to learn advanced language features with the confidence that all the basics have been covered. The book draws clear distinctions between all three languages, each of which represents a different way of thinking about programming. If you are looking for an excellent book on programming languages, or you just want to get a feel about different programming paradigms, this is your book!

I just finished using this book teaching our Programming Languages course. We easily covered the entire book in a 15 week semester while adding additional material on Formal Semantics and Concurrent Programming. I really loved the book; the writing was engaging (I'm not kidding, this is the best textbook I've ever seen) and the supporting materials were extremely helpful. The greater-than-usual attention to functional programming languages (Webber covers ML, Java and Prolog) was initially the most important feature for me.

The only possible complaint about the text is that it doesn't go into more detail on a number of topics. The next time I teach the class, I would be happy to use it again while providing supplemental material, although I am considering Friedman et al's Essentials of Programming Languages.

This is the extension to the first book, Process Patterns, and covers the testing, release and production milestone processes in the system development life cycle.

Highlights:

- All processes are cataloged by life cycle milestone and presented in pattern format for quick reference and consistency.

- The author provides an excellent tutorial on patterns in the front of the book.

- Will work with any life cycle model (waterfall, spiral, iterative, etc.).

The material is well thought out and complete. I was impressed at the depth and detail in each of the patterns, and am gratified that someone has taken the time to write a book that covers what happens after development. If you are working in the Rational Unified Process environment you may want to consider, instead, the author's newer book titled "The Unified Process Transition and Production Phases" (ISBN 0521652626), which contains the same material, but aligns it to the Unified Process (the book calls it the Enterprise Unified Process, but it's essentially the RUP).

I was really impressed with this book. When you first read the description of it - it's about releasing software and then maintaining and supporting it - you wouldn't guess how valuable it really is to developers. Writing the greatest software in the world won't do you any good if you can't get it in the hands of your users, and the author tells you exactly how to do this. Gems of wisdom permeate the book, for example you need to plan to rework your software once you've tested it and that you should take the time to do an assessment, what I would consider a post-mortem, to learn from your mistakes (the author says experiences but call it like it is). The material in the book isn't rocket science, which the author is quick to point out, but it is something that is key to the success of your project.

I really liked his idea of assessing your staff once your software is baselined for his "testing in the large." I think its exactly as he says, that developers will stick it out until the current release is ready to go out the door and then leave for greener pastures. By assessing them and investing the time to do career management you increase the chance of keeping your staff.

I also liked his treatment of how to release the software, he's one of the few people that seem to recognize that you have to release software to your operations department, your support department, and to your end users. Once again, not rocket science but something that is often overlooked until the last minute.

A strength of the book is the Maintain & Support phase. I've done software support before and it's a bitch. It's about time somebody finally wrote about it and told people how hard it actually is. Including Maintenance & Support in your software process is really important in my mind.

Just like the author points out, the best developers take maintenance into consideration, the best project managers must also take into consideration how their software will be supported too. This philosophy is a big strength over the Unified Process in my mind because the full spectrum of the software lifecycle is taken into account, not just development. The author's "Identify Defects and Enhancement" stage process pattern is really just basic change control once your software is out the door but once again he did a really good job of saying how to do it.

Another strength of the book is that it is based on real-world experience -- this stuff sounds to me like it would actually work. The book also has a solid foundation in theory, bringing both proven and theoretical practices together in an effective manner.

I also liked chapter 10 because it summarizes key project management issues, such as training and education of your staff, risk management, metrics, quality assurance, and risk management from both Process Patterns and this book, More Process Patterns. These are all important issues that must be taken into account to succeed. In fact, for many people this book is a good buy just to get this chapter alone.

The one thing that I don't like is that you really do need to buy two books, this one and the one before it, Process Patterns, to get a full picture of the overall software process. However, both books are pretty big and they both contain excellent information so its not such a bad thing in the end.

This book provides set of well designed patterns from which to develop service delivery processes. This is the only book I have come across that manages a clean, seamless segue from application delivery to service delivery.

First, to appreciate this book's approach it is important to know what OOSP and patterns are - this will set your expectations about the book and what you can get from it.

OOSP stands for Object-Oriented Software Process. It is an approach to software development within the context of object-orientation. Put another way, it is an object oriented approach to application delivery. Both of my definitions fall short, but if you are familiar with the unified modeling language (UML) or the Rational Unified Process (both of which are nearly inescapable judging from the sheer volume of literature on both subjects) then you will get the idea.

Patterns are like templates for actions and activities. Using a pattern assures a high degree of consistency in presenting a collection of activities, and also allows you to distill the key elements of a particular process into a succinct format. What I especially like about the concept of patterns is that provide a "container" into which you can capture best practices for any process.

This book presents a set of patterns for the final stages of application delivery (i.e., software development)and segues directly into service delivery. The patterns grouped into phases that roughly follow the Rational Unified Process, and the phases are further grouped into stages.

From the application delivery point of view, the processes are: test and rework. The bridge to service delivery is provided in the release stage processes. From there the processes are firmly in the service delivery domain, starting with the assess stage, and moving into the maintain and support phase. One of the best parts of this book from a service delivery practitioner's point of view is the "Identify Defects and Enhancements". This if often overlooked in the body of literature for applications and service delivery (but is a key process in software quality assurance). The patterns associated with this stage are an ideal vehicle to communicate operational requirements from service delivery back to application delivery.

I also liked the project and cross-project tasks that are presented in this book. As the co-developer of the Tarrani-Zarate Information Technology Management Model one of the fuzzy areas was the link between maintenance and support and the project-related tasks. This section clarified some of the dependencies and linkages.

What did this book do for me? As a service delivery practitioner it gave me a clear understanding of the potential synergies that can be achieved if application and service delivery are treated as a coherent whole. It also heavily influenced my thoughts when developing the Tarrani-Zarate model, and refined my view of service delivery. It also showed the value and power of employing patterns for capturing best practices. As such, this book is probably of value to knowledge management practitioners.

What does this mean to you? It depends on your role. If your role is project manager, in development or QA/test, then the process patterns provided will underscore the fact that development is not complete until the product is in production. If you are in production control, production support or applications support (help desk, tier 2 or 3), then this book provides some excellent ideas on how to "connect" service delivery to application delivery. If you are a project sponsor or business process owner, the defects and enhancement stages are a good starting point for understanding your role on a configuration control board at the project or product management level.

The author sums up the key point of this book with a quote from his web page: "A good developer knows that there is more to development than programming. A great developer knows that there is more to development than development." To paraphrase, development isn't what it is about - it's about delivering functions to business users so they can do their job. This book provides ideas and tools to do this.

William Liu (SML Modeling Expert/DMTS) has recently authored an excellent text on the BSIM3 and BSIM4 SPICE models. It is a "must have" text for modeling engineers, designers, or PIs who would like a deeper understanding of the BSIM3/4 models. William's sense of humor is evident throughout the text which makes the deep technical aspects even more fun. Check out "Mosfet Models for Spice Simulation."

This is clearly the best and newest book on MOSFET models. It's Liu's third book, and it's delightful. That's a strange word for a technical book, but it's true! This book is both practical (down to earth) and occasionally funny.

I must admit... I haven't read all 588 pages yet, but the sections I have read are all clearly written, well illustrated and there is just enough background information to make the topics interesting. For example when he discusses the possibility of BSIM3 calculating a negative back-gate transconductance, gmb, or a negative mutual transconductance, gm, he points out that a negative gm has actually been reported in a real device, and gives the reference. Then he gives a checklist you can use to help prevent the negative gmb problem in your model.

I was particularly interested and amused by his explanation of the "Killer NOR Gate" in section 4.2 "Problems with the 40/60 Partition." This circuit caused a lot of interesting e-mail discussion a couple of years ago.

His chapter 3 contains a very good 130-page "ALPHABETICAL GLOSSARY OF BSIM3 PARAMETERS." Anybody who works with BSIM3 knows you need a handy list of all the model parameters and what they mean. Liu devotes a couple of paragraphs to each, and he recommends leaving many of them equal to zero!

I'm more of a SPICE model user, not so much a theorist, and I found this book to be exactly what I needed.

The other recent classics on this subject are Cheng & Hu's MOSFET Modeling & BSIM3 User's Guide (1999), Arora's MOSFET Models for VLSI Circuit Simulation (1993) and Foty's MOSFET Modeling with SPICE (1996).

I am the author William Liu. I notice there is no link to the book content (as of May, 2001). Therefore, I thought I would add that here. I am sorry to have to rate my own book a five star before I can put put forth the book content in this review space. Nonetheless, it is indeed my view that the book is a five star, an opinion which I believe, can be justified by the content shown next.

Anyway, here is the content:

CHAPTER 1 MODELING JARGONS

1-1 SPICE Simulator and SPICE Model 1-2 Numerical Convergence 1-3 Digital and Analog Models 1-4 Smoothing Function and Single Equation 1-5 Chain Rule 1-6 Quasi-Static Approximation 1-7 Terminal Charges and Charge Partition 1-8 Charge Conservation 1-9 Non-Quasi-Static and Quasi-Static y-Parameters 1-10 Source-Referencing and Inverse Modeling 1-11 Physical vs. Table-Lookup Models 1-12 Scalable Model and Device Binning

CHAPTER 2 BASIC FACTS OF BSIM3

2-1 What Is and What's Not Implemented in BSIM3 2-2 D.C. Equivalent Circuit and Leakage Current 2-3 Large-Signal Equivalent Circuit 2-4 Small-Signal Equivalent Circuit and y-Parameters 2-5 Noise Equivalent Circuit 2-6 Special Operating Conditions: VDS < 0, VBS > 0, VGS < 0, or VBD > 0

CHAPTER 3 BSIM3 PARAMETERS

3-1 List of Parameters According to Function 3-2 Alphabetical Glossary of Parameters 3-3 Flow Diagram of SPICE Simulation

CHAPTER 4 IMPROVABLE AREAS OF BSIM3

4-1 Lack of Robust Non-Quasi-Static Model; Transient Analysis 4-2 Problem with the 40/60 Partition: The "Killer NOR Gate" 4-3 Lack of Channel Resistance (NQS Effect; Small-Signal Analysis) 4-4 Incorrect Transconductance Dependency on Frequency 4-5 Lack of Gate Resistance (and Associated Noise) 4-6 Lack of Substrate Distibuted Resistance (and Associated Noise) 4-7 Incorrect Source/Drain Asymmetry at VDS = 0 4-8 Incorrect Cgb Behaviors 4-9 Capacitances with Wrong Signs 4-10 Cgg Fit and Other Capacitance Issues 4-11 Insufficient Noise Modeling (No Excess Short-Channel Thermal Noise) 4-12 Insufficient Noise Modeling (No Channel-Induced Gate Noise) 4-13 Incorrect Noise Figure Behavior 4-14 Inconsistent Input-Referred Noise Behavior 4-15 Possible Negative Transconductances 4-16 Lack of GIDL (Gate Induced Drain Leakage) Current 4-17 Incorrect Subthreshold behaviors 4-18 Threshold Voltage Rollup 4-19 Problems associated with a nonzero RDSW 4-20 Other Nuisances

CHAPTER 5 IMPROVEMENTS IN BSIM4

5-1 Introduction 5-2 Physical and Electrical Oxide Thicknesses 5-3 Strong Inversion Potential For Vertical Nonuniform Doping Profile 5-4 Threshold Voltage Modifications 5-5 VGST,eff In Moderate Inversion 5-6 Drain Conductance Model 5-7 Mobility Model 5-8 Diode Capacitance 5-9 Diode Breakdown 5-10 GIDL (Gate Induced Drain Leakage) Current 5-11 Bias-Dependent Drain-Source Resistance 5-12 Gate Resistance

5-13 Substrate Resistance 5-14 Overlap Capacitance 5-15 Thermal Noise Models 5-16 Flicker Noise Model 5-17 Non-Quasi-Static AC Model 5-18 Gate Tunneling Currents 5-19 Layout-Dependent Parasitics

APPENDIX

A. BSIM3 Equations B. Capacitances and Charges for All Bias Conditions C. Non-Quasi-Static y-parameters D. Fringing Capactiance E. BSIM3 Non-Quasi-Static Modeling F. Noise Figure G. BSIM4 Equations INDEX