The AnswerSleuth: Architecture
Wiki is a website that allows the visitors to quickly and easily add, remove and otherwise edit and change some content, sometimes without the need for registering. This ease of interaction and use makes the Hive Wiki an effective tool for collaborative authoring. Start Fresh Hive Wiki Now!
 Home | Edit | Index | Recent Changes

Architecture

Search for Architecture
  1. Cyburbia - urban planning community - Planning resource center includes a detailed resource directory, numerous message boards, a wiki, and image galleries. www.cyburbia.org Mama
  2. Modern Architecture Since 1900
    • Book by William Curtis.
  3. AECasia - Architecture Engineering Construction Design & Products - architecture. . > product directory. . > new product release. . > ... www.architectureasia.com Mama
  4. Modular Architecture Protocol - Providers of Modular Architecture Protocol resources. www.business.com Mama
  5. Marivi's Origamic Architecture - Many elaborate card designs, featuring models based upon the architecture of Gaudi. Also includes instructions and a section on Heraldic Origamic Architecture. marivi_10.tripod.com Mama
  6. Faculty of Engineering - The highly accredited faculty is the largest in Scotland, and spans nine departments, from architecture to ship and marine technology. www.strath.ac.uk Mama
  7. Chicago Tribune news : Architecture - ... Chicago Tribune news : Architecture Home News Business Sports Travel ... www.chicagotribune.com Mama
  8. Sipapu--The Anasazi Emergence into the Cyber World - Prehistory, interactive reconstructions of Anasazi architecture, online research papers, and searchable databases on Anasazi sites and bibliographic references. sipapu.ucsb.edu Mama
  9. Architecture Schools - Use this directory to find colleges, universities, libraries and other education resources for architecture, historic preservation and landscape design. Also listed are school rankings and application advice. architecture.about.com Mama
  10. Architecture Web Resources - Architecture Internet Resources, a database of valuable internet resources created and maintained by the UNLV Architecture Studies Library, Jeanne library.nevada.edu Mama
  11. Patterns of Enterprise Application Architecture
    • Book by Martin Fowler.
  12. The Information Architecture Institute | Home - ... The Information Architecture Institute The Information Architecture Institute is a non-profit volunteer organization dedicated to advancing and promoting information architecture. Founded in 2002 ... www.iainstitute.org Mama
  13. Architecture Forum - DesignCommunity.com - Design Community Great Buildings Discussion, discussing architecture, architectural design, history, travel, great buildings, architects, and related topics. ... www.designcommunity.com Mama
  14. WWW Computer Architecture Page - Computer Architecture is the science and art of selecting and ... Computer architecture is not about using computers to design buildings ... www.cs.wisc.edu Mama
  15. History of Western Architecture - HISTORY OF WESTERN ARCHITECTURE EGYPTIAN ARCHITECTURE : Giza : Deir El-Bahali : Karnak : Luxor : Abu Simbel : Dendera : Philae web.kyoto-inet.or.jp Mama
  16. Art & Architecture Thesaurus (Research at the Getty) - Learn about the Getty Vocabularies Art & Architecture Thesaurus Online ... Architecture Thesaurus (AAT) is a structured vocabulary for ... www.getty.edu Mama
  17. © ASLA.org - A national professional society that represents the landscape architecture profession. Searchable listing of firms, news, information on ... www.asla.org Mama
  18. Environmental Consultants for Architecture, Engineering and Construction - Consulting and engineering firms focused on environmental services for the architecture, engineering and construction industries. www.business.com Mama
  19. culturevulture.net - art & architecture - index - Index of Art and Architecture Reviews home | books & cds | dance | destinations | film | opera | television | theater | archives art & architecture .. www.culturevulture.net Mama
  20. Information Architecture for the World Wide Web- Designing Large-Scale Web Sites
    Cover of ISBN 0596000359Information Architecture for the World Wide Web
    Designing Large-Scale Web Sites:
    • Book by Louis Rosenfeld and Peter Morville.
  21. Orlando architecture firm designing Urbana condo project - Orlando Business Journal: - ... Orlando architecture firm designing Urbana condo project ... orlando.bizjournals.com Mama
  22. MSDN Solution Architecture Center - ... Code and Downloads Product Information Knowledge Base (KB) Advanced Search MSDN Solution Architecture Center Think Ahead Learn More Solve Now Share Ideas The Architecture Journal New Modeling ... msdn.microsoft.com Mama
  23. Architecture Schools - How to Choose a College for Architecture or Design - Hundreds of colleges and universities offer classes in architecture and related fields. How do you choose? These links and resources will help you find the best schools for architecture and to decide which one is right for you. architecture.about.com Mama
  24. The American Institute of Architects - National professional association of architects. Includes career center, book store, continuing education, AIA chapters. www.aia.org Mama
  25. What is Architecture? - What is Architecture requires a forms-capable and [JavaScript]Create? capable browser (preferably Netscape 2.0 or above, but Explorer 3.0 and above may work). www.wsu.edu Mama
  26. ABOUT ARCHITECTURE - Most Recent Articles on Architecture and Home Design - Browse our index of most recent articles on architecture and home design, archived by date. architecture.about.com Mama
  27. Architecture in the The United States - Use this directory to find facts and photos for historic or important architecture in the USA architecture.about.com Mama
  28. The Pritzker Architecture Prize - Current information about the world's most ... - The Pritzker Architecture Prize World Wide Web Site provides current ... information about the world's most prestigious architecture award and ... www.pritzkerprize.com Mama
  29. A Global History of Architecture
    • Book by Francis D. K. Ching, Mark M. Jarzombek and Vikramaditya Prakash.

