Amazon.com
Good software starts with a good design, and the subtitle of Applying UML and Patterns, "An Introduction to Object-Oriented Analysis and Design (OOA/D) and the Unified Process" reinforces that that's what this book is about.
The first edition of Applying UML and Patterns became a standard. The second edition uses the unified process (UP) as the iterative process within which OOA/D is introduced, and extends the case study used in the first edition. Other changes have been made to reflect the growing consensus on the most effective ways to work with OOA/D and patterns.
Although you will learn UML, this isn't what Applying UML and Patterns is all about. It's designed to teach you to think of software as a collection of objects with properties and to manipulate the relationships between them. This is far more profound.
The case study enables Craig Larman to carry the design through to Java code. In practice, you will need a basic understanding of OO programming to benefit from Applying UML and Patterns, though you needn't know Java--you can implement the designs in the OO language of your choice with equal facility.
When it comes right down to it, Applying UML and Patterns is all about providing you with a language in which to think about software design. This is quite different from learning a language in which to code a design.
A facility with OOA/D will enable you to design and discuss programs independent of code, to produce more elegant and maintainable software, and to take a 30,000-foot view of the way your software interacts with the world. In effect, it can shift your viewpoint from that of a mechanic to that more sophisticated viewpoint of an engineer. Recommended. --Steve Patient. Amazon.co.uk
Book Description
“People often ask me which is the best book to introduce them to the world of OO design. Ever since I came across it, `Applying UML and Patterns' has been my unreserved choice.” —Martin Fowler, author, “UML Distilled” and “Refactoring”
The first edition of “Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design” quickly emerged as the leading OOA/D introduction; translated to many languages and adopted in universities and businesses worldwide. In this second edition, well-known object technology and iterative methods leader Craig Larman refines and expands this text for developers and students new to OOA/D, the UML, patterns, use cases, iterative development, and related topics.
The book helps newcomers to OOA/D learn how to “think in objects” by presenting three iterations of a single, cohesive case study, incrementally introducing the requirements and OOA/D activities, principles, and patterns that are most critical to success. It introduces the most frequently used UML diagramming notation, while emphasizing that OOA/D is much more than knowing UML notation. All case study iterations and skills are presented in the context of an “agile” version of the Unified Process -- a popular, modern iterative approach to software development. Throughout, Larman presents the topics in a fashion designed for learning and comprehension.
Among the topics introduced in Applying UML and Patterns are: * requirements and use cases, * domain object modeling, * core UML, * designing objects with responsibilities, * “Gang of Four” and other design patterns, * mapping designs to code (using Java as an example), * layered architectures, * architectural analysis, * package design, * iterative development, * the Unified Process.Foreword by Philippe Kruchten, the lead architect of the Rational Unified Process.
“Too few people have a knack for explaining things. Fewer still have a handle on software analysis and design. Craig Larman has both.” —John Vlissides, author, “Design Patterns” and “Pattern Hatching”
“This edition contains Larman's usual accurate and thoughtful writing. It is a very good book made even better.” —Alistair Cockburn, author, “Writing Effective Use Cases” and “Surviving OO Projects”
Customer Reviews:
First book for anyone learning to create business software.......2007-08-11
Craig Larman's classic has reach 10 years of prime position on my professional book shelf, the 1st edition now replaced with the 3rd. Whenever anyone asks for an introduction to UML, this is always my first recommendation. Though the book focusses on software construction from scratch, it still contains much brilliant guidance for enhancement work or implementation of software packages.
This book takes you in a logical, distilled process through pragmatic application of Unified Modelling Language on real projects for which people pay. Of course the examples are simple, but relevant and helpful. The book is chock full of diagrams and little text, which makes it quick to read and easy for reference.
You could do little wrong if you used only this book to guide your first application of UML to a real project.
Review of Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Editi.......2007-07-19
I have 30 years in the industry (and in different industries in IS management) and one thing I dislike is the author's persistence do down-grade the waterfall or modified waterfall models. He should be more objective on his comments since the waterfall and modified waterfall do have their merits on projects -- refer to "Rapid Development, Training Wild Software Schedules" by Steve McConnell, Microsoft Press, ISBN 1-55615-900-5. I have used them very successfully on big programs. The key here is, with any model, in order to be successful you need quality communications with ALL stakeholders. Just like in our personal life's, communications is everything; the models can be secondary.
The author should also strictly follow the attributes of writing good requirements. On page 72, he wrote for "frequency of occurrence", "Could be nearly continuous". Now, I ask, how ambiguous is that????
The single best book for your OO development team.......2007-07-06
As others have pointed out, the content on OO analysis and design is excellent. Equally important - Larman's book is also an excellent on "process".
Unlike many books that simply focus only on "programming", Larman gives you a working examples and excellent advice on overlapping fields like "requirements", "testing", "architecture" and "project management".
Craig Larman's "Applying UML and Patterns, 3rd Ed" is a wealth of practical advise, covering *all* significant aspects of successfully defining and implementing a non-trivial software project. If your team were to choose only one book as your "Bible" - this would be that book.
Excellent Work!.......2007-04-23
As pointed out by many, this book is a very nice introduction to Object Oriented Analysis and Design. The author's explanations were very clear. This book covers agile practices, UML, many patterns including Gang of Four (GoF), and software architecture. Overall I really enjoyed reading this book. From an industry standpoint as well as an academic standpoint, I believe this book does an excellent job. This book will be part of my library for a long time to come. Highly recommended.
Excellent guide!.......2006-11-10
Well, I think this book should be a must read for any pro or beginer in the software design/build area, it takes you from the start trying to make you understand what your client want you to understand, until the best practices to have patterns, tests, and a good team development, so do not hesitate to buy it!.
Average customer rating:
- Worth the buy!
- A book serves all your needs
- Full of information and errors
- A matchless guide
- Application Oriented
|
Design for Six Sigma : A Roadmap for Product Development
Kai Yang , and
Basem S. EI-Haik
Manufacturer: McGraw-Hill Professional
ProductGroup: Book
Binding: Hardcover
 General
| Business & Investing
| Subjects
| Books
Operations Research
| Management & Leadership
| Business & Investing
| Subjects
| Books
Total Quality Management
| Management & Leadership
| Business & Investing
| Subjects
| Books
Industrial Design
| Industrial, Manufacturing & Operational Systems
| Engineering
| Professional & Technical
| Subjects
| Books
Manufacturing
| Industrial, Manufacturing & Operational Systems
| Engineering
| Professional & Technical
| Subjects
| Books
Production, Operation & Management
| Industrial, Manufacturing & Operational Systems
| Engineering
| Professional & Technical
| Subjects
| Books
Quality Control
| Industrial, Manufacturing & Operational Systems
| Engineering
| Professional & Technical
| Subjects
| Books
Systems Analysis & Design
| Computer Science
| Computers & Internet
| Subjects
| Books
Quality
| Quality Engineering
| McGraw-Hill Engineering Store
| McGraw-Hill
| By Publisher
| Books
TQM
| Quality Engineering
| McGraw-Hill Engineering Store
| McGraw-Hill
| By Publisher
| Books
Look Inside Business Books
| Trip
| Specialty Stores
| Books
Look Inside Computer Books
| Trip
| Specialty Stores
| Books
All Amazon Upgrade
| Amazon Upgrade
| Stores
| Books
Business & Investing
| Amazon Upgrade
| Stores
| Books
Computers & Internet
| Amazon Upgrade
| Stores
| Books
Engineering
| Amazon Upgrade
| Stores
| Books
Professional & Technical
| Amazon Upgrade
| Stores
| Books
All Titles
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Business & Investing
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Computers & Internet
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Professional
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Similar Items:
-
Design for Six Sigma in Technology and Product Development
-
The Design for Six Sigma Memory Jogger: Tools and Methods for Robust Processes and Products
-
Design for Six Sigma for Service (Six SIGMA Operational Methods)
-
Design for Six Sigma (Briefcase Books Series)
-
Design for Six Sigma Statistics
ASIN: 0071412085 |
Book Description
Here's the book that clearly and logically answers the complex question quality managers and product developers face almost every day: WHICH PRODUCT DEVELOPMENT TOOLS SHOULD I USE AND WHEN?
This much-needed, well-written roadmap for robust, efficient product development features:
* All the coverage needed to implement six sigma in any manufacturing concern
* A complete review of both traditional and contemporary design methods
* Systems discussed include: DOE (Design Of Experiment), Taguchi Method, QFD (Quality Function Deployment), Axiomatic Design, and TRIZ (Theory for Inventive Problem-Solving)
* Practical examples to highlight important elements of each system
* A unique multi-systems approach to designing products, incorporating the traditional and contemporary methods discussed, detailing how and when to use them
* Valuable assistance when preparing for certification exams
Customer Reviews:
Worth the buy!.......2004-04-02
I have not found such a comprehensive book for design of six sigma. I started using this book for advanced experimental design and taguchi methods, but ended understanding the complete roadmap for design of six sigma. The systems approach allows an enthusiast reader to start anywhere, without having to spend time refering back to earlier chapters. The relatively newer trends as TRIZ and axiomatic design have also been nicely dealt with.
Overall, this is a very nice and easy read book, with excellent and well defined examples. A must for everyone who wants a quick refresher on the design principles of six sigma.
A book serves all your needs.......2004-04-02
This is an outstanding DFSS book for production development. It contains integrated information and some of which you could hardly find anywhere else, thus with one book in hand, you have all the tools to get to your destination. This is also a easy to read book providing the reader with a solid understanding- Concepts are clearly defined, real world examples/ case studies are fully described and the chapters are well organized. It can serve as a textbook for students/beginners and also can serve as a handbook for experienced engineers.
The title says it all- this is a roadmap for you to find the way correctly and easily. I am reading the book right now, and the book is really beneficial to me.
Full of information and errors.......2004-03-30
This is a book with a lot of information. Each chapter can be used as a starting point for a specific six sigma technique. However, this is the worst edited book I have ever read. You can hardly find one page without errors/typos.
A matchless guide.......2003-08-03
While the concept of six-sigma is a very popular one, it is not often that one can find such a comprehensive yet clearly-written volume devoted to the most important topics of six-sigma. A book that contains so much information and not just hot air is especially hard to find. Yang and El-Haik have successfully written one of the most impressive and useful reads I have ever encountered within this field. Especially intriguing and novel concept of TRIZ. A very worthwhile book, in any case.
Application Oriented.......2003-07-01
In recent times, there has been a lot of talk and hype about DFSS with very little substance thus far--until this one! I found the book an easy read, application oriented and a relatively prescritive approach to apply DFSS for products, processes and/or services. The sections on TRIZ and Axiomatic Design expose the opportunities largely untapped in the design world today. A must read book for organizations serious about Six Sigma--whether they are focused on delivering worldclass products and services to their customers or designing processes to run world class business operations--a thumbs up all the way!!
Book Description
Today's students want to practice the application of concepts. As with the previous editions of this book, the authors write to balance the coverage of concepts, tools, techniques, and their applications, and to provide the most examples of system analysis and design deliverables available in any book. The textbook also serves the reader as a professional reference for best current practices.
Customer Reviews:
Good.......2007-09-24
The book has arrived in the range of the days they premised. The qualities of the item and the service are good- they sent the book within a big box filled with many soft balls so that they could protect the hard coverage of the book.
Yeah, it is a good way of shopping. Well, it will be better if the price is lower or the good can arrive sooner. Thank you.
Wonderful Scope of Systems Analysis and Design Methods.......2007-07-03
Provides a wonderful scope of systems analysis and design methods, and a bunch of related topics. After reading this book, you should feel comfortable going to any organization and providing them with a model/graphic of their business processes.
as well written as could be for a dry subject of systems analysis.......2007-05-24
I had to take Systems Analysis as part of my masters degree and usually, anything you _must_ take becomes less interesting BUT, this book does a good job of clearly explaining the process of systems analysis.
From identifying entities in a process flow diagram with visual aides to the accompanying CDROM with slide show presentations of the content, I think this book provides a painless way to learn the material.
It's concisely written but a little verbose at times.
The author makes heavy use of graphics and sample diagrams so you can see how industry professionals do it.
Broad, but sometimes not deep.......2007-04-19
Whitten and Bentley have put together a very good text for a one-semester intro to systems analysis. After a wide-ranging introductory section, the real meat of this book appears in Parts 2 and 3: Analysis and Design.
Part 2 spends just one chapter on requirements discovery. This is the one section of the book that I found a lot thinner than it should be. The first problem is that requirements engineering is a field all its own, and has (or should have) direct connections to every work product that comes after in the development cycle. Although later chapters (especially use cases and even protoyping) offer additional ways to elicit meaningful requests from users, the whole task of making sure that the requirements are complete, consistent, and traceable to downstream effort is barely addressed. The second, and I think bigger problem is that the authors talk only about requirements from the users, plus "non-functional" requirements like reliability and performance. There's a lot to debate in categorizing requirements as non- or functional, depending on the kind of application, but the real defect in the discussion is one they share with most other authors in the field: they simply ignore the standards and regulations that affect system development. The SEC, FAA, and FDA impose requirements, as do legal enactments (HIPAA, ITAR for crypto, Sorbanes-Oxley), look&feel, and standards for networking, data exchange, and a gazillion other areas. Depending on the field you work in, you'll spend a lot more time worrying about regulatory and standards compliance than about anything the customer said.
Despite this uninspiring start, Part 2 moves along well. It presents use cases (though in a particularly fussy way), modeling techniques, and enough UML to help but not enough to overwhelm - and the whole can be quite overwhelming.
Part 3 addresses high level design. If your classroom is a typical one, this is where the students students with little, no, or ancient programming experience may start to struggle. It does a fair job with the common kinds of human-oriented IO, even if it shortchanges other systems with more intricate kinds of data manipulation (e.g. compilers or weather modeling). Because this addresses analysis as a separate task from programming, the authors have no reason to go into a lot of directly codable depth. This will frustrate the techies, but the little depth that it does address might intimidate thosewith more of a business orientation. It's a problem that I think has no solution as long as the people who build systems and the people who want them are in the same classroom.
Finally, Part 4 acknowledges the fact that systems are not just designed. Although it skips deployment and maintenance, this section does touch on low-level implementation and day to day operations. Now that they've gotten away from the core requirements, specification, and design content, I think the authors are making a quiet suggestion to the instructor who uses this book: it's your curriculum, add your spin to it. Everyone who looks this text over will see soft spots, but I'll bet that no two people see the same ones. We all come into this text with our own interests, specialties, experience, and strengths. One of the joys of teaching is the chance to add your own kind of depth to a course.
This is a fair cookbook. By that, I mean that you can follow the instructions and get a reliable set of results from it. Or, if you read this a little more broadly, it invites all the embellisments and complements that an active researcher or practitioner is sure to think of.
//wiredweird
Good to go.......2007-04-02
Product was delivered on time and in the condition as described. Good deal.
Average customer rating:
- From a newbie ...
- Very difficult to read
- Excelent but to many repeatings...
- The Data Warehouse Lifecycle Toolkit
- Excellence for starter and advanced data warehouse practioners
|
The Data Warehouse Lifecycle Toolkit : Expert Methods for Designing, Developing, and Deploying Data Warehouses
Ralph Kimball ,
Laura Reeves ,
Margy Ross , and
Warren Thornthwaite
Manufacturer: Wiley
ProductGroup: Book
Binding: Paperback
Management & Leadership
| Business & Investing
| Subjects
| Books
| Business Ethics
| Consolidation & Merger
| Decision-Making & Problem Solving
| Distribution & Warehouse Management
| Industrial
| Information Management
| Leadership
| Management
| Management Science
| Motivational
| Negotiating
| Operations Research
| Planning & Forecasting
| Pricing
| Production & Operations
| Project Management
| Quality Control
| Risk Assessment
| Statistics
| Strategy & Competition
| Systems & Planning
| Systems Analysis
| Teams
| Total Quality Management
| Training
Data Warehousing
| Databases
| Computers & Internet
| Subjects
| Books
Database Design
| Databases
| Computers & Internet
| Subjects
| Books
General
| Databases
| Computers & Internet
| Subjects
| Books
Structured Design
| Software Design, Testing & Engineering
| Programming
| Computers & Internet
| Subjects
| Books
Methodology
| Software Engineering
| Computer Science
| Computers & Internet
| Subjects
| Books
Systems Analysis & Design
| Computer Science
| Computers & Internet
| Subjects
| Books
Modeling & Simulation
| Computer Science
| Computers & Internet
| Subjects
| Books
General
| Computers & Internet
| Subjects
| Books
Mathematics
| Professional Science
| Professional & Technical
| Subjects
| Books
| Applied
| Chaos & Systems
| Geometry & Topology
| Mathematical Analysis
| Mathematical Physics
| Number Systems
| Pure Mathematics
| Transformations
| Trigonometry
Look Inside Business Books
| Trip
| Specialty Stores
| Books
Look Inside Computer Books
| Trip
| Specialty Stores
| Books
All Amazon Upgrade
| Amazon Upgrade
| Stores
| Books
Business & Investing
| Amazon Upgrade
| Stores
| Books
Computers & Internet
| Amazon Upgrade
| Stores
| Books
Professional & Technical
| Amazon Upgrade
| Stores
| Books
All Titles
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Business & Investing
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Computers & Internet
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Professional
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Similar Items:
-
The Data Warehouse Toolkit: The Complete Guide to Dimensional Modeling (Second Edition)
-
The Data Warehouse ETL Toolkit: Practical Techniques for Extracting, Cleanin
-
The Microsoft Data Warehouse Toolkit: With SQL Server 2005 and the Microsoft Business Intelligence Toolset
-
Building the Data Warehouse
-
Business Intelligence Roadmap: The Complete Project Lifecycle for Decision-Support Applications
ASIN: 0471255475 |
Amazon.com
In The Data Warehouse Lifecycle Toolkit, authors Ralph Kimball, Laura Reeves, Margy Ross, and Warren Thornthwaite present a structure for undertaking the awesome task of implementing a data warehouse. As part of a rather select group of professionals actually experienced in building data warehouses, the authors attempt to convey their expertise about how to approach the job. The book focuses on the "Star Lifecycle"--a high-level project-planning approach to evolving existing information systems into an ever-changing data-warehouse solution. --Stephen Plain
Book Description
"A comprehensive, thoughtful, and detailed book that will be of inestimable value to anyone struggling with the complex details of designing, building, and maintaining an enterprise-wide decision support system. Highly recommended." -Robert S. Craig, Vice President, Application Architectures, Hurwitz Group, Inc.
In his bestselling book, The Data Warehouse Toolkit, Ralph Kimball showed you how to use dimensional modeling to design effective and usable data warehouses. Now, he carries these techniques to the larger issues of delivering complete data marts and data warehouses. Drawing upon their experiences with numerous data warehouse implementations, he and his coauthors show you all the practical details involved in planning, designing, developing, deploying, and growing data warehouses. Important topics include:
* The Business Dimensional Lifecycle(TM) approach to data warehouse project planning and management
* Techniques for gathering requirements more effectively and efficiently
* Advanced dimensional modeling techniques to capture the most complex business rules
* The Data Warehouse Bus Architecture and other approaches for integrating data marts into super-flexible data warehouses
* A framework for creating your technical architecture
* Techniques for minimizing the risks involved with data staging
* Aggregations and other effective ways to boost data warehouse performance
* Cutting-edge, Internet-based data warehouse security techniques
The CD-ROM supplies you with:
* Complete data warehouse project plan tasks and responsibilities
* A set of sample models that demonstrate the Bus Architecture
* Blank versions of the templates and tools described in the book
* Checklists to use at key points in the project
Customer Reviews:
From a newbie ..........2007-06-28
I just used this for a class and I thought it was a good book. I'm a data warehouse newbie and it was easy to understand and presented a lot of information that was very useful. I think it will be a good reference down the road.
Very difficult to read.......2007-05-07
I find this book very difficult to read and understand. It tells you a great deal about what you're supposed to do to build a warehouse but does not tell you how to do it.
Excelent but to many repeatings..........2007-01-09
Excelent book for introduction to data warehouse architecture. However author makes a lot of repeating about conformed dimensions and conformed facts. This book could be half sized without these. Yet, I am very happy to own it. Recommended for every developer.
The Data Warehouse Lifecycle Toolkit.......2006-03-10
The bible of Data Warehousing by the guru of the Data Warehouse for all levels of expertise.
Excellence for starter and advanced data warehouse practioners.......2005-10-24
For a data warehouse novice this excellent starting point and it take through the advance concepts. In short, it's a reference book for any data warehouse practitioner
Book Description
For graduate and upper-level undergraduate courses in Marketing Research and Marketing Data Analysis.
Marketing Research: An Applied Orientation, 5e allows students to actually
experience the interaction between marketing research and marketing decision-making.
Customer Reviews:
A bible for MR.......2007-06-02
An excellent book for those who are new to MR or for those who wants to revisit the concepts. A well organised book with many real time examples and case studies to learn the concepts from.
I consider this book as a "Must have" one for MR field.
Customer Reviews:
SPSS 13 Student version.......2006-11-03
I have tried for years a lot of demo, free and shareware related to statistics, econometric and data analysis software. It was good, tired, and finaly I choose SPSS, because has excelent tools, options and interfase to user. Not PC crashes, no unknown format files. If you no not have enough money, don't waste time and money, use SPSS Student version.
Perfect for small projects!.......2006-07-08
Note: SPSS 13.0 for Windows Student Version cannot open data files containing more than 50 variables or 1,500 cases. Having said that, if you have less than 50 variables and 1,500 cases to deal with then this is the software for you. It came with a (brief) 227-page users guide that was pretty comprehensive all by itself. Order the SPSS 13.0 Guide to Data Analysis to go with it, and you have just about everything you need to fiddle with and learn the basics of statistical analysis.
Excellent for SPSS and statistics students.......2006-03-10
I have used this product in a research methods class and found it to perform quite well. While it may not have all the features of the full SPSS package it is more than adequate and does not require the student to pay the hefty fee of the full version.
Very disappointed.......2006-03-02
Beware - if you buy the student version it is not big enough to run the files necessary that you work on in class. Nowhere did it indicate on the Amazon site that it had limits of file size. Wouldn't one assume that if you are selling a "student" verson, that it will be able to run your school files? Don't buy it if you are a college student and need this software to complete your projects. I wasted $80 plus dollars. Didn't learn of its limitations until AFTER I loaded it, and when it wouldn't work found the limitation statement in the manual. Very disappointed.
If your Statistics Class text uses SPSS and did not include it.......2005-12-18
SPSS Student is a dremendous value: over 75% off the retail version and nearly as powerful. It is limited, but is more than adequate for most cases you will encounter in class.
If you need a more advanced package, get SPSS Career Builder or SPSS Graduate Pack -- they include the full version of SPSS.
Amazon.com
Patterns are higher-order designs that can be reused across projects and types of computer systems. Analysis Patterns: Reusable Object Models defines over 70 patterns, beginning with some from the business world, such as the Party and Accountability patterns, which define the players in organizations and whom they report to. Many of the other patterns are drawn from the health care industry and mainly show patterns of doctor-patient interactions.
The patterns for financial markets will probably be accessible for the majority of readers. Author Martin Fowler defines a Transaction pattern (and related patterns) as well as several patterns for the Accounting of Objects. He moves on to modeling stock markets with Portfolio, Quote, and Scenario patterns, which define how a price for a stock is determined for a given moment. Interestingly, he establishes patterns for Forward Contracts (for derivatives) as well as Options, and so takes on a complicated area in today's financial markets.
Fowler's considerable design experience in these fields is beneficial, as he is able to define each pattern in both text and software engineering diagrams. Only rarely does the author provide implementations of these designs and those that are furnished are done in Smalltalk, which makes this book more suitable for those who have experience in object design.
Customer Reviews:
A bit dated in a few spots, but quite good........2005-11-30
This is Martin Fowler's first book, published in 1997. The book is divided into two large sections.
The first section details analysis patterns that Fowler has encountered across industries. These chapters cover several common domain patterns including representing organizational hierarchies, inventory, accounting, and others. Fowler approaches these chapters by starting with a simple model and repeatedly expanding on this model to fit more and more complex needs. This section of the book is interesting from an academic and a practical perspective. It was interesting to see how Fowler has approached different domain problems and I expect to reference these chapters as I tackle similar problems in the future.
The second section of the book covers what Fowler calls Support Patterns. In these chapters Fowler discusses tiered architecture, presentation layers, facades, and association patterns. The second section on support patterns is less useful and some chapters are quite dated. While this information may have been useful in 1997, if you are looking for more information on layered architectures read Enterprise Application Architecture - a more recent book by the same author.
I found this book to be quite good. I enjoy Fowler's style of writing and for the most part I found the book easy to follow. However, this is Fowler's first book and it lacks the polish of his more recent other books -- in a few spots it was hard for me to follow the author's train of thought.
This book predates UML and the diagrams used throughout the book take a while to understand. There is a key to the models on the inside cover of the book, but if the diagrams had been updated to UML they would have been easier to understand. If needed, you can find UML diagrams for this book on Martin Fowler's website. I think sample code would have helped clarify some of the models as well, as was used in the "Gang of Four" book.
If you are designing a domain model for a complex business, I think this book would be useful for you. If you are looking for similar books, I would suggest Design Patterns by Gamma, et al. ("Gang of Four" book), Patterns of Enterprise Application Architecture, and Refactoring both by Fowler.
The only "practical" book on deciding which design to use.......2004-11-13
What I am nearly always missing when reading about design (esp. when sifting through design case studies) is the path that lead to a design. The weighing of arguments that made the author/designer choose the solution at hand. The context and the "drivers". Fowler is the only one achieving this: offering different solutions and discussing their advantages and disadvanteges. Yes he dives deep and goes into abstract concepts, but sometimes solutions only differ from an abstract viewpoint. You need quite some understanding of design principles, to (i) understand the book and (ii) be a good designer.
For me this is the book that helped me understand the design process as it should be. And using "analysis patterns" he gives plentiful of concrete examples, sharpening your mind.
One remark to everyone critcizing Fowler for not using UML: This book does not use UML since it dates back to 1996! When UML was not really there. Version 0.9 of the UML came out in the second half of 1996. And btw. Martin Fowler has written the very first -- and still one of the best -- book on UML ("UML Distilled", now in its 3rd edition).
Truly Unique, Extremely Valuable Entry.......2004-07-16
Kind of funny, reading the reviews here makes it clear that this book is something of a sleeper, it has not gotten the exposure that a lot of the other pillars of the pattern community have. I think the reason is that people may glance at it and think that it is too domain-specific. In fact, this book does a lot of great things, it is a meditation on some crucial OO modeling issues.
The first problem Fowler broaches is a patient's weight and he states, correctly I'm sure, that most programmers would just make weight a class property and make it be of type integer. But there are problems with that approach. First one is the issue of units. If you make it an int you are assuming that it is just a count of pounds. What happens if you want another measure? Furthermore, what happens when someone asks where the patient's weight has gone in the last month.
From this point of departure, many issues are taken up. For people who have grappled with OLAP before and know something about dimensional models, it will seem as though he is trying to make an operational into an analytical model, which experience has taught us is not good. But, in fact, there is sanity to Fowler's approach.
Personally, if he ever does rev this book (read on his site that he is thinking about it), I wish he would consider writing a section that attempts to hide the observation elements and seamlessly map them back into the object model. Having a separate class keeping track of what the weight of a person represented by another class is does ultimately seem to undo the objectness of the model, but that's a minor nit. Definitely a book that I've returned to many times.
Study, don't just read this book........2003-02-09
I bet you are an object oriented software developer striving to build better applications. If you have not read GoF Design Patterns and followed that with Vlissides's Pattern Hatching, read those first. Follow those with this, Martin Fowler's Analysis Patterns.
As two readings of Design Patterns took my OO knowledge from infancy to adolecence, Analysis Patterns will take you from adolecence to adulthood. Fowler's work does not put together patterns from the Design Patterns book, but takes its time to decompose actual application domain concepts to applicable object models. It will then be up to you to use your knowledge from Design Patterns to create mechanisms that support properly modeled business concepts as Analysis Patterns describes.
If you like OO modeling and design, but are wondering how better to apply your modeling concepts, Fowler's book is something you will definitely benefit from. However, make a pot of coffee per chapter-this book is very dense with concepts.
Fowler ends Analysis Patterns with some more easily read chapters on application design on a larger scale. You've heard of "n-tier," his discussion of the concepts of "n-tier" at the end of the book are possibly worth reading first.
After reading this book-and understanding it's motivations-you will never again be tempted to take "innocent" shortcuts in your application design. You will not be motivated to use "Strings" for "measurements" or "doubles" for "distances." You will look upon your peer's object designs either with a new understanding that they know that going the distance with their object model is worth it-and you won't demand they dumb down their design ever again-and you'll likewise gain intuition about where a simplistic business domain model is going to fail.
A bit too abstract.......2002-07-18
There are lots of interesting ideas here, but the actual patterns themselves are not that useful as they are too abstract.
Book Description
- A highly anticipated book from a world-class authority who has trained on every continent and taught on many corporate campuses, from GTE to Microsoft
- First book publication of the two critically acclaimed and widely used testing methodologies developed by the author, known as MITs and S-curves, and more methods and metrics not previously available to the public
- Presents practical, hands-on testing skills that can be used everyday in real-life development tasks
- Includes three in-depth case studies that demonstrate how the tests are used
- Companion Web site includes sample worksheets, support materials, a discussion group for readers, and links to other resources
Customer Reviews:
Good book on software testing, but interesting also for other test engineers.......2005-12-09
Recommended book for software test engineers. Since the author also discusses political aspects of testing in today's real business world, where the CFO rather than the CEO rules, this is an interesting book for other test engineers, too.
One of the main topics of the book are what the author calls MITs, the "most important tests". The MITs are determined using various methods, including path analysis, boundary value analysis, expert interviews, and test ranking.
While there are nice explanations of the other methods, my first impression was that the author's explanation of her ranking method was lacking technical details. Actually, that ranking method is rather simple. Use of consistent terminology and some detracting errors in examples just make it more difficult than necessary for the reader to understand.
Meat ratio is too low.......2005-03-12
I am a graduate of Computer Science and found a job in software testing. I bought this book based on the Recommendations on Amazon. However, after reading a few chapters, I am disappointed:
The topic of the book is about Software Testing. However, many times the author goes off the topic, discussing something like:
"A software bug has properties much like a real insect: height, length, weight, type or class( family, genus, spider, beetle, ant, etc ... ), color, and so on. It also has attributes like poisonous or non poisonous, flying or nonflying, vegetarian or carnivorous ..." (page 109)
I wondered: Am I reading a Biology book?
In many other places, the author introduced the content of other books. Several times, he quoted the definitions from the Webster dictionary. Of course, references or quoting is good, but the author has overused them.
In order to save time, I have to skip many pages of the book when the author goes off the topic. Overall, the book has around 400 pages, but in my opinion, the author can reduce the book's size to one third and the book can still be able to carry the same information.
My suggestion for the new edition: keep the content as precise as possible by going straight into the details. It will save the time of the readers.
Risk based software testing.......2004-09-07
This text describes MITs (Most Important Tests), a risk based test methodology. MITs makes use of prioritized test cases, which collectively are referred to as a test inventory. The book is organized in 3 sections. Chapters 1 through 5 focus on background concepts. Chapters 6 through 8 focus on the test inventory and how to create it. Chapters 9 through 14 discuss risk analysis, test techniques , and test planning and estimation.
Although the author describes how her methods fit with either traditional or agile software development, I feel it is geared towards tradtional software development with its heavy investment in upfront planning. Agreed upon test inventories she asserts are important to communicate both the value and cost of testing, as well as to establish a contract of what will and what won't be tested for the project.
Although the subtitle of the text is "methods and metrics", there was just one chapter devoted to test metrics.
Overall, I appreciated the "how - to" orientation of the text; this is a book for the test practioner. There are several examples which can be used for sample test templates and checklists. There is also a companion web site, a glossary of terms, and comprehensive end notes.
Unique perspective aimed at product line testing.......2004-06-20
Traditional software testing focuses two key metrics - defect removal efficiency and, in mature environments, defect density. This book takes a different approach that, on first read, may seem like anarchy to experienced test professionals who work on internal projects. However, when you stop and consider the context in which Ms. Hutcheson is using, the methods and metrics she sets forth make perfect sense.
The context is delivery of commercial products or getting company-critical applications rolled out for purposes of competitive advantage. Within this context she defines the following goals: (1) first to market with the product, (2) optimum pricing model, (3) products with the right features, (4) keeping unacceptable bugs to an absolute minimum. For the last she has a corollary, "Make sure your bugs are less expensive and less irritating than your competitor's", which is not the 'party line' in testing, especially in organizations that strive for zero defects, but is realistic, and especially so when time-to-market is critical. In some ways this book reflects software testing in marketing-driven product development. This is further reinforced by the following definitions and objectives:
- definition of quality is customer satisfaction.
- system for achieving quality is constant refinement.
- measure of quality is the profit.
- target goal of the quality process is a hit every time.
Achieving the above within the software testing domain does require a departure from conventional thinking and methods, and how to go about achieving them is thoroughly covered in the body of the book. The key approach is to develop a test strategy that is based on 'Most Important Tests'. Supporting activities covered include building a test inventory, managing risk, and a feedback loop of data analysis.
In addition to being aligned to product line development, this book's approach can also be easily tailored to rapid, iterative development approaches such as agile methods. If you are working in an internal development environment that uses 'heavier' development lifecycles this book is not going to fit; however, if you work in a product-oriented environment this book will not only change your thinking, but will provide the basis for an integrated development-marketing approach that could make a real difference in competitive advantage.
Customer Reviews:
Excellent textbook.......2006-06-21
As my headline suggests, this book is more suitable for the classroom environment than for the professional systems analyst or systems developer.
What the author did was to basically take the Zachman Framwork with all the columns and rows and explain every possible combination by using the usual modelling techniques (UML, DFDs, IDEF0, ERMs, CRUD matrix etc.). You therefore get a very - and I really mean VERY - broad overview over many of the current, state-of-the-art methods available to systems analysts (from data normalization to analyzing objectivied relationships).
I recommend you to read this book if you are someone from the academic world who wants to get a very good overview of the Zachman Framework. Especially if you are specifically interested in data analysis you will find this book to be very helpful.
aggreed there is no OOA.......2005-08-28
OOA is some "super magic" that uml people found it for commercial reasons.As Mr.Hay mentions there is no OOA.there is only "analysis" of the bussiness.
I am a bussiness owner and a coder for a long long time.The concept that david hay is talking about will take developers life time period to understand.
The most simple explanation is for the reviewer to look at his/heer database tables and see the replication places as they had no abstraction in mind when they were coding the "thing"(prefered design over analysis).
David Hay's,Len Silverstone's and Martin Fowlers(analysis patterns) should be read over and over again.it is like swimming u do not pick it up in the first try.
PS:These books are for an analists who can understand the meaning of polymorfism
PS2:By the way OO people even could not agree about compostion over aggregation ,method over operation.Keep in mind UML is a design tool should not be used like a "golden hammer"
It will broaden your horizons, but it is not a cookbook........2003-11-15
_Requirements Analysis_ is just the opposite of a book like Craig Larman's _Applying UML and Patterns_ or Ed Yourdon's _Modern Structured Analysis_. Both of those books--in fact, most books on analysis--present a single methodology and a single set of tools and notations, then walk you through the steps of the analysis process according to DeMarco or according to Jacobson or whatever.
David Hay is after larger fish in this book, or at least more fish: in these 400 pages, you will find a survey of more techniques and models than you probably could have dreamed of, from the very old to the very new, from the flashy to the obscure: data flow diagrams, UML, Object-Role Modeling, cybernetics, business rules, IDEF0, and on and on. This book will teach you a little bit about a whole lot of analysis techniques and what they can accomplish.
The material is all organized and discussed from the point of view of the Zachman Framework, a beautiful and expansive system that shows us how various techniques fit in to the "total picture" of the who, what, when, where, why and how of enterprises and information systems. It gives us a broader perspective, and often shows us where we are focusing too much on one or two aspects of a system, to the detriment of the others.
But this book is not a cookbook or a procedural guide to performing analysis. There is very little prescriptive advice, and relatively little on the nuts and bolts of what you should do and when. I don't want to suggest that is a shortcoming: it is intrinsic in the very nature of a survey-type book. If you have done some analysis work or studied one or more particular methodologies, this book will give you context and perspective and introduce you to new possibilities you probably weren't even aware of before.
But if you are approaching analysis for the first time, you need guidance more than you need options, and you may find this book more confusing than useful. You might, instead, want to look at _Applying UML and Patterns_(Larman) if you are approaching analysis from an object-oriented programming perspective; _Modern Structured Analysis_ (Yourdon) if you are coming from a more traditional Data-Flow and Entity-Relationship shop; or _Mastering the Requirements Process_ (Robertson)for a more generalized, but still procedural, perspective on requirements definition. Then, in six months or a year, open Mr. Hay's book and feel the horizons rushing back from your eyes. This is basically what I have done, and I'm very happy I did. David Hay has given me a larger context at a time when I can start to appreciate it, and new options at a time that they can be useful to me.
I should point out that I feel the book is not without its shortcomings.
--Mr. Hay gives pretty short shrift to Use Cases, which are emerging as a really useful technique for discovering and capturing functional requirements. This book talks about use cases, but clearly considers them of secondary value, burying them in a fairly obscure corner of the Framework. Craig Larman, Alistair Cockburn, Ivar Jacobson and Doug Rosenberg all have good titles out that place Use Cases in a more central role.
--Certain object-oriented techniques seem to have a pretty low opinion of Analysis work, or call things "analysis" that are more properly considered design. Mr. Hay makes some good points in response, but I can't help feeling he's going a little too far when he says things like "there is no such thing as object-oriented analysis." No less a figure in the world of methodology than Ed Yourdon would seem to disagree, unless the title of his book, "Object-Oriented Analysis," is some kind of very subtle joke. You may want to pick up an OO title or two, and see what conclusions you come to.
--Last of all, I found the treatment of some of the areas of the Framework to be esoteric and difficult to follow. Most notable here is the discussion of business rules that makes up the book's treatment of the Motivation, or "why," column. I realize that business rules thinking is still in its infancy, but the presentation in the book is too nebulous, academic and abstract to come to any kind of grips with--it was like trying to learn the UML by looking at the "meta-model" documents. Another example is in the People, or "who," column, which consists of a very academic treatment of the science of "cybernetics." Intriguing, but darned if I got much of practical use out of it. Shouldn't the People column have something to do with characterizing and categorizing users, their preferences, environments, levels of experience? Perhaps all the stuff on cybernetics _does_ that, but it was all a little too rarefied for me to follow.
In summary, this was a very valuable book for me. I'm a better analyst for having read it, and I have a whole list of new things to think about and learn about (including the above-mentioned business rules and cybernetics). I can't recommend this as a _first_ book on analysis, but I can heartily recommend it to anyone who wants to learn _more_ about analysis.
Giving the Zachman framework a new lease on life.......2003-04-16
'Rather than reviewing requirement analysis from the perspective of a particular implementation of technology, this book views it as fundamentally an architecture process. This books premise is that requirements analysis is the translation of a set of business owners' view of the enterprise to a single, comprehensive architectural view of that enterprise'
David inspired by the Zachman framework shows how various methodologies and techniques can be organised for a omprehensive requirements analysis approach leading to an architecture solution. This book really brings forward the briliance of the Zachman framework. It gives a new perspective on Zachman and brings the framework back into the contempory enterprise strategies framework.
David shows not only how to avoid the common mistake of building an architecture from a single business view but also how to integrate various views into a common architectural view.
The book keeps to it focus on "Requirement analysis" and the reader is not really helped to go beyond the requirement analysis phase into the design and implementation phases. A good reference to have for people with an appetite for enterprise architecture strategies
Good on data modeling, but little else.......2003-03-20
I had a good book on OO analysis and the UML, but though it weak on data modeling and business rules. So I went looking...
I read the 4 reviews on this page and purchased the book. Given the reviews and the fact that it was just published, I thought I would be getting a book that unifies a broad sweep of modern analysis techniques (OO, UML, Data Modeling, Design Patterns, Business Rules, Requirements Gathering Techniques, Iterative Development, etc.).
On the contrary, I received a book that is 90% data modeling biased and steeped-in analysis techniques of the pre-OO era, such as data flow diagrams (people still use these?). This looks like a book I had in school 10 years ago.
There are passing and, at best, cursory references to UML modeling approaches, but that is all that is in this book with respect to modern OO approaches.
There is absolutely nothing said with regards to Design Patterns nor an iterative approach to building systems and mitigating risk. I find this lack of coverage absolutely incredible in a software requirements analysis book published in 2003. Unbelievable!
Ten years ago, this book might have been considered a good benchmark. Not today. This author's sole idea of architecture is the data model and functional decomposition. Ugh.
If you are weak on relational data modeling, this book has redeeming value. Otherwise, if you are trying to figure-out how to elaborate requirements and transform them into a working OO system using UML, Design Patterns, and an iterative approach, I highly recommend Craig Larman's top-notch "Applying UML and Patterns: ...". It really sets the standard.
The Larman book is weak on data modeling and business rules - which I thought Hay's book would address better (and is why I bought it sight unseen). It does, but at the expense of everything else.
Average customer rating:
|
Thermal Analysis and Design of Passive Solar Buildings
A. K. Athienitis , and
Mat Santamouris
Manufacturer: Earthscan Publications Ltd.
ProductGroup: Book
Binding: Hardcover
General
| Architecture
| Professional & Technical
| Subjects
| Books
Materials
| Architecture
| Professional & Technical
| Subjects
| Books
Fiber Optics
| Optics
| Electrical & Electronics
| Engineering
| Professional & Technical
| Subjects
| Books
General
| Engineering
| Professional & Technical
| Subjects
| Books
Structural
| Civil
| Engineering
| Professional & Technical
| Subjects
| Books
Energy
| Physics
| Professional Science
| Professional & Technical
| Subjects
| Books
Environmental Science
| Earth Sciences
| Professional Science
| Professional & Technical
| Subjects
| Books
Environmental Science
| Earth Sciences
| Science
| Subjects
| Books
Energy
| Physics
| Science
| Subjects
| Books
Renewable Energy
| Technology
| Science
| Subjects
| Books
Look Inside Art Books
| Trip
| Specialty Stores
| Books
Look Inside Outdoors & Nature Books
| Trip
| Specialty Stores
| Books
Look Inside Science Books
| Trip
| Specialty Stores
| Books
All Titles
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Similar Items:
-
The Solar House: Passive Heating and Cooling
-
The New Ecological Home: A Complete Guide to Green Building Options (Chelsea Green Guides for Homeowners)
ASIN: 1902916026 |
Book Description
Passive solar design techniques are becoming increasingly important in building design. This design reference book takes the building engineer or physicist step-by-step through the thermal analysis and design of passive solar buildings. In particular it emphasizes two important topics: the maximum utilization of available solar energy and thermal storage, and the sizing of an appropriate auxiliary heating/cooling system in conjunction with good thermal control.
Topics include:
* transient heat transfer and thermal storage
* fenestration components, systems and daylighting
* dynamic models of heat transfer in solar buildings
* the passive response of solar buildings and its use in design
* ventilation and indoor air quality
* analysis and sizing of small auxiliary heating/cooling systems
* control of passive solar buildings
* solar energy utilization techniques and systems
"Thermal Analysis and Design of Passive Solar Buildings" is an important contribution towards the optimization of buildings as systems that act as natural filters between the indoor and outdoor environments, while maximizing the utilization of solar energy. As such it will be an essential source of information to engineers, architects, HVAC engineers and building physicists.
Books:
- ASP in a Nutshell, 2nd Edition
- Beautiful Evidence
- Beginning Programming with Java For Dummies (For Dummies (Computer/Tech))
- Bridal Gowns: How to Make the Wedding Dress of Your Dreams
- Build Your Own Standards Compliant Website Using Dreamweaver 8 (Build Your Own)
- C++ How to Program (5th Edition) (How to Program)
- CCIE Routing and Switching Official Exam Certification Guide (2nd Edition) (Exam Certification Guide)
- CCNA for Dummies, Second Edition
- Chosen Soldier: The Making of a Special Forces Warrior
- Circuit Design with VHDL
Books Index
Books Home
Recommended Books
- Power System Analysis and Design
- History: Fiction or Science
- Accounting Interactive Pre MBA 2000
- Colonialist Photography: Imag
- Economics of Money, Banking, and Financial Markets, Update
- How Porcupines Make Love III: Readers, Texts, Cultures in the Response-Based Literature Classroom
- Heavy Duty Truck Systems
- Hbj Federal Tax Course, 1988
- Doing Business in 2004: Understanding Regulation
- Death of a Romance Writer and Other Stories
UML Distilled: A Brief Guide to the Standard Object Modeling Language (3rd Edition) (The Addison-Wesley Object Technology Series)
Design Patterns: Elements of Reusable Object-Oriented Software (Addison-Wesley Professional Computing Series)
Head First Design Patterns (Head First)
Agile and Iterative Development: A Manager's Guide
Writing Effective Use Cases
