<< 1 >>
Rating: 
Summary: Really comprehensive and usable for real projects
Review: Although this book comes from an academic background, I used it in a real client project in industry for the first time. The book offers a rather complete overview of software engineering in general: requirements engineering, analysis, system design, object design, implementation, testing. It also includes specialities, for instance rationale management, project management and others. I agree with a previous annotator who wrote that not all of the samples are 'perfectly helpful'. However, some are and some are quite amusing, e.g., in the Design Rationale chapter.Overall, the best collection of Software Engineering best practices I found in a single book. Really helpful for academic use as well as in industry.
Rating:
Summary: I disagree with current reviewers
Review: I'm a Software Engineer and Software Engineering/OOAD teacher with a modest bibliography on Object Technology and Software Engineering: This book is pretty good for both worlds. Maybe it could be confusing for someone with little exposure to UML, because authors creatively used UML for any illustration required (design, software engineering concepts and artifacts, and even reading map). This book is now within my favorites in OOAD/Software Engineering, and I just waiting for my 2nd edition unit.
Rating: 
Summary: Poor Information and very confusing
Review: The information in this book is very confusing and the example are not clear.
Rating: 
Summary: Good book, just a little boring
Review: This book contains excellent information. However, it is a little boring to read sometimes.
Rating:
Summary: Poor Instruction for Diagramming
Review: This book is very inadequate for learning how to do the requisite diagramming. It would help if the authors included lists of rules related to diagramming (state charts, sequence diagrams, and use cases). Also, they could give examples of how not to do diagrams, and lists of diagramming don'ts. If you want to learn how to draw up state charts, sequence diagrams, and use cases, from a requirements document you'll have to find a better book than this one.
Rating:
Summary: A good introduction and overview
Review: This book provides a general overview of the issues involved in the practice of software engineering. Covers requirements elicitation/analysis, design (both high level/architectural and lower level/object-oriented), testing, and a process and project management issues. The book is up do date with current practice covering topics such as UML, design patterns, and software lifecycles and development methodologies. The examples used tend to become very stale after a while, and the text doesn't always read as well as it could. Overall, this book is a good introduction to software engineering and a good starting point, but should not be considered a final reference.
Rating:
Summary: A good introduction and overview
Review: This book provides a general overview of the issues involved in the practice of software engineering. Covers requirements elicitation/analysis, design (both high level/architectural and lower level/object-oriented), testing, and a process and project management issues. The book is up do date with current practice covering topics such as UML, design patterns, and software lifecycles and development methodologies. The examples used tend to become very stale after a while, and the text doesn't always read as well as it could. Overall, this book is a good introduction to software engineering and a good starting point, but should not be considered a final reference.
Rating: 
Summary: Not the greatest..
Review: This book was used in my software engineering class at college. Overall, the material in this book was presented in a very boring and complex manner, focusing on jargon definitions and a few isolated examples. Although the book does explain software engineering, it tends to do so in a painful way. Do yourself a favor and pick another book on the subject.
<< 1 >>
| 