Modern Architecture Since 1900

Book by William Curtis. Phaidon Press 736 pages Paperback Published 1996-06-27.
      • Review:: 'pretty survey This is the kind of book I found stimulating before I went to architecture school. Curtis seems to argue that composition, tectonics, personal triumph, modernist orthodoxy and mythos are the big ingredients of 20th Century architecture. As if you can't make junky architecture from that recipe, and the damage from those ideas isn't all around us. Any "Uncomplicated" reading (to me) is non-compelling, but I guess that's what surveys are. I'll be damned if I can tell you what Curtis' overall thrust or polemic is, beyond "Modern Architecture is neat." Social responsibility and political meaning are pretty much missing here. No matter how much I read it, nothing sticks. The design is nice, which is what I suspect people are reviewing here.
      • Review:: 'Modern Architecture Much like all the other architecture books I own, Modern Architecture Since 1900 is a great reference for basic knowledge on the history of Architecture. Some sections I enjoyed were Louis Kahn, Frank L. Wright and Mario Botta. The book overall is wonderful adn appealing; it is a good read.
      • Review:: 'difficult for me to read as others have said, it's impressive, from what i gathered anyway. i got about 100 pages in, and it's just too difficult for me to read right now, i just began looking into architecture, and this is a little advanced for me. anyhow i love looking at the pictures, however childish that may sound. just for the photos it was worth the purchase.
      • Review:: 'Quick Service! I'm happy with the quick service and the condition of the book. I would buy books from this company again.
      • Review:: 'The world of architecure 1900 This is book is one of the best books I've read concerning the world of architecture especially since the modern era. It covers every aspect in the field from history to theory, to inspiration and the connections in between. Everything since 1900 has impacted the world of architecture and architecture today in a much greater way than we realize. I recommend this book and it vastly covers all the needed areas of architecture and its subjects. The student of architecture must have this one in your library and is a must have to anyone covering the field. I rate this five stars because of the knowledge it contains and all the world of architecture it covers. I believe this one contains the most in depth knowledge of the subject and covers the history in a much greater way than any book I've seen before. It is a lengthly read but worth the patience, the knowledge it contains is much more than the time, especially in the world of architecture.

