- Paperback: 696 pages
- Publisher: Wiley; 1 edition (September 24, 2004)
- Language: English
- ISBN-10: 0471202843
- ISBN-13: 978-0471202844
- Product Dimensions: 7.4 x 1.4 x 9.2 inches
- Shipping Weight: 2.2 pounds
- Average Customer Review: 15 customer reviews
- Amazon Best Sellers Rank: #2,359,812 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Customers who viewed this item also viewed
From the Back Cover
"Software Factories does a wonderful job integrating modeling with patterns, frameworks, and agile development. The authors provide a compelling look at how a new generation of tools will make this a reality. A must read for software architects and developers."
John Crupi, Sun Distinguished Engineer, and coauthor, Core J2EE Patterns
Many of the challenges currently facing software developers are symptoms of problems with software development practices. Software Factories solves these problems by integrating critical innovations that have been proven over the last ten years but have not yet been brought together.
A team of industry experts led by Jack Greenfield explains that a Software Factory is a configuration of languages, patterns, frameworks, and tools that can be used to rapidly and cost-effectively produce an open-ended set of unique variants of a standard product.
Their ground-breaking methodology promises to industrialize software development, first by automating software development within individual organizations, and then by connecting these processes across organizational boundaries to form supply chains that distribute cost and risk. Featuring an example introduced in the first chapter and revisited throughout the book, the authors explain such topics as:
- Chronic problems that object orientation has not been able to overcome, and critical innovations that solve them
- How models can become first class software development artifacts, not just documentation
- How software product lines can be used to consistently achieve commercially significant levels of reuse
- How patterns, frameworks, tools, and other reusable assets can be used to scale up agile development methods
- How orchestration and other adaptive mechanisms can be used to enable development by assembly
About the Author
JACK GREENFIELD (Redmond, WA) is an Architect for Visual Studio Team System. He is an author, frequent speaker, and key contributor to component, model, and pattern technologies at Microsoft.
KEITH SHORT (Redmond, WA) is an Architect for Visual Studio Team System. He is responsible for strategy and architecture for enterprise tools at Microsoft.
STEVE COOK (Canterbury, UK) is an Architect for Visual Studio Team System. He was formerly an IBM Distinguished Engineer and a major contributor to UML and UML2.
STUART KENT (Bishop’s Stortford, UK) is a Program Manager for Visual Studio Team System. He focuses on modeling technology and is an internationally recognized authority on UML.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
Since the material is strongly consolidated, one would re-read the books several times each time finding something new to perceive. Authors are great guys - I would eagerly read any other book of their authorship.
I became interested in reading on this topic from my work on software assembly, and I really had high hopes for it. I wanted to see how frameworks are formed, and perhaps take it to the next level, but there is nothing of value in this book. There really is a need for a book on this topic, but it needs to begin where the Spring Framework left off. How do you define an application template? How do you create a framework that facilitates easy assembly based on templates? There are bits and pieces of it out there: graphical plugins for IDE's like Eclipse that generate code and link components together with meta data, server nodes like those in Erlang OTP which can be joined on demand to clusters for load balancing. We are on the eve of discovery in this area, but this book won't help you get there.
VSTS 2005 missed the mark on Software Architecting Tools, and only includes System Architecting tools. With my own MSDN subscription I opted for the Developer version instead of the Architect version because of this. Microsoft is banking on the Software Architecture Tools of Domain Specific Languages (DSL) instead of UML and Software Factories (which Product Line Engineering is the heart of).
This is great except for the fact that to use it properly is going to cause a huge learning curve. Not so much with just DSL, but in applying the industry standards that exist in the architecture world to this new way of architecting. It is going to be hard to move software factories into most development communities. It will be great for engineering firms that take 3 to 5 years between releases, but in the type of environment that needs to consider time to market, software factories are going to be difficult to sell.
If you get this book, I suggest not getting to carried away with the software factory part of it. Software Factory information only takes up about 20% of the book. The rest is great material.
But..this book is too Microsoft biased. As written by a MSFT emplyee this is kind of expected but the fact is that the guy makes everything to say C#/.Net is the future of Java. This includes saying that JIT compilation was first introduced by .Net, that JavaBeans are a convention that are evolved in C# by delegates and properties and lots of other tries to make people believe that .Net is an evolution of the Java platform. I think this really compromises the book and would be much, much better if it just used C# and forgot all comparisson.
I'd suggest that people intersted in MDA, DSL and new trends read this book but just skip all the Java bashing.
An extensive survey is also given of various design/modelling tools that are available. These might be open source, proprietary or of the academic research type. One easy thing you can do with this book is to use its analysis of these tools. This is doable without having to wade through most of the rest of the book.
The book will not be an easy read to some. A lot of material is covered and a considerable amount is fairly abstract. Without significant prior experience in design and coding, you may miss the full meanings and appreciation of much of the text.
It makes a typical computer book look trivial.