| Subcategories |
 |
Biographies & Primers |
|
|
|
|
 |
 |
| |
|
|
|
|
|
Systems Analysis and Design (7th Edition)
written by Kenneth E. Kendall, Julie E Kendall
Studio : Prentice Hall
by Prentice Hall
Publisher : Prentice Hall
Released : 2007-04-06
Availability : Usually ships in 1-2 business days
Number of Items : 1
EAN : 9780132240857
Avg. Customer Rating: (based on 9 reviews)
List Price : $170.67
Our Price : $33.53
|
|
| |
|
Product Description |
|
Dynamic, comprehensive coverage makes this the perfect book on systems analysis and design, with a reader-friendly presentation of development, methods, tools, and techniques. A variety of review questions and problems, an ongoing case study, and an Internet-based case study offer learners an understandable and motivating look at the SAD field. For production supervisors and other business personnel in similar positions who want a working knowledge–without the in-depth command–of information systems. |
| |
|
| |
|
Great Resource |
|
This book is a great resource for anyone wanting to learn the 'how to' of Systems Analysis and Design. It is easy to read and the examples are interesting and relevant. I definitely recommend this book. |
| |
|
E-commerce & business |
Please,,,,,,display that book's pages no 23,& 84 .book name:management information system(5th edition).
writer:james A. |
| |
|
Comprehensive but pricey |
|
The text covers the topic with ample examples and diagrams, plus cases short and long. The level of detail is appropriate for a graduate level course. The book is too ... The authors could eliminate the chapter on the office environment. They should condense the chapters on questionnaires and system presentation. Another solution: put the lengthy end-of-chapter case material on a CD; it is doubtful that all of it is used in any course. Perhaps the authors have too much clout to be edited. |
| |
|
Everything you ever wanted to know, and then some... |
|
The Kendalls have definitely created a comprehensive book on systems analysis. Virtually every aspect is covered here, and in plenty of detail. There are plenty of review questions and problems, hypothetical consulting situations, an ongoing case-study, and even an associated web-based case study. While being well written, I feel that this text may be a bit overdone. Most sections are longer than neccessary, over-explaining fairly obvious concepts. So although the reader can never complain about being short-changed, I would be amazed if any reader needed ALL of the explanations to understand what was being discussed. I have also noticed a few cases of dated information creeping through from previous editions. One example is a discussion on groupware that talks about features of Windows for Workgroups and Windows NT, and mentions the 'upcoming' Chicago release. Chicago was the working name for Windows 95, which was hardly 'upcoming' for a text published in 1999. It feels as if the Kendalls have been adding new information to their revised editions, but not revising thoroughly enough to remove old or out of date references. If a really good job of revision was done here, I think this text could be reduced by at least a hundred pages or so without any real loss of useful content. Since it emphasises practice more than theory, it may not appeal to all types, but for anyone who needs to know HOW to be a systems analyst, this is probably the book to read. |
| |
|
Doesn't Teach Much |
|
I used this book in my systems analysis and design course. First off, it is over priced. I understand that college books are expensive, but this one was too overpriced. Second, it is not helpful. It spends chapters talking about how to get information from users. Did I really need several chapters to tell me to interview them, send out surveys, and observe them? That is kind of obvious information. Following this course, I took a software development course. The two classes are in series. Techniques learned from this book did not help me. When it came time to write documents (project proposals, documents for external design and internal design phases, etc.) this book was no help. There were no examples of what should be in them. Not helpful unless you are clueless as to where to begin. Even then it's not a tremendous help. |
| |
|
|
|