Patterns of Enterprise Application Architecture

Book by Martin Fowler. Addison-Wesley Professional 560 pages Hardcover Published 2002-11-05. Description: In the spring of 1999 I flew to Chicago to consult on a project being done by [ThoughtWorks]Create?, a small but rapidly growing application development company. The project was one of those ambitious enterprise application projects: a back-end leasing system. Essentially it deals with everything that happens to a lease after you've signed on the dotted line: sending out bills, handling someone upgrading one of the assets on the lease, chasing people who don't pay their bills on time, and figuring out what happens when someone returns the assets early. That doesn't sound too bad until you realize that leasing agreements are infinitely varied and horrendously complicated. The business "logic" rarely fits any logical pattern, because, after all, it's written by business people to capture business, where odd small variations can make all the difference in winning a deal. Each of those little victories adds yet more complexity to the system. That's the kind of thing that gets me excited: how to take all that complexity and come up with a system of objects that can make the problem more tractable. Indeed, I believe that the primary benefit of objects is in making complex logic tractable. Developing a good Domain Model (116) for a complex business problem is difficult but wonderfully satisfying. Yet that's not the end of the problem. Our domain model had to be persisted to a database, and, like many projects, we were using a relational database. We also had to connect this model to a user interface, provide support to allow remote applications to use our software, and integrate our software with third-party packages. All of this on a new technology called [J2EE]Create?, which nobody in the world had any real experience in using. Even though this technology was new, we did have the benefit of experience. I'd been doing this kind of thing for ages with C++, Smalltalk, and CORBA. Many of the [ThoughtWorkers]Create? had a lot of experience with Forte. We already had the key architectural ideas in our heads, and we just had to figure out how to apply them to [J2EE]Create?. Looking back on it three years later, the design is not perfect but it has stood the test of time pretty damn well. That's the kind of situation this book was written for. Over the years I've seen many enterprise application projects. These projects often contain similar design ideas that have proven effective in dealing with the inevitable complexity that enterprise applications possess. This book is a starting point to capture these design ideas as patterns. The book is organized in two parts, with the first part a set of narrative chapters on a number of important topics in the design of enterprise applications. These chapters introduce various problems in the architecture of enterprise applications and their solutions. However, they don't go into much detail on these solutions. The details of the solutions are in the second part, organized as patterns. These patterns are a reference, and I don't expect you to read them cover to cover. My intention is that you read the narrative chapters in Part 1 from start to finish to get a broad picture of what the book covers; then you dip into the patterns chapters of Part 2 as your interest and needs drive you. Thus, the book is a short narrative book and a longer reference book combined into one. This is a book on enterprise application design. Enterprise applications are about the display, manipulation, and storage of large amounts of often complex data and the support or automation of business processes with that data. Examples include reservation systems, financial systems, supply chain systems, and many others that run modern business. Enterprise applications have their own particular challenges and solutions, and they are different from embedded systems, control systems, telecoms, or desktop productivity software. Thus, if you work in these other fields, there's nothing really in this book for you (unless you want to get a feel for what enterprise applications are like.) There are many architectural issues in building enterprise applications. I'm afraid this book can't be a comprehensive guide to them. In building software I'm a great believer in iterative development. At the heart of iterative development is the notion that you should deliver software as soon as you have something useful to the user, even if it's not complete. Although there are many differences between writing a book and writing software, this notion is one that I think the two share. That said, this book is an incomplete but (I trust) useful compendium of advice on enterprise application architecture. The primary topics I talk about are Layering of enterprise applications Structuring domain (business) logic Structuring a Web user interface Linking in-memory modules (particularly objects) to a relational database Handling session state in stateless environments Principles of distribution The list of things I don't talk about is rather longer. I really fancied writing about organizing validation, incorporating messaging and asynchronous communication, security, error handling, clustering, application integration, architectural refactoring, structuring rich-client user interfaces, among other topics. However, because of space and time constraints and lack of cogitation, you won't find them in this book. I can only hope to see some patterns for this work in the near future. Perhaps I'll do a second volume someday and get into these topics, or maybe someone else will fill these and other gaps. Of these, message-based communication is a particularly big issue. People who are integrating multiple applications are increasingly making use of asynchronous message-based communication approaches. There's much to be said for using them within an application as well. This book is not intended to be specific for any particular software platform. I first came across these patterns while working with Smalltalk, C++, and CORBA in the late '80s and early '90s. In the late '90s I started to do extensive work in Java and found that these patterns applied well to both early Java/CORBA systems and later [J2EE]Create?-based work. More recently I've been doing some initial work with Microsoft's .NET platform and find the patterns apply again. My [ThoughtWorks]Create? colleagues have also introduced their experiences, particularly with Forte. I can't claim generality across all platforms that have ever been or will be used for enterprise applications, but so far these patterns have shown enough recurrence to be useful. I have provided code examples for most of the patterns. My choice of language for them is based on what I think most readers are likely to be able to read and understand. Java is a good choice here. Anyone who can read C or C++ can read Java, yet Java is much less complex than C++. Essentially most C++ programmers can read Java but not vice versa. I'm an object bigot, so I inevitably lean to an OO language. As a result, most of the code examples are in Java. As I was working on the book, Microsoft started stabilizing its .NET environment, and its C# language has most of the same properties as Java for an author. So I did some of the code examples in C# as well, although that introduced some risk since developers don't have much experience with .NET and so the idioms for using it well are less mature. Both are C-based languages, so if you can read one you should be able to read both, even if you aren't deeply into that language or platform. My aim was to use a language that the largest amount of software developers can read, even if it's not their primary or preferred language. (My apologies to those who like Smalltalk, Delphi, Visual Basic, Perl, Python, Ruby, COBOL, or any other language. I know you think you know a better language than Java or C#. All I can say is I do, too!) The examples are there for inspiration and explanation of the ideas in the patterns. They aren't canned solutions; in all cases you'll need to do a fair bit of work to fit them into your application. Patterns are useful starting points, but they are not destinations. Who This Book Is For I've written this book for programmers, designers, and architects who are building enterprise applications and who want to improve either their understanding of architectural issues or their communication about them. I'm assuming that most of my readers will fall into two groups: those with modest needs who are looking to build their own software and readers with more demanding needs who will be using a tool. For those of modest needs, my intention is that these patterns should get you started. In many areas you'll need more than the patterns will give you, but I'll provide you more of a headstart in this field than I got. For tool users I hope this book will give you some idea of what's happening under the hood and also help you choose which of the tool-supported patterns to use. Using, say, an object-relational mapping tool still means that you have to make decisions about how to map certain situations. Reading the patterns should give you some guidance in making the choices. There is a third category; those with demanding needs who want to build their own software. The first thing I'd say here is to look carefully at using tools. I've seen more than one project get sucked into a long exercise at building frameworks, which wasn't what the project was really about. If you're still convinced, go ahead. Remember in this case that many of the code examples in this book are deliberately simplified to help understanding, and you'll find you'll need to do a lot tweaking to handle the greater demands you face. Since patterns are common solutions to recurring problems, there's a good chance that you have already come across some of them. If you've been working in enterprise applications for a while, you may well know most of them. I'm not claiming to present anything new in this book. Indeed, I claim the opposite--this is a book of (for our industry) old ideas. If you're new to this field, I hope the book will help you learn about these techniques. If you're familiar ...
      • Review:: 'Key book on enterprise patterns Even if you find enterprise stuff immensely dull, dealing with databases and web pages is a pretty common task, most of the action in software development revolves around it, and who wants to be completely ignorant of the the alphabet soup of various technologies the IT blogs, books and websites are floating in? So if you must immerse yourself in this area, what better than a Martin Fowler book? The code is mainly in Java, with a fairly large smattering of C#. It would probably help if you understood some basics of enterprise development in those languages, e.g. servlets and JDBC for Java. The patterns in this book cover organising domain logic, database mapping and access, web presentation, concurrency, and the book finishes by covering base patterns, a mixture of lower level abstractions of the sort covered in Fowler's first book, Analysis Patterns (e.g. Money), and those that bear a close resemblance to the classic Gang of Four patterns, with an enterprise twist (e.g. Plugin and Gateway). Nearly all the other patterns refer to these, so I don't know why these didn't appear first. Apart from that though, the book is very well organised. And the opening essay, that discusses the trade offs of every pattern and how they fit together in an application, is immensely helpful. Wizened enterprisers looking for new material will not find much new here, but surely the point of patterns catalogues are to get down on paper the practices of those same wizened enterprisers, not to strike off in new directions. Therefore, an experienced developer should see this as a way to organise what they already know, and maybe in doing so, reveal some new insights. A newcomer to enterprise development will definitely get a lot out of this, as the underpinnings to the plethora of modern enterprise applications are laid bare. You're not going to become a Hibernate, Struts or EJB expert from this book, but you should at least have a clue about what problems they're trying to solve. As usual, Fowler manages to be a model of clarity, while still injecting regular touches of wry humour, quite an achievement given the potentially bone-dry material. If you want to know the basics of enterprise software, start here.
      • Review:: 'A must-read for tech leads and architects Martin Fowler is making a name for himself as a luminary in the area of Software Development. He writes very practical books that have a wonderful blend of theory (e.g. design patterns, UML, refactoring etc.) with experience as you can tell he has applied many if not all of these patterns in real-life projects. This book is an exposition into architectural building blocks that will help every architect and tech lead / senior developer build code that is more extensible and easily maintained (among other things). I found the chapters on O/R structural and behavioral patterns particularly enlightening. By reading this book your "toolbox" of solutions rapidly expands and you get to focus more on the business problem at hand rather than infrstructural "plumbing" things (e.g. how do I build my objects when my data is in a relational table). Very highly recommended - and definitely one of the top 5 software books I have *EVER* had the pleasure to read.
      • Review:: 'Patterns for Business Applications I loved this book! It was exactly what I was looking for when I went searching for patterns that would help with a new business application. It provides alternative solutions to the typical implementation problems associated with business systems, both from a design standpoint and from the perspective of the implementation. The alternatives are compared and weighed in light of the execution environment and cost of implementation, with a comparison of advantages and disadvantages, along with Martin's recommendations. I had the feeling that the comparisons and recommendations were made not based purely upon a theoretical optimum, but also based upon practical and real-world experience with these patterns.
      • Review:: 'Great Learning Resource If you are already well-versed in architectural patterns, you probably won't find much to interest you here. But if you are new to the subject, this is a great book. It goes beyond design patterns to show how to combine and implement the patterns in the real world. In particular, the 100-page tutorial that starts the book is a great intro to the subject. If I had to recommend two books to someone wanting to learn OOP, I'd recommend 'Head First Design Patterns', then this book.
      • Review:: 'Great and useful pattern concepts for enterprise solutions Another great pattern which is absolutely benefitial to large-scale enterprise development. The enriched and practical content provides a framework-level design skeletion and references for architects and developers to study and apply. Patterns like Domain Model, Data Mapper, Unit of Work, Identity Map, (Single/Class/Concrete) Table Inheritance, Layer Supertype, Value Object etc are nowadays most popular in the software design or even in framework design(e.g. [J2EE]Create?/.NET) that can use any language to implement(C++/Java etc).

From Arts

Fresh copy to be cached until 7:58:49 AM
124 hits
This Page: Edit | History
This Wiki: Home | Related To Architecture | Index | Recent Changes | Random Page | Search
Login | Create New Wiki | Wiki List
10/15/2008 11:58 PM v0.61.106 ADBEFEED
Wiki Site Resource List 500ms