rjmaster19
Member
Since there is always so little info about the EE-comp exam, I'll share my thoughts while it’s still relatively fresh in my mind.
First off here are the books that I used to study.
-NEECS Sample Exam
-PPI Electrical-Comp Package
-Schaum’s Computer Architecture (ISBN: 0-07-136207-X)
-Schaum’s Computer Networking (ISBN: 0-07-136285-1)
-Electrical Engineering Dictionary
Obviously the NEECS exam was the closest to the real thing, without getting specific; I was surprised that there were several questions with the same diagrams. Now you're thinking that it’s the same problem with a twist, but nope, it’s the same diagram but a completely different problem. So that’s one thing I would be aware of. When you take the sample exam, don't just try to understand the stated problem, try to understand the topic. I know that sounds vague, but the exam topics are quite varied.
After reviewing the NEECS exam problems I realized that there were several problems where I wasn't familiar at all with the terms used. So I ended up printing out about 200 pages of Wikipedia articles detailing those subjects. If I have to take the test again, I would definitely take my binder of wiki notes. However, it wasn't quite as much help as I thought it would be, it may have helped on 1-2 questions.
I was pretty disappointed in the PPI material before the test. I felt that the EERM, was not in depth, and didn't cover enough topics. The computer architecture section is 3 pages, but according to the test specifications Comp Arch is 35% of the test!! However, after taking the test I've softened a bit on that. The book actually was a good place to start reviewing material. If you can spend the money just get it, you get a decent deal on the whole package. However, if money is tight I would recommend to just get the PPI sample exam. I would NOT recommend the PPI exam cafe. The questions aren't anything like the test; it’s more like a review of concepts. I like that I can work on them from any where (even my phone). But if you're looking to practice exam problems, it’s not worth it.
The two Schaums' books are DEFinitely worth it. Almost everyone who has taken the test recommends these two books. The Networking book is just jammed packed with info. I wouldn't want to learn those topics from scratch using this book, but it’s a great review and reference. The Comp Arch book is a great review of the topic. The sample problems are a good review of the subject material, but are unlike the exam questions.
The EE dictionary was really invaluable. I had enough time to re-check all of my answers on the test. If on the re-check I was unclear about a word or vague on my understanding of it, I looked it up in the EE dictionary. This book saved my ass on at least 5 questions! I found it online at: http://timeanhalfelectrical.blogspot.com/
The rest of the books are books I had left over from school. I wouldn't really recommend going out and buying those specific books, just get some decent text books that cover the material in those books. Specifically, logic design with VHDL, software life cycle, software development/testing.
Again the NEECS sample exam really sets the tone for how the exam will be. But don't expect the same problems; I did, in retrospect I was being hopeful that it was all laid out for me.
Here are some other general tips:
* The problems on this test are more knowledge based than analysis based. If you’re good at circuits, you can stare at a circuit problem and mush your way through it. If you don’t know what rate-monotonic means you will never figure it out by starring at it. (Mr. NEECS forum officer: this is a question off the sample exam!, I'm not revealing exam info, please don't invalidate my test
* A lot of people say if you bring too many references you’ll spend all your time flipping pages. That’s true, if you’re an idiot. I had approximately 8 books, and if I take it again, I’m bringing more reference materials. Here was my plan. If I came across a question where I knew approximately where it was located, I looked it up. If I didn’t feel comfortable with any of the answers I flagged it and came back to it at the end. Sure I spent time flipping pages, but I also found a lot of answers.
* I saw a girl with what looked like those European shopping carts, short and about 3 feet deep, and it was FILLED to the top with books. That might be excessive (and embarrassing), but would it hurt if you got even one more question because of it?
* Be familiar with your references. I didn’t read every page of my books before hand. But if it was a VHDL question I knew which of my books had the most comprehensive, easy to access section on VHDL. Also, become one with the index. Love the index. Practice the alphabet. (I’m sort of dyslexic, so yes, I practiced the alphabet (but I did it with my kid, so get a kid and it won’t feel weird))
* Like I said, I had time to double check all my questions. I’m a fairly fast reader, but I think for this test, most people would have enough time to go back and re-check all the questions (AM & PM). Just be aware that it’s mentally exhausting to do this.
*
Of course I may have failed this test, and you may want to do the opposite of these tips!!
R
First off here are the books that I used to study.
-NEECS Sample Exam
-PPI Electrical-Comp Package
-Schaum’s Computer Architecture (ISBN: 0-07-136207-X)
-Schaum’s Computer Networking (ISBN: 0-07-136285-1)
-Electrical Engineering Dictionary
Obviously the NEECS exam was the closest to the real thing, without getting specific; I was surprised that there were several questions with the same diagrams. Now you're thinking that it’s the same problem with a twist, but nope, it’s the same diagram but a completely different problem. So that’s one thing I would be aware of. When you take the sample exam, don't just try to understand the stated problem, try to understand the topic. I know that sounds vague, but the exam topics are quite varied.
After reviewing the NEECS exam problems I realized that there were several problems where I wasn't familiar at all with the terms used. So I ended up printing out about 200 pages of Wikipedia articles detailing those subjects. If I have to take the test again, I would definitely take my binder of wiki notes. However, it wasn't quite as much help as I thought it would be, it may have helped on 1-2 questions.
I was pretty disappointed in the PPI material before the test. I felt that the EERM, was not in depth, and didn't cover enough topics. The computer architecture section is 3 pages, but according to the test specifications Comp Arch is 35% of the test!! However, after taking the test I've softened a bit on that. The book actually was a good place to start reviewing material. If you can spend the money just get it, you get a decent deal on the whole package. However, if money is tight I would recommend to just get the PPI sample exam. I would NOT recommend the PPI exam cafe. The questions aren't anything like the test; it’s more like a review of concepts. I like that I can work on them from any where (even my phone). But if you're looking to practice exam problems, it’s not worth it.
The two Schaums' books are DEFinitely worth it. Almost everyone who has taken the test recommends these two books. The Networking book is just jammed packed with info. I wouldn't want to learn those topics from scratch using this book, but it’s a great review and reference. The Comp Arch book is a great review of the topic. The sample problems are a good review of the subject material, but are unlike the exam questions.
The EE dictionary was really invaluable. I had enough time to re-check all of my answers on the test. If on the re-check I was unclear about a word or vague on my understanding of it, I looked it up in the EE dictionary. This book saved my ass on at least 5 questions! I found it online at: http://timeanhalfelectrical.blogspot.com/
The rest of the books are books I had left over from school. I wouldn't really recommend going out and buying those specific books, just get some decent text books that cover the material in those books. Specifically, logic design with VHDL, software life cycle, software development/testing.
Again the NEECS sample exam really sets the tone for how the exam will be. But don't expect the same problems; I did, in retrospect I was being hopeful that it was all laid out for me.
Here are some other general tips:
* The problems on this test are more knowledge based than analysis based. If you’re good at circuits, you can stare at a circuit problem and mush your way through it. If you don’t know what rate-monotonic means you will never figure it out by starring at it. (Mr. NEECS forum officer: this is a question off the sample exam!, I'm not revealing exam info, please don't invalidate my test
* A lot of people say if you bring too many references you’ll spend all your time flipping pages. That’s true, if you’re an idiot. I had approximately 8 books, and if I take it again, I’m bringing more reference materials. Here was my plan. If I came across a question where I knew approximately where it was located, I looked it up. If I didn’t feel comfortable with any of the answers I flagged it and came back to it at the end. Sure I spent time flipping pages, but I also found a lot of answers.
* I saw a girl with what looked like those European shopping carts, short and about 3 feet deep, and it was FILLED to the top with books. That might be excessive (and embarrassing), but would it hurt if you got even one more question because of it?
* Be familiar with your references. I didn’t read every page of my books before hand. But if it was a VHDL question I knew which of my books had the most comprehensive, easy to access section on VHDL. Also, become one with the index. Love the index. Practice the alphabet. (I’m sort of dyslexic, so yes, I practiced the alphabet (but I did it with my kid, so get a kid and it won’t feel weird))
* Like I said, I had time to double check all my questions. I’m a fairly fast reader, but I think for this test, most people would have enough time to go back and re-check all the questions (AM & PM). Just be aware that it’s mentally exhausting to do this.
*
Of course I may have failed this test, and you may want to do the opposite of these tips!!
R
